informationToys

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. You notice that this isn’t like other error messages that you usually experience. There isn’t an option to simply click ‘ok’ and resume with your work. 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. You have a worrying feeling that it won’t be the last time you’ll be seeing that screen again. The next day it happens again and again without warning. You’re more prepared this time and you finish writing down the rest of the stop code. Not knowing what on earth the error code means, you start your search on the Net for any help.

This is where you begin, like most people who experience blue screens, the cycle of trial, failure and more trials. 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.

This is what bugs me and thousands of people the most. 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. 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. It may take several tries to repair this particular issue. 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. You may be fortunate enough to six your computer with these simple methods. 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:

-If you’ve made any changes recently, try undoing them.
-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.
-Update your Service Pack.
-Do a full system scan for infections such as rootkits and viruses.

It’s a good idea to stop Windows from automatically rebooting at blue screens. 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.