XP NTFS Sys Blue Screen Crashes
It’s a regular evening, you’re at your computer doing whatever you do and then suddenly appears an ntfs.sys blue screen message. You panic seeing this error message for the first time. You notice that this isn’t like other error messages that you usually experience. You realize that there is no ‘accept’ or ‘ok’ to return to what you were previously doing. Unsurprisingly you regret not having saved your work.
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. Sure enough a day later, ‘Zzzpt’ the blue screen appears again just as you were about to save your work. 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.
This is where you begin, like most people who experience blue screens, the cycle of trial, failure and more trials. Don’t throw in the towel just yet though as there is probably a fix out there somewhere. If you’re fortunate to stumble on the answer straight away, then count yourself lucky. Even with the error message in hand, you will find that it gives little information on exactly how to fix the BSOD.
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. Ok, it might be a little helpful, but just a little. Moreover, there are lots of error codes that are harder to solve than others. If you’re lucky enough to get an Ati2dvag Blue Screen, it probably only needs a driver update, but get a Mup Sys Blue Screen and you will be in for a ride.
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. The best thing to do when you get a blue screen is to take down the message and do an online search of the issue or better still, contact someone who knows about computers.
Before you start making any major changes to your computer, make sure you try some basic fixes first to rule out the obvious problems. These should cause no harm to your computer or operating system. It’s unlikely that you’ll have to do anything drastic such as reinstalling Windows or replacing hardware. Give these quick fixes a try first:
-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.
-Install the latest Service Pack from Microsoft’s website.
-Scan your computer for any nasty viruses or malware.
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. Next time the BSOD pops up again you don’t have to worry about missing the message.
