Page 7 - Mup.sys

The problem has NOTHING TO DO WITH MUP.SYS, but with the driver loaded after mup.sys.
Boot windows with "boot logging enabled", wait half-an-hour, windows will start eventually!
Look in windows\ntbtlog.txt, find your last log, find the problem driver after mup.sys. These are in most cases system specific hardware drivers e.g. cdrom, usb, scsi drivers.
How to solve your specific problem I cannot say, but at least you can find the cause this way.

God luck!

I had a similar problem and here is how i fixed it
booted from cd
then repair install
command console
type fixboot (if thats not the right command type help and find one that is similar)

I had a similar problem and here is how i fixed it
booted from cd
then repair install
command console
type disable MUP
** this didn't work
so I went into the recovery console again
type chkdsk c: /R
** this repaired some files. rebooted in safe mode.
Did a System restore to the last checkpoint
System reboot normally!!!!


Thanks guys.

i have had computers for 22 years and i just got hit by this bug to nite ... and i have been using all kinds of puters and systems ... this is the first time i get a realy nasty bug ...

still trying to fix it...

have new puter with 2 sata and prescott 520 the new ones ..

í just hope it's only one of the problems listed here ...

My winXP box got stuck on windiws logo screen and in safe mode seemed to get stuck at mup.sys or would go into repeating reboot cycle based on the bios setting for apm.
I have a via sata raid-0 disks, athlon64 3400+, via k8t800 chipset, asus mb.
Most promising seemed to be a bios/mb change.
I checked all the bios settings making sure I had ACPI enabled and pnp-os. I reset the NVRAM by setting the jumpers incase the autoESCD had bad values. i also flashed the latest BIOS (making a bootable cdrom and everything) I tried safe modes and optimized modes. Important settings are to have acpi and let the os handle the pnp. All this did not change the problem. Only setting the appm allowed the computer to reboot itself or just hang if it could not turn its power off.

I got the original winXP install CD and sata driver and tried to repair since I really wanted the data on my drives... winXP hung when it tried to logon to the C:/WINDOWS ! I tried this several times but nothing. (so I could not do the disable mup trick or chkdsk)

Since the boot got pretty far, I figure the physical disks were OK. The USB mouse had problems while playing around with BIOS settings, but always worked after resetting NVRAM. So, I got a new hard drive and did a fresh windows install, then installed raid-0 drivers and mounted my old drive. winXP wanted to do chkdsk and started repairing several files including some windows32 file... I was unable to access many files and there was some real filesystem damage that caused my windows boot problems.
A happy ending: I was able to recover all my files with some a file recovery program and letting the disks warm up. I think damage was done when the drives were used while they were really hot. overclockers be careful!
-- kevin
http://hillcountry.homelinux.com

Before I started a course of action on the issue of an XP PRO locking at mup.sys, I spent 45 minutes reading through this forum. There are obviously many sides to this problem. I fixed my problem after assessing the options. I hope this reply helps someone.

The known-knowns: (see bottom line below)
1. I had inserted a USB2 Connect PCI card into the motherboard (AND, stupidly, I plugged in USB flash drive into one of the slots BEFORE the OS loaded the drivers for the card.)
2. Got the issue of the OS lock at the splash screen.
3. Restarted in safe mode, noticed it stopped at mup.sys
4. Took out the USB2 Connect card and restarted.
5. SAME problem
6. After futile attempts to fix - found the forum on google
----
7. Ran NORTON Recovery Disk (did scan on system - was OK)
8. Removed all PCI cards (except Video card and network card) Took out a Adaptec SCSI card for scanner, SoundBlaster audio card and modem card.
9. Turned sys on and worked!
10. Added back PCI cards, except USB2 connect. RESULT: Worked.
11. Added USB2 Card, this time did not hook in the USB Flash drive. RESULT: Worked.
12. DID NOT INSTALL DRIVERS YET for USB2 Connect- for test purposes. NOW, added on USB Flash drive. RESULT: ERROR at the Mup.sys
13. Took out the USB2 Card. RESULT: still errored at mup.sys.
14. Removed all cards as before. RESULT: WORKED.
15. Renamed Mup.sys in the WIN DIR (as some had stated in the forum---for test purposes)
16. Added back all cards, plugged in USB flash drive. RESULT: HUNG at next via**** after where the mup.sys was.
17. Removed cards as before. Got the system working. Added back cards. Did NOT connect USB Flash drive.
18. Loaded USB2 Connect drivers.Tested. RESULT: worked.
19. Plugged in USB Flash drive. Tested. RESULT: worked.

Bottom line for my experience is that if any USB device is added to the card before the drivers of the card are fully installed, it hangs regardless. Doesn't appear that mup.sys had anything to do with it except being a noticable stopping point ---- and a waste of time to deal with mup.sys. The energy, in my case, was all about correct and orderly installation of USB2 PCI card drivers.

did a bit of looking in to mup.sys. It is not just for Novell. According to Microsoft, it is necessary for the starting of the workstation service----which is necessary if you want your computer to get onto a workgroup.

seems my problem persisted after disabling mup. eventually i unplugged all my "extras" as someone else suggested in this thread, and isolated the problem to my dvd and cd-rw drives.

1. wipe system drive...

2. ripp everything out and clear your bios

3. reinsert display card and reboot.(leave bios in default)

4. plug in your system drive reintall windos

5. install all mainboard drivers

6. plug in your other hardware starting with the basic main board things like drives and usb wires.

7. reboot your system and setup your bios.

now you should have your puter working again if not you shouldhave found out what causes the problem.
i lost my PCIe slot for awhile the puter didi notfind my ati card but i could manualforce the dierver in after that it worked fine..

like to take this chance to point you to driverguides latest tool ....
a brilliant hardware identifier and driver thingy....testit and you will like it http://www.driverguide.com you find it here..

happy hunting..

ps: i don't have an USB card but the prob started from and usb mouse plugedto my front panel ..i'm pretty sure it was..

All,

I have just received a Dell GX 280 and found that it was hanging on boot, it appeared to be
mup.sys, shown from a safe boot, this was misleading when in fact the problem was caused by
the GX280 using SATA disk drives, I changed the bios information for the SATA Drive so that it was running
in Combination mode, this is used for older OS's apparently, it all works now!

This was just for information in case anybody else has a problem with the SATA drives.

Regards
Steve

yup my prob had to do with serial ata as well as bad oem main baord from a major pc maker ..Medion... they cut ccost a bit to much ..

I have the same problem, cannot boot, cannot boot in safe mode, cannot boot from boot disk, cannot boot from boot floppy disk set, cannot boot to recovery console, cannot repair windows installation. It just gets hung up at mup.sys, I've tried a barebones boot, everything out except the monitor and keyboard, and the motherboard of course. I've tried waiting with it on overnight, I've tried switching ram sticks around, I've tried booting with another HDD, I've tried running a diagnostic on my hdd with another computer.*breaths*

okay what else have I tried? oh I fooled around with my bios, trying optimal settings and failsafe setting, switching boot modes, display modes, etc etc...

I have been looking on various forums for about two days now, trying whatever I possibly can...I just cant find a solution, and I have some VERY valuable data stored on my HDD, so a reformat is NOT an option...please, for the love of god, help me!

Swap the HD out immediately into another computer and make backups.

If you can't do that download a copy of Knoppix or Bart's PE and make backups.

There's a lot of tips and potential solutions in this thread...it may be long, but its worth reading. There is no magic bullet solution.

good idea, I guess Ill go "borrow" my friends computer for a little longer then...I need a new hdd anyways, instead of this 5 year old one. :/

Just for info, the virus W32.Jeefo may also cause this problem.