WindowsXP Restart

A problem which has outwitted me to date is affecting the automatic restarting of windows XP after hibernation over night. I have power option set to go to standby first, and then later to hibernate after 1 hr.

It would appear that restoration works fine after the 1 hr, provided the power light on the PC is still alight, but when restoring in the morning the power light is off, and the following appears on screen: "The system could not be restored from its previous location due to a read failure." The only option provided is "Delete restoration data and proceed to a system boot menu." A reboot start then prompts a Checkdisk which usually reports "size of the \hyperfil.sys entry is not valid." I have seen another file mentioned once but was not quick enough to record it. A correction is made automatically by windows, no other errors, and reboot is successful.

I have done a disk defrag (in safe mode), I use Registry FirstAid program, and several anti-spyware programs, but these have not made any difference. Each restart failure has been reported to microsoft via the automatic error reporting feature but no advice to repair is available from MS. No new programs had been installed just prior to this problem arising other than an automatic Windows update.

I run XP Home (Service pack 2 Build 2600) on an AcerPower ST at 2.4GHz with 512 MB & 40GB HDD.

Has anybody had similar experence or any suggestions?
Thanks
Brian

 

No experience but three suggestions:
- click on start, on run, key in

Code:

sfc /scannow

and OK. See if the system file checker can replace any damaged or missing system files.
- check for any BIOS updates to your motherboard.
- check your event logs for any errors/warnings that contain more diagnostic information. start=>run=>eventvwr.msc and OK. If you find likely looking entries, open one, click on the icon below the up/down arrows (sends a text copy to your clipboard) and paste it here.

 

Do you have write caching enabled on any of your drives?

 

Thanks to the 2 who responded to my query, Newt & Mron. I tried your suggestions, and the problem has now been fixed. I dont know which was effective as no mention was made in the logs of any file fixes after the scannow or the full scandisk (on restart).
Thanks anyway
Brian

 

Glad it is working.

The sfc /scannow should have written results to your event logs as should chkdsk /f or chkdsk /r. I may be wrong but I could swear that both utilities create an entry even if nothing much needed fixing.