BSOD regularly

[Blake]

BSOD almost daily ( randomly )

My computer started blue screening randomly since late July.

I already RMA-ed my motherboard and RAM but issue still persist.

Sometimes after the blue screen , when i look at the Windows Experience Index , it says new hardware detected and I have to re-run the assessment to get a new index ( the number that rates ur computer up to 7.9 )

Seems like a hardware issue since I already reinstall my windows a few times. Dump files are attached ty.

 

[Arc]

Hello Blake.

Your crash dumps are not showing any finite probable cause.

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 memtest comes free from errors, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_____________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff8a027b051d0, fffff8a027b051d0, fffbf8a027b051d0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )

Followup: Pool_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8a027b051d0, the pool entry being checked.
Arg3: fffff8a027b051d0, the read back flink freelist value (should be the same as 2).
Arg4: fffbf8a027b051d0, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  hon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800029b26ea to fffff8000287fc00

STACK_TEXT:  
fffff880`0908d5e8 fffff800`029b26ea : 00000000`00000019 00000000`00000003 fffff8a0`27b051d0 fffff8a0`27b051d0 : nt!KeBugCheckEx
fffff880`0908d5f0 fffff800`029b34f1 : 00000000`00000000 fffff8a0`0014bdb0 fffffa80`130cb010 00000000`00000000 : nt!ExDeferredFreePool+0xc96
fffff880`0908d680 fffff880`04051523 : fffff8a0`0014bdc0 00000000`00000000 fffff880`4b677844 00000000`00000799 : nt!ExFreePoolWithTag+0x411
fffff880`0908d730 fffff960`002118c2 : fffffa80`0ffedb50 fffffa80`0ffedb50 00000000`fff44000 00000000`00000020 : dxgkrnl!DxgkEscape+0xc3f
fffff880`0908dab0 fffff800`0287ee93 : fffffa80`0ffedb50 00000000`00000384 00000000`00000000 fffffa80`16ec9f10 : win32k!NtGdiDdDDIEscape+0x12
fffff880`0908dae0 00000000`752e148a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0494e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752e148a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+c96
fffff800`029b26ea cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+c96

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c96

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c96

Followup: Pool_corruption
---------

 

[Blake]

If I RMA-ed my RAM for a new kit, there might still be error?

I will disable the driver thingy to test my computer. Do I have to run it as an administator or it doesn't matter?

And also for the memtest86+ , is it okay to run all the 4 sticks at once together and do a test. If no errors are found , then I won't need to test each stick individually right?

However if errors are found, I will need to follow Part 3 of the guide u posted?

 

[Arc]

Yes, the BRAND new RAM also may have errors.

First run memtest with ALL the RAM sticks .... if errors are shown, then only go for the part 3. But as it is new RAM, simply get it replaced in that case.

 

[Blake]

Yes, the BRAND new RAM also may have errors.

First run memtest with ALL the RAM sticks .... if errors are shown, then only go for the part 3. But as it is new RAM, simply get it replaced in that case.

I took out my GTX 670 FTW just to troubleshoot

I tested the RAM with Memtest86+ , theres no error

I enabled Verifier for 12 hours and used the computer. It was pretty laggy though but I manage to play a game or 2 without BSOD.

I will disable it now and try to use my computer.

If I get a BSOD , i will repost here and we will know my GPU isn't causing the issue