Find and Fix Errors

Picture the usual day - you’re home working on your PC and then out of nowhere up pops an ntfs.sys blue screen. Fear and panic strikes you as you try and read the message. It looks completely alien compared to other errors, almost dated, like it belongs to a lesser machine. The opportunity to acknowledge the error and go back to whatever you were doing doesn’t exist. 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. Something tells you however that you’ll be seeing the blue screen again very soon. Unfortunately it happens just a few hours later. You’re more prepared this time and you finish writing down the rest of the stop code. So you do what pretty much anyone would do, you search online for the NTFS Sys error and hope for a solution.

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. 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 being lost in a town in a foreign country and being given directions in a foreign language. Sure it’s helpful, but not that helpful. 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 faulty Mup.sys file, malware, a corrupt registry entry and badly installed hardware; any one of these and a lot more can cause Mup.sys problems. 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. These should cause no harm to your computer or operating system. In most instances taking your computer apart or doing a full system reinstallation isn’t required. Apply the following fixes before undertaking more difficult ones:

-Roll back changes that you’ve made recently before the BSOD occurrence.
-You might want to try uninstalling newly added hardware.
-Scan your computer for damaged or duplicate registry entries.
-Check for any driver updates.
-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. 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.

Share This

Tags: computer, drivers, PC, registry, technology