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

Mattrhorn · 08 Oct 2012

Well around an hour and a half has gone by without any isues, Ive been putting gaming stress tests on my computer because that was usually when it happened soo i did that, Nothing soo far. I am a Small Youtube Gamer Commentator, so i was using Fraps as well as Vegas Pro to test the stress of everything, and everything worked out great, so im crossing my fingers with this one hoping its solved. Ill update again every few hours. You dont need to reply to this if you dont want to because it is unnecessary. Ill keep Updating on a regular basis and if anything happens ill let you know. Thanks again

Mattrhorn · 08 Oct 2012

I just got my blue screen like 5 minutes ago

I opened up and ran that SF tool thing and got the files for you, Let me know what you think. This happened while editing a video in Vegas Pro. There isnt allot of edits and i didnt use up more than 45% of my cpu power. Im very concerned now about anything i do and to make sure i save EVERYTHING. so yea, let me know what you think

EDIT 1: Well I opened up WhoCrashed.exe and it came up with this:
EDIT 2: Im starting to notice that most of the BSOD's prop up 2 Files at the same time, Could this be because of Conflicting Drivers?

On Mon 08/10/2012 10:52:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-32541-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA803117D2C0, 0x2, 0x1, 0xFFFFF80003539366)
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 08/10/2012 10:52:53 PM 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 (0xFFFFFA803117D2C0, 0x2, 0x1, 0xFFFFF80003539366)
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 Mon 08/10/2012 2:42:05 AM GMT your computer crashed
On Mon 08/10/2012 2:42:05 AM GMT your computer crashed

Arc · 08 Oct 2012

First, run a disc check.

Reseat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Second, uninstall Norton for the time being, use Microsoft Security Essentials - Free Antivirus for Windows. The fltmgr.sys error causes by the antivirus programs, too.

And, run memtest for at least 8 passes, preferably overnight, for each module placed in each slot, one by one.
RAM - Test with Memtest86+

Let us know the results.

Mattrhorn · 09 Oct 2012

Arc said:

First, run a disc check.

Reseat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Well this is sort of a problem due to the fact that i cant burn to a cd/dvd/bluray because my computer for some reason cant see my optical drive inside windows. Only in the bios. I will uninstall norton's though tomorrow. Aswell as sorry for the late response my school went on 11 hours today :S

Is there any other ways of doing this?

Arc · 09 Oct 2012

You can do it by making a bootable USB, too.

But, before that, you can follow step 1 and 2 easily.

Mattrhorn · 09 Oct 2012

Alright man, Is it possible to start conversations through skype just for easier conversations cause even though these forums are pretty amazing, communication is just a bit harder through here?.

Aswell as i uninstalled nortons and got a BSOD like 10 minutes before that.

This is what came up and ill send the SF Files

On Wed 10/10/2012 2:49:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-39889-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003594E1B)
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 10/10/2012 2:49:26 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, 0xFFFFF80003594E1B)
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.

Arc · 10 Oct 2012

OK, here is it. Apparently your crash is network caused.

► You have a Realtek PCI GBE Family Controller, the driver is somehow old.

Code:

 Driver     c:\windows\system32\drivers\rt64win7.sys (7.46.610.2011, 526.60 KB (539,240 bytes), 10/06/2011 6:34 AM)

► You also have a Hamachi Network Interface, that one is even old.

Code:

 Driver     c:\windows\system32\drivers\hamachi.sys (7.0.1.1, 33.06 KB (33,856 bytes), 18/03/2009 5:35 PM)

Update both the network drivers.

► Norton is a known cause of crash. It blocks some network elements off and on. As a test, uninstall Norton and use Free Microsoft Scurity Essentials.

► 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 · 10 Oct 2012

Nortons Gone for the time being, Startup is free'd. I dont know how to get an updated realtek driver caused i used the one i got from the link you sent me w while back. Ill try again. Adn for Hamachi, ill have to look around for that. But thanks. Ill look into everything you have said

EDIT 1: No Drivers are available for Hamachi, This is the Most recent one. The Realtek driver however was updated to the current version as it wasn't before
EDIT 2: Running Hard Processes on My computer and everything... So far no issues, so i have my fingers crossed. Hope its fixed

Arc · 11 Oct 2012

I also hope it fixed, but if it still crashes, and pointed the cause to network, we may need to think for log me in hamachi, unfortunately.

Best of luck.

Mattrhorn · 31 Oct 2012

Bad News... After all this time:

On Thu 01/11/2012 1:10:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-49561-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xF5985)
Bugcheck code: 0xA (0xFFFFFA8030846290, 0x2, 0x1, 0xFFFFF8000353B376)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 306.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 306.23
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.23 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL

On Thu 01/11/2012 1:10:52 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 (0xFFFFFA8030846290, 0x2, 0x1, 0xFFFFF8000353B376)
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.

--------------------------------------------------------------------------------------------------------------

It said that windows removed a malicious item of the computer after it restarted soo I tthink that has something to do with it and it may just be nothing but please take a look if you have time...

EDIT1: I went ahead and updated my NVIDIA Driver because it was out of date by like 2 months soo...

Thanks,
Mattrhorn