Hibernate on Desktop

[Oldster]

Is it possible? I have windows 7 Ultimate 64 SP1. There is no option to
turn on/apply Hibernate in any of the usual places in power options. If I
run a Command prompt "powercfg -h on"(with admin permissions) I get a blue
screen crash with " STOP 24". I believe the 24 is a hex number. I don't
believe I have any disc problems nor Infections. The "STOP" is consistent. I
did try the command prompt in safe mode, and got a prompt to the effect
that there was a "Legacy Driver" preventing the action ... but if so, how do
I delete the legacy driver, and should I?
Incidentally the machine is and AMD 4 processor 4GB machine M4A78LT-M LE
motherboard.

 

[Paul]

Is it possible? I have windows 7 Ultimate 64 SP1. There is no option
to turn on/apply Hibernate in any of the usual places in power options.
If I run a Command prompt "powercfg -h on"(with admin permissions) I get
a blue screen crash with " STOP 24". I believe the 24 is a hex number. I
don't believe I have any disc problems nor Infections. The "STOP" is
consistent. I did try the command prompt in safe mode, and got a prompt
to the effect that there was a "Legacy Driver" preventing the action ...
but if so, how do I delete the legacy driver, and should I?
Incidentally the machine is and AMD 4 processor 4GB machine M4A78LT-M
LE motherboard.

If it looks like this, the 24 would be hex.

STOP 0x00000024 : NTFS_FILE_SYSTEM

http://aumha.org/a/stop.htm

Now, how unlikely is that ?

The "Legacy driver" may not be a driver in the conventional sense.
It's probably not something you installed to correct a blemish
in Device Manager. But it could be some other software which
works at driver level, installs a filter in the driver stack
or the like.

There is a fixit here, but the comment text in here makes no
suggestion the tool does any checking before duplicating
the command you tried.

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

Since you got a BSOD, there could be a minidmp file to look at.
Something like Nirsoft BlueScreenViewer could be used to
browse the fresh new .dmp file.

http://www.nirsoft.net/utils/blue_screen_view.html

(Setup Windows 7 to collect minidmp files... This is sufficient for
a kernel level program, but there is another recipe for debugging
application problems [LocalDumps]. Application problems are
different than kernel problems. The kernel is in the same ring
as the driver code.)

http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/

You might also want to do a quick chkdsk, to see if the
dirty shutdown has caused any file system problems. It's
better to fix chkdsk problems, before too many of them
accumulate (assuming the system doesn't realize it
was shut down dirty).

It could be something like a virtual CD mounter, or some
other kind of file system software, which is affecting
your system. Perhaps some older software, which you installed
on your new system, and it's the source of the problem ?

Paul

 

[Oldster]

Is it possible? I have windows 7 Ultimate 64 SP1. There is no option
to turn on/apply Hibernate in any of the usual places in power
options. If I run a Command prompt "powercfg -h on"(with admin
permissions) I get a blue screen crash with " STOP 24". I believe the
24 is a hex number. I don't believe I have any disc problems nor
Infections. The "STOP" is consistent. I did try the command prompt in
safe mode, and got a prompt to the effect that there was a "Legacy
Driver" preventing the action ... but if so, how do I delete the
legacy driver, and should I?
Incidentally the machine is and AMD 4 processor 4GB machine M4A78LT-M
LE motherboard.

If it looks like this, the 24 would be hex.

STOP 0x00000024 : NTFS_FILE_SYSTEM

http://aumha.org/a/stop.htm

Now, how unlikely is that ?

The "Legacy driver" may not be a driver in the conventional sense.
It's probably not something you installed to correct a blemish
in Device Manager. But it could be some other software which
works at driver level, installs a filter in the driver stack
or the like.

There is a fixit here, but the comment text in here makes no
suggestion the tool does any checking before duplicating
the command you tried.

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

Since you got a BSOD, there could be a minidmp file to look at.
Something like Nirsoft BlueScreenViewer could be used to
browse the fresh new .dmp file.

http://www.nirsoft.net/utils/blue_screen_view.html

(Setup Windows 7 to collect minidmp files... This is sufficient for
a kernel level program, but there is another recipe for debugging
application problems [LocalDumps]. Application problems are
different than kernel problems. The kernel is in the same ring
as the driver code.)

http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/


You might also want to do a quick chkdsk, to see if the
dirty shutdown has caused any file system problems. It's
better to fix chkdsk problems, before too many of them
accumulate (assuming the system doesn't realize it
was shut down dirty).

It could be something like a virtual CD mounter, or some
other kind of file system software, which is affecting
your system. Perhaps some older software, which you installed
on your new system, and it's the source of the problem ?

Paul

Problem Solved. Not exactly certain how, but I turned off my virus
checker completely, then ran powercfg -h SIZE 80 to create the Hibernate
file, followed by powercfg -h ON. Result:- NOW OK.

Oldster

 

[Gene E. Bloch]

Is it possible? I have windows 7 Ultimate 64 SP1. There is no option
to turn on/apply Hibernate in any of the usual places in power
options. If I run a Command prompt "powercfg -h on"(with admin
permissions) I get a blue screen crash with " STOP 24". I believe the
24 is a hex number. I don't believe I have any disc problems nor
Infections. The "STOP" is consistent. I did try the command prompt in
safe mode, and got a prompt to the effect that there was a "Legacy
Driver" preventing the action ... but if so, how do I delete the
legacy driver, and should I?
Incidentally the machine is and AMD 4 processor 4GB machine M4A78LT-M
LE motherboard.

If it looks like this, the 24 would be hex.

STOP 0x00000024 : NTFS_FILE_SYSTEM

http://aumha.org/a/stop.htm

Now, how unlikely is that ?

The "Legacy driver" may not be a driver in the conventional sense.
It's probably not something you installed to correct a blemish
in Device Manager. But it could be some other software which
works at driver level, installs a filter in the driver stack
or the like.

There is a fixit here, but the comment text in here makes no
suggestion the tool does any checking before duplicating
the command you tried.

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

Since you got a BSOD, there could be a minidmp file to look at.
Something like Nirsoft BlueScreenViewer could be used to
browse the fresh new .dmp file.

http://www.nirsoft.net/utils/blue_screen_view.html

(Setup Windows 7 to collect minidmp files... This is sufficient for
a kernel level program, but there is another recipe for debugging
application problems [LocalDumps]. Application problems are
different than kernel problems. The kernel is in the same ring
as the driver code.)

http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/


You might also want to do a quick chkdsk, to see if the
dirty shutdown has caused any file system problems. It's
better to fix chkdsk problems, before too many of them
accumulate (assuming the system doesn't realize it
was shut down dirty).

It could be something like a virtual CD mounter, or some
other kind of file system software, which is affecting
your system. Perhaps some older software, which you installed
on your new system, and it's the source of the problem ?

Paul

Problem Solved. Not exactly certain how, but I turned off my virus checker
completely, then ran powercfg -h SIZE 80 to create the Hibernate file,
followed by powercfg -h ON. Result:- NOW OK.

Oldster

It might be interesting to find out which antivirus program blocked
that setting...

 

[Yousuf Khan]

Is it possible? I have windows 7 Ultimate 64 SP1. There is no option to
turn on/apply Hibernate in any of the usual places in power options. If
I run a Command prompt "powercfg -h on"(with admin permissions) I get a
blue screen crash with " STOP 24". I believe the 24 is a hex number. I
don't believe I have any disc problems nor Infections. The "STOP" is
consistent. I did try the command prompt in safe mode, and got a prompt
to the effect that there was a "Legacy Driver" preventing the action ...
but if so, how do I delete the legacy driver, and should I?
Incidentally the machine is and AMD 4 processor 4GB machine M4A78LT-M LE
motherboard.

In Windows 7, there is now a "hybrid sleep mode" which replaces the
traditional hibernate on desktops (laptops still have the regular
hibernate). The hybrid sleep is simply the standby and hibernate modes
combined into one. In standby mode, the machine's state would be saved
to RAM, and then everything would go into standby; on resume, the state
would be quickly recovered from RAM in a few seconds. There would be
only a little power sent to the RAM to keep it refreshed. In hibernate,
the machine's state would be saved to disk instead, and power would be
completely shut-off; on resume, the state would be slowly recovered from
disk in a few dozen seconds.

In hybrid sleep mode, the machine's state is saved to both RAM and disk.
If the machine had uninterrupted power, then on resume the state would
come from RAM and be just as fast as the previous standby mode. If the
power failed in the middle of standby, then the state would be restored
from disk, and it would act just like it came out of hibernate.

If you want the traditional separate standby and hibernate modes again,
then what you have to do is go into your power options, Advanced
settings, Sleep, Allow Hybrid Sleep, Setting: Off.

Yousuf Khan

 

[Rob]

In Windows 7, there is now a "hybrid sleep mode" which replaces the traditional hibernate on desktops (laptops still have the regular hibernate). The hybrid sleep is simply the standby and hibernate modes combined into one. In standby mode, the machine's state would be saved to RAM, and then everything would go into standby; on resume, the state would be quickly recovered from RAM in a few seconds. There would be only a little power sent to the RAM to keep it refreshed. In hibernate, the machine's state would be saved to disk instead, and power would be completely shut-off; on resume, the state would be slowly recovered from disk in a few dozen seconds.

In hybrid sleep mode, the machine's state is saved to both RAM and disk. If the machine had uninterrupted power, then on resume the state would come from RAM and be just as fast as the previous standby mode. If the power failed in the middle of standby, then the state would be restored from disk, and it would act just like it came out of hibernate.

If you want the traditional separate standby and hibernate modes again, then what you have to do is go into your power options, Advanced settings, Sleep, Allow Hybrid Sleep, Setting: Off.

Yousuf Khan

That change is also worth trying for general issues with sleep mode.
I've looked at several PCs lately which would not wake properly
from sleep mode and disabling hybrid sleep fixed the problems instantly.
I suspect the underlying cause is certain device driver power saving
features not being set/implemented correctly.

 

[choro]

In Windows 7, there is now a "hybrid sleep mode" which replaces the
traditional hibernate on desktops (laptops still have the regular
hibernate). The hybrid sleep is simply the standby and hibernate modes
combined into one. In standby mode, the machine's state would be saved
to RAM, and then everything would go into standby; on resume, the state
would be quickly recovered from RAM in a few seconds. There would be
only a little power sent to the RAM to keep it refreshed. In hibernate,
the machine's state would be saved to disk instead, and power would be
completely shut-off; on resume, the state would be slowly recovered from
disk in a few dozen seconds.

In hybrid sleep mode, the machine's state is saved to both RAM and disk.
If the machine had uninterrupted power, then on resume the state would
come from RAM and be just as fast as the previous standby mode. If the
power failed in the middle of standby, then the state would be restored
from disk, and it would act just like it came out of hibernate.

If you want the traditional separate standby and hibernate modes again,
then what you have to do is go into your power options, Advanced
settings, Sleep, Allow Hybrid Sleep, Setting: Off.

Yousuf Khan

Yousouf,

I must admit that I admire your postings which are not only very brief
and to the point but also extremely informative.

I have to add that I also admire your ability to express yourself so
clearly and precisely in English.

I wonder whether English was your mother tongue or whether, like me, you
learned English as a second language.
-- choro

 

[Yousuf Khan]

Yousouf,

I must admit that I admire your postings which are not only very brief
and to the point but also extremely informative.

I have to add that I also admire your ability to express yourself so
clearly and precisely in English.

I wonder whether English was your mother tongue or whether, like me, you
learned English as a second language.

It's not my mother tongue but it is my primary language, as I moved to
Canada as a small kid.

Yousuf Khan

 

[Yousuf Khan]

That change is also worth trying for general issues with sleep mode.
I've looked at several PCs lately which would not wake properly
from sleep mode and disabling hybrid sleep fixed the problems instantly.
I suspect the underlying cause is certain device driver power saving
features not being set/implemented correctly.

It would be interesting to see if those same PC's recover from
old-fashioned hibernate properly too. If they can recover from
hibernate, and old-fashioned standby properly, then what could cause
them problems with hybrid sleep since that's just the two modes combined?

Yousuf Khan