Mup.sys, Cannot boot to xp... Options

[Guest_Troy M (xenogrug21@hotmail.com)_*]

Ok, to all of you who have had this problem.. I have read about 5 different forum sites, relating to this problem.. and there is NO CLEAR fix for the problem.. as of yet.

Basically.. i have read it to do with USB drivers.. Master Boot Records of HD's..., BIOS.. old motherboard rivers.. and SP2.. but, from my experience.. I honestly think it can be a combination of many things.. not just the one issue..

Or.. has anyone been thinking power supply? Maybe the power supply isn't providing the adequate power requirments of the MB.. and therefore is failing when it goes to try to Boot.

Or maybe it's the MBR of the hd, like others said.. casuing my pc to black screen, before loading XP.

Many people have remarked that thier pc will reset itself... Well, mine in question will not restart. It just goes to black screen when i try to boot normally, and if i try safemode, the ol MUP.SYS file is the last one shown....

(For those of you who don't know.. this problem apparently has nothing really to do with MUP.SYS. It is the last file loaded, before the kernel will allocate resources to the OS..(XP/2000) MUP.SYS is a driver file for USB devices i believe)

....then, when i try to boot off the CD..., to load the recovery console.. i can't!!! because the windows XP SP2 cd i have, won't go past "setup is starting windows", and i never actually see an installation option.. (R for repair, Automated recoevery console, etc) and it just hangs there... untill i restart the puter. Has anyone tried swapping back to a SP1 cd, and booting off that? does it make a difference? I even tried a Win2000 Pro cd, and ssame problem.

So, in conclusion... i have swapped out all hardware, other than the power supply, the CPU and that is it.. I believe that when it stopps at Mup.sys.. that is just windows way of saying some hardware is kapuut. It's then a combination of the software and the hardware.. (Software initializing instructions.. and the hardware not able to perform them) This then causing the freeze when trying to get to re-install options.

Many people also talk about when they get new hardware.. well.. i pose the question.. Did you get a new case too? Maybe it's the actuall power switch.. that somehow might have something to do with it.. As any tech would know.. it's not always the most difficult thing that is the problem. And sometimes never just the one thing.

Just a thought to add to this overwhelmingly puzzling issue.

Troy M
IT Tech Support.

[Guest_KennV_*]

I don't know if anyone has solved this issue yet but I'm working on the same problem. I will work through the posts and suggestions here and let you know how it turns out.

What I can tell you though is that it is probably not a hardware problem as I can boot into Linux without issue.

Kenn

[Guest_KennV_*]

From the Repair console I did a CHKDSK and now my problems are solved.

Kenn

[Guest_cshockey_*]

I have a fix for the problem:

IF:
1) Locking up at MUP.sys in both normal boot and any safe mode boot.
2) Any attempt to read from the disk locks up the application that is attempting to read/modify etc.

Problem:
Corrupt sectors on the disk.

Solution:
1) Take the harddrive and add it to another bootable WinXP image.
2) Chkdisk should automatically run on the corrupted disk.
3) Chkdisk will delete and replace corrupted files and mark the sectors as bad.
4) Add the disk back to the original system.
5) Boot twice (The first time you boot it may give you some form of "No OS exists on this disk, the Bios will update the drive information after the first boot).

Your good to go.

I'm from Microsoft and I appologize for any inconvience this may have caused. Though ultimately this could be attributed to the disk, hopefully the robustness of the chkdisk process is some sort of consolation. Also I appologize for having to have another computer, personally I just got a big IDE cable and ran it to the orignal computers drive (as to not be forced to remove it).

Thanks again.
Chris.

[Guest_blake_*]

I am just curious to how many of you own AMD processors paired with either VIA or ECS boards.  On top of that how many of you have SATA/RAID drives?  A machine I built about 3 weeks ago for a friend mysteriously died the other day.  It *supposedly* freezes at MUP.sys  However upon further investigation that is not the case.  SATA drives are fast....too fast for windows.  As people shut them down PROPERLY windows is still trying to write the PageFile and flush it out, well it just takes one shutdown in the middle of flushing out the registry for it to ruin the registry and not allow system files to boot. 

The only fix is to update your RAID/SATA drivers as well as flash your MB with an update. 

Particularly this affects VIA KT600 with the NorthBridge/Southbridge chipsets.

[Guest_blake_*]

Wow!!! So far I've seen everything on this MUP problem. Unfortunately, Chris, I tried what you suggested before you suggested it to no avail...other system, chkdsk, + defrag. Yes...corruption found, but here's what else I tried/discovered.

Replaced memory (you'll soon be able to tell I have access to MUCH hardware)
Replaced AGP video card w/ ATI
Default bios settings
Manipulated bios setting w/ no power management turned on
Removed PCI modem
Tried to boot from a different KNOWN GOOD XP drive...same problem
Formatted said drive KNOWN GOOD (Maxtor) and began installing OS...and here's the kicker:

Got a CRC error reading the OS files from the CD (known good CD)...install failed!

This sytem's 4 months old...unfortunately one of those buddie's system who thought he could build it himself & save...could we be looking at bad writes all initiated by a bad CD drive?

I'm going to try a few more things w/in the bios...haven't flashed it yet.

This wil be one for the books!

Blake

PS IDE drive w/Intel processor...rules out AMD & SATA

[amir]

ha ha ha it's my turn restarted my PC, I got a BSOD right before the XP logo, after mup.sys, complaining about unknown hardware problems (as BSODs usually do!)

Turned it off, checked cables & slots. Turned on, same again ... choosed Last good config from start up menu & it's ok now.

These must be caused by registry bad entries since i found out that whenever i install a Windows Service which is made by myself in dotNet & hence has some bugs (), this happens on next boot. Sth really different from other's!

Didn't read all posts but it seems like that these are all irrelative to the file mup.sys. They are different problems showing up just after mup.sys is loaded which is the last file in the sequence.

[indo]

AMD +2600, Asus A7N8X-X (VIA 400), NVidia Geforce MX 420, with some Cheap High Latency Ram.

I was having similar problems. I have a machine that is Win2k SP4. Everything was working fine for a while. I upgraded to DirectX 9, then rebooted. I kept getting the blue screen "failed to initialize graphics driver."

I tried every solution I found including learning a great deal about the recovery console, which in my opinion is worthless junk.

All of my drivers are up to date, motherboard, graphics card, etc. I tried all the different safe modes of course. They all led me to the same annoying blue screen. (I was having Win98 flashbacks, seriously.)

1. Ran the auto-recover option from the setup CD. Replaced many system files with original from the CD. Didn't work. (Ended up screwing all my programs up though.)
2. Tried Emergency Boot CD (http://www.ebcd.pcministry.com/) to get the pictures off my disc before I formatted and reinstalled. EBCD wouldn't read my NTFS partition! So I decided to do what was necassary to boot my machine.
3. Started stripping my other PCs and switching out components. Graphics Card first, then the RAM. Nothing worked.
4. Reluctantly spent an hour learning the in's and out's of the Recovery Console. I started disabling services that I thought may have caused the graphic driver error. Nothing...
5. Came to this forum, read the suggestion about the Boot Virus Detection and mup.sys. So I disabled the Boot Virus Detection in the BIOS, restarted and got the blue screen again. I then went to the recovery console and disabled mup.sys which was listed as BOOT. Restarted, and presto... straight to Windows.

I am now reinstalling Win2k and all my programs. I still have no clue what caused this problem. If it involved DirectX, why did disabling mup.sys finally allow me to boot? Was it because of the Boot Virus Detection on my MB, and maybe Windows needed to boot up first and do some hocus pocus to the MBR? What the hell Microsoft, I hate you.

So if you are having a similar problem, I would suggest trying to disable the Boot Virus Detection and reboot a few times. If that doesn't work, go into the recovery console (or perhaps Safe Mode if you are lucky) and disable mup.sys before you start tearing the OS apart.

BTW - What the hell is mup.sys anyway? I couldn't find any reliable information on the file. Hope this helps some how.

This post has been edited by indo: Jul 22 2005, 07:45 AM

[usr.c]

According to the Microsoft KB, it's the Multiple UNC Provider, which creates transparencies between different types of file servers in order for file paths with different naming conventions (e.g. //abc/abc) to be accessed.

[amir]

I bet restoring the registry (by whatever means possible) is the solution. I don't remember how we do it in win2k. Tapping F8 at startup brings the startup menu up. If there is a "last good config" thing, then choose that.

Does win2k have ScanReg.exe? If so that's another option. I got Alzheimer

[NanoRuler]

However upon further investigation that is not the case.  SATA drives are fast....too fast for windows. 

Blake, I don't want to sound disrespectfull, but what a load of crock!

My network servers run 15 000 rpm SCSI drives that'll make ANY SATA drive look slow by comparison (they can push out 320 MB per second - what can yer SATA do?) and Windows still ends up waiting for them.

The "problem" as you described it refers to hardware and has diddly-squat to do with the OS!

[suprchgtnt]

hey kids mup.sys is used for shared folders/driver
rename to mupisbad.sys kidding you can name the files mupwhatever.sys
reboot your system
go into the repair console and replace mupisbad.sys with mup.sys you can find it in SP4

[seaharrior]

I have been experiencing same problem for months now. The only workaround I found so far was using XP 64. It works fine and no problem at all. Every time I try to load XP, I get the balank screen. I tried ALL Drives.. SATA.. IDE.. SCSI Card SCSI disks...the fresh install works fine some times till I reboot. However, one thing I stress is for me, this problem started after I upgraded my processors from Opteron 250 to Opteron 275. So I thought IWill didn't have good support for this processor and was causing, eventhough I updated to their latest BIOS that clearly says supports 275. Below is my post from AMD fourms website. See if someone can help me, which I doubt would be successfull.

I have never seen this. My Dual Core Opteron 275 was working fine for few days. After I rebooted by computer, it won't load windows XP and I have a green light on monitor but nohting on the screen. After 15 minutes I recycled the power, it said"XP did not load normally, do you want to start Safe mode". I wanted to start in safe mode, then same thing once the OS Menu goes, does not load windows. I ran Setup thinking something wrong, and choose the option to Repair the installation after it detected the System FIles folder, it copied the installation files and when it came time to reboot to start Windows XP installation from windows mode. IT got stuck on the black screen again. No windows installation. I thought there might be problem with the systems files. So I started a Fresh install and even formatted the HDD, it formatted fine and copied files then when it came to load windows or run the windows part of setup it would stay in black screen. Here's all i tried:

Things tried so far to fix the system boot problem:
-Tried to reinstall operating system by formatting HDD
-Replaced Video Card with MSI 8x Graphics card
-Replaced HDD with ATA HDD and tried to install OS, but does not go past DOS installation screen. Also, tried installing SCSI card and SCSI disks.
-Replaced Memory with other Memory tried 1 Memory chip, and 2 diferent chips
- Reset BIOS from Jumper
- Removed the PCI NIC and removed changed Keyboard/Mouse/monitor/CD Drive
- Tried to install Windows 2003, still does not go past the dos screen.
- One Amazing thing is, When I had this problem on IDE drive. I removed the drive and hooked up to a different system as Primary drive and was able to boot to XP on that system. When I brought back to this system, same problem.

SO I tried to install XP - didn't work, so to make sure it is not the CD, i tried to install 2003 same problem.

My computer specs are:

Motherboard: IWill DK8N
Bios: lates V11
CPU: Dual Core Opteron 275 (single processor)
Mem: CorSair 2 GB CAS 2.0 2-3-2-6 3200
Video: ATI AIW x800 Pro (tried other card too from MSI)
All PCI Slots Empty.

The above configuration was working fine for few days, when I rebooted the problem started.

Your Help would be highly appreciated and Thanks in advance!

[amir]

Can u try installing a copy of XP with built in SP2?

[Hughesy]

Hello all,

I have suffered with this problem like many of you have. In my case i am fortunate enough to have a copy of the original Windows XP disc, i.e. not even SP1. In order to fix this problem i took a roundabout way of doing it after trying many of the suggestions i have seen here and other sites.

I installed a second copy of XP onto the HDD, in a folder called WINDOWS2

Once i had done this, i was able to boot from the new copy and access all my files. In my case, i was really only interested in data recovery so i managed to burn all of the data i needed to CD, which took a while!

Upon completing this, i downloaded a piece of software called KillDisk (free version) and used this to completely wipe the HDD since the Windows reformat was not working.

I know this is a kind of long way of doing it but for those in a similar situation to me, i.e. no 2nd HDD to connect up and collect data and only being interested in data recovery, it works.

I have sympathy for anyone who has come across this problem, because it's a pain in the ass!

Ant