XP SP2 Yukon Marvel gigabit loosing connection and requiring reboot

[~~~ .NET Ed ~~~]

For the past month or so there is a problem that has agravated. Originally I
thought this was related to the hibernation but this happens even after a
fresh reboot.

Then I thought it was the router or cable modem getting stuck but I was able
to verify that when the anomaly occurs I can still access internet from the
laptop on my network.

My system is a Pentium VI 3.0GHz with 1GB running Windows XP Pro SP2 with
all known updates. It has some virtual network adapters (VMWare) and a real
hardware network adapter which is built-in into the ASUS motherboard, it is
a Marvell Yukon 88E001/8003/8010 PCI Gigabit Ethernet Controller with driver
from 19/09/2005 (latest AFAIK) from Marvell, v8.41.1.3. The PC I must say
is virus and spyware free as I not only run it on a restricted account but
have up-to-date scanners and subscriptions and check it regularly.

The problem is when I am doing large file transfers, for example using wget
(same problem if I use IE or FireFox) to download a 4.0-4.2 GB ISO image
then at some point during the download the PC totally and completely
isolates itself from the network.

When the anomaly occurs I am not able to talk to the internet nor am I able
to ping the laptop on my local network (or the other way around). The laptop
as I mention still has access to internet. When this happens I notice in
IPCONFIG that the IP address is changed to the default address set in the
properties with mask 255.255.0.0 and it is then totally impossible to
"renew" via DHCP (running "ipconfig /renew" as admin says there has been an
error trying to renew).

This is quite annoying so I have high speed (2.0Mbit) internet connection
for nothing. Reinstalling the OS is out of the question.

Any ideas?

Emilio

 

[Oliver Breitfelder]

[..]

a Marvell Yukon 88E001/8003/8010 PCI Gigabit Ethernet Controller with
driver
The problem is when I am doing large file transfers, for example using
wget (same problem if I use IE or FireFox) to download a 4.0-4.2 GB ISO
image then at some point during the download the PC totally and completely
isolates itself from the network.

EAXCTLY the same here! Asus P4P800-E Deluxe with P4 Northwood 3Ghz: When
producing contant traffic on the LAN the system isolates itself completely
form local network and internet (no toher computers in newtork neighborhood,
no WWW access).

If I then open "network connections" > right-click on LAN-Connection >
disable and afterwards enable it again, access to LAN and internet is
restored, everything is working again. Until I produce traffic on LAN
again... In my situation it happens when I try indexing my music archive
with media center software. The music files are located on an NAS which is
part of the LAN. The media center needs to look up every single one of the
files to check for MP3 tags and so on. This produces heavy traffic as if you
were copying large files of consecutive data (huge files).

I am still not sure: Win XP SP2 problem? Marvell problem? Marvell driver
problem? Not sure how to find out... All I can remember is that I did a
re-install of XP and used the most recent Marvell drivers from Asus. Perhaps
I'll try the stock drivers that came with the Asus P4P800 motherboard driver
CD for tewsting purposes. Before re-installing the OS everything was perfect
concerning the Marvell LAN capabilities.

Bye Oliver

 

[Ricky]

In device manager right click the NIC..properties and on the Power
management tab make sure 'Allow the computer to turn off this device to save
power' is not checked.

[..]

a Marvell Yukon 88E001/8003/8010 PCI Gigabit Ethernet Controller with
driver
The problem is when I am doing large file transfers, for example using
wget (same problem if I use IE or FireFox) to download a 4.0-4.2 GB ISO
image then at some point during the download the PC totally and
completely isolates itself from the network.

EAXCTLY the same here! Asus P4P800-E Deluxe with P4 Northwood 3Ghz: When
producing contant traffic on the LAN the system isolates itself completely
form local network and internet (no toher computers in newtork
neighborhood, no WWW access).

If I then open "network connections" > right-click on LAN-Connection >
disable and afterwards enable it again, access to LAN and internet is
restored, everything is working again. Until I produce traffic on LAN
again... In my situation it happens when I try indexing my music archive
with media center software. The music files are located on an NAS which is
part of the LAN. The media center needs to look up every single one of the
files to check for MP3 tags and so on. This produces heavy traffic as if
you were copying large files of consecutive data (huge files).

I am still not sure: Win XP SP2 problem? Marvell problem? Marvell driver
problem? Not sure how to find out... All I can remember is that I did a
re-install of XP and used the most recent Marvell drivers from Asus.
Perhaps I'll try the stock drivers that came with the Asus P4P800
motherboard driver CD for tewsting purposes. Before re-installing the OS
everything was perfect concerning the Marvell LAN capabilities.

Bye Oliver

 

[Oliver Breitfelder]

In device manager right click the NIC..properties and on the Power
management tab make sure 'Allow the computer to turn off this device to
save power' is not checked.

Thanks, I'll have a look at this. At the moment it works. My solution (needs
extensive testing):

When I setup the system at the beginning I was using Marvell driver 7.xx
(Asus only offeres 6.28 as latest version on their homepage). "Windows
Update" then offered an optional hardware driver update. I agreed and
installed the version delivered by Windows Update. This was v8.xx. Yesterday
I opened device manager > properties of Marvell > "Installed driver" to set
the driver back from v8 to v7. Tried indexing files again: system got stuck,
NIC isolates itself from network again. So neither v7 nor v8 are working
correctly in my case.

Then I downloaded v10.xx directly from marvell.com (this is the latest
release, dated August 2007 and not yet offered by Windows Update). After
installation and reboot the system successfully indexed all the files
without any problems. I hope the problems are fixed now.

I'll test large file transfer today and report.


Bye Oliver