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. So, naturally you feel annoyed as the any work you’ve done gets lost.
Before you have time to write down the entire message the system reboots. 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. 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.
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. 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. 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.
Initially you should rule out any simple issues that could be causing the blue screen and avoid making big changes to your PC. There’s a good chance that the problem is only minor. In most instances taking your computer apart or doing a full system reinstallation isn’t required. Try the following simple steps;
-Roll back changes that you’ve made recently before the BSOD occurrence.
-Uninstall any recently installed hardware.
-Check the registry for any invalid or corrupt entries with a registry cleaner.
-Make sure you have the newest drivers installed.
-Update your Service Pack.
-Run a complete scan on your computer with a good antivirus program.
A quick tip; make sure you disable Windows automatic restart function. First go to Control Panel and access System; click on the Advanced tab located in System Properties; then uncheck the Automatically Restart box in Startup and Recovery. Next time the BSOD pops up again you don’t have to worry about missing the message.

