Windows 7 - Hibernate not working

So after all that stress of getting my system back after a failed clone operation, I am finally operating from a new, fast 2TB disk.

Ever since the migration, I have lost hibernation. I get no error, it just briefly displays the "Windows is hibernating" screen and then switches back to the desktop without hibernating.

The hibernation hotfix that I got a year or so again on this newsgroup now does not work because I am on SP3 (I knew there was a catch to upgrading.)

There is a fixit file here, but I doubt this is going to
fix it, seeing as the computer thought it was going into
Hibernation, and then the file creation step failed.

http://support.microsoft.com/kb/920730

I'd say there was something wrong with the actual file
operation itself. Like, the Hibernation process was not
able to create a file. Is there a hiberfil.sys in there ?
It could be hidden, in terms of file explorer visibility.

If there was an ACPI state issue, you probably would not have
been offered a Hibernate option at all. The option would
have been missing.

If it was the SP2 issue, would not you have seen a dialog
mentioning "Insufficient resources" ? The reason there
would not be a hotfix for SP3, is the replaced files for
the SP2 version, would have been rolled into SP3 so it
already has the fix.

I have a 4GB RAM system, WinXP SP3 32 bit, and the
C:\hiberfil.sys is 3,220,295,680 bytes. My pagefile
is smaller, but since the dump on error is set to
64KB file, that is not a problem. Pagefile just adds
to memory size, in terms of total virtual memory available,
and pagefile does not have to match anything otherwise.
Hiberfil.sys has to be able to store the entire RAM image,
in case all the bytes are in use. (The fewer bytes needing
to be written, the faster the Hibernate progress bar
moves during shutdown.)

Paul

Yeah I have tried everything and nothing is working. Tried to boot up with all services and startup disabled as well. What could it be?

Have you looked in Event Viewer ?

Any error message recorded in there ?

Paul

N


No, just "The Windows Image Acquisition (WIA) service entered the running state."

I do not know where else to look for error messages.


http://support.microsoft.com/kb/907477

*******

The SATA interface, has some power state info. This is not consistent
with your problem, but it is about the only thing I can think of,
other than a disk problem of some sort, that might explain it.

http://www.sevenforums.com/tutorials/177819-ahci-link-power-management-enable-hipm-dipm.html

One similar to HIPM/DIPM is LPMDSTATE, which is something used on
Intel storage interfaces.

I'd want the disk interface to *not* have power states, but
to just keep running until shutdown. That way, less can go wrong.

But an issue with one of those, is just grasping at straws. If a
power state error occurred, you would  think there would be a dialog of
some sort, with an error number. The idea would be, you lose
communications with the drive, and some disk operation times out.
If that drive was also the place storing "Events", perhaps there'd
be no log either. I wonder if it is possible to move the
hiberfil.sys to another disk ?

Paul

That second link you sent appears to be for Win7. The XP hibernation troubleshooting guide does not seem to have anything relevant to my case.

I tried installing a new WinXP on a seperate partition and the hibernate tab was not there at all. I also tried installing on a VM and got the same thing. Trying to do powercfg /h on returned a "not supported by your system" error. Wtf?

All this because I got a new HDD? Can't be, because why would the VM fail?

Power Management is via APM or ACPI. ACPI has been in usage
since at least Win2K (because I had a Win2K install fail once
because the BIOS did not do ACPI right).

If you are not installing in a VM, check the BIOS and make sure
ACPI 2.0 is enabled in there. When the install is finished,
go to Device Manager, and check the "Computer" entry. If
you have a multi-core processor, the properties should
say "ACPI Multiprocessor PC". The ACPI is important.

If it says "Standard PC", you may have to reinstall! If
you have not had problems doing a "regular" shutdown, then
do not despair.

If you mess up the setting for that, like specify S1 instead
of S1 & S3 or Auto in the BIOS, after the fact you can use
Standby Suspend to RAM (S3).

This site is down right now.

http://forums.pcper.com/showthread.php?p=1825058&postcount=31

Try the archive, for info on running Dumppo, and a download
link from Microsoft for it. Unfortunately, the archive copy
is not loading properly for me either. The web code could be
trying to ping the originating site.

http://web.archive.org/web/20081028131452/http://forums.pcper.com/showthread.php?p=1825058&postcount=31

Anyway, the steps would be:

1) Enter BIOS at startup.

Power Menu:

Suspend Mode [ S1 only, S1 and S3, Auto ]    Try anything but "S1 only".
I use Auto.

ACPI 2.0 Support [ Enabled ]                 Why Asus disables this by
default I will never know...

2) Boot system.
3) Get a copy of dumppo and do an "Administrative Override".

This is the contents of the pcper article...

This tells you how to do the override.

******************************************************************
http://forums.pcper.com/showthread.php?p=1825058&postcount=31

05-27-2003, 04:11 PM  UserID=nameless


The "best" way to go about using STR is to enable "Suspend To RAM"
in the BIOS before installing the operating system. Unfortunately, this
is not common knowledge, and no one (i.e. Asus) goes out of their way to
TELL you this. I did not know myself, back in January when I built my
A7N8X Deluxe system.

The good news is that DUMPPO.EXE can correct the matter -- without having to
be run at every boot. Here is how:

1) Download DUMPPO.EXE from Microsoft (to ensure you get the correct file):

ftp://ftp.microsoft.com/products/Oemtest/v1.1/WOSTest/Tools/Acpi/dumppo.exe

2) Go to a command line rooted in the directory DUMPPO.EXE resides in, and
enter this command:

DUMPPO.EXE admin

DUMPPO.EXE will list some basic information about the current sleep policies.
For example, here is what I had before correcting matters using DUMPPO.EXE:

C:\Downloads>DUMPPO.EXE admin

Admin policy overrides
Min sleep state......: S1
Max sleep state......: S4 - hibernate
Min video timeout....: 0
Max video timeout....: -1
Min spindown timeout.: 0
Max spindown timeout.: -1

The problem here is the "Min sleep state" value. When you tell WinXP to enter
standby mode, WinXP uses the "Min sleep state" setting to determine what ACPI
standby mode to use. In the case above, WinXP sees and uses S1 (which is normal
standby, where all that happens is that the hard drive(s) and monitor(s) power
down).

3) Correct the "Min sleep state" value using the following command line:

DUMPPO.EXE admin /ac minsleep=s3

4) Reboot, and when you do, go into the BIOS and ensure that the "Suspend To RAM"
value is enabled(!). [i.e S3]

5) Back in Windows, issue the DUMPPO.EXE admin command again, exactly as in step
(2), and you should see something similar to this:

C:\Downloads>DUMPPO.EXE admin
Admin policy overrides
Min sleep state......: S3
Max sleep state......: S4 - hibernate
Min video timeout....: 0
Max video timeout....: -1
Min spindown timeout.: 0
Max spindown timeout.: -1

The "Min sleep state" value should stay at S3, across reboots, and your system
should be able to enter STR mode. (Incidentally, when I ran DUMPPO.EXE, I tried
half-heartedly to monitor the registry and file system for the changes it made,
but came up with nothing.)

If your system enters STR (i.e. S3) mode properly, but does not restore itself
properly (e.g. the monitor stays blank, you get BSOD errors, etc.), the most
likely culprit is a buggy or incompatible driver or piece of hardware.

I figured it was worth resurrecting this old thread in order to try to help..."
**************************************************

HTH,
Paul

Try disabling your keyboard and mouse from bringing your computer back
to life. Sometimes these two devices are just too sensitive, and any
little movement might cause them to abort the hibernate or sleep.

Yousuf Khan

troubleshooting guide doesn't seem to have anything relevant to my cas=
e.
nate tab was not there at all. I also tried installing on a VM and got the =
same thing. Trying to do powercfg /h on returned a "not supported by y=
our system" error. Wtf?
e VM fail?
ead.php?p=3D1825058&postcount=3D31
1 only".
y
now...
nt to change anyway -- "minsleep" is.
nd To RAM"
y to
y
ng to
le):
ppo.exe
and
icies.
EXE:
l WinXP to enter
ermine what ACPI
s normal
) power
mmand line:
Suspend To RAM"
s in step
, and your system
I tried
it made,
itself
most
help..."

My BIOS has been unchanged since the migration to the new HDD, but I did no=
tice that ACPI 2.0 was disabled, which meant that hibernate worked before w=
ith this off. I tried to re-enable it and change Auto to S3 and did that du=
mppo trick as well but the problem remains.

DUMPPO tricks never worked for me in the past when I had similar hibernate =
problems anyway.

How do I do this, I forget. I doubt it is the issue since I did not move my mouse or press any other key except the sleep key on the keyboard.

I do not know, but that seemed to clear up a problem I was having with
hibernate and sleep under Windows 7. It may not be the same thing.

Try this instead:

Windows XP Standby and Hibernate Problem (Update 5/2009) | Five Percent:
Conserve Energy
http://fivepercent.us/2008/08/15/windows-xp-standby-and-hibernate-problem-update-82008/

Yousuf Khan