Hello, all... Rick, I guess I wasn't clear on my problem.. This forum originally began (over two years ago!)because of people getting the BSOD, then a constant reboot loop. Then, when trying to boot into safe mode, it was found the last thing loaded is mup.sys. This is exactly the problem I experienced with my friends computer (3 times), which after all this, I feel is related to SP2 updates. I have my friend up and running (again), but this time without SP2. Is there any problem NOT installing SP2 if you have AdAware, AVG and things of that sort? Thanks for everyones input.

Hi Gayle. I was remiss in checking the exact nature of the thread and didn't realise that it started out as BSOD. If that is your friend's problem then I can't help. To clear the problem you must at least be able to get to control panel-add/remove programs. If you CAN get this far (ie- comp works normally but locks at mup.sys ONLY in safe mode) you should be able to replicate both the problem and solution I posted on page 24. It would not surprise me in the least if the BSOD problem originates from the same source. Please read the post on page 24 dated Jun 17, 04:03 am and my subsequent posts carefully. Especially note that svchost.exe should only be allowed access to your 'trusted zone'. SP2 in itself may not pose a threat, but in my opinion the 'security upgrades' most definitely do.

I guess I was forgetful and didn't mention that my comp's "reboot cycle of death" meant that when attemptin to open safemode I stopped on mup.sys. Thankfully this forum helped me to look beyond that as the source of the problem. A new problem has arisen, however, in which explorer.exe keeps shutting down and immediately restarting when I open such things as My Documents, Control Panel, or My Computer. Firefox still works though, as to Word and other such things...this is very wierd and very irritating, but probably for some other post.

Hello, well, I get to join the crowd with this problem.
However, I was successful in fixing the problem.
My system is dual booted so I was able to log into my backup sys. and transfer my files over from Drv C to D drive while I sorted out my problem.

I booted in safe mode and found it ended at this Mup.sys. I had thought I would do a reinstall which searches for previous versions of windows and if you continue on to a fresh install, it searches again, finds it and asks if you want to repair it which works well.

While I was expecting to do that, I thought I'd trie Last Known Good Configuration. It worked. What was changed in the Reg was undone, and I'm good to go.

This may be helpful for some of you.

Hey All,

I too experienced the mup.sys freeze during the boot process. (Yesterday/ Today)
However I was running Win2k. So for some of you, you might start thinking hardware.

This has been a tricky problem because of all the responses that are conflicting
Alot of people claim it to be Software, and some say its hardware. So what is it?
After reading all of this thread it seems it can be either or.

As previously stated by other users, the problem is not mup.sys.
The reason it stops is because of the next task in line.
This task checks all hardware configurations, and tests to see if they are working properly.
Therefore the problem could be the hardware, or the drivers associated with it.
So if the suggestions below dont help, then maybe it will point you in the right direction.

My problem was due to hardware changes/ conflicts.
To be brief, it was caused by my USB HDD that was left plugged in during boot-up.
So if you have any USB device I would advice taking that out and trying that.
(I think if you make sure your computer is updated after that then you should be ok.)

Also if you have made any hardware changes, ex. HDD, CD, DVD, RAM, etc.,
Make sure you have installed them correctly, as far as slave/ master (jumpers or cables)
With RAM - remove and install again - and possibly restart the CMOS
Either by jumper on the mother board, or removing the battery for an hour or so.

Another option is to update your BIOS, or disable/ enable features
specifically in power management if you have an older motherboard
this appears to be a solution for some users on the forum.
If this is the case there are plenty of replies on here for this topic of solution.

For those of you with XP2, and you know it isnt hardware
If you install all updates after installation it should be fine.
However, its probably too late for you to do that now.
Again, there are 25 pages of replies to this problem specifically for XP2.
So look around for more detailed solutions.

Most people have suggested reinstalling Windows XP
or
Reparing Windows XP

You need your XP disc in order to do this
The suggested method is to Select Install Instead of Repair
Once you have done this, Windows will detect your current OS
It will then ask you if you would like to repair the current OS
Select yes for this option, and try this before completely reinstalling.
Since it may just happen again if you reinstall.

Hopefully this will help at least 90% of you out there.
If you dont understand one of the steps, then you should google instructions first.
Make sure you are doing the process right so you dont cause more problems.
Other replies will be more in detail than mine so read some others if necissary.

I hope this helps everyone out!

Micah Chasteen

I suppose I am joining the club here. My problem seems to be a little different than the ones here yet very similar as well.

Essentially, I can't even get to the reinstall/repair/recovery screen from the windows CD. Here's my story...

I just purchased a new hard drive (WD 160GB EIDE). I planned to install Win XP on it, copy everything from my existing HD on to the new one, then wipe out the old one and use it as a slave drive.

I was able to install Win on the new drive and navigate around in my newly installed OS. I could see my old hard drive and copy my files over that I wanted to keep. I installed Win XP with the old drive connected, so it gave my new drive the designation "e:". I was going to make an effort to give the new drive the "c:" designation. when I rebooted, the new drive froze at the WinXP splash screen.

If I try to boot from the CD, it loads the files, then gets stuck on "Windows is starting up". I never get to a screen asking to repair, reinstall, or recover. I ran the WD Data Lifeguard tools software which let me (I think) wipe the drive clean. I thought this would let me do a fresh install of WinXP, but again the CD never gives me the option to install. It always tries to start up windows on its own. I've tried this with the old drive connected and disconnected.

I can still boot to Windows using my old drive. I cannot, however, use my old drive as the master, the new drive as the slave, and boot up. It will freeze at the splash screen.

I did just install the updated BIOS for my motherboard (Asus P4PE), but this did not solve the problem.

Any ideas....short of throwing this new HD out the window?

Thanks,
Mark

Hi Rick,

It's great to see that you have added yet another potential fix for this topic. Your solution is by far only one solution of many, each one capable of fixing a specific instance of this problem. The real issue is that XP does not provide enough information to determine the actual cause that anyone machine is experiencing. The failure to get any further than MUP.SYS is because the OS has failed to load after that driver. Their are too many reaons to document why a system fails after MUP.SYS.

I, like Jim, are one of the original contributors to this thread and I check back from time to time to see how it's progressing. I myselft have experienced this problem with two different machines and both had completely different issues. One was a faulty SATA cable causing a bad read of data. The other, more annoying issue was caused by the BIOS data in the registry getting out of sync with the actual BIOS due to having to hard boot after a locked up application. The latter was a monster pain because it ended up with having to RMA the motherboard to have them fix the BIOS.

I'm a software/hardware consultant and certainly have access to legal copies of XP. No doubt if you're running a cracked copy of XP then I'd expect no end of issues after patching the security updates. However, this is not the only cause. After MUP.SYS is loaded the OS loads a host of thrid party driver any of which can cause a failure.

So this thread is ultimately dedicated to all those users who have issues that apparently look the same but in reality may have reasons that are all over the map. This is probably why this thread just keeps on going because there is no silver bullet fix.

What is really needed is for XP to log more specific information after MUP.SYS so once and for all everyone could identify the area of their problem.

Best regards all.

Pete.

Hi
I have to tell you that I am one of the mup.sys victims. But I resolved my problem. Actually I did read the solution from this thread.
My situation was that my mobo died. At the same time my two ram modules died too. So I bought a new mobo and tried to install slipstreamed XP Home SP2, but everytime boot crashed to that mup.sys. Of course it crashed when I tried to log in safe mode. When I tried boot normally, my computer just rebooted until I switched the power off.
But my problem was that I tried to use wrong SATA-driver with my mobo. I was thinking that my old NF4 chipset driver will work. I had Asus AN8E and I replaced it with MSI K8 Diamond the both are NF4.
So, I went to basics and installed XP Home from the original CD and loaded correct sata drivers when the install program ask you to do so (Press F6 if you...)
Now my computer is up and running and no problems at all. I Updated to SP2 and updated the rest of the updates from automatic update.
I hope my experiences helps some of you ppl.

regards
koneworks

hi,

i had the same problem - windows XP pro froze at loading mup.sys
could not get into safe mode, or even safe mode command prompt.

at first i thought it was because i had resized the windows partition in linux. (i had made the windows partition like 2 gigs smaller in puppy linux, thus giving me 2 gigs to save puppy linux data to)

but the problem was this:
i had disabled my secondary IDE slave in bios, but left it plugged in right before i made the partition changes.
i turned off the computer, unplugged the drive*, turned the computer back on and XP pro booted right up with no problem.

*the drive is a dvd-rom drive. i accidentally knocked the tray off track when it was open, then pushed it shut manually. now it won't open at all.
so i had just disabled it in bios so windows would stop trying to access it.
i didn't feel like opening the case and unplugging it, b/c i didn't think there would be a problem.
HA! a google search lead me to this thread, and i've spent three hours trying to get windows to boot from hdd, instal cd and floppy so i could replace MUP.sys - all to no avail.
well, i got tired of the motor and gear grinding noise from that dvd drive, so i unplugged it - not even thinking it was the root of the problem.
but somehow, it was. lol

n-e-way, XP Pro boots up just fine now - with my partitions intact the way I wanted them.

I fixed this problem simply removing all usb-devices and resetting bios, that worked for me, hope it works for you too. I think my mup.sys error was because that workstation is connected to ups and that ups failed, so mup.sys propably broke there (mup.sys can break in system errors etc.)

-- Niilo Himberg

As the newest member of the agp440...mup therapy group I want to thank the 2+ YEARS of info here.

My testimony..
My son is a gamer. I upgrade his computer often. We both have Dell , but different models. I changed vid cards on his from FX5200 to ATI9800PRO..easy as usual. He is 2.6G/ 1M ram, XP SP2..

I ugrade daughters older DELL..again easy as usual..

I am happy killing on COD with my old 5200. (Dell 8300 3.0 512 XP2)..but son is bugging me to play F.E.A.R. It's a REAL HOG....

Won't run on the 5200..sooo..easy fix..buy a 9800. Install..hmmm..no RED..after the usual..ATI CATALYST download..uninstall several times..put 5200 back in..still no reds.. ( I know this is not Apgp440..but will be..!)

It's late..2 AM..
So two days ago I think..maybe bad AGP or monitor cable... Examinig the cable I see a pin is bent. Get another monitor..I got all colors.
I put in Radeon fine..but I need to put back in the drivers..as I do that..computer locks..hmmm..
I cold reboot. Safe mode..no good..

Welp..this is why I found you all.
I can here the Windows sounds..but BSOD..(some backilght)..so mine loads..but no video. Go to safe mode..hangs no load.
Put in XP disk..as usually here..Restore..last working..then console..do the agp440. I disable..locks at mup.sys..

I spent till early morning on several google found sites this morning..this was absolutely the best. I killed most of my day at work (not computers as you may tell)..reading everything I can.

I was contemplating a new MB as I thought perhaps a dead AGP slot..now I see the huge problems with the loader.

Before I did the update driver..I checked properties. Device had conflicts in several places. I thought..just reload drivers and all set. I think the device conflicts caused my original lock that interrupted the driver update.

I did the 1 AM Skinner box repair..hitting the start button..numerous times..so I have even more messed the base. However I still can hear the windows desktop sounds..just not see anything.

Tonight I'll start all the work arounds..(doesn't seem to be a real repair) and perhaps I can go happily back to killing on my beloved COD UO...

I am not confident..but due to all the pages here..read every post..I am a much wiser..yet unhappy man..
I found several others along my google path with similar disaster..sent them here..

I have had this box for 2 years or so..several upgrade video cards. Every USB slot filled..Scanner..dig camera..Ipod..Mini Disk..USB joystick. Always such and easy task..

HOWEVER..flash new BIOS 10 day prior. New drivers for ATI..then removed then Nvidia drivers..then removed..then ATI..!!

So I got a mes to deal with..from what I read even a total wipe and re-install may not work..so..

I'm going in....

Ok I've battled this for awhile now.
I happen to have 6 fresh brand new laptop drives.

Multiple laptops in the house have let me try a few things.
First I can't do a fresh install on the laptop that freezes during boot.
So I had tried disabling files, copying files and such.
Next I loaded xp on several drives on a good computer.
2 with xp and 2 with xp2. Now putting them in other laptops
they all booted fine. But when i put each of them in the bad laptop
same problem with each of them. Ive installed 2 different versions
of linux on drives and one won't boot and then once watching
the suse 10 linux boot I found a issue where the bios was not liking
the mouse setting. So I moved the mouse setting to both internal and external.
That booted fine. So then I tried the xp disks that did not work.
Put suse in and that worked fine still.
So then I removed all cards, cd rom, and tried that with xp disks nothing!
If the files on the xp drives were corrupt they wouldn't boot on other laptops.
My guess its hardware or bios issues. As I have installed the latest update
for my bios Im not sure that would be it. For some reason the install of
suse linux works. Thats fine with me though as Im pretty fed up with windows
anyway and Im used to working with linux anyway.

Kevin, I don't know enough about your setups to be much help, but I will point this out: Unless your computers are essentially identical (same CPU, same motherboard, etc.), you can't install WinXP on one machine then swap the drive into a second machine and expect it to boot. Older versions of Windows could do that; WinXP won't.

That doesn't explain why you can't do a clean install on a blank hard drive, which was (I think) your original problem, of course...

I actually was just letting it boot not start and run. But Ive swithced xp from a gateway to a hp laptop many times with no issue. XP when swithing it from one computer to another will adjust by installing new drivers and settings. Sometimes a new activation is needed. Ive even used an adapter to run the laptop drives in a desktop and install windows on and then put back in the machine.

I think its just time for a new laptop. I have a brand new gaming system to trade Ill just have to find a friend wanting it.

Kevin said, "XP when swithing it from one computer to another will adjust by installing new drivers and settings."

If you had said "Win95" or "Win98" instead of XP, I'd have agreed with you. However, for XP, this is not a true statement in general. Unless the hardware used by the two machines is similar enough to use the drivers already present in the installed version of XP, the OS will fail to boot. Your laptops must have been similar enough that XP could "survive" the swap.

This is a well-known behavior of XP (see this Microsoft site for info: http://tinyurl.com/j9u7 ).

I only point this out because some folks posting to this thread have tried to troubleshoot their rigs by swapping HDDs between two machines, and that often introduces yet another probelm into the mix.

Jim

In the "tinyurl" mentioned in the previous post, I notice that MS assumes that you have a Windows CD. What can those MANY of us do who have only a restart CD set (an image of the hard drive as originally provided) but NO actual Windows CD? We have a legal copy of Windows, but no direct access to it. I had this problem when facing the MUP.sys problem last year (finally had to simply reformat and start over).

PeteJ

Peter, I think that's one of the ways that PC manufacturers keep the cost down. MS will sell an OEM a "full" version of the OS, where the OEM can include a "full" Windows install disc with the system, for one price. Or, for a discounted price, MS will license an OEM to pre-install Windows and only supply a CD-ROM with the image of the hard drive as it was shipped, with Windows pre-installed. That's why all inexpensive PCs (and even some "premium" brands) only come with a HD image disc--it's a key way of keeping the cost down.

An end user who buys the latter machine is licensed to use Windows the way it was pre-installed. But in return for the lower up-front price, they give up the ability to re-install Windows without reformatting and starting over from the "factory fresh" config.

It's not necessarily an unfair trade. "You get what you pay for", pretty much. What I think is unfortunate is that most users don't understand they're making that tradeoff when they buy a discount machine, nor do they typically have an easy way to upgrade to a full version of Windows at the time of purchase. If it turns out they want to reinstall Windows down the road without reformatting, they have to go buy a full version separately.

Caveat emptor, I suppose...

Jim,
I understand the economic angle to the mfr, BUT, it is hard to say "caveat emptor" when one does not know of what to be aware! How many less expensive systems state on the box that no Windows CD is provided? They proclaim that the system comes with Windows XP (or whatever) and some will even tell you that it was pre-installed, but I have never seen one that says "only restore disks provided" on the outside of the package.

Next question, how much "restoration" can be done with a borrowed full Windows install CD before it asks for the 25-digit serial number of that borrowed version? I assume (but don't know) that one could not use the original serial number. Again I emphasize that I own a legitimate version of Windows XP, and am NOT trying to install it on a second machine. Have you or others carried out this experiment?

Thanks,
Pete

There are multiple flavors of WinXP: Everyone knows there's WinXP Home and WinXP Pro, but there are OEM, Upgrade, and Full Retail versions of each, also. Serial numbers are not compatible across all flavors of XP (i.e., a Full Retail WinXP Home CD-ROM will not allow you to enter an OEM serial number during install).

I once tried to use WinXP Home OEM and Full Retail disks to do a "Repair Install" of WinXP on an eMachines PC that didn't come with its own Windows disk. I'm a fairly savvy user, and I was unable to ever even get the option to do a repair install, much less get far enough along for it to ask for a serial number.

I eventually wiped the hard drive and reinstalled Windows from my OEM disk (rather than the restore disks), using the WinXP serial number from the tag on the PC case. That worked (though I don't know that was something the license actually allowed me to do--I've never seen the WinXP license for that eMachines PC!).

Jim

Wow, this thread has been going for all most two years.......

Sorry, but I didn't feel like reading down through the entire thread so pardon me if this is a repeat;

I believe that my mup.sys file is corrupted but when I run System Recovery, it says no hard drive is detected and I think this is because my hard drive is SATA 150 (well actually I know it is, but I mean I think this is why its not being detected by the System Recovery console on the WinXP CD). Do I have to press F3 and load "third party SCSI and RAID" drivers or something? Will this allow the System Recovery console to see my SATA C:\ drive and allow me to replace the corrupted Mup.sys file?

Thanks in advance!

-Luke