Re: SYSTEM File Corruption Repair Didn't Work

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Jeremy,

The auto-detect acting up suggests a problem with the BIOs. Most likely
the CMOS battery (the battery on the motherboard) is failing. You may
want to check with the system manufacture, and for instruction on how to
replace the battery.

--
Regards,
Bert Kinney MS-MVP Shell/User
http://bertk.mvps.org

Jeremy B wrote:
Hello. Last night I go to turn off my computer (which runs Windows XP
SP2). I have AIM running so I turn it off first. Right after that I
go to Start > Turn off computer > Shut Down. As XP is logging off it
pauses as an error message appears concerning AIM. It says that AIM
had some sort of problem shutting down. The only button in the error
window is "close" at the bottom right corner. I click it, the window
goes away and XP shuts down like normal.

This morning I turn my computer back on. The POST test runs but then
instead of auto-detecting my primary master drive immediately like
normal it hangs there for several seconds. Uh-oh. It doesn't detect
any drives and I get an error message saying "Windows XP could not
start because the following file is missing or corrupt:
D:\WINDOWS\SYSTEM32\CONFIG\SYSTEM." I've had this problem before and
know how to fix it. I follow the instructions from the Microsoft
website (Article ID 307545).

After I finish I go to reboot and it STILL won't boot right. Now the
auto-detection of my primary master still hangs but is eventually
detected. My primary slave is not, though. The POST test ends and I
get the XP logo screen for a while and then a quick flash of a blue
screen that lasts for only an instant. All I can make out is some
white text at the top of the screen and some hexadecimal code a third
of the way down. After that the computer reboots on its own.
Auto-detect eventually detects my primary master and I get the "We
apologize for the inconvenience." Safe Mode prompt. I select Safe
Mode (if I select anything else it won't work and the computer just
reboots) and I AM able to log on with Safe Mode. I've checked to make
sure that the files I copied over from the Restore Point into
windows\system32\config\* are the right ones and they are. They are
not copies of the files created from the most recent Restore Point. I
did follow Article 307545 correctly. I also tried restoring to a
Restore Point older than the one I used to replace the corrupted
files and still it doesn't boot right. Though I am no longer getting
the error message about the SYSTEM file corruption I am still not
able to boot. There must be another error besides that. Does anyone
have any ideas? Thank you very much.

Jeremy


.

Quantcast