BlueScreen Of Death Error : Whats It Mean?

so i just got this error:

*** STOP: OXOOOOOO 7E (0XFFFFFFFFCOOOOOO5, OXFFFFFA6OOO78B248, OXFFFFFA6001B9F798, OXFFFFFA6001B9F170)
*** fltkmgr.sys - address FFFFFA600078B248 base at FFFFFA6000786000, Datestamp 47919082

can anyone tell me what this means, i havent had a bluescreen of death before so i have no idea about any of this,

thanx

 

Blue screen errors can be caused by several different things. Most commonly, there is a driver conflict in your configuration. Did you recently add a new driver?

 

Usually googling the error code and any related info would help you get some general troubleshooting tips.

In your case it is 0x7E or 0x0000007E. And the culprit seems to be the .sys file in the 2nd line.

 

Are you certain it is fltkmgr?

 

Has to be fltmgr.sys. He probably wrote the code down from an image or still, since he got the error codes wrong too. Those O's are obviously 0's.

 

Just as a precaution, run an A/V scan first; however, it's probably not malware, but potentially something going haywire with your file system. According to this file.net webpage, fltmgr.sys is the Windows filesystem filter manager.

There is a somewhat related discussion of stop code 0x0000007e in connection with a BSOD on XP that's related to a hard drive device here, which might be worth reviewing to see if it gives you any leads.

However, as it's a problem with your filesystem filter manager, it's unlikely to be a badly written driver problem, so it could be a corrupted driver problem, or it could be hardware-related - if it is, the best-case scenario is that you just added a piece of hardware, such as a drive of some sort, and it's not fitting in with the rest of your system - have you added anything recently? The worst case scenario, and the one I'm inclined to think might be the source, is that your hard drive is beginning to die, and it's causing the driver in question to malfunction. For this, I would get the diagnostic utility you can download for free from the website of the company that manufactured the actual hard drive, and then test it to see if it's still within spec, or if it's showing some failure in the SMART data.

 

yeah i wrote it down while looking at it, and i couldnt tell which was o and which were 0. i think i have an idea though as it happened twice and both times it was during a file downloading. i KNOW its not a driver problem as 1. i havent installed any drivers lately and 2. this is the first time that its happened so i would expect that if it was a driver problem that it would have happened before.

 

do you have norton installed?

 

no i dont, too many people i know seem to have trouble with it. i have Comodo SafeSurf and Comodo Internet Security as well as Avast Home, but i also use windows defender as well

 

Neither (1) nor (2) has any real bearing on whether this is a driver problem or not. In particular, every driver problem has to have a first time, so (2) is pretty obviously not that relevant, and (1) is neither here nor there as it doesn't cover the circumstance of either (a) a driver getting corrupted, or (b) a good driver being fed data that causes it to throw an exception it cannot handle correctly.

The fact that this BSOD happened only two times, and each time you were downloading a file, is consistent with the fact that the code responsible for the BSOD was fltmgr.sys which is the file system filter manager.

Microsoft has a basic layperson's description of what a file system filter does here. That webpage also contains a brief description of what the filesystem filter manager does, to wit:

Based on that, it sounds like what happened is there was a conflict between two or more of your A/V products - all of which use various file filters that are managed by the file system filter manager (the process that caused the BSOD) - when your various A/Vs tried to scan the file you were downloading.

Were those files you were downloading particularly large, or were they from a suspect source?

 

having multiple antivirus programs with real time monitoring as you do is a recipe for disaster.

Comodo IS and Avast are both trying to look at the same file at the same time while you are downloading it.

If you must have two, choose one with Realtime monitoring and one with manual scanning.

You are not doing yourself any favors

 

i have never had trouble with it before, so i dont think its that - i have had it like this for months with no trouble at all and i havent had a BSOD since trying to download a specific file that gave me BSOD both times i tried to download it, everything seems fine now.

 

Ash, just because you haven't had trouble to date does not mean that having multiple A/V products competing with each other is not the cause - in fact, it may only happen when you download files such as the two you were downloading when you got the BSOD.

Why not try this: uninstall the surplus A/V apps, so you're just running with one, and then go back to the last file download that caused a BSOD and try downloading the file again to see if it triggers another BSOD.

 

Ash,

Why do you ask for help but dismiss the help that is offered

Given your erros message, it is almost certainly a driver issue, and it is almost certainly caused by two av programs

fltmgr.sys is the Microsoft file system manager DRIVER and its job is to run interference for programs accessing files. The fact you have two AV programs with realtime monitoring running and they are both trying to check the files you are downloading, it is not only not surprising this is your issue, but it is more surprising it doesn't happen more often.

It is a testiment to how efficient Windows has become because trust me, if you were doing the same thing with windows 98 you would be crashing all over the place.

 

im just saying that i havent had this before so how could it be a driver problem? surely if it were (correct me if im wrong) but if it were a driver problem wouldnt the problem start when i installed the driver and on just randomly start several months after it was installed?

which AV should i uninstall? would it be best to uninstall Avast? as with Comodo i have Internext Security and some other things with it that work well.

after i have uninstalled it i will try and download the file again and see if i get the BSOD error again

 

I'd say you were lucky it din't cause issues all along--nothing more, nothing less.

As for what to uninstall--depends on your comfort level with the products you use

You COULD leave both, but simple disable the realtime monitoring feature of one of them. In AVast you do this by turning off RESIDENT PROTECTION....although the AVAST kernal is still running and may continue to access the file manager filter system driver.

I woudl probably uninstall it completely to start and then add it back later or add another pogram with simple manual scanning like CLAMWIN