If you use a script to wake it, what does powercfg -lastwake say was the last wakeup event? Hopefully it's the event you expect, but if not, that's a good place to start.
You could also run powercfg -devicequery wake_armed to see what devices CAN wake the system. It'd be interesting to see the output of these three commands (-lastwake, -devicequery, -energy) compared to your working box.
So this is getting downright weird...for these two machines that will not co-op.
First - a wee bit of history. The one workstation that is now working is my personal machine. It has a GigaByte motherboard...standard issue EP45-UD3L. It will wake, perform a task and then return to sleep (idle) state within 120 seconds of the task completing. One thing that is totally "right" about this machine - when I watch it do the wake cycle - is that the monitor attached - ALSO stays in some sort of suspend mode while the task is being completed - the screen remains black...power light is solid - instead of blinking and the machine does it's business quickly and goes back to sleep.
For the other two machine - that are not co-operating - they have identical motherboards Gigabyte EP45-UD3R with standard issue hardware (nVidia graphics, Corsair RAM..etc etc...both have the same PSU). They wake up okay...they perform the task okay...but they cannot seem to attain that "system idle" state that is required to kick in after the 120 second timeout period. Also very different for these two - their monitors come of full blast during wakeup...full desktop, full power...and the of course - they stay on. Just wondering if video has anything to do with this...?
Anyhoo - onto Powercfg. I have tried a boatload of things on one machine:
1. Pulled ALL the powercfg reports using the above commands.
2. devicequery is normal - only one device on thr machine - the keyboard can wake the machine
3. -requests - shows nothing on all three stages
4. -energy shows nothing out of the ordinary - except that every single USB device cannot enter "suspend" state...I saw a few of these in the report for my working machine so I do not see this as a barrier to attaining a "system idle" state.
Every more strange is that I can change the Power Options on this box and change the "put this computer to sleep" value to 1 minute...stand back - and the box faithfully goes to sleep in one minute. It works perfectly. So I am stumped.
Something is keeping it from reaching that "system idle" state after an unattended wakeup....in my last tests...I did a wake cycle and after the machine did not go back to sleep in 120 seconds...I ran -requests again and saw a
filesystem\srvnet
under the System area...something on the network is chatting away to this machine...but then I run it again 5 minutes later and -requests show nothing. I have shut of Antivirus thinking that may be the problem. I removed this machine from the Homegroup and shut off any sharing of media...basically this thing is just out there on the network with no ties to anything and it still does not go back to sleep...
sigh...
I will keep digging :)
VP
Quote