Xp stuck in a reboot loop..Mup.sys..

ExRayTed · 18 Oct 2008 at 13:54

Hey,
Friends pc is stuck in a reboot loop.When booted it will get to the XP loading screen then reboot itself.Last known good config does the same.Safe mode gets to loading Mup.sys then reboots.

Tried fixboot and fixmbr from recovery console,same thing.Short of doing a full system restore,is there anything else I can do?

It's a pile of rubbish compaq bought from a retail store a few years ago.It's also suffered this problem before but a system restore seemed to sort out the problem.I'm tending more towards a hardware problem but wanted to pick your brains before taking things apart.

Thanks.

wolvers · 18 Oct 2008 at 14:37

I'd be thinking hardware fault too. I take it there's no BSOD before it reboots as you haven't mentioned it?

kmufc77 · 18 Oct 2008 at 14:41

i had a very simiar problem and it turned out to be the motherboard which was damaged

Tombo · 18 Oct 2008 at 14:59

Had this problem, was my ram.

ExRayTed · 18 Oct 2008 at 15:16

Forgot to mention,no blue screen just a reboot.Also tried each individual stick of ram,still the same.It's almost as if the PSU isnt up to the job,but voltages in bios are fine.

Dano · 18 Oct 2008 at 15:23

ExRayTed said:
Forgot to mention,no blue screen just a reboot.Also tried each individual stick of ram,still the same.It's almost as if the PSU isnt up to the job,but voltages in bios are fine.

Tried selecting 'disable automatic system restart' or whatever it is in the boot options menu?

--Mike-- · 18 Oct 2008 at 17:46

I've just had this on a pc I was fixing for someone. It turned out to be the hard disk having bad sectors.

ExRayTed · 18 Oct 2008 at 18:58

--Mike-- said:
I've just had this on a pc I was fixing for someone. It turned out to be the hard disk having bad sectors.

I'll take it out and give it a scan in my machine..i'll give anything a go at this point.

SentineL-X · 18 Oct 2008 at 20:04

The most random solution I've had for this was to take out all USB devices and then boot the system.

Strangely enough, that worked!

Greenlizard0 · 18 Oct 2008 at 20:54

It's not a very specific error code (well there is none), which means it's quite hard to fix. I had a while back and the only thing that comes into mind is that it's a driver issue :confused:

pjansell · 18 Oct 2008 at 20:58

Do you have the winxp cd, have you tried repairing from the repair console?

ticktock · 19 Oct 2008 at 03:05

Take Hard drive out, attach it to your pc and do a antivirus / spyware check on it. This happened to a mate of mine and it had loads of spyware and viruses on it. Sorted his out. Worth a try.