up vote 0 down vote favorite
share [g+] share [fb]

My personal desktop, running 32-bit Windows XP SP2 (with 4GB RAM, 2.75GB addressable, swap disabled, hiberfil.sys existing and contiguous on C:\; SP3 is not installed because SP2 has been working fine and I do not want to re-qualify with SP3 just for sheer perversity) typically gets hibernated at night. For a long time this worked great, but recently the machine has had trouble entering hibernation.

Sometimes when I press my power button (configured to hibernate), the box will start the procedure for hibernating (i.e., go to the blue "Windows XP" background logo and display a message about entering hibernation), but before displaying the usual blue-on-black hibernation progress bar it will drop back to the desktop. No error messages appear, on screen or in the system log. The only record of unsuccessful hibernation attempts in the system log, which proudly proclaims that "The Windows Image Acquisition (WIA) service entered the running state." once per failed hibernation attempt.

The problem is almost certainly resource related: if I then close one or more applications which are running, and repeat the exact same process, the machine will hibernate perfectly. There does not appear to be a reliable high-water mark for virtual or physical memory use, below which the machine is guaranteed to hibernate; it's different every time (though typically, below about 1.1–1.4 GB memory usage seems to be where hibernate succeeds most often). Memory may not even be the relevant resource; as far as I know, it could also be handles or sockets.

This behavior is relatively recent: it has only started in the last few months; before then, I could hibernate reliably no matter what the current resource use of the system. This machine claims to have hotfix Q909095 installed, but since the symptoms of my problem match KB909095 rather well, I'm suspicious if this fix is actually working as intended.

Any ideas on how to fix this or where to start debugging?

link|improve this question
Is your HD nearly full? – JP. Jul 20 '09 at 20:35
C: is rather full, yes (417 MB free at the moment), but 1. The hibernation file already exists and counts against that free space 2. I have virtual memory/swap disabled, so no additional space should be needed for that 3. The machine hibernates perfectly fine with that amount of disk space if I close programs first – kquinn Jul 20 '09 at 20:53
It’s possible that you’re experiencing KB909095, but if the fix didn’t work, then it’s indeed probably something else. Programs can abort shutdown (or hibernate/standby/etc.) From your description, it sounds like something is preventing the shutdown/hibernation from completing. Maybe an application, or likely a driver, needs to do some cleanup or something, and is causing the hibernation to cancel, but then you can do it a few moments later because it has finished. Have you installed any new applications recently (ie since it last worked without problem)? Any new hardware or updated drivers? – Synetech Jul 16 '11 at 21:58
feedback

1 Answer

It would seem to me that the more memory is in use, the more disk space would be required to hibernate. Try clearing more space on your HD and see if that allows you to hibernate without killing any applications. Also, here are some more potential diagnostic steps you could look at.

link|improve this answer
Sorry, but most of those suggestions aren't useful for troubleshooting intermittent problems. I can't hibernate, then I close one program (and recover memory but no disk space), and all of a sudden I can. How to test if my machine supports hibernation at all is not particularly useful. – kquinn Jul 20 '09 at 23:09
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.