Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[BTH]

Hello,

I apologize beforehand for my brevity and lack of knowledge in this area, but I am experiencing an annoying problem that I am unable to resolve on my own.

I currently have 2 desktop PCs on a new home network set up with a brand new DIR-655 router.  One computer is running 32 bit WinXP pro and the other is running 64 bit WinXP pro.  I also have a brand new D-Link network enclosure supporting 2 brand new HDDs.  The 32 bit system is working flawlessly, however, the 64 bit system is not.  It is difficult to pinpoint the problem, but basically the 64 bit system is frequently crashing with the new network.  Sometimes it freezes, other times I get a quick blue-screen flash and the system restarts.  I have reformatted this system and installed a small selection of apps that were known to run flawlessly before the new network was set up (old network was set up with a wireless G router, no network HDDs), however the problem still occurs.  I also have the OS updated fully, however the crashing still occurs.

Some other useful facts:

- I am not sure if the firmware on the router is updated and not sure if this might help at all or make things worse considering I'm running x64

- My network HDDs contain over 90,000 audio files that are in a folder being automatically monitored by Windows Media Player v11

I am happy to provide any more information that may be required.  Does anybody have any suggestions or reccommendations???

Thanks

[Lycan]

The issues is local to the computer, not the network.
Please describe in detail the machine in question.

[BTH]

Motherboard: ASUS MAXIMUS FORMULA LGA 775 Intel X38 ATX Intel Motherboard
http://www.asus.com/products.aspx?l1=3&l2=11&l3=572&l4=0&model=1889&modelmenu=1
Processor: Intel Core 2 Quad Q6600 2.4Ghz
Memory: 8GB (4x2GB) DDR2 800Mhz Memory
Ethernet Controller: Marvell Yukon 88e8056 PCI-E Ethernet Controller
OS: Windows XP Professional x64 (version 2003 SP2)

Further notes:

- The latest firmware posted on http://support.dlink.ca/products/view.asp?productid=DIR%2D655#faq has been installed on the router.
- It also seems that whenever there is an inconsistency with the network connection, the system in question freezes.  For example, this morning all computers lost connection to the router, and the 64bit system froze at this moment while the other PC remained otherwise functional.  Also a peculiar note:  no system was even able to log on to 192.168.0.1 during this down period (including a laptop with a wireless and hardwired connection).  The automatic IP address being assigned to these systems was 169.  The network connection was restored after several power cycles, leaving over a minute of disconnection betweeen each time.

[lotacus]

sounds like a computer or other device set to a static IP address, same of the router, causing an IP conflict effectivly taking down the router.

Other than that, more simplisticly, your router just plain crashing.

x64 machine, doing install anything but the drivers. no software no extras. run it for a day or two, see if it bsods. Windows usually will bsod due to driver issues, or memory curruption.

[ttmcmurry]

Have you tried Marvell's reference driver?

http://www.marvell.com/drivers/driverDisplay.do?driverId=155 

Released 12/9/2008.

[BTH]

I will double check the static IP allocation, as well as install the reference drivers for the ethernet controller.

I have not installed any drivers whatsoever for the router (or any additional software), since they are unavailable for WinXP x64.

[BTH]

This issue is still causing major problems for me.

Are there no further suggestions or support?

[EddieZ]

This issue is still causing major problems for me.

Are there no further suggestions or support?

Vista 64 / W7 64.

XP 64 bit is known to have very odd issues. This seems one of them. You coul try to completely remove the network drivers and start from scratch with reference drivers.

[Fatman]

If you stop cataloguing the HDs does the crash stop.  That is how does one say a serious load of music.

[lotacus]

You could probably start by unchecking the automatically restart in the system properties, startup/recovery under system failure. and right down what driver or system file is causing the bsod.

You may also want to check the event viewer as well and filter out everything but critical errors, errors. example below:

[EddieZ]

Give us some BSOD description and failing devices. Those will tell all...

[BTH]

I have unchecked automatic system restart option so that the next time I get a BSOD I will have time to write down any information provided.

Note that only sometimes when it crashed did I get the BSOD flash, quite often it just simply freezes in Windows without the BSOD.  Does this suggest anything?

I will also check the event viewer when I crash next.  The problem is that I don't often crash unless I start to run uTorrent and WMP11 simulataneously.  In fact, I am quite stable when running WMP11 for days on end... but as soon as both are open, the freeze is iminent.

Also note that the second PC (32 bit) on the network is also running uTorrent and WMP11 (monitoring the same network HDDs with the extensive file library) without any problems whatsoever.  This user has suggested that I purchase a new ethernet card... would anybody else recommend this?

[BTH]

So my computer has continued to freeze recently, without the BSOD.  I have learned that I can provoke such freezes if I simply overload the network connection by opening WMP with music streaming from the monitored HDDs while downloading/uploading significantly from uTorrent.  I opened the system clock so that when the comp froze I would know exactly what time this was so that I could reference the event viewer properly.  Unfortunately, no messages were issued in the event viewer up to 10 minutes before the freeze.  However, I started scanning the "information" messages after restart, and I found one of them that was a bit peculiar.  It was issued by TCPIP during Windows boot:

"The system detected that network adapter \DEVICE\TCPIP_{A7B04369-BE67-491F-AE63-5E8FF0E9CAC6} was disconnected from the network, and the adapter's network configuration has been released. If the network adapter was not disconnected, this may indicate that it has malfunctioned. Please contact your vendor for updated drivers."

But of course, as indicated earlier, the most updated drivers have been installed for my network adapter. 

Suggestions?  Should I buy a new ethernet card?

[EddieZ]

A new network adapter is not too expensive, so give it a try. Try to avoid Realtek 

[BTH]

Ok, so I came across a BSOD the other day with the following information:

"DRIVER_IRQL_NOT_LESS_OR_EQUAL
...
*** STOP: 0x0...0D1 ( 0x0...02C, 0x0...02, 0x0...01, 0xFFFFFADF2637A1EO)
*** tcpip6.sys - Address FFFFFADF2637A1EO base at FFFFFADF26340000, DateStamp 485bb4f5
Beginning dump of physical memory
Physical memory dump complete"

Does this help or mean anything?