windows\system32\config\system is missing or corrupt.. every boot

  • Thread starter Thread starter Martin Brodie
  • Start date Start date
M

Martin Brodie

I have a PC that reports

Windows XP could not start because the following file is missing or
corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

every power-on boot, thereafter you press a key and the system
performs soft-reset, and attempts to boot, you would expect the same
message to appear again, however continues to the Windows XP starting
screen loader and loads successfully.

History:
This message above was happening infrequently and would be recovered
by using the technique on MS KB 307545 but now it is on every boot of
the machine from a cold/power-on start of the machine. And a press of
a key reboots and now XP loads fine. (weird!!)

I wonder if anyone can shed any light as to what might be happening
here.
I am thinking a shutdown problem or writing of cache to hard drive
issue.

Any known fixes or things to check.

OS: Windows XP Professional SP1 & latest Critical Updates.
No Device Manager conflicts.
MB: ASUS A7V333

Thanks
 
Martin said:
I have a PC that reports

Windows XP could not start because the following file is missing or
corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

every power-on boot, thereafter you press a key and the system
performs soft-reset, and attempts to boot, you would expect the same
message to appear again, however continues to the Windows XP starting
screen loader and loads successfully.

History:
This message above was happening infrequently and would be recovered
by using the technique on MS KB 307545 but now it is on every boot of
the machine from a cold/power-on start of the machine. And a press of
a key reboots and now XP loads fine. (weird!!)

I wonder if anyone can shed any light as to what might be happening
here.
I am thinking a shutdown problem or writing of cache to hard drive
issue.

Any known fixes or things to check.
Click to expand...

The ERUNT utility available here may make it easier to fix if it recurs...
http://HOME.T-ONLINE.DE/home/lars.hederer/erunt

If the problem persists, try swapping current RAM (even if it checks
good) for a single, high-quality 512Mb chip. XP reportedly is sensitive
to memory timing.
 
Back
Top