Since I have my new computer & Vista x86 I had problems with putting it into sleep or hibernate state – as soon it went to sleep/hibernate state it would wake up immediately and return to happy working mode (like my children – putting them to sleep is always an adventure). The motherboard is Intel based Gigabyte GA-965P-DS4 and it really shouldn’t have problems. Thanks to the comment of PetarR I soon isolated the problem to Wake-On-Lan feature. For the test I disconnected computer from network (by pulling out the network cable) and it didn’t wake up anymore until I didn’t make him to. Good, but not good enough since I didn’t know how to disable it (WOL was disabled in BIOS already) and I really didn’t have time to play with it as the issue wasn’t critical and I had a lot of other, more important, work to do. Fortunately Alex Feinman (.net CF MVP) suggested device manager’s advanced features and that was it. I right clicked on my network adapter leaf
and turned off the only option that was “suspicious”: Wake Up Capabilities (from Magic Packet & Pattern Matching to None).
And computer finally gets some sleep…
Interestingly, this device wasn’t allowed to wake the computer even before.
Note that I am not yet on official drivers since Gigabyte didn’t relase them yet.
I have the same problem with an Asus N4L-VM DH motherboard. I checked every single device in the device manager, but everything seems in order. The mobo mounts an Intel Tekoa LAN which does not offer any power management options in the “Advanced” tab. Not happy. Not happy at all.
Massacrino, yes, I can feel your pain. Did you try putting computer to sleep with LAN cabel unplugged?
Yes, I did, and it didn’t work. I also checked the BIOS power management settings. My pain is constant and sharp 😉
For me it was turning off the “Allow this device to wake up the computer.” setting in the power management category for the mouse device settings in control panel/device manager.
It would be really nice to have an event log entry on who woke up the computer (perhaps there is one?) – it would be far easier to pinpoint the source of the problem
I did find an eventlog entry, but it didn’t say much. I’ll check if the new settings produce more useful evenlogs. Maybe MSDN has info on putting power management in a sort of “debug” mode for this sort of investigation, or maybe I can start debugging OS machine code,…d%$£! Why does a poor user have to endure this pain?!
Microsoft, I do have a daily job, you know! And it’s not in the Vista Quality Assurance team!!
FINALLY I FIXED IT! It was the HID peripheral drivers for the wireless USB keyboard and mouse. They appear as a normal keyboard and mouse. I got so used to them, that I forgot that they were USB devices.
Thing to remember: the don’t-allow-to-wake-up-PC setting does NOT survive peripheral disconnection. So I have to repeat the trick in Device Manager every time I let Vista detect they have been disconnected. I can see why they have done it, but my guess is this sort of behavior will drive loads of people crazy…
If you are able to connect the wireless receiver to the PS/2 ports you will find it fixes the sleep/hibernate problem. I have the HID fix but it did not correct this problem only the screensaver issue. If you have an earlier than 3.0A receiver you might find that works as well.
I’ve got the same issue with my GA-965P-DS4 . I’ll start searching the VISTA power settings as it seems that VISTA overrides the BIOS settings.
Had the same problem, but finally fixed it by setting the USB device Wake Up Jumpers on my ASUS P4P800 board to +5VSB (factory setting is +5V). This enables the S3/S4 mode for the USB controller. Now my systems enjoy’s a good nights sleep without any problems.