Sleep mode only locks computer after reinstall?

[Zukaro]

For some reason after reinstalling Windows 7 Home Premium on my computer I can't go into sleep mode anymore. When I tell my computer to go into sleep mode the screen goes dark and it looks like it's going to do it, but then it wakes up immediately and brings me to the lock screen (basically it just locks my computer rather than actually sleeps).

Reinstalling Windows isn't an option as I've just spent a week getting everything setup and installing all my games and such.
(I'd rather live without sleep mode than go through that again)

 

[Maguscreed]

open a elevated command prompt and try using the command
powercfg /requests

This should name all the things that may be/ or are interfering with the sleep function.

 

[Zukaro]

When I type in that command it says:

Display:
None.

System:
None.

Awaymode:
None.

 

[Maguscreed]

Windows 7 won't sleep or hibernate. - Microsoft Answers

There is this, but it is hit and miss on positive results. Though it can't really harm anything either.

It is also a setting in most bios configurations/types.

 

[Zukaro]

I've tried that, it does the same thing still. I'll check my BIOS settings later, however, I don't see how they'd be affecting sleep mode now when using the same settings on my previous installation didn't do that.

(I had changed one setting however, but it had nothing to do with power (it was just which hard drive the BIOS saw; I changed it to my second hard drive as I have Ubuntu 12.04 on here as well and I needed to boot from my other hard drive for the grub bootmanager to work so I could actually get into Ubuntu (I'm not sure if this could be it, but it's really the only thing that's much different from my previous installation)))

 

[Maguscreed]

I've heard of grub causing some odd problems with windows, but this is not one of them.
My only other thought is you are running a driver the system doesn't like.
The only way to work that out is a bit involved though.

If you are willing to press through turn on driver verifier:

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
(Please read all instructions for driver verifier before using as it's possible it will make the machine behave badly and you need to know how to undo it.)

The actual intent is to cause the system to blue screen creating a memory dump I can read in the debugger.

If you get a blue screen you can then just follow these instructions
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

(once it's created a dump file for us you can turn driver verifier back off)

 

[DavidE]

Based on the OP it sounds like the PC is going to sleep, then waking up.

From an elevated command prompt enter these commends

powercfg -lastwake
powercfg -devicequery wake_armed
powercfg -energy
​

if -lastwake returns something, that may be your problem
wake_armed will list devices capable of waking the PC
-energy will create a report that may help

 

[Zukaro]

I've heard of grub causing some odd problems with windows, but this is not one of them.
My only other thought is you are running a driver the system doesn't like.
The only way to work that out is a bit involved though.

If you are willing to press through turn on driver verifier:

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
(Please read all instructions for driver verifier before using as it's possible it will make the machine behave badly and you need to know how to undo it.)

The actual intent is to cause the system to blue screen creating a memory dump I can read in the debugger.

If you get a blue screen you can then just follow these instructions
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

(once it's created a dump file for us you can turn driver verifier back off)

I'd rather not deal with all that stuff right now.
I don't think it's a drive though, as I'm using the same drivers as were on my last installation.

(maybe later I'll attempt that)

 

[Maguscreed]

the the post just above your last one there.
if his idea gives blank results.. yeah I'm out of other ideas.

 

[Zukaro]

Based on the OP it sounds like the PC is going to sleep, then waking up.

From an elevated command prompt enter these commends

powercfg -lastwake
powercfg -devicequery wake_armed
powercfg -energy
​

if -lastwake returns something, that may be your problem
wake_armed will list devices capable of waking the PC
-energy will create a report that may help

1.
Wake History Count - 0

2.
HID-compliant mouse
HID-compliant mouse <001>
HID Keyboard Device

3.
I've attached the report to this post.

 

[DavidE]

In Control Panel / Power Options /Advanced settings

make sure USB Selective suspend is set to disabled
check that multimedia is set to allow the computer to sleep
​

a wireless mouse can cause problems...
These elevated CMD commands will disable the devices that can wake the PC

Powercfg -devicedisablewake "HID-compliant mouse <001>"
Powercfg -devicedisablewake "HID-compliant mouse"
Powercfg -devicedisablewake "HID Keyboard Device"
​

to make sure these commands worked re-run
powercfg -devicequery wake_armed

Also make sure you don't have an unsaved Theme.

 

[Zukaro]

I just tried all that stuff; none seem to work.
(also, my mouse is wired)

 

[DavidE]

One thing that seems odd to me is in your Energy report it shows S1 AND S3 Sleep are supported.
On my systems I have only ever seen S1 OR S3 supported.

I don't understand how Windows would know which sleep mode to use.

I set S1 or S3 in the BIOS, and that is what shows in my report.
I'm not sure what you have in your BIOS for this.
You may want to check your BIOS setting for this.

 

[DavidE]

Another thing you can check is the Event Viewer to see if you are getting the Sleep event after you click on Sleep.
It's Event ID 42 in System Logs - see my screen print.

 

[Zukaro]

In my BIOS S1 and S3 were set to auto (something like that).
Also, the event viewer shows the sleep event.

 

[DavidE]

OK
From what I learned Win7 will default to S1 Sleep.

For me after the Sleep Event #42, the next System Event is #1.
You can see this in my last Screen Print.
Event #1 sets the Windows time - and that is the first system event when I wake up the PC.

What is your next system event after Event ID #42?
Maybe we can find a problem looking at your Event Log?

Given that you do get a Sleep Event, using a Sleep Trace may have the answer.
I've never used it, but I would for a situation like this.
http://www.sevenforums.com/tutorial...up-shutdown-sleep-hibernate-reboot-trace.html