WhoCrashed reports 0x1000007E, 0x3B, 0x50…, with verifier: 0xC4

[huffcs]

WhoCrashed reports 0x1000007E, 0x3B, 0x50…, with verifier: 0xC4

I am at a loss for anything more to try and pin this system's problem(s) down. I have run WhoCrashed (home use / free version) after several BSODs and get seemingly random causes. I was having a problem with an earlier system, so I replaced the mobo, cpu, video, power supply, disks, ran memcheck for multiple passes on both pairs of dimms as individual pairs and as a set of 4 dimms, ran disk diagnostics, and then did clean install on new SDD with tested HD for user data. I have run DriverDoc to check (and update) drivers, but updates didn't fix anything, AFAIK. I have run Windows Update, and again, no help. These have all been re-run several times.

 

[Arc]

Hi huffcs.

Disable Driver Verifier. This issue may not be driver caused, as per the verifier recorded bugchecks.

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 result.

 

[huffcs]

Ran Win7 memory test for 4+ passes in addition to 13+ passes of Memtest86+ with no errors found by either.

 

[Britton30]

You may have a bad SSD even if it's new. Check to see if there is a firmware update for it, if so update following SanDisk instructions.
You could test by installing w7 on the HDD. Also make sure the SATA driver are up to date and the SSD is attached via SATA_0 or SATA_1, which ever you have.

 

[huffcs]

Strange... Got notified of message from Arc, but I don't see it in the thread. Got notified again (before accessing thread) of message from Britton30 after that, even though supposedly I shouldn't get notified about that one because I hadn't accessed the thread yet. Weird.

Anyway, here's what happened after I read Arc's reply:
1) With no applications running, went through Control Panel > System > System Protection to create a new restore point and exited after successful creation.
2) Attempted to launch Firefox and got a BSOD instead.
3) After reboot, launched Firefox successfully, read HowTo on Driver Verifier setup and performed steps as directed.
4) Closed Driver Verifier setup and Firefox, and then rebooted.
5) Got a BSOD before reaching login dialog, rebooted and got another one.
6) Booted into safe mode and turned DV off.
7) Rebooted system normally to report findings.

While I only saw three BSODs today, there are more minidumps than that in C:\Windows\Minidump with today's date, so I attached all of them. I was also going to include C:\Windows\MEMORY.DMP, but even zipped up it is too big (.zip = 64MB), but I'll keep it around in case it is wanted and can be supplied another way.


Regarding Britton30's message, I run Solvusoft's DriverDoc at least daily and it reports (now, anyway) that all drivers are up-to-date.
I will investigate:
1) Whether it is only reporting that the drivers in use are current and the SSD vendor (SanDisk) has a better/newer driver available,
2) If there is any firmware for the SSD that might need updating,
3) If there is any firmware/BIOS updates I may have missed from ASRock for the mobo,
and I will verify that the SSD is attached to the first SATA-III port on the mobo.

 

[huffcs]

P.S. Since WhoCrashed pointed a finger at mbfilt64.sys, I will also see if I can find anything about that or any updates/replacements.

 

[Arc]

For mbfilt64.sys, you need to update the realtek audio driver.

 

[huffcs]

Downloaded driver from realtek website and also from ASRock driver support page for mobo. Ran kdiff3 against existing mbfilt64.sys in c:\windows\system32\drivers vs. ones extracted from each of these two downloads and found them binary matches. Also ran MD5 hashes, which also matched. Does not seem there is a newer version of this file available. Also, the version number of the realtek audio driver from the ASRock website is the same as that installed in this system. I'm not sure if there is anything to be gained by figuring out how to rip out the whole audio driver set and reinstalling from the download version instead of the version supplied on the mobo support CD/DVD. If you think there is, I'd appreciate any suggestions on how this should be done (in case there are good/bad ways to do it -- my luck is always to find the most complicated and error-prone way to get it done when I don't ask for help!).

 

[huffcs]

Checked with SanDisk website and installed their SSD Dashboard tool. Firmware verified up-to-date and SMART reported no problems.

 

[huffcs]

Verified SSD connected to SATA-III port supported by Intel B75 chipset SATA3_0, not either of the two SATA-III ports supported by the ASMedia ASM1061. This means that the SSD, HD, and CD/DVD drive are all supported by the Intel B75 chipset. Don't know if that's good/bad -- suspect not important.

 

[huffcs]

Still crashing, Still don't have a clear root cause

Been on vacation awhile. System still crashing and still haven't found any smoking guns. WhoCrashed routinely reports:
"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 that cannot be identified at this time."

 

[Arc]

If you want to report a BSOD, you always have to upload the data following the Blue Screen of Death (BSOD) Posting Instructions.