Problems recovering from sleep in Windows 7

Soldato
Joined
30 May 2009
Posts
4,629
Location
Maidenhead
As the title says, I am having problems with my PC recovering from sleep in Windows 7. I put it into sleep today, went out for around an hour and came back. I booted the PC up, and it didn't go into Windows properly. The keyboard and mouse are recognised, and it gets past POST fine, but it will not go into Windows for some reason. Rig is in sig. Anyone got any ideas what it could be?
 
i have a much older mobo than you but i have problems with windows sleep if power saving turns off the hard drive first. by default, it's set to power off the hard drive after 20 minutes and then sleep after 30 minutes.

if i set the hard drive to never turn off by setting the timeout to 0, recovering from sleep works fine.
 
correct ram voltage set?

Yeah. I'm running my RAM at 1.64V as I can't select 1.65V exactly. Maybe 1.66V instead?

i have a much older mobo than you but i have problems with windows sleep if power saving turns off the hard drive first. by default, it's set to power off the hard drive after 20 minutes and then sleep after 30 minutes.

if i set the hard drive to never turn off by setting the timeout to 0, recovering from sleep works fine.

I might try setting the hard drive to never turn off. Might be worth a try.
 
Sorry to post again in here, but I'm still having problems recovering from sleep in Windows 7. When I start the PC, the monitor just stays black. The PC powers up it seems, but nothing happens. Anyone got any ideas as to what could be causing this?
 
Ah nice. Thanks mate =)

Edit: Ran it. It generated the report. The report didn't really help me much sadly. Was all a bit confusing. And told me some stuff I already knew.
 
Last edited:
Sorry to post again in here, but I'm still having problems recovering from sleep in Windows 7. When I start the PC, the monitor just stays black. The PC powers up it seems, but nothing happens. Anyone got any ideas as to what could be causing this?

I used to have this issue with one of my older PC using Vista - go into BIOS and alter the STR setting, this usually cures it.
 
STR setting?

S1 (POS) Standby: All processor caches are flushed, and the CPU(s) stop executing instructions. Power to the CPU(s) and RAM is maintained; RAM is refreshed; devices that do not indicate they must remain on may be powered down. Some newer machines do not support S1; older machines are more likely to support S1 than S3. This state can operate when a card or peripheral does not recognize S3. The most power-hungry of sleep-modes. POS means Power On Standby.

S2 Standby: System appears off. The CPU has no power; RAM is refreshed; the system is in a lower power mode than S1. It is not commonly implemented.

S3 (STR) Standby: In this state, the CPU has no power, the power supply is in a reduced power mode, main memory (RAM) is still powered, although it is almost the only component that is. Since the state of the operating system and all applications, open documents, etc. lies all in main memory, the user can resume work exactly where they left off the main memory content when the computer comes back from S3 is the same as when it was put into S3. S3 has two advantages over S4; the computer is faster to resume than to reboot, secondly if any running applications (opened documents, etc) have private information in them, this will not be written to the disk. However, disk caches may be flushed to prevent data corruption in case the system doesn't wake up e.g. due to power failure. STR means Save To RAM. In modern operating systems it's called as: Standby in versions of Windows through Windows XP and in some varieties of Linux, Sleep in Windows Vista and Mac OS X.

S4 Hibernate: In this state, all content of main memory is saved to non-volatile memory such as a hard drive, preserving the state of the operating system, all applications, open documents etc. That means that after coming back from S4, the user can resume work where it was left off in much the same way as with S3. The difference between S4 and S3, apart from the added time of moving the main memory content to disk and back, is that a power loss of a computer in S3 makes it lose all data in main memory, including all unsaved documents, while a computer in S4 is unaffected. A system that's in S4 can also be Mechanically Off (no power at all) and still keep its S4 save state information, so that it can resume the operating state after getting back power. This mode is also referred to as Save To Disk, Suspend to Disk, Hibernation in Windows
 
I'm already running the F7 bios on my UD5.

Tried again, and again same problem. The PC seems to boot ok, but the monitor doesn't respond. I switch off the PC by holding the button, and when it reboots, it says resuming Windows. Very strange. I put my RAM voltage to 1.66V, as that may have been the problem. But the PC runs fine with RAM at 1.64V. Stupid Gigabyte BIOS won't let you select 1.65V exactly.

Edit: Took the side off my PC to see the debug display as it booted. I started the PC up, and all it said was E1. I couldn't find out what E1 means in the manual. Anyone know what this could mean?
 
Last edited:
. The PC seems to boot ok, but the monitor doesn't respond. I switch off the PC by holding the button, and when it reboots, it says resuming Windows. Very strange. ?

I had exactly the same problem with a PC running Vista, now I've moved over to Windows 7 it's fixed. Maybe it could be a ACPI driver problem ??
 
I had exactly the same problem with a PC running Vista, now I've moved over to Windows 7 it's fixed. Maybe it could be a ACPI driver problem ??

Well, the thing is, it used to work fine with the RTM build. That was Windows 7 Ultimate. Now I'm running Pro retail, and it doesn't work properly. It's very annoying and weird. I don't understand it.

Anyone else got any ideas on what could be causing it?
 
I've changed my SATA controller back to IDE mode, and everything seems to have fixed itself. Don't have a clue what was going on there. Decided it's not worth running AHCI if I can't use sleep properly.
 
I'm a big fan of sleep mode, and the only time I've ever had a problem with powering up and getting a black screen, are when the PC has decided to update and reboot itself when I'm not around, then it sits at the log on screen, gets bored, goes to sleep, and never comes back to life properly.

I turned off auto reboot for updates, and I've never had this since.
 
Back
Top Bottom