Windows 8 BSOD caused by ntoskrnl.exe


I have been getting a lot of the dreaded BSODs lately. 

Early on I thought it to be nvidia drivers. Updating those fixed all but one BSOD i get.
Now i keep getting the same BSOD, and it's caused by ntoskrnl.exe and problems reading memory.

I have been searching all around for help, and using memtest86 without any result.

The Msinfo32 and .dmp-files are located here: 

Do anyone have an idea what may be causing this? 
I couldn't find the RAM I'm using in the compatibility chart for the motherboard. So that is what I'm thinking may cause the problem.

Any help is greatly appreciated.



Hi Arve,

All of the attached DMP files are of the IRQL_NOT_LESS_OR_EQUAL (a) bug check.

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If we look at the call stack:

fffff880`0335caf0 fffff880`06a4d817 : fffff880`00000000 fffffa80`00000008 fffffa80`12fdbe10 00000005`00001f80 : nt!KeSetEvent+0x2ad
fffff880`0335cb60 fffff880`00000000 : fffffa80`00000008 fffffa80`12fdbe10 00000005`00001f80 fffffa80`1458a6a0 : MBfilt64+0x1817
fffff880`0335cb68 fffffa80`00000008 : fffffa80`12fdbe10 00000005`00001f80 fffffa80`1458a6a0 fffff800`9bc62d4c : 0xfffff880`00000000
fffff880`0335cb70 fffffa80`12fdbe10 : 00000005`00001f80 fffffa80`1458a6a0 fffff800`9bc62d4c fffffa80`1458a6a0 : 0xfffffa80`00000008
fffff880`0335cb78 00000005`00001f80 : fffffa80`1458a6a0 fffff800`9bc62d4c fffffa80`1458a6a0 fffffa80`1458a6a0 : 0xfffffa80`12fdbe10
fffff880`0335cb80 fffffa80`1458a6a0 : fffff800`9bc62d4c fffffa80`1458a6a0 fffffa80`1458a6a0 fffffa80`12fdbe10 : 0x5`00001f80
fffff880`0335cb88 fffff800`9bc62d4c : fffffa80`1458a6a0 fffffa80`1458a6a0 fffffa80`12fdbe10 fffff880`02fc9f00 : 0xfffffa80`1458a6a0
fffff880`0335cb90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ViPendingCompleteAfterWait+0xc4

Unable to load image MBfilt64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by : MBfilt64.sys ( MBfilt64+1817 )

Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver).

If we run an lmvm on yours:

4: kd> lmvm MBfilt64
start             end                 module name
fffff880`06a4c000 fffff880`06a5a000   MBfilt64 T (no symbols)          
    Loaded symbol image file: MBfilt64.sys
    Image path: MBfilt64.sys
    Image name: MBfilt64.sys
    Timestamp:        Thu Jul 30 23:40:32 2009 (4A7267B0)

^^ Yours is dated from ~2009. The latest AFAIK is from Sept. 2013 via Realtek's website -

Update this driver ASAP.


Also, to provide peace of mind in regards to your RAM query. When you get a motherboard and they have a list of compatible RAM in the manual, etc, that's called a QVL (Qualified Vendor List). This is simply a list of RAM that was tested in house and is PROVEN to be absolutely 100% compatible. If RAM is not on the list, it does not by any means whatsoever imply that the RAM will be incompatible and cause issues. That's actually nowadays very rare. Your RAM doesn't seem to be the issue at all in these crashes.


Debugger/Reverse Engineer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated March 24, 2018 Views 2,251 Applies to: