New
#1
Win7 system or monitor not wake from sleep, solved?
(fans running but no monitor so have no idea where it's stuck)
I had been experiencing this on and off for a long while - finally posted something over on MS technet social, not expecting an answer
Win7 system not wake from sleep - sometimes.
substance is repeated below in quotes...
was "monitor not wake from sleep - sometimes". only recourse is to press reset and restart computer.
I have googled and recognize the futility of asking this, but I'll try anyway... - many incidents - no solutions that I could find.
About 1 in 5 times when I wake from sleep the monitor stays blank. This has happened with the current and last 3 Nvidia drivers.
No overclocking.
Win7 oem Home Premium.
Relatively new, uncluttered build
Monitor Hannspree HF289H, recognized, with current drivers.
9800 gtx+ recognized currently with 197.45 driver - happened with 2 previous drivers.
Happened with BIOS F9 and F10 flash.
Gigabyte GA-EP45-UD3P, Q8200, 2x2GB OCZ Reaper1150, EVGA 9800GTX+ N863 ,
BFG GS-650, Win 7 Home Premium
No overclocking, latest drivers.
I am a geek and Win since 3.11 so please only constructive help after reading the above.
Thanks.> Please note I generalized the title from "Monitor" to "system"
Further investigation on this has led me to notice
1. that when I use the USB (eg mouse movement) to wake the computer, I am much more likely to have it hang / not fully wake from sleep. So I removed the check mark on the mouse driver, and wake from sleep by pressing the computer case power on button - it then quickly goes to the user logon screen.
1a. I also may have noticed that a quick flick of the power on/off button MAY result in a hang. I now do a firm 1/2 second press with no problems. (it takes holding it for 4 seconds to signal to the bios to shut down.)
2. Then I found that (in BIOS setup) the Timing of the DRAM vs the timing of the cpu/fsb, and (I would suspect) how the MS wake from sleep software responds to the bios, is a factor.
a. Overclocking does, as we would expect, increase the wake from sleep hang incidence.
b. Setting the (G)MCH Frequency Latch, and or the System Memory Multiplier to anything other than AUTO, ALSO increases the hang incidence, which might suggest a phasing problem.
So , so far, I have found that, with those 2 set to auto, I can run a default 333 system at 400, but not 444, with no problems as far as hang in wake from sleep.
I consider this a work in progress, for the moment, but post this as I know lots of folks are having Win7 problems with this, and may find this useful.
Please note that after proving 2 a and b, I have not gone back to test the validity of 1.
The only reason this could not directly be considered Win7 problem is because Win7 does not give us a pause for x seconds before executing wake from sleep opsys software . in the control panel Power settings. Should it be there? Dunno - next time I see Bill I'll mention it to him. (Fixed in Win9!) )
I will post back in a bit. I am also playing with the BIOS "Delay for HDD x seconds ". This is showing great promise even at 444! Is it really that simple???
I have seen a ton of folks on 6.0 and 6.1 with this problem, various symptoms, but no solution.
I wonder if the above, which may well be a full solution for me, would help anyone here, or who lands here via google....
This forum may be a better repository for such a solution than social net.
As stated above, I see this as a work in progress, but have successfully woken from sleep a bunch of times with clock set to 444. (HDD delay set to 3 sec) No hangs yet...
Cheers!