I have very modestly overclocked my system to 150bclk x 21 multi (with turbo on) so far. Running F3g bios with S3 sleep selected in bios.
With Windows 7 64-bit, pressing Windows sleep button seemed to initiate a sleep to disk (hibernate) shutdown, actually taking much longer (about 25 seconds) than a regular complete shutdown (about 7 seconds).
When I changed the power settings in Windows to eliminate hibernate, pressing the Windows sleep button puts the system to sleep very quickly (as expected with S3 sleep to RAM) but then 3 seconds later it turns itself on without any user input and shows the Windows desktop again. If I then put the system to sleep again, it goes into S3 sleep and stays there, as expected.
I have not noticed any problems in resuming from S3 sleep.
Why is a double sleep shutdown necessary with S3 sleep? The hibernate sleep required only one shutdown.
With Windows 7 64-bit, pressing Windows sleep button seemed to initiate a sleep to disk (hibernate) shutdown, actually taking much longer (about 25 seconds) than a regular complete shutdown (about 7 seconds).
When I changed the power settings in Windows to eliminate hibernate, pressing the Windows sleep button puts the system to sleep very quickly (as expected with S3 sleep to RAM) but then 3 seconds later it turns itself on without any user input and shows the Windows desktop again. If I then put the system to sleep again, it goes into S3 sleep and stays there, as expected.
I have not noticed any problems in resuming from S3 sleep.
Why is a double sleep shutdown necessary with S3 sleep? The hibernate sleep required only one shutdown.
Comment