re: Mup.sys? Hangs but not? Wha's happening?
Wednesday, August 18, 2004 at 4:14 pm
Windows XP Annoyances Discussion Forum
Posted by Mike
(1 messages posted)
Happy to say I fixed mine with the help of everyone who wrote on this thread. It
seems to me that the MUP file comes in conflict with many different types of problems
since there is one problem and many solutions. For me is was swapping out my harddrive
into another system and letting it do a chkdsk on the good system discover a couple
of bad segments. Then I copied MUP.sys on to the bad drive from the good drive and
it works. This is another testiment to the switching of harddrives solution. Good
Luck and Patience to you.
On Sunday, August 15, 2004 at 9:28 am, Kelly wrote:
>I am posting to second Mr. Browns' assertion that this is NOT an AMD problem. This
>is definitely a Windows problem and I think it is related to activation as moses
>explains in his awesome troubleshooting post. Like many of you, I have looked desperately
>for a solution but will end up wiping the hard drive for a clean install. I ran
into
>the situation doing an on-site job networking two computers. Simple, right? Due
to
>this thing we call "Mup.sys" (viaagp.sys and ntfs.sys were also implicated at different
>points!) I never got that far. Before I bought the hardware I went to look at the
>computers in question. The main computer is a Pentium 4, 2.40 Ghz with 256 MB of
>RAM running Windows XP Home edition, built by a reputable local company. I suggested
>that when I buy the hardware, I also get some additional memory as his Pentium 4
>is shackled with only 256MB. Agreed. When I purchased the memory I matched everything
>except the manufacturer. I popped the card in and immediately got a message that
>it didn't have a necessary driver. A driver?? I tried again and got the black screen
>offering safe mode. I selected Start Windows normally. No go. So I took out the
new
>RAM and tried again. This time I did select safe mode and got hung up on Mup.sys.
>The adventure began, from there I got the hideous constant boot-cycle described
by
>so many. ***
>
>I am posting because I did eventually have success accessing the drive by installing
>a second copy of Windows XP under the directory \WINDOWS2\. On boot up I had the
>opportunity to select which copy to use, the newer version was the top listing.
I
>opened in to the empty shell of XP but all of the files are on the drive, and accessible
>from My Computer. Of course, I could not actually run any of the programs, but
the
>reinstall into the "new" windows allowed access to the data from the previous version
>and, most importantly, let me copy the files there. I am waiting now to meet up
with
>the computer owner on Monday to be sure I got everything before doing a fresh install.
>I had been swapping components as recommended by many when I installed the second
>version of Windows using the boot disk. Curiously, at the time the only memory card
>in the computer was the new 512 MB. So given that everything works fine when I use
>the newest copy of XP, I DO NOT have a hardware problem - not even with the new
card.
>Before installing the second version, through the Recovery console I tried disabling
>mup.sys, disk check - which did find and fix 1 error, DFC Client on/off, renaming
>files and replacing them with good files from the disk, specifically \system32\config\system,
>\software, \sam, \security and \default. I did try to copy files from the XP disk
>into the version that doesn't work to re-boot in Internet explorer as moses suggested
>in his post but I found that any attempt to reinstall installs over the working
version
>of windows, not the corrupt one. This computer initially had a modem card but no
>others - I ultimately took that out as it is unnecessary - one hard drive, one floppy
>and one cd-rom. Pretty bare bones. No usb hardware attached. I tried as many combinations
>in the BIOS as I could paying particular attention to the USB drivers, ACPI Aware
>O/S, caching and shadowing and SDRAM timing. Resetting or forced update of ESCD
wasn't
>an option. I wasn't able to find information on the power supply but less than
a
>third of the cables coming out of it are being used. While I know this doesn't eliminate
>the power problem many have suggested, it makes it pretty unlikely. I submit that
>Microsoft, in their attempts to prevent piracy, included a cynide capsule for the
>operating system to "byte" when it detected certain parameters such as a different
>hardware setup. If Microsoft didn't deliberately create the problem then why won't
>they address it? There are thousands of anguished posts on the Internet and not
a
>peep on the Microsoft website. Hmmm. Byte this...it's time to learn Linux.
>
>
>
>
|
All messages in this thread [show all]
 |  | |  | re: Mup.sys? Hangs but not? Wha's happening? (Mike: Wed, Aug 18, 2004, 4:14 pm) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
