Constant Reboot after MUP.SYS
Kevin
(latest one, plus something to do with messenger)XP will not boot. It
will not go into safe mode. If i turn on logging, I get no log.
On my Athlon 1800 I get a brief flash of some blue screen, but it's
too fast to read it. Tried slowing the machine down to a 100mhz bus,
but I still can't read it.
I then swapped the drive to a slower machine. It just hangs at
MUP.SYS.
Ok, so I tried to do an upgrade over my existing install. No dice.
The setup says it will delete my stuff...IOW, it won't do an upgrade,
only a clean install.
Ok, how about a 2nd install. Unfortunately, I've been unable to
figure out what to copy into my old setup to get me running...and in
some cases, it won't let me copy a file.
At that point, I decided to try another upgrade (the first was from
floppies). THis time it lets me upgrade, but only the one that I'm
currently in.
Of course that doesn't help me at all.
OTOH, if I go into the repair CLI, it recognizes both as XP setups.
But I really don't have the expertise to fix it.
Any help is appreciated. I'd also appreciate it if you'd copy me via
email (if only to tell me there's been a response).
Thanks,
Kevin
ABIT K266a MB
Athlon 1800
Hercules TI200
NetGear Ethernet Card
512mb Crucial DDR Memory (one stick)
T.P.
I had the same problem. The screen that flashes is a STOP screen. Basically
your computer wasn't compatible with Windows XP. Some device driver was out
of date or your motherboard is old. There is basically no way to fix it. The
update that you downloaded required a certain device to be ran and if the
device has the wrong driver it won't run resulting in incorrect functioning
of Windows XP.
Let me ask you a question, did your computer ever just restart without any
apparent cause?
I have a whole load of more information, so please contact me @
whirl_...@hotmail.com
--
Please use this advice at your own risk.
I am not responsible for any damage caused
by using this advice.
I hope this information has been of service to you.
If you need any further help, feel free to contact me directly via e-mail
at:
Gazwad
--
Gazwad
Freelance scientist and people tester.
"T.P." <whirl_...@hotmail.com> wrote in message
news:u6DWuHa2BHA.2048@tkmsftngp05...
Mayhem_or_Death
"Kevin" <cra...@yahoo.com> wrote in message
news:c505e817.0204...@posting.google.com...
Kevin
> Why can't you use a system restore point?
If I could actually get into XP, even under Safe mode, there are lots
of things I'd do, including System Restore.
Kevin
Kevin
> I had the same problem. The screen that flashes is a STOP screen. Basically
> your computer wasn't compatible with Windows XP. Some device driver was out
> of date or your motherboard is old. There is basically no way to fix it. The
> update that you downloaded required a certain device to be ran and if the
> device has the wrong driver it won't run resulting in incorrect functioning
> of Windows XP.
Well that's just dumb. This is the first time I've ever had a windows
setup that wouldn't at least go into safe mode.
> Let me ask you a question, did your computer ever just restart without any
> apparent cause?
Um...no not really. I've had Everquest crash, and a few
CTRL-ALT-Deletes later it reboots...though normaly a reset was
required.
> I have a whole load of more information, so please contact me @
> whirl_...@hotmail.com
I'll send you an email. IF I can just recover my settings from the
old install, that'd be a bit better. At least I wouldn't have to
reinstall everything again.
Kevin
Joan Hansen
Do you happen to have a zip drive attached? I read a post where a guy
has the same problem and has to disconnect his zip drive. Maybe one of
your other devices is not acceptable after the update.
Also, the mup.sys Is in the system32\drivers and reads
Description: Multiple UNC Provider Driver Microsofts V5.......
A search on google for mup.sys mostly refers to Windows NT and Novell.
Microsoft only gives information on NT and a small amount on 2000.
Try Dells newsgroup there are some pretty knowledgeable people their.
alt.sys.pc-clone.dell
Joan Here is what I mean All NT maybe you
could just try to rename driver and see if it boots.
MUP Service failed to initialize
DISCUSSION
After installing Maestro and rebooting the machine
an error message is received stating
that one or more services failed to load. In the
event viewer it is stated that the MUP
service failed to load because there is another
instance of the service already running. The
HCLInetd failed to load as well.
RESOLUTION
"MUP" stands for "Multiple UNC(Universal Naming
Convention) Provider." The MUP provider is
contacted by the NFS protocol to register itself as
a UNC provider. When a UNC name is
entered by a user, the MUP calls the network
providers registered with it and finds out
which protocol owns the UNC name. Once ownership of
the UNC name is established, the
i/o request is then redirected to the file system
driver for that network provider (Microsoft
Windows Network, NetWare or Compatible Network or
Hummingbird NFS).
All services under NT run once. Any service can
depend on any other service. The NFS
protocol cannot be started until the MUP provider
is started. As a result the NFS protocol
calls the MUP provider in its startup procedures.
If another network protocol has been
started before the NFS protocol, then the first has
already called the MUP provider and
Windows NT has already started it. Windows NT
attempts to start the MUP provider a
second time and fails because the MUP service is
already runnning. In order to prevent this
problem stop the NFS protocol's request to start
the provider.
ACTION:
Run regedt32 in Windows NT 3.51 or regedit in
Windows NT 4.0. Scroll down through the
following keys:
HKEY_LOCAL_MACHINE
System
CurrentControlSet
Services
HCLNFS
In the data section of the HCLNFS key highlight and
double click on the Multi-String named
Depend on service.
Remove the Mup entry (leave Afd in there).
Close up the registry and reboot.
Kevin wrote:
> Ok this is driving me nuts. After doing a critical update on friday
> (latest one, plus something to do with messenger)XP will not boot. It
> will not go into safe mode. If i turn on logging, I get no log.
> <snip>
Neil Gould
too, including putting in a 3 gig drive and loading xp on it, then
setting my real 40 gig drive as a slave, then running Norton on it.
The solution was sent to me by someone else on this list.
Go to
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307545
and follow the instructions. This proceedure SOLVED the problem with
no loss of anything in about 10 minutes. The registry file is
corrupted. The directions are not the clearest. After Part 1, reboot.
It will work this time, but with a very limited registry file. Ignore
the note about Part 2 being for FAT32. I have NTFS and it did not
matter. The rest went quickly and without any problems.
Good luck, and thanks to 'Jeff' for sending this to me.
Neil
Kevin
> I had the EXACT problem last week and tried most of everything you did
> too, including putting in a 3 gig drive and loading xp on it, then
> setting my real 40 gig drive as a slave, then running Norton on it.
>
> The solution was sent to me by someone else on this list.
> Go to
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307545
Neil thanks!! This was exactly what I needed. Took me a bit more
than 10 minutes, although I probably could have gotten it done even
quicker had I skipped using the repair tool. Since i had a 2nd XP
install, i could have just made all the changes in XP then rebooted to
the old version.
No matter, it worked, and all is well again.
Thanks.
Kevin