[HELP] ntoskrnl.exe & ntkrnlmp.exe & fltmgr.sys BSOD Issue

Mattrhorn · 07 Oct 2012

Ive been getting BSOD's recently that i cant quite fix, I have updated A LOT of drivers recently to try to fix it and it has got quiet, but today i had 2 in a the span of 1 hour relating to what I had before. I dont really know what it is but I really want to find out the answer. Just Some information that This started happening after I got

A New Power Supply
a Second EVGA GTX 550 Ti GPU
and a Khuler Whater Colling CPU System

One Other Problem i have had is that I can use my OPTICAL DRIVE through the bios but the computer doesnt see or recognise it in the actual accounts. If there is an explaination for that in this please let me know

Files Needed in Description

This is all the Information collected from WhoCrashed (HOME EDITION) v3.06:

On Mon 08/10/2012 2:42:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-29265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003583E1B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 08/10/2012 2:42:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003583E1B)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 03/10/2012 9:31:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100312-44491-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003587E1B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 29/09/2012 11:44:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-27534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8000353BE1B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 28/09/2012 2:30:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-30560-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003593E1B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 26/09/2012 10:46:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-32011-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80305A1260, 0x2, 0x1, 0xFFFFF80003594366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Sat 22/09/2012 6:40:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-38859-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8031110280, 0x2, 0x1, 0xFFFFF80003533366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Sat 22/09/2012 5:00:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-29031-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80313CC1B8, 0x2, 0x1, 0xFFFFF80003541366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Thu 20/09/2012 9:04:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-25256-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80311E01C8, 0x2, 0x1, 0xFFFFF80003586366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Thu 20/09/2012 4:05:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-27596-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80312101C0, 0x2, 0x1, 0xFFFFF80003549366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Thu 20/09/2012 8:32:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-24913-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030B24290, 0x2, 0x1, 0xFFFFF80003538366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Mon 17/09/2012 9:24:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-28828-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030E0D2C8, 0x2, 0x1, 0xFFFFF80003543366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Fri 14/09/2012 10:55:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091412-28017-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030CBC218, 0x2, 0x1, 0xFFFFF80003588366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Fri 14/09/2012 11:16:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091412-26379-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030A12258, 0x2, 0x1, 0xFFFFF80003587366)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Thu 13/09/2012 8:44:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091312-29140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8000354BE1B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Arc · 08 Oct 2012

First of all, you need to update your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC.

► update the network driver.
First, download the network card driver from manufactuer's website, Realtek
Then reinstall the driver:

Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
Double click to expand "Network adaptors".
Right click your network card and click Uninstall.
Check "Delete driver software for this device" check box, click OK.
Restart the computer
If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

► This error is often caused by Notron, and Mcafee.

Code:

fffff880`0354d568  fffff880`01005132 fltmgr!GetContextFromStreamList+0x192

My suggestion, you uninstall those both for the time being (McAfee permanently) and use Microsoft Security Essentials - Free Antivirus for Windows.

► Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

Let us know the results.

Mattrhorn · 08 Oct 2012

Hey Arc,
Thanks for all the help, I have not done anything yet, but i am going to get to that right now. My one question is for the security software, is it because of mcafee and norton's conflicting with eachother, or are both of those just a source of the problem. The reason is ive been using Nortons for around 2 years now and I accidentally download McAfee while getting a new flashplayer and havent gotten around to uninstalling it cause i dont need it. So will removing McAfee be alright or is it Important that I remove both...

Thanks for the reply by the way, I REALLY appreciate it. Ill do what you said and give feedback at the end of the day (10:00pm EST).

as well as look for things relating to:

One Other Problem i have had is that I can use my OPTICAL DRIVE through the bios but the computer doesnt see or recognize it in the actual accounts. If there is an explanation for that in this please let me know

Thanks for everything arc

EDIT 1: Hey Arc, Uninstalled McAfee, as well as I realized that most of my blue screens are caused while playing games in extreme graphics, and one of the times it said something like dxsmmg1.sys or something like that, so see if this could be a DirctX thing. I let Steam handle downloading directx for me, so should look into actually downloading it from microsoft site to get a clean install?

One other thing is that everytime i start up i get a permession thing asking if its ok to run "jucheck.exe" or something really similar to that, it says its from orical and it has flash so i assumed that it was flash player related. but i never got this before, just recently like 1-2 months ago when this started happening

Arc · 08 Oct 2012

Mat, McAfee is the worst program ever coded, perhaps. It causes a huge lot of troubles, we see every day. You MUST to remove it.

About norton, that is good, no doubt. but if you use it tactfully. Norton, if used normally, also cause a lot of troubles.

On the other hand, MSE is the best security, and never causes a problem. It does not cost anything, just needs WGA to pass before installation.

That is why, if there is a security software related issue, we suggest to use MSE.

And, NEVER use multiple security software at once.

Mattrhorn · 08 Oct 2012

Alright, well I removed McAfee aswell as i uptaded the driver you told me to which was sthe Realtek one, I was on an old one, and when I uninstalled it, it went back and downloaded the old one again so i went in and manually downloaded it, Hope that helps. So ya, looks like its a waiting game now. Thanks for all the help Arc.

As well as Norton's is only used to check downloads for viruses as well as scans 1 every other week so its not heavily used, but i guess ill see if anything comes up.

Arc · 08 Oct 2012

Let us know the results :)

Mattrhorn · 08 Oct 2012

Did you read my edit on post #3?

Arc · 08 Oct 2012

Sorry I havent seen it.

That jucheck.exe is Java automatic update utility. If you dont need Java, you may uninstall it.

Otherwise Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

I guess the jucheck.exe will not prompt up at startup anymore.

For the games, your thought are almost right. In such a situation, you may set the games preference settings to minimum, hopefully it will work there.

Mattrhorn · 08 Oct 2012

Alright, So i freed up the startup with some exceptions:

USB 3.0 Monitor
Microsoft(R) Windows(R) Operating System
And a few Logitech controllers for my keyboard, so that my keyboard works properly

Other than that everything is off. My computer has the power to run games at extreme graphics, but i think that the problem meybe with a corrupt DirectX install, so i am going to try a fresh install with that and see how that works.

Thanks again for the Assistance

!!!

Arc · 08 Oct 2012

You are welcome. Let us know the results when you are done :)