[Vista64] network not working after sleep

[JTsyo]

For the past 5 years things have been fine with the computer but the last two days when the computer comes out of sleep, the network adapter doesn't work. Restarting the computer brings it back. When checking device manger, everything is fine but the network settings thinks the cable is unplugged. Also when coming back from sleep the system is unresponsive (mouse doesn't move) for 30 sec and there are a few error type sounds. The last thing I did before things went bonkers was install Mumble.

So far I've tried:
-updated drivers for network adapter (Intel)
-disabled turn device off in power management for Ethernet
-disabled IPV6

Any ideas where to look?

 

[Ketchup]

Check to see if Windows Update did anything around the time the issue started.

 

[JTsyo]

Check to see if Windows Update did anything around the time the issue started.

Now that I think about it, I had gone to sleep at least once and came back without issue after installing mumble. Where can I find the log for windows updates?

 

[Ketchup]

Windows Update in the start menu, click on view update history, or click on installed updates at the bottom if you find one you want to remove.

 

[JTsyo]

No updates in the last few days seem to deal with networking or power management. Looking at the Event viewer I see the error are being caused by Bonjour service, an apple itunes service. I'm currently trying to remove it.

 

[Ketchup]

No updates in the last few days seem to deal with networking or power management. Looking at the Event viewer I see the error are being caused by Bonjour service, an apple itunes service. I'm currently trying to remove it.

Ah! Dang you Apple, lol.

 

[JTsyo]

No luck with that. Also tried a clean boot but that didn't help, so it's not software. I do get an error for the driver now (either code 10 or 43). If I don't find a solution by the weekend, I'll just do a clean install.

I have my steam and origin installs on the D drive. If I wipe teh C and install Vista, can I just keep those or do I need to save the local data and re-install them?

 

[ViRGE]

Just out of curiosity, is a reboot strictly necessary, or does disabling and reenabling the network connection fix that issue? I once had a Marvell based system that when paired up with one of my GigE switches did something similar to what you describe; cycling the NIC worked in that case, which would be faster than cycling the whole system. (I never did find a permanent solution)

 

[JTsyo]

Just out of curiosity, is a reboot strictly necessary, or does disabling and reenabling the network connection fix that issue? I once had a Marvell based system that when paired up with one of my GigE switches did something similar to what you describe; cycling the NIC worked in that case, which would be faster than cycling the whole system. (I never did find a permanent solution)

Disabling the NIC in device manager and then re-enabling is not enough to bring back the network. I'm sure the key is system freezing and the error beeps I hear but I can't figure out what is causing that. The event logger had Bonjour causing the most errors but uninstalling that didn't help. Weird that this happened without any changes I can think of.

 

[Ketchup]

Might want to start removing updates, any updates, back to when the issue started. That is weird for sure. You could always try a system restore back to a previous date I suppose, if there is nothing you have to lose.

 

[ViRGE]

Disabling the NIC in device manager and then re-enabling is not enough to bring back the network. I'm sure the key is system freezing and the error beeps I hear but I can't figure out what is causing that. The event logger had Bonjour causing the most errors but uninstalling that didn't help. Weird that this happened without any changes I can think of.

This is just a lark, but try switching out your current switch for another. The fact that cycling the NIC doesn't fix it means this likely won't do anything for you, but assuming you have anything else on hand it's quick and easy to test.

 

[JTsyo]

Might want to start removing updates, any updates, back to when the issue started. That is weird for sure. You could always try a system restore back to a previous date I suppose, if there is nothing you have to lose.

For some reason I only had one system restore point. I didn't see where you would set how many to keep.

This is just a lark, but try switching out your current switch for another. The fact that cycling the NIC doesn't fix it means this likely won't do anything for you, but assuming you have anything else on hand it's quick and easy to test.

I do have my old router that I can try.

 

[VirtualLarry]

Might want to start removing updates, any updates, back to when the issue started. That is weird for sure. You could always try a system restore back to a previous date I suppose, if there is nothing you have to lose.

I had the same thing happen to me on a client's Win7 PC. I was reformatting it, and the factory wifi driver would work... until I did the full compliment of updates, then it wouldn't. I ended up reformatting, and then not doing Windows Updates.

 

[SMark7]

I had the same thing happen to me on a client's Win7 PC. I was reformatting it, and the factory wifi driver would work... until I did the full compliment of updates, then it wouldn't. I ended up reformatting, and then not doing Windows Updates.

I'm having similar problem since last week on Windows 7. The same computer was working fine for the last 3 years. The only thing I did recently was installing the regular Windows Updates, so I think it might be related.

After waking up from sleep mode the network adapter disappears completely from the device manager, so it is impossible to restore or configure the network. Even restarting the computer doesn't help. I must shut it down, wait a few seconds, then switch it back on. The network adapter then reappears and works without any problem.

My workaround for the moment is to disable the automatic sleep mode.

 

[JTsyo]

I reinstalled windows and still have the issue. So guessing it's hardware. I had already tried deleting all the updates from last week.

One of the errors I still get is from WMI

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Anyone know if this is due to the network being down?

 

[Ketchup]

You could see if this fixes that error:

http://support.microsoft.com/kb/950375

or this:

http://social.msdn.microsoft.com/Fo...winserver2008appcompatabilityandcertification

 

[JTsyo]

You could see if this fixes that error:

http://support.microsoft.com/kb/950375

or this:

http://social.msdn.microsoft.com/Fo...winserver2008appcompatabilityandcertification

This particular Event ID 10 error message listed above can be safely ignored, this is not indicative of a problem with the Service Pack or with the operating system.

seems it's not a big deal. It doesn't come up after every wake. I'll try picking up a Ethernet -> usb and see if that works.

 

[JTsyo]

Here's the update: Got my Ethernet to USB adapter and now I have internet after coming back from sleep. But I still get the 20-30 second freeze and a few beeps. My guess is something crapped out on the motherboard and it takes effect after sleep. Ethernet is the thing I notice but must be causing other errors in windows.

Quick question: this adapter is only 100MB, can I plug-in two cables and have let windows pick which one to use?

EDIT: SO this morning, waking from sleep internet wasn't working again. Unplugging the USB and plugging it back in got it up again. Not sure what to make of that.