New custom computer BSOD at seemingly random times

Kharma · 20 Jun 2014

I have a new (less than a month old) custom built computer that is throwing BSOD's at random times (multiple times per day). Each time it BSOD's it gives a different error. So far I have received the "Memory Management" and "Bad Pool Header" to list two of them.

I have already run memchk for 5 passes with 0 errors.

Attached in my log collection zip. Any assistance you can provide would be greatly appreciated.

Boozad · 20 Jun 2014

Code:

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000000e88
Arg4: 0000170d00007d10

Code:

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a0052f8e60, the pool entry being checked.
Arg3: fffff8a0052f8e60, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a00531b640, the read back blink freelist value (should be the same as 2).

Run MemTest86+ again to test your RAM. Read the note below on this recommendation.

Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable

Enable Driver Verifier but only enable these options:
Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Warning

Make a System Restore point before enabling Driver Verifier.

Note

Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Report back with any dump files caused by DV.

For testing purposes, uninstall Comodo Firewall and enable Windows Firewall.

Code:

C:\Program Files (x86)\Common Files\COMODO\launcher_service.exe

Kharma · 23 Jun 2014

Thanks for the assistance on this. I ran both. Memtest completed 8 full passes (32 gb of ram takes a while) with 0 errors.

Driver verifier caused BSOD's as soon as windows was rebooted. I had it bluescreen twice and am attaching the DM zip to this post (this zip contains my older dumps as well). Any additional help is appreciated.

Boozad · 23 Jun 2014

I'll get round to looking at these tonight mate, I'm at work for the next several hours.

Kharma · 04 Jul 2014

Any update on the review of the updated files?

derekimo · 04 Jul 2014

I'll step in for Boozad temporarily, he's been pretty busy lately,

Both of your verifier enabled dumps are blaming Comodo,

Code:

Unable to load image \SystemRoot\system32\DRIVERS\CFRMD.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CFRMD.sys
*** ERROR: Module load completed but symbols could not be loaded for CFRMD.sys

I see he asked you to uninstall that already, go ahead and remove it for the time being then try the verifier again.

Boozad · 04 Jul 2014

Apologies Kharma for letting this one slip me by.

Massive thanks Derek, I appreciate that very much mate

derekimo · 04 Jul 2014

You're welcome Gav. :)

Kharma · 07 Jul 2014

I have removed all Comodo applications and the amount of BSOD's has decreased significantly. I just had one that Stated "Memory Management" as the cause. I have already done the test for 8 passes on my Ram with 0 errors. Attached is a new DM log Dump.

Your help is much appreciated.

Kharma · 19 Jul 2014

Uploading new file as I am continuing to have more crashes.