What is the Wake from hibernation sequence after sleep mode activated?

Mobo BIOS S3 Suspend to RAM

Power Plan options set to "sleep" sleep. Hibernate option seems missing (see photo).



I removed case side panel and watched more closely as computer tried to resume from wake. There is vibration from the main disk drive device. The Graphics card fan switch on, but the CPU fan doesn't. Or rather the CPU fan kind of jolts half a cycle or one cycle only at the point computer powers down again.

I used to use the optimisation feature from Norton antivirus. This problem occurred nearly a month before subscription ended. I think the Norton did disk optimisations.

I also have PowerTools jv16. That does more startup optimisations and registry compaction, if enabled.

If I were to gather a sleep trace, which trace flags would I enable?

I've never needed the trace log, no experience here.
I would try the boot flags and see what i get.
Maybe there are other flags not listed in the tutorial.

I never use optimizers or registry cleaners (tune up programs as asked by @torchwood).
No telling what they changed.
You might want to consider a Repair Install or Clean Install.
Repair Install
Clean Install Windows 7

As hibernation is NOT showing,
something has dissabled it, ive only ever done it using a command line entry. (powercfg -h off)

Roy

if you selected S3 in bios that disables hibernation at the bios level therefore windows knows you cannot hibernate and does not give you the option. Having said that, it would still be best if you told windows to disable hibernation as discussed in posts #9 and #13.

Problems coming out of sleep are usually a failure on windows part to re-establish a driver, so first check your device manager (start > run > devmgmt.msc > enter) to make sure there are no checkmarks indicating bad drivers

Next upplug any usb devices other than your keyboard and mouse. USB devices are sometimes the culprit in this situation. Our goal here is to identify the component that is the cause here, cuz its probably just one component that is causing this issue.

It sounds like your cpu fan starts very briefly then shuts down when coming out of sleep. Makes me wonder if your system is shutting down on purpose. I would go into bios and disable chassis intrusion detect (if you have it), also put the cpu fan mode on full instead of auto, or pwm. I kind of doubt its either of these, but we're just trying things here until we find the culprit.

If none of the above fixes the issue, your hard drives are the next possibility. Since hard drives take a few seconds to start spinning when coming out of sleep, windows can get hung up in trying to detect them. So in order to rule this out as your problem, I would try disabling them from entering sleep in the first place to see if that makes a difference. Note that it might just be one of the drives that is the issue, so you might try this with each drive one at a time. This link will tell you how to keep them from spinning down at sleep time.

Prevent Hard Drive from going to sleep in Windows 10 / 8 / 7

@iko22
You're getting a lot of good help and suggestions.
Try everything suggested.

johnhoh said:

if you selected S3 in bios that disables hibernation at the bios level therefore windows knows you cannot hibernate and does not give you the option.

My PC's/motherboards don't work that way.
I can select S3 sleep in bios and still use S4 hibernate in Windows.
Here's a snip from a powercfg -energy report:

Source instructions for the energy report:
Power Options and Sleep Mode Problems

I don't think this will help the OP issue, but for anyone interested, additional Sleep Options can be enabled:

johnhoh said:

Problems coming out of sleep are usually a failure on windows part to re-establish a driver, so first check your device manager (start > run > devmgmt.msc > enter) to make sure there are no checkmarks indicating bad drivers

Device Manager currently shows no check-marks against bad drivers.

It has sort of reported my mouse device driver description "wrong". Device Manager describes my device as Razer Diamondback 3G which is an 1800dpi device, and reports the device to be "working properly" .

However, mine is the 1600 dpi device - could it be that I've installed wrong driver file? I searched web to check what I had been given. Driver version 1.0.0.2 07/03/2007 seems to be the most recent file, according to several sites.

torchwood said:

As hibernation is NOT showing,
something has dissabled it, ive only ever done it using a command line entry. (powercfg -h off)

Roy

johnhoh said:

if you selected S3 in bios that disables hibernation at the bios level therefore windows knows you cannot hibernate and does not give you the option. Having said that, it would still be best if you told windows to disable hibernation as discussed in posts #9 and #13.

It's all floding back to me .. I disabled hibernation months ago when computer started responding extremely slowly waking on resume.

It might be that Windows installed updates not compatable with my machine. I have yet diagnosed that issue.

Maybe that earlier issue has become the problem right now

Lessons learned : Power Options DOES NOT gray out disabled hibernate option, as option is removed altogether from menu.

johnhoh said:

It sounds like your cpu fan starts very briefly then shuts down when coming out of sleep. Makes me wonder if your system is shutting down on purpose. I would go into bios and disable chassis intrusion detect (if you have it), also put the cpu fan mode on full instead of auto, or pwm. I kind of doubt its either of these, but we're just trying things here until we find the culprit.

Yes that is fair assessment, the cpu fan just cuts out. Is it system automation on purpose?

johnhoh said:

I see your motherboard is a desktop motherboard, I assume your system is always plugged in. If so, you might just disable hibernation altogether and use normal sleep mode instead.

If none of the above fixes the issue, your hard drives are the next possibility. Since hard drives take a few seconds to start spinning when coming out of sleep, windows can get hung up in trying to detect them.

Well, I went into routine of powering down computer into it's BIOS, rebooting the machine, then trying resume sleep ... each time same symptoms ... tried cpu fan on full and tried prevent hard drive going sleep windows , also the chassis intrusion setting is disabled.
I see HPET was set to 32-bit, probably after I refreshed BIOS configuration to default one time. Setting HPET to 64-bit has no overriding change in this scenario.

I don't think I am able turn off hard drives individually (?). There is only one system HDD. I'll consider options to removing the others HDD from power supply.

johnhoh said:

But when you "wake" from hibernation, EVERYTHING that was in ram back when you hibernated (i.e. everything in that first paragraph!) which was stuffed into one giant file and stored on a hard drive, is INSTANTLY reloaded back into ram in the hope that it will pick up exactly where it left off. That all drivers will simultaneously become reaquainted without conflict, that all programs will resume interacting with the operating system without error. It is a giant task of cooperation, and shows you why the Power On Boot Process that loads everything sequentially and slowly has been in effect for decades. Do a search on "computer won't wake from hibernation" and you'll get the same number of hits as if you searched on "why can't I meet a nice girl/guy". Its a complex question with a million possible answers and one practical path to take is to just admit you're probably never going to meet anyone and your computer is probably never going to come out of hibernation either.

At cmd command line, I typed:

Code:

powercfg -devicequery wake_from_S3_supported

Output:

Code:

Intel(R) 4 Series Chipset PCI Express Root Port - 2E21
Intel(R) ICH10 Family USB Universal Host Controller - 3A37
Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4A
UMBus Enumerator
Communications Port (COM1)
USB Composite Device (003)
Intel(R) ICH10 Family USB Universal Host Controller - 3A38
HID-compliant consumer control device (001)
USB Root Hub
PCI bus
USB Root Hub (001)
Intel(R) ICH10 Family USB Universal Host Controller - 3A39
USB Root Hub (002)
USB Root Hub (003)
Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A
Razer Diamondback 3G
USB Root Hub (004)
USB Root Hub (005)
USB Input Device (010)
Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)
Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C
HID Keyboard Device
USB Root Hub (006)
USB Root Hub (007)
Intel(R) ICH10 Family USB Universal Host Controller - 3A34
High Definition Audio Controller (001)
HID-compliant device (008)
Intel(R) 82801 PCI Bridge - 244E
Intel(R) ICH10 Family USB Universal Host Controller - 3A35
Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40
HID-compliant mouse
USB Input Device (016)
Intel(R) ICH10 Family USB Universal Host Controller - 3A36
Intel(R) ICH10 Family PCI Express Root Port 5 - 3A48
Realtek High Definition Audio

Perhaps if I kneew what order these device drivers are reloaded, then I'd stand a better chance of diagnosing the resume fail. Maybe immediately before CPU fan, maybe thousandths of a second after CPU fan? Or maybe a giant juggernaut driver that is sluggish to load, like as you say, the disks.