Solved BSOD Involving ntoskrnl.exe

[Faldaga]

Well, after scouring the internet in an attempt to figure a solution for myself I have finally admitted defeat and here I am.

The issue is hard to pinpoint as it happens at random. Be it gaming, browsing the net, or even opening a window to navigate around my computer. It is always the same. The stop error reads as 0x000000 with no other indicators. Thankfully, through checking with a program called BlueScreenView, I was able to isolate the culprits and get a general idea of what is causing this.

Keep in mind I have already tested the RAM thoroughly, switched hard drives, fully reformatted, and even installing a fresh installation of Win7...multiple times. This has happened on two separate motherboards with varied processors as well. This leaves me assuming that it is the graphics card.

I will include three minidumps. The first only shows the ntoskrnl.exe as the issue, the second ties it in with nvlddmkm.sys, and the third ties it in with pacer.sys.

Thanks!

 

[Lemur]

Hi Faldaga and welcome to SF.

Please do the following:

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Faldaga]

Sorry, should read things before I start posting. Here you go!

Windows 7 is:
-64bit
-Original is installed
-Full Retail
-Less than a year?
-Less than a year

 

[Lemur]

Please start by updating your Nvidia Nforce driver.

 

[zigzag3143]

Sorry, should read things before I start posting. Here you go!

Windows 7 is:
-64bit
-Original is installed
-Full Retail
-Less than a year?
-Less than a year

These were Related to Mo3Fltr.sys WinDDK from Microsoft Windows Hardware Compatibility Publisher

Updating to SP-1 may fix it.



Learn how to install Windows 7 Service Pack 1 (SP1)

 

[Faldaga]

Updated my Nforce drivers to check that first - will stress test it by doing whatever, seeing as it is random. If it happens again I will attempt the second fix posted. The spacing between BSODs appears to be random but at least occurs once every two days if I am active on my computer. We will see.

 

[Faldaga]

Well, wasn't the nForce drivers. At least, not entirely. Just had another BSOD. Attempting Fix #2.

 

[Faldaga]

Alright - I installed SP1 and ran for a few days without issue. Did the tried-and-true method to force a BSOD and played PvP on WoW. Seeing as my computer hates me, it BSOD'd in the middle of match number two. Now the report is tying itself to tcpip.sys as well - which I've never seen on any of the numerous reports before.

To sum up: No solution has worked as of yet. Appreciate that you are at least trying to help ^.^

Included is another set of files with updates drivers and two of the most recent minidumps.

 

[zigzag3143]

Alright - I installed SP1 and ran for a few days without issue. Did the tried-and-true method to force a BSOD and played PvP on WoW. Seeing as my computer hates me, it BSOD'd in the middle of match number two. Now the report is tying itself to tcpip.sys as well - which I've never seen on any of the numerous reports before.

To sum up: No solution has worked as of yet. Appreciate that you are at least trying to help ^.^

Included is another set of files with updates drivers and two of the most recent minidumps.

BINGO

One of the largest causes of bsod's


Asacpi.sys

The pre 2009 version of this driver is a known bsod cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).

ALSO please note thie below file is from 2008 and needs to be updated.
Related to Mo3Fltr.sys WinDDK from Microsoft Windows Hardware Compatibility Publisher

 

[Faldaga]

Updated the ASUS file - but I don't understand what you mean by the Mo3Fltr.sys file. I am unable to find a link to update with when I click the link.

 

[zigzag3143]

Updated the ASUS file - but I don't understand what you mean by the Mo3Fltr.sys file. I am unable to find a link to update with when I click the link.

You can simply rename the file to *.bak to prevent it from loading. Let us know if you still crash.

 

[Faldaga]

I am not even finding a file named Mo3Fltr.sys - confused on what is needing to be done here.

 

[zigzag3143]

I am not even finding a file named Mo3Fltr.sys - confused on what is needing to be done here.

It is on your system. If you are indexing your entire "C" drive then it should show.

 

[Faldaga]

Alright - full search on C yielded a handfull of Mo3Fltr.sys files. Here are the file directories:

C:\Windows\System32\DriverStore\FileRepository\mo3.inf_amd64_neutral_baa66c170b669ce3

C:\Windows\System32\drivers

And the rest are tied in with my SteelSeries MMO Gaming Mouse.

Also, updated Asacpi.sys - the file is no longer dated prior to 2009. Regardless, still having BSOD issues.

Thanks!

 

[zigzag3143]

Alright - full search on C yielded a handfull of Mo3Fltr.sys files. Here are the file directories:

C:\Windows\System32\DriverStore\FileRepository\mo3.inf_amd64_neutral_baa66c170b669ce3

C:\Windows\System32\drivers Ths is the most important

And the rest are tied in with my SteelSeries MMO Gaming Mouse.

Also, updated Asacpi.sys - the file is no longer dated prior to 2009. Regardless, still having BSOD issues.

Thanks!

Also if you havent run a system file check


Run a system file check to verify and repair your system files.

To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful
Let us know the results from the report at the end.

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Faldaga]

Renamed the Mo3Fltr.sys associated with C:\Windows\System32\drivers to Mo3Fltr.bak - didn't know if this is the correct solution?

Currently running a system file check - will post upon completion.

 

[Faldaga]

System file check did not find any integrity violations.

Will try to force a BSOD.

 

[Faldaga]

Managed another BSOD, frequency increased when playing WoW. After reboot, my WoW Gaming Mouse became unresponsive. I have noted that this mouse is tied in with the Mo3Fltr.sys files you were mentioning.

Included is another report with my perfmon report and BSOD errors, only the most current two BSOD's are from the current fix.

Thanks!

 

[zigzag3143]

Managed another BSOD, frequency increased when playing WoW. After reboot, my WoW Gaming Mouse became unresponsive. I have noted that this mouse is tied in with the Mo3Fltr.sys files you were mentioning.

Included is another report with my perfmon report and BSOD errors, only the most current two BSOD's are from the current fix.

Thanks!

Still related to the Mo3fltr.sys. Any way you can try a different mouse?

 

[Faldaga]

Switched out a Habu Razor and uninstalled all drivers and programs associated with the SteelSeries MMO Gaming Mouse. Will reply if it corrects the situation.