Windows Update NTFS Sys Blue Screen Crashes
Imagine working away on your computer, when all of a sudden you get an NTFS Sys Blue Screen error message. Naturally, a wave of dread flows through you having never seen this message before. 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. So, naturally you feel annoyed as the any work you’ve done gets lost.
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. This time you manage to write down the rest of the message. 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. While some people continue to experience the BSOD, most users find a fix. 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.
Like most individuals, I find this really irritating to say the least. 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. 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.
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. 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. In most instances taking your computer apart or doing a full system reinstallation isn’t required. Give these quick fixes a try first:
-Undo any recent changes that might be causing the BSOD.
-Uninstall any recently installed hardware.
-Clean out your registry of faulty or redundant entries.
-Make sure you have the newest drivers installed.
-Update your Service Pack.
-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. By doing this you’ll have time to actually take down the error message when it appears.
