Quote: Originally Posted by kenmdotexe
The hibernation feature may be convenient for some people to use, but it doesn't work well in many computers and it's more trouble than it's worth.
If it does work properly and without adverse consequences, it's certainly useful. System reboot out of hibernation is much much faster than a "cold boot" from a previous total shutdown state.
I've had THREE separate problems with hibernation, which have influenced whether or not I use it on a given system:
(1) WinXP SP3 "broke" hibernation, by modifying either the approach or mechanism. Obviously, this couldn't have affected 100% of the installed WinXP SP2 user base (unless almost 0% of WinXP users also use hibernation and thus didn't notice the SP3 defect) but it certainly affected 100% of the WinXP SP3 systems I was involved with. The symptom was loss of network adapter, loss of sound, and other very major and obvious effects, when the system was brought back up out of hibernation.
The solution was to use "SAFE MODE" to replace the four broken DLL's in SP3, with their earlier SP2 versions: WSCSVC.DLL, WZCDLG.DLL, WZCSAPI.DLL and WZCSVC.DLL.
Once restored to the SP2 versions of these DLLs, WinXP SP3 hibernation (which actually was now SP2 hibernation) once again worked perfectly as it always had before SP3 broke it. No more loss of network, sound, etc., after coming out of hibernation.
(2) One of my Windows 7 systems (Supermicro C2SBX motherboard) has a UPS, which has software that runs on Windows 7 which can automatically induce hibernation if there's a power outage that lasts long enough to drop the battery capacity down to "5 minutes remaining".
The UPS is connected by a USB cable to the PC, which is how the software and UPS box hardware communicate.
Well, there are problems that arise if I manually put that machine into hibernation, when I bring it back out of hibernation. Either the UPS finds itself in an odd state, or maybe the software restarts before the USB connection to the UPS is reestablished, or something else odd that I'm not describing correctly.
Whatever the real story, it just turns out not to be worth it to fight the aggravating messages and problems which arise when the hibernated machine is brought out of hibernation... tied to the USB-connected UPS.
I simply shut this system down when it's not required (although now it's my HTPC and is up 24/7... as I don't let it sleep or hibernate though I know I could/should, because of this UPS-related issue).
(3) A second Windows 7 system (ASUS P5Q3 motherboard) used to go into and come out of hibernation perfectly. However about six months ago the machine began to show signs that either one of my SATA hard drives was failing, or perhaps that the connected SATA controller on the motherboard was beginning to flake out, or something.
Symptom was that coming out of hibernation that drive would be "gone"! BIOS would show it not present, and of course Windows 7 kind of missed it too.
I've replaced the drive with a new one, tried three different motherboard SATA connectors, reseated the SATA cable at both ends, and even changed the SATA cable. Each corrective action was successful... for a while, and then astonishingly the symptom would return and I'd have to try something else.
Anyway, at the moment, the latest combination of "kick starts" has seemingly accomplished a 100% successful stable state, and I have not seen the drive "disappear" in about two months now.
However... I also have a SCSI hard drive in the machine, running off of an Adaptec 29320 SCSI controller. And strangely, as of late, when coming out of hibernation the hard drive itself had also seemingly "disappeared"... just as the SATA drive had done six months ago.
Getting into the 29320 BIOS at boot time, it sure looked like the drive was there. And if I then re-booted after examining things in the 29320 BIOS, sure enough the drive would once again be present. But fairly consistently, simply coming right out of hibernation that drive would simply be gone.
I'd then have to RESTART (essentially doing a full cold re-boot, through SHUTDOWN was not first required to cure the problem) to correct things. Sure enough, after a true normal restart (or, coming out of a true SHUTDOWN state), that SCSI drive would always be present.
I've now just taken to no longer hibernating that machine. I simply SHUTDOWN and accept the longer startup when I next bring it back up.
It's interesting how I used hibernation on this system for about 1 1/2 hears (including under WinXP, before migrating to Windows 7) and never had trouble. But obviously something about the OFF/ON transitions involving hibernation have taken their toll on the motherboard, SATA controllers, Adaptec SCSI controller, hard drives, etc.
Perhaps it's better just to leave it on, let the drives spin down after a period of non-use as a way of reducing wear-and-tear, noise, heat, and electricity usage, and just let it be available 24/7. Or, if you're going to be away from the system for an extended period, just do a real SHUTDOWN.
Anyway, that's just my own personal experience with hibernation. I'd like to use it all the time, but it's apparently a bit "delicate"... depending on configuration.