XP NTFS Sys Blue Screen
Imagine working away on your computer, when all of a sudden you get an ntfs.sys blue screen error message. 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. From that moment, you anxiously anticipate another blue screen error occurrence. Unfortunately it happens just a few hours later. You have a pen and pad ready, so you get down the final part of the error code in time. 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. Don’t throw in the towel just yet though as there is probably a fix out there somewhere. However, without any technical PC knowledge the answer is unlikely to fall in your lap. 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 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. Furthermore, this doesn’t really address the fact that many error messages have a variety of causes and fixes. 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.
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. 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. You may be fortunate enough to six your computer with these simple methods. It’s unlikely that you’ll have to do anything drastic such as reinstalling Windows or replacing hardware. Try the following simple steps;
-Roll back changes that you’ve made recently before the BSOD occurrence.
-Uninstall any recently installed hardware.
-Clean out your registry of faulty or redundant entries.
-Install the latest drivers.
-Check that you’re running the latest Service Pack.
-Do a full system scan for infections such as rootkits and viruses.
A quick tip; make sure you disable Windows automatic restart function. 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.
