Everyday Blog

Picture the usual day - you’re home working on your PC and then out of nowhere up pops an ntfs sys blue screen. 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. There isn’t an option to simply click ‘ok’ and resume with your work. So, naturally you feel annoyed as the any work you’ve done gets lost.

As you get pen and paper and begin to jot the error message, the PC restarts automatically. You have a worrying feeling that it won’t be the last time you’ll be seeing that screen again. Sure enough a day later, ‘Zzzpt’ the blue screen appears again just as you were about to save your work. 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. But unless you’re lucky and you really know what you’re doing, the solution will not come easily. 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.

Like most individuals, I find this really irritating to say the least. It’s like being lost in a town in a foreign country and being given directions in a foreign language. Not exactly what you would hope for when after a solution. And this doesn’t take into account that some stop error codes are a lot more difficult 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. 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.

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. Usually you will not have to go as far as opening your PC up or doing a full system restore. Try the following simple steps;

-If you’ve made any changes recently, try undoing them.
-Try removing any hardware that you’ve added recently.
-Check the registry for any invalid or corrupt entries with a registry cleaner.
-Install the latest drivers.
-Update your Service Pack.
-Scan your computer for any nasty viruses or malware.

A quick tip; make sure you disable Windows automatic restart function. 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.