Picture the usual day - you're home working on your PC and then out of nowhere up pops an NTFS Sys Blue Screen. Naturally, a wave of dread flows through you having never seen this message before. The error is unfamiliar to you and looks unlike any other error that you've encountered before. You realize that there is no ‘accept' or ‘ok' to return to what you were previously doing. So, naturally you feel annoyed as the any work you've done gets lost.

Before you have time to write down the entire message the system reboots. Something tells you however that you'll be seeing the blue screen again very soon. The next day it happens again and again without warning. You have a pen and pad ready, so you get down the final part of the error code in time. As most people do, you begin searching online for the error message meaning and fix.

And so you start the merry-go-round of looking for and trying out different possible fixes. Don't throw in the towel just yet though as there is probably a fix out there somewhere. If you're fortunate to stumble on the answer straight away, then count yourself lucky. Even with the error message in hand, you will find that it gives little information on exactly how to fix the BSOD.

Most people who have experienced the BSOD would agree that this is really annoying. It's like someone throwing a needle into a bunch of haystacks and then pointing to the haystack that the needle is in. Not exactly what you would hope for when after a solution. And this doesn't take into account that some stop error codes are a lot more difficult to solve than others. For example, an Ati2dvag Blue Screen usually means there's a graphics card or driver issue, but if you experience a mup sys blue screen it's a whole different story.

Mup.sys errors are notoriously difficult to fix, since there are so many causes, including; damaged or corrupted hard drive, badly installed applications, outdated drivers and power failure. To fix mup.sys errors you might have to attempt a number of possible fixes before you find the answer. One of the first things to do is enter the BSOD error code into a search engine and see if there is already a solution online.

First of all you should run some simple checks before attempting fixes that may need a little more expertise. There's a good chance that the problem is only minor. In most instances taking your computer apart or doing a full system reinstallation isn't required. Apply the following fixes before undertaking more difficult ones:

-Roll back changes that you've made recently before the BSOD occurrence.
-Uninstall any recently installed hardware.
-Check the registry for any invalid or corrupt entries with a registry cleaner.
-Make sure you have the newest drivers installed.
-Install the latest Service Pack from Microsoft's website.
-Scan your computer for any nasty viruses or malware.

If the blue screen restarts to quickly, you can change Windows auto-reboot settings. For Windows XP, the settings can be changed by going to the System folder and disabling the ‘automatically restart' ability in the Startup and Recovery menu. Now you will be able to write down the blue screen message without it restarting on you midway.