Usually the BAD_POOL_HEADER BSODs are caused by some malfunctioning driver, but no driver is found to be failing there. Moreover, some of the BSODs are saying that those are caused by memory corruption.
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.
If memtest does not show any error, 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.
Let us know the results, with the subsequent crash dumps, if any.
__________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa800260d000, fffffa800260d600, 4600000}
GetPointerFromAddress: unable to read from fffff80002aca100
GetUlongFromAddress: unable to read from fffff80002aca1c0
Probably caused by : memory_corruption ( nt!MiSegmentDelete+b1 )
Followup: MachineOwner
---------
1: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800260d000, The pool entry we were looking for within the page.
Arg3: fffffa800260d600, The next pool entry.
Arg4: 0000000004600000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: fffffa800260d000 Nonpaged pool
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff800029c5cae to fffff80002892bc0
STACK_TEXT:
fffff880`02fffb08 fffff800`029c5cae : 00000000`00000019 00000000`00000020 fffffa80`0260d000 fffffa80`0260d600 : nt!KeBugCheckEx
fffff880`02fffb10 fffff800`02b335c1 : 00000000`00000001 00000000`000800a1 fffffa80`69436d4d fffffa80`04575f10 : nt!ExDeferredFreePool+0x12da
fffff880`02fffbc0 fffff800`028df311 : fffffa80`0260d018 00000000`00000001 00000000`00000000 001d0001`00000631 : nt!MiSegmentDelete+0xb1
fffff880`02fffc00 fffff800`028df1d5 : 00000000`00000000 00000000`00000080 fffffa80`023349e0 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`02fffcc0 fffff800`02b2f2ea : 001d0001`00000027 526d6574`7379535c 74737973`5c746f6f 6972645c`32336d65 : nt!MiDereferenceSegmentThread+0x10d
fffff880`02fffd40 fffff800`028838e6 : fffff800`02a0de80 fffffa80`023513b0 fffff800`02a1bcc0 ffff6fff`efbfbeff : nt!PspSystemThreadStartup+0x5a
fffff880`02fffd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiSegmentDelete+b1
fffff800`02b335c1 33d2 xor edx,edx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!MiSegmentDelete+b1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
IMAGE_VERSION: 6.1.7601.18247
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x19_20_nt!MiSegmentDelete+b1
BUCKET_ID: X64_0x19_20_nt!MiSegmentDelete+b1
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x19_20_nt!misegmentdelete+b1
FAILURE_ID_HASH: {8cd68805-f3e1-e2fb-0bad-babcb406525e}
Followup: MachineOwner
---------