Sleep mode only locks computer after reinstall?

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. :P
(I'd rather live without sleep mode than go through that again)

When I type in that command it says:

Display:
None.

System:
None.

Awaymode:
None.

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)))

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

Maguscreed said:

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:

Driver Verifier - Enable and Disable
(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
https://www.sevenforums.com/crashes-d...tructions.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. :P
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)

DavidW7ncus said:

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.