Windows NTFS Sys Blue Screen Reboot

Mar.27, 2010 in Computers

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. It looks completely alien compared to other errors, almost dated, like it belongs to a lesser machine. You realize that there is no ‘accept’ or ‘ok’ to return to what you were previously doing. You begin to curse myself for not saving your work more often.

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. So you do what pretty much anyone would do, you search online for the NTFS Sys error and hope for a solution.

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. Even with the error message in hand, you will find that it gives little information on exactly how to fix the BSOD.

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. 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 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. 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. It’s unlikely that you’ll have to do anything drastic such as reinstalling Windows or replacing hardware. Apply the following fixes before undertaking more difficult ones:

-Undo any recent changes that might be causing the BSOD.
-You might want to try uninstalling newly added hardware.
-Clean out your registry of faulty or redundant 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.

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. Next time the BSOD pops up again you don’t have to worry about missing the message.