Picture the usual day – you’re home working on your PC and then out of nowhere up pops an ntfs sys blue screen. You panic seeing this error message for the first time. The error is unfamiliar to you and looks unlike any other error that you’ve encountered before. 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. You have a worrying feeling that it won’t be the last time you’ll be seeing that screen again. Sure enough a day later, ‘Zzzpt’ the blue screen appears again just as you were about to save your work. This time you manage to write down the rest of the message. 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.
Like most individuals, I find this really irritating to say the least. It’s like being lost in a town in a foreign country and being given directions in a foreign language. Ok, it might be a little helpful, but just a little. 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. These should cause no harm to your computer or operating system. Usually you will not have to go as far as opening your PC up or doing a full system restore. Apply the following fixes before undertaking more difficult ones:
-If you’ve made any changes recently, try undoing them.
-Uninstall any recently installed hardware.
-Scan your computer for damaged or duplicate registry entries.
-Make sure you have the newest drivers installed.
-Install the latest Service Pack from Microsoft‘s website.
-Do a full system scan for infections such as rootkits and viruses.
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. Next time the BSOD pops up again you don’t have to worry about missing the message.
