• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Trouble waking out of S4 hibernation.

C

Compman55

Golden Member
Motherboard is a ASUS Z87-Pro. Has the latest BIOS.

I know it is not wise to hibernate with a SSD, but I gave it a try. The issue is I have 32GB ram so it does take some time to complete the hibernation and power down. Upon power up, the LED display once is windows just stays at "40" - Resuming from S4 state.

It never goes past this, and the computer functions with exception to no internet, the network card cannot get an IP address.

Any reason why the motherboard is not coming out of the S4 state? Could it have something to do with having an SSD?
 
anyone??????

Not sure where to being troubleshooting.

I forgot to mention this is Windows 7 x64 bit. UEFI is set to legacy with CSM enabled. Secure boot is off, and intel rapid start is turned off.
 
Last edited:
Have you tried s6/7 sleep state? just to see if hardware recovers from that.

Might be better off using sleep in the future as I can't imagine writing 32GB of data written every time you hibernate would be good for the SSD.
 
How do I activate s6/s7 states?

I need this to work so when the power goes out the UPS will properly put the computer into hibernate, so all my open work does not get lost. Even though work is saved, I can never remeber what 40-50 tabs I have open. And often the browser cannot recover all the tabs.

It will not be all that often, so I am not concerned about SSD life.
 
It should be activated by default in the bios. What happens if you wake the computer from sleep?
 
Whatever sleep states are actually effected on this or that motherboard, they show up in motherboard settings in combinations of three -- mostly among S1, S3, and S5. S1 would be the "least asleep" or require greater power consumption. Options may appear like "S1 & S3" and there's a feature called "hybrid sleep" -- not to be confused entirely with "hibernation."

You can have trouble with various sleep states for equally various reasons, including a power supply or PSU on the decline and other motherboard settings. For instance, disabling the power-saving features C1E etc. on the motherboard may cause trouble for resuming from a given sleep-state deeper than S1 or S3. Depending on the combination of factors, it may be wiser to choose some state other than "hibernation," or otherwise live with what works.
 
I turned on Erp Ready for S4 & S5 within the BIOS. When resuming from hibernate, the motherbaord staus LED reads out "40" - Waking up from S4 state.

However everything works fine. So I guess I should ignore the code then as well as everything works? Normally in windows the code is "A0".
 
Compman55 said:
I turned on Erp Ready for S4 & S5 within the BIOS. When resuming from hibernate, the motherbaord staus LED reads out "40" - Waking up from S4 state.

However everything works fine. So I guess I should ignore the code then as well as everything works? Normally in windows the code is "A0".
Click to expand...

Without a lot of detail on my own current glitches, I've been tuning up my
WHS 2011 server. This brought to my attention the rare occasion when the server sleeps.

So given my own observations, you may want to check your event logs after the machine wakes up, to see if it throws up an error message suggesting corrupted memory. This likely wouldn't have anything to do with your status LED message. I just think you ought to keep an eye on these things as you sort it out. The good thing: you have a current-gen motherboard and fairly new parts, so . . .
 
I don;t even need to hibernate, but when the UPS exhausts it battery, the only option is to hibernate so the info does not get lost.
 
Update.

Threw in a 200GB spinpoint hard drive, and the hibernate works perfect. It does take a bit of time for the session to save to disk, but otherwise it resumes just fine.

So what am I missing with the crucial m500. Upon resume it say the system firmware was unable to save to session to the disk.....or something like tat.
 
This is not an option.

As stated above, I will get several power outages a year. My UPS will automatically hibernate the system, thus saving my session to disk. All outages are murphys law examples, "when I am not home".

So I guess I am lost if this is a motherboard problem with SSD. A bug in the SSD that prevents proper hibernation. Or a problem with windows 7 in relation to SSD's and large amounts of RAM (32GB). Or somthing else completely.
 
Compman55 said:
This is not an option.

As stated above, I will get several power outages a year. My UPS will automatically hibernate the system, thus saving my session to disk. All outages are murphys law examples, "when I am not home".

So I guess I am lost if this is a motherboard problem with SSD. A bug in the SSD that prevents proper hibernation. Or a problem with windows 7 in relation to SSD's and large amounts of RAM (32GB). Or somthing else completely.
Click to expand...

Why don't you just put your hibernate partition on the spinpoint.

http://superuser.com/questions/376593/creating-a-hibernation-partition-on-windows-7
 
Spinpoint is a test hard drive I use. It is S.L.O.W at SATA I.

I would rather troubleshoot why my new $1500 system will not hibernate on a SSD. My laptops all do.

Should I replace the Crucial with a Samsung?

I can always use the cruicial in another system less important.

I don't know if this has anything to do with it, but when there was only 4GB memory in use, it seemed to hibernate fine. With more, it doesn't seem to. Don't be thrown off by this, as I have no way of knowing for sure.
 
I used the powercfg -h off, rebooted, then powercfg -h on

Seemed to work, but would soft lock once at the desktop.

Updated to the newest RST drivers from intels site and the problem seems fixed.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top