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. 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.
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. Unfortunately it happens just a few hours later. This time you manage to write down the rest of the message. Not knowing what on earth the error code means, you start your search on the Net for any help.
Like anyone in the same situation you try the suggested fixes you find online and you begin the process of slow elimination. While some people continue to experience the BSOD, most users find a fix. But unless you're lucky and you really know what you're doing, the solution will not come easily. 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. Moreover, there are lots of error codes that are harder to solve than others. The difference between getting an Ati2dvag blue screen and a Mup.sys blue screen is a lot more problems.
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.
Initially you should rule out any simple issues that could be causing the blue screen and avoid making big changes to your PC. 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. Give these quick fixes a try first:
-Undo any recent changes that might be causing the BSOD.
-You might want to try uninstalling newly added 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.
It's a good idea to stop Windows from automatically rebooting at blue screens. First go to Control Panel and access System; click on the Advanced tab located in System Properties; then uncheck the Automatically Restart box in Startup and Recovery. Now you will be able to write down the blue screen message without it restarting on you midway.
Visit my site on how to repair
NTFS Sys Blue Screen and the
Ati2dvag Blue Screen.
