Booting error message

Archman

Senior member
Apr 25, 2002
458
0
0
System specs:

AMD XP 1833 MHz cpu
256 MB DDR Ram
128 MB ATI 9800 Pro
XP Home
Asus A7V8X Motherboard (recently flashed to the latest BIOS)

Okay, this is what happened:

tried overclocking this system little by little, to see how far I could push it and now I can not boot into windows XP home, it goes to the Advanced Startup Options (Safe Mode, Safe Mode with Networking, last known good config of Win XP, or start Windows normally) but whichever option I choose the machine starts to boot, and then a brief blue screen appears, and it reboots itself.

I also installed a new PSU, the old one was dying.

Anyways, I tried to install Win XP Home on top of itself, using the CD, and I got this error message:

"A problem has been detected and windows has been shut down to prevent damage to your computer.

REGISTRY_ERROR

If this is the first time you've seen this stop error screen...

Check to make sure any new hardware or software is properly installed. If this is a new install, ask your hardware or software manufacturer for any Windows updates you may need.

If problems continue, disable or remove any newly installed hardware, or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your comp, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical Information:

*** STOP: 0x00000051 (0x00000004, 0x00000001,0xE1115CF8, 0x0004D1C0)"

please help with ideas or suggestions
 

imported_Phil

Diamond Member
Feb 10, 2001
9,837
0
0
Have you stopped overclocking yet? If not, you need to do that before installing Windows- installing any version of Windows when overclocked is a risk as you have a chance of corrupting the OS as it is installed.
 

imported_Phil

Diamond Member
Feb 10, 2001
9,837
0
0
Originally posted by: Archman
okay, I reinstalled Windows XP on top of itself

:D

System boots normally now

It's more than likely that a core part of Windows (or even a non-core part :p) was damaged while you were overclocking. This, unfortunately, is the risk you take when overclocking ;)

Glad it's sorted.