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. It looks completely alien compared to other errors, almost dated, like it belongs to a lesser machine. You realize that there is no ‘accept’ or ‘ok’ to return to what you were previously doing. You begin to curse myself for not saving your work more often.
To add insult to injury the computer reboots on it’s own accord, just as you start writing the error code down. 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. You’re more prepared this time and you finish writing down the rest of the stop code. 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. This isn’t to say that the blue screen error code doesn’t give some hints to what the problem is, but it won’t provide a detailed solution.
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. Sure it’s helpful, but not that helpful. And this doesn’t take into account that some stop error codes are a lot more difficult to solve than others. 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. It’s a good idea to search for the error message online since there’s a chance that someone has already fixed the same problem and posted their fix on a website.
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. Usually you will not have to go as far as opening your PC up or doing a full system restore. Try the following simple steps;
-If you’ve made any changes recently, try undoing them.
-You might want to try uninstalling newly added hardware.
-Scan your computer for damaged or duplicate registry entries.
-Check for any driver updates.
-Check that you’re running the latest Service Pack.
-Scan your computer for any nasty viruses or malware.
A quick tip; make sure you disable Windows automatic restart function. 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. Now you will be able to write down the blue screen message without it restarting on you midway.
