tips and tricks
Save Up to $60 Instantly at MusiciansFriend.com
 »  Home  »  Recording Engineers  »  Technical Problems  »  Windows XP Freezes After Loading Mup.sys

Windows XP Freezes After Loading Mup.sys

By  Brandon Drury | Published  09/8/2006 | Technical Problems
Rating:

Mup.sys error in Windows XP

?Well, fall is right around the corner. And just in time is the good old Mup.sys error in Windows XP.


Let me start off by saying that it was 10:30pm. I have 3 songs that need to be mixed in the next week or so. I had no plans of doing any serious mixing. I just wanted to take a few hours and get each song ready to rock. I wanted to render down the DHF Superior drum tracks to .wav files, clean up all my edit, etc so that I could hop right in and begin mixing without any major obstacles.


I fired up Cubase SX 3.0.0 and, of course, it crashed. It seams to do this constantly when a song is near completion. (Needless to say, I'll be rendering down my DHF Superior drum tracks much sooner down the road). Anyway, I decided to go ahead and restart as I typically do. When I restarted, I was faced with a black screen for way too long. I know the BIOS had loaded, but it appeared that Windows was having trouble. I did the usual “restart 4 times” trick. It didn't work. Damn! On to plan B which consisted of the “remove the video card and put it right back in” trick. No good there either.


Next I did the “try every possible option given when tapping F8 during startup” trick. Of course, in trying to load in safe mode, Windows stopped after loading Mup.sys. YES! MY FAVORITE!!! This little problem is one I'm used after dealing with so many home computers, but not one I've faced in a recording machine / DAW. Well good. Me and Mup.sys are like arch nemesis who respect each other. We the other to die, but we'll be saddened for losing a worthy opponent.


Yeah, Anyway! Back to reality. The old Mup.sys thing is a bitch. It's a real pain because it's very hard to tell if it's hardware of software related. So I did the usual PC troubleshooting. I yanked out the Firewire / USB 2.0 card. I yanked out the soundcard. I started to take out one of the RAM chips, but got lazy and decided not to. (It didn't feel like a RAM problem anyway...whatever that means!). Finally, I unhooked all hard drives, but my C: Windows drive.


Of course, while doing this, I did the “restart a zillion times” trick, which never panned out either.

So back to the “click every possible option after tapping F8 during restart” trick. Safe mode and all it's variations still froze at Mup.sys, but I was able to get into Windows with the “Most Recent Settings That Worked” option. I don't think that one has EVER worked for me before. Oh well, it got me in. I decided to run Scandisk or chkdsk or whatever you call it on the C: drive. I did the usual right click on C: in My Computer, selected “tools” and “check this disk for errors”. Of course, it needs Windows to restart.... DAMN! I'm back to the black screen again.


So, I figure I'll launch it from the command line. So, I dig up my Windows XP SP2 disk and boot it (I had to change my boot order in the BIOS by tapping “delete” when starting the computer). After Windows loads a bunch of junk for 5 minutes I launched the “Recovery Console” which is basically just DOS or what I call “DOS”. I typed “chkdisk /p and (I can't remember if it was /r or /f because I just learned this trick tonight. Look it up if you don't know, but I'm sure it's one of those two). Anyway, that took about 30 minutes to run and it didn't spit out any errors. So, I try to restart Windows the normal way. What do know? The same black screen!!


It turns out that “Use The Last Settings That Actually Worked” thing fixes my black screen problem every single time. So I go round and round fighting this PC. As long as I don't select scandisk, the computer boots fine. So, I started plugging back in my hard drives, net cards, etc. Of course, it wanted me to reinstall a bunch of drivers, but for the first time in history, Windows found them all without me needing to dig up driver disks.


So right now my home recording computer is technically functioning, but I'm just a little less confident in it than I usually am...which is not that high to begin with!


So now it's 2:22am. I wasted close to 4 hours and essentially solved nothing and learned nothing. Oh well. That's kind of been the story of my life since I got into this whole recording thing anyway!.

Save Up to $60 Instantly at MusiciansFriend.com
How would you rate the quality of this article?
1 2 3 4 5
Poor Excellent

Verification:
Enter the security code shown below:
img


Add comment
Related Articles
Recording Forum

If you have a question, please post on the Recording Forum.

Comments
  • Comment #1 (Posted by Brad Sith)
    Rating
    Thats why I end up reformating all the time. Sometimes I get lucky and the stupid thing will last 3 months. This time its like 1 month and allready time for a reformat. Oh well.
     
  • Comment #2 (Posted by Argonauta)
    Rating
    I had a similar problem once. Sometimes it fixed misteriously, like in your case, sometimes the computer started working a couple of days after the problem...i disconnected-reconnected every single thing inside, change the ram, the drives, everything, and then i was thinking on buying a new MB an a new procesor when it came to me...the power supply...no more trouble after that. I dont know why, cause i checked the voltages of the old one at the bios, and it was supposed to be allright, but surely that was the problem. No trouble in 2 years after that.
    Good luck.
     
  • Comment #3 (Posted by Philip)
    Rating
    You should try using system restore in start > accessories > system tools. I imagine it will work because your use previous settings worked.

    I don't have much faith in the tool, but it seems this would be a really good thing to try.
     
  • Comment #4 (Posted by Brandon Drury)
    Rating
    If you are geting the dreaded Mup.sys error, there is no system restore. There is no getting into Windows at all. That's the whole problem. It's generally a hardware issue that stops you from accessing the software required to fix it.

    Of course, I disable system restore from all my computers anyway. I've not needed it in the 5 years I've used XP. System restore is a performance hog that I want no part in.
     
  • Comment #5 (Posted by Adam Taylor)
    Rating
    If you had the Windows XP disk, you could have booted up off the CD and loaded the recovery console.

    Then, just do a chkdsk /r and it will check the disk, fix any problems and you should then be able to boot normally.

    Hope this helps someone!!!
     
  • Comment #6 (Posted by Aaron Charron)
    Rating
    Another option is to install the Recovery Console as a startup option. This way you have the option to boot into it whenever you start up your machine.

    To do so just insert your Windows XP Cd and Click Start > Run then type the following (assuming D: is the drive letter assigned to your CDROM):

    d:i386winnt32.exe /cmdcons

    (Note the space between exe and the foreslash).

    If the delay on the boot menu that appears gets too annoying since it defaults to 25 seconds or so then just edit your boot.ini file to reduce that to whatever amount of time you choose.
     
  • Comment #7 (Posted by Aaron Charron)
    Rating
    Sorry, I made a typo in the command line i specified in the last post.

    It should read:

    d:i386winnt32.exe /cmdcons

    I accidentally erased the backslash after the drive letter. Sorry for double posting.
     
  • Comment #8 (Posted by A stressed out Aaron Charron)
    Rating
    It wasn't a typo i guess but for some reason it won't post my backslashes.

    So here goes again

    d:BACKSLASHi386BACKSLASHwinnt32.exe /cmdcons

    I wish now I could just edit my post.

    I also remembered to rate the article this time
     
  • Comment #9 (Posted by techgrl)
    Rating
    TruDat brutha. The old mup.sys has just been on the loose again. I have found that I always have to go the recovery console route just once. Works 30% of the time! I have a workstation that is plagued with mup right now. Damn thing!
     
  • Comment #10 (Posted by Michael)
    Rating
    Dude! Your instructions fixed my mup.sys problem. You are my hero!! Thanks so much for taking the time to write the article!

    Cheers!
     
  • Comment #11 (Posted by Bob)
    Rating
    thanks for your fucking life story i asked how to fix the fucking problem ot your fucking life story
     
  • Comment #12 (Posted by Ken)
    Rating
    I do studio too and if you want to stop nightmaring...simply get a mac! I got a Pc sh** and a mac. Always problems with Windows, re-installing 5 times a year its a nightmare and I don't know why it still alive. And my mac, I install one time, ans never re-install it or have a single probleme, for studio its an easy choice to make buddy ...wake up !!! ;)
     
Submit Comment