Earlier many reported this problem with win 7 x64 build 7100, now I did a clean install of build 7600 x64 & the problem is now more frequently happening every 15 mins it freezes the comp.
Uploading stops
downloading sometime stops
sound/video freezes
applications stop responding
nothing can be done to the system at that time.
I am using asus P5B dlx wifi mobo with Marvell Yukon Gigabit Ethernet lan drivers latest v 11.10.6.3 dated 6/15/09.
Is there any solution to this I am pulling my hair due to this issue & cant use the comp.
I'm running a clean install of Windows 7 Home Premium. All I've installed is firefox and imgburn, I've installed the latest Marvel Yukon drivers for my nic and I'm still getting it randomly stopping dead. Troubleshooting / disabling and reenabling the card aren't working. I have to do a full reboot .
My Computer
At a glance
Windows 7 Home Premium RetailInte Core 2 Duo E8600Mushkin Redline 2 x 2gbInno3D Nvidia GeForce GTX295
i have the same problem and the newest driver didn't solve it. My internet connection freezes, ffox opens google in 3 minutes when marvell ethernet freezes..
any suggestion?
-----------------------------------------------
edit:
i found something on google :
"\bring it up in the device manager. Go to the tab that says "allow this device to be turned off to conserve power" uncheck that.
I have found that that can be an issue at times./"
i guess this may be a solution but i am still waiting for your suggestions...
-----------------------------
edit again:
my above suggestion didn't solve the problem.
the only way that i can bring up my ethernet card from freezing is waiting or changing its mac addresss.
I don't remember what I all tried to get a fix for this. Mainly:
- different drivers including one from Windows XP and Vista
- different NICs (even one from 1999 with an old DEC chip)
- completely disable IPV6 (remove the complete TCP IP stack)
- change the tons of tcpip parameters in the registry
- disable the win firewall
- disab all unnecessary services.msc (barebone Black Viper's Web Site)
Nothing of this worked. All TCP packets going out through the default route (gateway) do not get a SYN ACK back (checked with Wireshark). Funny: UDP traffic is not affected at all and ongoing connections (like downloads in progress) are not halted. It must be something very wrong in the TCPIP stack itself. I think it's not driver releated at all. May be your best bet is change the Switch/Router environment. The problem is known since the win7betas and did not get fixed in the RTM. My hope is not very high to get a fix from M$ before SP1.
If the latest driver didn't solve it, I'd start looking elsewhere at what the problem could be.
It could be some program you have to start with Windows, possibly from the motherboard manufacturer. It could be other software making internet connections that is running and not working so well.
Check the event logs for anything suspicious or related. Alleviate those problems and this might go away with them.
Ups. I forgot to mention. This happens without any third party involved. No other SW was installed beside Win7 and of course Wireshark to do some packet traces. BTW: based on this and other quirks our company shelved Win7 (as they did with Vista before). Even no testing are ongoing in the labs anymore. Oh well may be SP1 will be reconsidered. If not - may be Win8 or 9 or... (hope M$ is still around then).
the strange thing is when i installed and tried to surf on windows xp mode on windows 7, it works pretty well. Even my internet connection is gone on windows 7, it works like charm on windows xp mode. i hope MS will solve this problem or I will be have to go back to xp or vista
I had the same problem. The solution that appears to work:
Under "Device Manager / Network adapters / Marvell . . . / Advanced" tab:
Energy Star: Disabled
Wake From Shutdown: Off
Wake-Up Capabilities: None
Any combination of the three might be the culprit. The leading culprit would be Energy Star. I can see where the OS would turn off the port after inactivity but fail to turn it on when activity resumes. Either Microsoft or Marvell didn't implement the feature correctly.