Booting after recovery

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

I posted this question before. The suggested solution didn't work. Is there
acorrection I can make to the registry to correct rhe following problem? If
so please provide me with the steps.
After my computer crashed, I reinstalled the system recovery and application
recovery disks. When the machine goes on hibernate and I try to activate it,
i get the following message: the system could not be restarted from its
previous location due to a read failure. Delete restoration date and proceed
to system boot menu. When I hit enter, the system boots but the message
reappears the next time after hibernation.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

On Tue, 1 Feb 2005 04:03:02 -0800, Annabelle wrote:

> I posted this question before. The suggested solution didn't work. Is there
> acorrection I can make to the registry to correct rhe following problem? If
> so please provide me with the steps.
> After my computer crashed, I reinstalled the system recovery and application
> recovery disks. When the machine goes on hibernate and I try to activate it,
> i get the following message: the system could not be restarted from its
> previous location due to a read failure. Delete restoration date and proceed
> to system boot menu. When I hit enter, the system boots but the message
> reappears the next time after hibernation.

Anabelle, it sounds like you have a hibernation issue.

When you take a system out of hibernation, it powers up and Windows begins
to load normally. At a certain point, the machine state that was stored in
the hiberfil.sys file when you placed the system into hibernation is
loaded. If there is a discrepancy between the machine state when you
hibernated and the current physical machine state - new hardware installed,
for example - that stored machine state is inaccurate and can cause errors
and/or problems.

It sounds like your system cannot match up the stored machine state with
the current physical state of the system and it failing to load. I don't
know what is matching or why it fails to match. It may be that you have
some hardware that is slow to initiate and it is causing the error but that
is only speculation on my part.

What you might try is deleting the hiberfil.sys file or temporarily disable
Hibernate in Power Options (this will automatically delete the hiberfil.sys
file for you). Then reboot normally -or- do a normal power off/power on.
Then re-enable hibernation.

If clearing the old hiberfil.sys file does not resolve the error for you,
you could check with tech support for your system. They may have updates
available for known hibernation issues that apply to your computer model or
they may help you track down what hardware component is not playing nicely
with your system's hibernate functions.

--
Sharon F
MS-MVP ~ Windows Shell/User