BSOD when resume from sleep (+1 hour)

**cluberti** · 03 Jul 2015

It's eminently possible that something you've installed into both systems is causing an issue, but this dump points to a page table page being corrupt so it could really be anything, software or hardware. It does have a 3rd param of ffff, so it's an underflow of some kind triggering the corruption. It could be a bad driver, or potentially some sort of hardware issue that triggers this (bad hardware, firmware bugs, etc) flipping of at least one (or more) PTEs in the page table page to a non-zero value (this very particular scenario is what triggers the bugcheck you've posted here).

If you truly believe that the RAM is good in this machine, you can try to reproduce these errors on a Windows 8.1 system, which will attempt to go about preserving the corrupted PTE value before issuing a bugcheck if this happens again, thus making it (hopefully) easier to analyze in that configuration. A trial version of Windows 8.1 would be sufficient, you wouldn't need to go out and purchase a license at all.

LiquidBlack NL · 03 Jul 2015

Thanks for your extensively answer! It clear things up for me :).

On the moment i've got a ticket on hold at Gigabyte (Motherboard manufacturer) maybe they can give me more informatie or maybe it is a know problem with this type mb.

Yes Windows 8 trail is a very good idea, i'm gonna try that and post an update soon! I don't know what to do else :P.

I also checked my ram with HCIMemtest because i read on the forums that it can provide with an error that memtest can't give you, but i came clean:

LiquidBlack NL · 04 Aug 2015

Hello,

Back from vacation so I can go further with fixing my BSOD problems.
Today I replaced the ram with 4x1 GB I loan from a colleague.

Today I've already got 4 BSOD's. I see there are "new" and have to do with the Creative Audio Driver. I've used the one on the Gigabyte's website:

Realtek HD Audio Driver R3.94 216.93 MB 2014/07/01
Creative SB X-Fi driver 1.00.03 70.19 MB 2014/05/02

The problem with sleeping overnight and resume in the morning I'm gonna test tonight.

Info from WhoCrashed:

(i have also included a new DM Log collector in de attachments from this post)

Code:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 4-8-2015 18:19:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080415-11637-01.dmp
uptime: 00:00:12
This was probably caused by the following module: mbfilt64.sys (MBfilt64+0x1817)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032DB82E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mbfilt64.sys
company: Creative Technology Ltd.
description: Creative Audio Driver
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: mbfilt64.sys (Creative Audio Driver, Creative Technology Ltd.).
Google query: Creative Technology Ltd. IRQL_NOT_LESS_OR_EQUAL

On Tue 4-8-2015 18:19:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:00:12
This was probably caused by the following module: mbfilt64.sys (MBfilt64+0x1817)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032DB82E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mbfilt64.sys
company: Creative Technology Ltd.
description: Creative Audio Driver
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: mbfilt64.sys (Creative Audio Driver, Creative Technology Ltd.).
Google query: Creative Technology Ltd. IRQL_NOT_LESS_OR_EQUAL

On Tue 4-8-2015 14:24:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080415-3900-01.dmp
uptime: 00:00:10
This was probably caused by the following module: mbfilt64.sys (MBfilt64+0x1817)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000327CCA5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mbfilt64.sys
company: Creative Technology Ltd.
description: Creative Audio Driver
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: mbfilt64.sys (Creative Audio Driver, Creative Technology Ltd.).
Google query: Creative Technology Ltd. IRQL_NOT_LESS_OR_EQUAL

Arc · 05 Aug 2015

Please upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

How to Create a System Information File in Windows.

Apparently the BSODs are caused by a realtek driver which is a very often BSOD causer, and not important IMHO. Because I have never got that driver installed, and havent lost anything without it.

Code:

BugCheck A, {0, 2, 1, fffff800032db82e}

*** 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 )

Followup: MachineOwner
---------

This page informs it is included in the driver package:

mbfilt64.sys : 6.10.0.8

And the removal procedure:

--------------------------
Remove Driver:
--------------------------
Windows Vista, Windows7 :

Step 1. Go to Start\Settings\Control Panel.
Step 2. Select [Programs] icon.
Step 3. Select [Programs and Features] icon.
Step 4. Select "Realtek High Definition Audio Driver" and press [uninstall] button.
Step 5. Click on [Yes] to finish the uninstallation.
Step 6. At the end of the procedure, select to restart the system and press [Finish] to complete the uninstallation.

After removal, download and install it from the source page: Realtek

See how it goes.

LiquidBlack NL · 05 Aug 2015

Thanks for your reply Arc! :)

Hopefully it's a good sign I don't get the other BSOD's anymore with this RAM.

I've uploaded the MSINFO32 in the attachment of this post.
I've also removed the driver with the described procedure and installed a new one from this link:
Realtek Definition Audio Codecs
I used 64bits version R2.79 from 2015/6/25.

Edit:
A update: my system is getting the same creative BSOD's with the new realtek driver and also without a realtek driver.

I tried reinstall my pc with the original Dreamspark Windows 7 and it freezes itself in the setup. (did not got any problems with the setup when using the original ram)

So i think my conclusion is: with the other RAM I also get a lot of strange errors and BSOD's. I've already tried another SSD disc and already tried to use the onboard VGA instead of the MSI card.

I think I need to send back my motherboard?

Arc · 05 Aug 2015

If you think that all the possible areas are checked, then if the board is within warranty, go for RMA the board.

LiquidBlack NL · 06 Aug 2015

Yeah the setup is just a few weeks old so I got warranty.
Sending back the MB today :).

I let you guys know how it goes when i get a new one. Thanks for the help so far!

Laith · 06 Aug 2015

Remember to never use counterfeit activation tools, it will ruin the system really bad.

LiquidBlack NL · 06 Aug 2015

Laith said:

Remember to never use counterfeit activation tools, it will ruin the system really bad.

Noted :). Only original DreamSprak editions from now on, no slipstreamed or whatever.

Laith · 06 Aug 2015

Good