Solved Frequent random BSOD, Chrome crashes even after clean format+install

[odattner]

Hi,

Win7 Ultimate, SP1
Core i5 + 4GB RAM (one stick).
Windows on SSD, other files on second HDD.
Memtest ran for a while with no errors. Same for windows memory check and hard disk check.
This is a fairly new computer BTW.

Getting frequent BSOD + crashes (chrome tabs, windows explorer, internet explorer).
Formatted the HD (SDD) reinstalled everything. Same type of problems.
Last few BSOD:
1. PFN_LIST_CORRUPT
Technical Information:
*** STOP: 0x0000004e (0x0000000000000099, 0x000000000006f7d7, 0x0000000000000002,
0x0000000000002656)
*** ntoskrnl.exe - Address 0xfffff80002cc2bc0 base at 0xfffff80002c4d000 DateStamp
0x521ea035

2. MEMORY_MANAGEMENT
Technical Information:
*** STOP: 0x0000001a (0x0000000000005002, 0xfffff780c0000000, 0x0000000000003281,
0x00007fc2fffffffe)
*** ntoskrnl.exe - Address 0xfffff80002c85bc0 base at 0xfffff80002c10000 DateStamp
0x521ea035

3. SYSTEM_SERVICE_EXCEPTION
Technical Information:
*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff80002d6d6c1, 0xfffff8800a41d020,
0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff80002a76bc0 base at 0xfffff80002a01000 DateStamp
0x521ea035

Attached is msinfo file.
The latest memory dump is > 100MB (zipped). I'll wait for another one and upload a minidump.

I'd appreciate any help.

Ori

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[odattner]

Here's the data in the zip file

Attached is the zip file with the data from the grab all command

More info: I tried switching to a different Hard Drive and installing windows there - same problems.

 

[Arc]

If you are using any creative audio card, remove it at first, at least as a test. Then observe if the BSODs are occurring again or not.

If BSODs continue to occur, test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
_____________________________________________________________________________________________

BugCheck 1A, {41201, fffff6800016e890, fb602000566b2867, fffffa8009075090}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )

Followup: MachineOwner
------------------------------------------------------------------------------------------
BugCheck A, {0, 2, 0, fffff80002cd6325}

*** 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
-------------------------------------------------------------------------------------------
BugCheck 4E, {99, 97398, 0, aca18}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

 

[odattner]

No audio card installed (on board audio).
No memory problems. Zero errors.

 

[Arc]

MBfilt64 is used by relatek HD sound driver and creative too. If yours is onboard, then update your onboard sound driver from Realtek.

 

[odattner]

Hi,

Thanks.
I couldn't find any drivers on their web site.
Tried updating through windows device manager and it told me it was up to date.
I disabled it for now. See what happens.
Any other ideas?

Ori

 

[odattner]

Still happening

here's another file from some more recent crashes

 

[Arc]

I hope you ram Memtest 86+ for at least 8 passes to decide it is free of errors.

Now enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[odattner]

Hi,

Thanks... here are a another file with more memory dumps. Driver verifier was enabled as per the instructions.
The last couple of days there have been fewer bugs and crashes but it hasn't been problem free.
The major change from the weekend when it was really really bad to today where it is just a little bad is that I switched the HDD cables between the two HDD (the one for the system and the one for my files). I also moved the memory from slot a to slot b. At the beginning the computer worked with no crashes but then it "started" again so I don't know if this is part of the reason or not.

Anyway, zip file attached.

Ori

 

[Arc]

First point: Verifier is not enabled.

Second point: It is still the audio driver.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8a00176f000, 2, 0, fffff80002cd5e52}

*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
[COLOR=Red]Probably caused by : MBfilt64.sys[/COLOR] ( MBfilt64+1817 )

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

 

[odattner]

Interesting. I thought I enabled the verifier as per the instructions.
Must have done something wrong.
I have a couple of questions:
1. Is the audio driver at fault in all the crashes you looked at?
2. In the device manager there are 2 audio drivers: Intel Display audio and Realtek Hi Definition Audio.
3. If I disable one or both of them (through the device manger) - should it stop the crashes?
4. Looking at the services, there is a "windows audio" service - does that have anything to do with it?

Thanks,

Ori

 

[Arc]

1. Not all, but most of all. The others are not specific about anything.
2. The second one, Realtek is found responsible.
3. Cannot be said with certainty, as the driver will still be present.
4. No. It is different thing, it is the audio service, not any driver that is driving an audio chip.

 

[odattner]

solved

Hi,

Seems to be solved.
Faulty memory (despite passing memtest, etc).
Thanks for all your efforts.

Ori

 

[Arc]

That's good.

Let us know for any further issue