Solved Homegroup Setup O.K. - now Computer won't Sleep

[HammerHead]

USB Power

Device Manager --> Universal Serial Bus Controllers --> "Which ever hub your mouse and keyboard is attached to" --> Properties --> Power Management

Tic the box to allow the computer to turn off. Leave other box unticked.

 

[rcanino]

Thanks Hammer -

I checked all the USB devices and they're all set up that way - "Allow the computer to turn off this device to save power" is checked and "Allow this device to wake..." is unchecked (grayed out). That accounts for all the ones that have a Power Management tab.

Both of my network adapters are set the same way under Power Management.

It's interesting you suggested this because when I look through the Event Viewer, under Application and Service Logs>Microsoft>Windows>Diagnostics-Performance I always get 3 or 4 errors whenever I try to enter Standby. One error is always Event 300 which is "Windows has resumed from standby." The other 2 are always Event 302, which is "This driver has caused a delay during standby while servicing a device." It's never the same driver(s) causing the delay.

I've googled Event 302 and haven't learned much yet other than this Event # seems to be used for a wide variety of problems.

I think this "delay" error refers to coming back from Standby, not going into it so maybe it's not relevant.

Anyway - Thanks again!

 

[HammerHead]

Toughie

"One error is always Event 300 which is "Windows has resumed from standby." The other 2 are always Event 302, which is "This driver has caused a delay during standby while servicing a device." It's never the same driver(s) causing the delay"

Well that would lead one to believe there is a driver problem. If the fault is varying between the drivers. They are probably not all bad. So it must be one that has some commonality. Check the ACPI Driver here is a clip of mine. It could be corrupt.

I apoligize for grabbing at straws. View attachment 181664

 

[rcanino]

Device Mngr reports "no driver files are required or have been loaded." I hesitate to run "Update Driver" from Dev Mngr (never trusted updating drivers that way). I checked MSI's site for anything new for my board and I'm up-to-date.

After looking further back in the log my guess is these driver "errors" aren't relevant to the Sleep problem. The log shows similar "errors" from months ago, long before I set up the Homegroup; at that time the machine never failed to enter Standby.

Thanks for your help HH - and to everyone else who responded.

I guess it's time to start over with the Homegroup. I'll remove it, make sure Standby works the way it always did and then set up the Homegroup again.

Hopefully that will do the trick.

Thanks again.

 

[rcanino]

Well I finally figured out what was wrong...

For some reason I thought I'd been running S1 all along so that's what I chose after I Cleared CMOS last month.

This morning I went through my notes of the build and I found I'd set it up using S3.

Once I switched to S3 my workstation's "insomnia" was gone. Now the machine sleeps on command without any fuss.

Thanks again for all your help - Everybody.

 

[Dave Atkin]

Good to hear that you got it resolved rcanino


Dave

 

[bg17]

I know this is an old thread, but it's a good reminder for some of us. S1 is technically a sleep state, but as the OP noted not all hardware shuts off on the PC (for example, cooling fans). So it appears as though the PC may not be sleeping. S3 as noted above is the preferred sleep state.

I found this out too recently, when I set sleep type to S1 in the BIOS. I wanted the power light to blink on my pc, so I could tell it was on and in sleep mode. On this particular motherboard, S3 turns off the power light completely, and I wasn't used to that. S1 left the fans running, S3 shuts everything off.