It’s a regular evening, you’re at your computer doing whatever you do and then suddenly appears an ntfs sys blue screen message. Naturally, a wave of dread flows through you having never seen this message before. You notice that this isn’t like other error messages that you usually experience. The opportunity to acknowledge the error and go back to whatever you were doing doesn’t exist. So, naturally you feel annoyed as the any work you’ve done gets lost.

As you get pen and paper and begin to jot the error message, the PC restarts automatically. From that moment, you anxiously anticipate another blue screen error occurrence. 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. It doesn’t necessarily mean you won’t find a fix, most people do, eventually. If you’re fortunate to stumble on the answer straight away, then count yourself lucky. Of course the stop message itself does provide a clue as to what could be wrong usually, but it doesn’t tell you the exact fix.

Most people who have experienced the BSOD would agree that this is really annoying. It’s like getting a replacement for a broken down photocopier but given a manual in a different language. Not exactly what you would hope for when after a solution. Furthermore, this doesn’t really address the fact that many error messages have a variety of causes and fixes. The difference between getting an Ati2dvag Blue Screen and a mup sys blue screen is a lot more problems.

A number of issues cause an Mup.sys blue screen, including hardware faults, applications that have been poorly removed, faulty BIOS settings and corrupt device drivers. For this error you may have to try various things to find the solution. The best thing to do when you get a blue screen is to take down the message and do an online search of the issue or better still, contact someone who knows about computers.

Before you start making any major changes to your computer, make sure you try some basic fixes first to rule out the obvious problems. There’s a good chance that the problem is only minor. It’s unlikely that you’ll have to do anything drastic such as reinstalling Windows or replacing hardware. Apply the following fixes before undertaking more difficult ones:

-Roll back changes that you’ve made recently before the BSOD occurrence.
-Try removing any hardware that you’ve added recently.
-Scan your computer for damaged or duplicate registry entries.
-Install the latest drivers.
-Update your Service Pack.
-Run a complete scan on your computer with a good antivirus program.

If the blue screen restarts to quickly, you can change Windows auto-reboot settings. You can do this by navigating to Control Panel (in XP), then going into System Properties, then un-checking the function in Startup and Recovery. By doing this you’ll have time to actually take down the error message when it appears.