Problems with hibernation

[Steve]

My computer generally seems to hibernate okay, except when running word.

What happens is either -

1. Nothing. Something writes to the hard drive and then it doesn't
hibernate.

2. It goes into hibernation, but when I switch back on, the computer hangs
at the text based loading progress bar.

3. It goes into hibernation, but when I switch back on, I get a blue screen
serious error message which is too fast to be readable. It then restarts as
a normal boot and tells me the computer's just recovered from a serious
error.

When not running Word, there's no problem (touch wood).

 

[Guest]

My generic fix for standby/hibernation problems is to update the video
drivers to the latest, WHQL certified versions. It seems to fix most of the
problems.

- John

 

[Doug]

For me, hibernation was problematic so I just disabled it and
only use standby.

Maybe this is the solution for you???

Doug
-

 

[Bob I]

"Autorecover" in Word causing the issue perhaps ?

 

[Haggis]

"Autorecover" in Word causing the issue perhaps ?

here is something to try... have Word open , but NO documents open ...does
it still do it ?

if it doesn't do it with no doc's open , then it is probably related to the
"autorecover" feature as stated (having a doc open creates an additionl
"temp" file of the doc...which it may be trying to save during hibernation
and is not able)

 

[Doug]

May I suggest: If there are problems with hibernation when Word
is open...wouldn't the simple solution be to CLOSE Word BEFORE
attempting hibernation.

Sometimes the easy and obvious solutions are right before our
eyes. We (collectively) tend to blame Windows but miss the
correct procedure.

Doug
-

 

[Steve]

Thanks for all that...

I think it is connected to autorecover, because even though I always save
before trying to hibernate, reloading the docs after one of these
hibernation crashes always comes up with the autorecovered documents
(identical to the last saved).

I tried closing all documents, but hibernation still didn't work. Then I
made sure I'd saved all - including normal.dot - and closed all... Then it
*did* go into hibernation, but again it still crashed on restart, but
differently - it got past the loading progress bar and just hung on a blank
screen.

To Doug - Yes, it's a solution, but not necessarily so simple when you've
got 6 or 7 docs open. It's a bit like saying the simple solution to a bad
bus service is walk. A truism, but not really the point. If hibernation is
provided, shouldn't the company that made it ensure it works as described -
at the very least with programmes made by that same company?

 

[Bob I]

Unfortunately the ability to break something ultimately rests squarely
on the users shoulders. You could not afford the operating system if it
was required to work completely without error in all configurations. The
other option is that the company dictate what is allowed to be used,
which will not be tolerated by the user. The middle course is to
determine the cause and provide feedback so a fix can be issued in the
case where many people are affected.

 

[Steve]

I don't hugely disagree with that... But I do have gripes about the dreadful
combination of complexity and opacity, which leaves us completely unable to
tackle a problem without having to become experts ourselves. The vast number
of running processes, for instance, many of which are not essential and take
up memory and could well be responsible for my hibernation problems for all
I know. I think this, and related things like the vertiginous registry (the
stuff of nightmares) are issues which affect many users, so I'm desperately
hoping MS will address these in the next windows. I've been a PC user for
nearly twenty years, but after XP I'm really ready to move to the Mac. Only
a wonderful Vista will convince me to stay. I'm not hopeful.

 

[Bob I]

We learn as we go. Of course the only difference in "Mac" is that the
manufacturer controlled the Operating system AND the hardware. But the
user still can mess it up by adding software.