MUP.sys

[Jim]

I have a computer with an AMD 2500 processor, XP Pro with SP2. I just
reinstalled the whole operating system after installing two SATA drives.
Everything has worked for three days until now. The problem is that the
computer now stops during the boot sequence. I have tried safe mode and it
stops while or after loading mup.sys. I can boot into safe with command
prompt. I have looked through the Window KB with little info. Google
produced a lot of other incidents with little relief. Does any one know
what the problem is and what I can do short of reformatting and
reinstalling.

Thanks Jim

 

[NobodyMan]

I have a computer with an AMD 2500 processor, XP Pro with SP2. I just
reinstalled the whole operating system after installing two SATA drives.
Everything has worked for three days until now. The problem is that the
computer now stops during the boot sequence. I have tried safe mode and it
stops while or after loading mup.sys. I can boot into safe with command
prompt. I have looked through the Window KB with little info. Google
produced a lot of other incidents with little relief. Does any one know
what the problem is and what I can do short of reformatting and
reinstalling.

Thanks Jim

I can assure you the problem does not reside with MUP.SYS. It is
always the last system file to load; what causes your problem is
occuring immediately after mup.sys loads. Most of the time the
problem is video related.

 

[Jim]

Where do I find what is loading next? I have the machine running and really
do not want to shut it down. Everything seems to be running well as long as
it does not shut down

Thanks

Jim

 

[R. McCarty]

BootVis(ual) is a MS tool for timeline graphic display of boot
driver and process creates. You can also do an XP boot with
logging to capture boot up events in chronological order.
Finally, you could use MSConfig.Exe to selectively remove
Startups & Watchdogs to locate the problem at boot. If you
can boot Safe mode then it's likely a driver or startup that's at
the root of your problem. I would also suggest that you update
your SATA drivers, Chipset and Video to latest releases.

 

[Jim]

Safe mode is just as problematical as normal. Its just safe mode command
prompt that is a little more sure which is why I am pretty sure that the
problem is a corrupted driver or a bad spot on the hard drive. I have just
done chkdsk /p (which came up with a bad spot that it says it repaired )
But I still have the problem. I would have done a boot log if I was
confident that the machine would reboot.

Is there any way to look at the registry to tell?

Thanks Jim

 

[Alex Nichol]

Safe mode is just as problematical as normal. Its just safe mode command
prompt that is a little more sure which is why I am pretty sure that the
problem is a corrupted driver or a bad spot on the hard drive.

It is in the initialisation phase (and Boot Vis will not help much).
And if it happens in Safe mode, it is probably *not* a matter of the
video driver, though it may well be trouble with the video hardware

 

[boss]

mup.sys usually has to do with the USB loading. Do you have anything hooked
up to a USB Port?
If not, just reboot and leave it sit on the "Loading Mup.sys" screen for a
couple minutes. It should time out and continue loading in a few minutes.
Most likely a USB Driver has (or is) failing.

 

[Alex Nichol]

mup.sys usually has to do with the USB loading. Do you have anything hooked
up to a USB Port?

But the point is that mup.sys has loaded. It just happens to be the
last item. The failure is happening *after* that and is not connected

 

[Guest]

This is happening to me also. The only thing I can add is that I installed
AVG anti virus the evening before. I thought KB885443 might be related......

 

[Guest]

Re: Windows XP freezes at mup.sys

I see many problems with "mup.sys". Here's my version. I was upgrading my
wife's system from an ABIT SR7-8X (1800 MHz Prescott) 512 meg ram to an ABIT
BH7 (2400MHz Prescott) 1gig ram. Same drives, CDROM and video card. Of
course, XP Home went crazy with such a massive hardware change. I tried a
repair ending up in this insidious "mup.sys" hang. Also I was not told to
call and re-register the hardware change. Quite odd don’t you think? It
installed or repaired like a new installation. Anyway this “hanging†was
manifested with the XP startup screen and the rolling ball. I reformatted the
drive for a fresh install with the same results. I went back to the SR7
original hardware configuration with the same anomaly occurring only when the
old BTC 24X CDROM was empty (IDE 1 PRI) . I closely watch the POST hardware
discovery screen. Every time the system failed at “mup.sysâ€, the CDROM was
not shown as discovered. I had left ATAPI spinning (disks and CDROM)
periphery on AUTO. When the system failed the CDROM was not ready and not
discovered by the BIOS. When the system came up the CDROM was discovered. I
narrowed it down to a power up kicks the old BTC in faster then a soft boot.
So the system would boot correctly on power up but not on reboot unless the
BTC 24X CDROM was discovered by the BIOS.


THE SOLUTION:

The solution was to go into the main setup (not the OC (Abit System Boards)
screen) screen and change the AUTO to CDROM (some system boards don’t have
that option) for IDE 1 Pri (in my case). Now the BIOS stalls on boot until
the CDROM reports its existents. ATAPI device drivers (40 pin) are not plug
and play. My empirical data suggests that “mup.sys†is not going to let you
add or remove non-plug and play hardware on the fly. I can’t begin to solve
all the other problems with “Mup.sysâ€. But I’ll bet its all got to do with
hardware change or hardware that fails to speak up in the allotted time
during boot.

I know Microsoft has hemmed and hawed about network redirectors etc. on
other versions of their OSs, but I believe that “mup.sys†is a hardware
change watch dog that has something to do with switching hardware around and
not reporting it to Microsoft. I know small hardware changes are acceptable,
but an algorithm kicks in if some major changes are made. This forces you to
call Microsoft for a new hardware ID and answer the question “Are you running
the copy of, in my case, XP Home on one machine?

I'm not saying that this is the panacea for all descriptions of the this
problem but I do believe it is hardware related with respect to change. I
have yet to see the duties supplied by "mup.sys" but I suspent its hardware
change related.

Post Edited On: Mar 13, 2005, 10:19 AM

Wayne Bjorken
www.springdivers.com

 

[Richard Urban]

Usually mup.sys is the last file that was "successfully" loaded. The file
immediately after mup.sys is the one that is hanging the system.

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Peter Foldes]

Prescott + and XP = Problem

http://cquirke.mvps.org/sp2intel.htm#Prescott

 

[Guest]

I can assure you the problem does not reside with MUP.SYS. It is
always the last system file to load; what causes your problem is
occuring immediately after mup.sys loads. Most of the time the
problem is video related.

If you can assure us the problem does not reside in "Mup.sys", then
surely you can tell us what "Mup.sys" does.

Wayne Bjorken
www.springdivers.com

 

[Guest]

Usually mup.sys is the last file that was "successfully" loaded. The file
immediately after mup.sys is the one that is hanging the system.

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Is that your post script. You do know what "empirical data suggests" is?
And yes I've written drivers for UNIX and Windows (VxD). In fact I've been
involved with Microsoft since its inception and UNIX since its inception. This
solution works for me consistently. Perhaps there's more to it then meets
the eye but since Microsoft isn't talking; who knows. So you're the AGPXX
driver is failing? Wish it were true but I've got the same ATI 7000 series as
always.

Wayne
www.springdivers.com

 

[Guest]

Prescott + and XP = Problem

http://cquirke.mvps.org/sp2intel.htm#Prescott

So says that one article. I've got Prescott all over the house and have had no
problems.

Wayne

 

[Richard Urban]

That article also says that it is the file after mup.sys that is failing to
load. If you look at the boot log you will see that mup.sys was successful!
The one after is agp440.sys on my computer.

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[NobodyMan]

If you can assure us the problem does not reside in "Mup.sys", then
surely you can tell us what "Mup.sys" does.

Wayne Bjorken
www.springdivers.com

OK, try this on:

When an application specifies a UNC name (rather than a standard file
name, such as C:\temp\myfile) to one of NT's file system APIs, such as
CreateFile, the I/O Manager passes the UNC name to a device driver
named mup.sys (Multiple UNC Provider—MUP). A resource redirector, such
as rdr.sys, registers with the I/O Manager as being able to locate
resources on remote systems. Mup.sys takes UNC names from the I/O
Manager and hands the names to registered redirectors for examination.
A redirector looks at the names and determines whether it knows how to
access the specified resource. If it does know how, the redirector
notifies mup.sys and the I/O Manager so that the redirector will
receive further I/O requests aimed at the resource. If no redirector
claims a name, the original application receives an error code.

This was found at the following URL:
http://www.windowsitpro.com/Windows/Articles/ArticleID/4907/pg/2/2.html

Is that good enough for you, Mr. Smartass?

 

[Richard Urban]

The bootlog from one of my other systems - up to the file subsequent to
mup.sys. This system had problems a year ago. I turned off the builtin
firewire on the M/B and the problem went away. But, the system was shown as
being stalled at mup.sys. What it doesn't say is that mup.sys was loaded
sucessfully and the file AFTER had a problem. Don't ask me why turning off
firewire solved the problem as the file still loads every boot.

Service Pack 2 3 13 2005 20:38:49.500
Loaded driver \WINDOWS\system32\ntoskrnl.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver ohci1394.sys
Loaded driver \WINDOWS\system32\DRIVERS\1394BUS.SYS
Loaded driver compbatt.sys
Loaded driver \WINDOWS\system32\DRIVERS\BATTC.SYS
Loaded driver pciide.sys
Loaded driver \WINDOWS\system32\DRIVERS\PCIIDEX.SYS
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver dmload.sys
Loaded driver dmio.sys
Loaded driver PartMgr.sys
Loaded driver VolSnap.sys
Loaded driver atapi.sys
Loaded driver ultra.sys
Loaded driver \WINDOWS\system32\DRIVERS\SCSIPORT.SYS
Loaded driver nvatabus.sys
Loaded driver disk.sys
Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
Loaded driver fltMgr.sys
Loaded driver drvmcdb.sys
Loaded driver PQV2i.sys
Loaded driver KSecDD.sys
Loaded driver Defrag32b.sys
Loaded driver Ntfs.sys
Loaded driver NDIS.sys
Loaded driver nv_agp.sys
Loaded driver Mup.sys
Loaded driver \SystemRoot\system32\DRIVERS\nic1394.sys


--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Richard Urban]

Way to go (-:

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Guest]

That article also says that it is the file after mup.sys that is failing to
load. If you look at the boot log you will see that mup.sys was successful!
The one after is agp440.sys on my computer.

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Dear Richard;

Please let's not get so argumentative about this problem. I don't work for
Microsoft and have no definitive answer for this fault. This is only my
version. Perhaps it's not a driver at all. Perhaps it's a mechanism in the
loader that's gone awry. I will stand by my thoughts on change though.

Secondly, the only reason I refer to “Mup.sys†is because of the pervasive
reference to it by the community. Anyway, just because any driver loads
successfully doesn’t prove (i.e. example) that it ( the driver) operates in a
fashion to our liking. I’ve written drivers that have taken three days to
produce to aberrant behavior. Let’s just refer to “Mup.sys†because it’s the
last driver loaded successfully. OK?

Also read my description of the XP OS loading fine but giving me (hardware
ID registration) a pass on a different system board, CPU and memory. I was on
the phone just days before when I upgraded an Abit BH7 with an Abit AI7
getting a new number. Every time I perform a major upgrade I have to make the
phone call to Microsoft. The fact is I don’t know what the problem is. I can
only give you my reproducible experience. Do you remember Andrew Schulman’s
Undocumented Windows, Undocumented DOS, and Unauthorized Windows 95. He wrote
about the behind the scenes facts of his so named OS books. Even today
they’re a good read. He couldn’t find a publisher in the US that would touch
manuscripts.

As far as your postscript is concerned, I agree.

Warm Regards;

Wayne Bjorken
www.springdivers.com