XP Constantly Reboots At Splash Screen

My PC Hates Me

Distinguished
Jun 29, 2014
140
8
18,585
XP Home constantly reboots at splash screen. Just started two days ago (machine had been working fine for 6 months).

After the Dell bios splash screen, it takes me into the black screen with white text that says: The computer restarted unexpectedly (or something like that) and gives the options to restart in safe mode, restart from last known good configuration, or restart normally.

If I choose Last Known Good configuration or start windows normally, it goes to the Windows splash screen and reboots, repeating the same thing.

If I choose ANY of the three Safe Mode options, it starts loading drivers and then it stops at Mup.sys driver, pauses, and then reboots.

I have tried disconnecting all peripherals except for the monitor, and it is still the same behavior.

This machine is a dual boot with Puppy Linux, and I can boot inot puppy linux fine (and GRUB seems to work fine).

I CAN go into the BIOS setup by pressing f2 key and make some changes.

This computer is NOT connected to the internet and only has 2 people using it (so VERY unlikely it is a virus). It hasn't been updated in any way in the last six months.

Of course, I forgot to write down all the system details, but it is a Dell P4 running at 2.4 GHz and has 1 Gig of Ram. I bought it used and it never had any problems up until two days ago.

My wife was the last person to use it while it was still working normally. She said that she WASN'T using it at the time it developed a problem, but that she looked over and saw the screen had "a bunch of writing on it" and she just ignored it. (My wife doesn't like reading.)

Thanks in advance.
 

lantrich

Honorable
Dec 20, 2012
438
0
10,960
The main reasons for this Windows XP or Win 2000 boot hang or alleged mup.sys issue are:

Hard disk failure or corruption
A corrupted registry or registry hive
New hardware has been installed but not did not completely "Register or re-Register" correctly
New hardware has been installed but it is faulty or failing
The new hardware's driver or windows itself has been compromised (Disk data corruption or by a virus) or (rare) needs to be updated
The power supply is marginal in output or failing (Common per user feedback)
BIOS\ESCD\Motherboard chipset driver conflict with a component, its driver, or its registry data
Existing hardware including the motherboard may have failed in a specific way but not catastrophically.

In your case as you probably don't have a virus I would say that Windows has a corrupt Registry.
 

My PC Hates Me

Distinguished
Jun 29, 2014
140
8
18,585


If that IS the case, what is the best way to fix a corrupt registry?

(And I forgot to mention that I have not added any hardware in the last six months, either.)