Computer wakes up immediately after sleep/hibernate

[WinSpecToR]

I checked and there is nothing in power options that is waking it up, I disabled wake on lan, mouse and keyboard and it is still waking up without me doing anything.

[themaster1]

Perhaps there is a task in the task scheduler that's doing something, you want to check that

[joy]

Control Panel->Device Manager->double click "Network Adapters"->right click controller ->Properties->Power Management Tab->Check the box "Allow the computer to turn off this device to save power".

[WinSpecToR]

Control Panel->Device Manager->double click "Network Adapters"->right click controller ->Properties->Power Management Tab->Check the box "Allow the computer to turn off this device to save power".

Tried that, didnt work.

[jagabo]

I had a similar problem once. I don't remember exactly what the problem was but I think it had to do with the NIC. Maybe the wake-on-lan feature.

[Budman1]

Check Task Scheduler, as themaster1 suggested, (CMD window type 'TASKSCHD.MSC') look for any that have 'Condition' tab showing 'Wake computer to run' checked. If Windows is truly causing the wake up, it will probably be listed here.

Also there area lot of CMD Windows 'powercfg' options such as POWERCFG -LASTWAKE that may tell you what woke your computer. There are other parameters to show what CAN wake your computer up. These options are listed at http://technet.microsoft.com/en-us/library/cc748940(v=ws.10).aspx. The most handy are -a. -q. and -devicequery.

[WinSpecToR]

Check Task Scheduler, as themaster1 suggested, (CMD window type 'TASKSCHD.MSC') look for any that have 'Condition' tab showing 'Wake computer to run' checked. If Windows is truly causing the wake up, it will probably be listed here.

Also there area lot of CMD Windows 'powercfg' options such as POWERCFG -LASTWAKE that may tell you what woke your computer. There are other parameters to show what CAN wake your computer up. These options are listed at http://technet.microsoft.com/en-us/library/cc748940(v=ws.10).aspx. The most handy are -a. -q. and -devicequery.

Nothing listed in taskschd. I will look at the powercfg tomorrow. Funny thing is this didn't happen before I cloned + switched my hdd.

Don't believe its a feature on the NIC.

[WinSpecToR]

Bump

[Nelson37]

Perhaps describing in detail the ONE THING that seems to be the triggering event for this problem might be somewhat useful.

Also try disconnecting Mouse, KB, Network cable, Audio, all USB devices, etc., Leave only the KB, use it to shut down, then pull the cable as soon as the command begins to execute.

This will ELIMINATE each and every one of these devices as a possible cause of the problem. I am exceptionally curious how it came to be that you were aware of this correlation yet failed to mention it in your very first post about this issue.

It certainly sounds like the HDD procedure might be involved, but without a LOT more information on this procedure, it is impossible to say.

[Budman1]

I just had an occurrence as you mentioned on my computer and I used this to find the source. Look in the system event log (Start->control Panel->System and Security->Admin tools->event viewer). Expand windows logs and select system. Hit CTRL-F to bring up find window and look for sleep:


Click the details tab and expand System plus sign to find Process ID:


Downloaded and opened Process Explorer to find Process ID:


Turns out it was Adobe updating so I turned off the ability to wake the computer as mentioned in the thread from themaster1.


If the PID had been such as Windows services, Host Process, and other non-specific items, it was probably caused by keyboard, mouse, usb device and then I would have pulled the usb items as Nelson37 explained in his post.

[handyguy]

Yes, Adobe was known to do this, but changed it in a new version.

[WinSpecToR]

Well after testing it out for a few days everything is fine now. Turns out it was my ssd migration manager (sort of like partition magic).

Thank you everyone.