Windows 7 Forums


Windows 7: BAD_POOL_HEADER BSOD, not the first time computer has BSOD

11 Jan 2013   #1

Windows 7 Home Premium 64bit
 
 
BAD_POOL_HEADER BSOD, not the first time computer has BSOD

Hey guys,

I recently have been getting some BSODs but this is the first 'BAD_POOL_HEADER' I would like to ask for some help in resolving this issue. Thankyou very much, attatched is my minidumps of ALL my previous BSODs.




Thanks in advance.

GCFSA


Edit: my computer is a HP Pavillion DV6 3132tx.
Attached Files
File Type: zip BSOD Log Files.zip (310.8 KB, 4 views)
My System SpecsSystem Spec

11 Jan 2013   #2
Arc

Windows 7 Home Premium 64 Bit SP 1
 
 

Hello GCFSA.
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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00e8f25a0, The pool entry we were looking for within the page.
Arg3: fffff8a00e8f27c0, The next pool entry.
Arg4: 0000000005220010, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a00e8f25a0 Paged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800037f6cae to fffff800036cbfc0

STACK_TEXT:  
fffff880`03d70b68 fffff800`037f6cae : 00000000`00000019 00000000`00000020 fffff8a0`0e8f25a0 fffff8a0`0e8f27c0 : nt!KeBugCheckEx
fffff880`03d70b70 fffff800`039ace83 : fffff800`038c9600 fffff800`039ab730 fffff800`624e4d43 fffff880`04c5ee90 : nt!ExDeferredFreePool+0x12da
fffff880`03d70c20 fffff800`039aba6e : fffff8a0`15433cc0 00000000`361076d3 fffff8a0`00bef410 00000000`00000000 : nt!CmpFreeKeyControlBlock+0x123
fffff880`03d70c50 fffff800`036d5641 : fffff800`038692d8 fffffa80`03cebb50 00000000`00000000 fffffa80`03cebb50 : nt!CmpDelayDerefKCBWorker+0x33e
fffff880`03d70cb0 fffff800`03962e5a : fffff880`03d6c040 fffffa80`03cebb50 00000000`00000080 fffffa80`03cd7b30 : nt!ExpWorkerThread+0x111
fffff880`03d70d40 fffff800`036bcd26 : fffff880`03b67180 fffffa80`03cebb50 fffff880`03b720c0 fffff800`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03d70d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpFreeKeyControlBlock+123
fffff800`039ace83 e90effffff      jmp     nt!CmpFreeKeyControlBlock+0x36 (fffff800`039acd96)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!CmpFreeKeyControlBlock+123

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

Followup: MachineOwner
---------
Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
11 Jan 2013   #3

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by Arc View Post
Hello GCFSA.
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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00e8f25a0, The pool entry we were looking for within the page.
Arg3: fffff8a00e8f27c0, The next pool entry.
Arg4: 0000000005220010, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a00e8f25a0 Paged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800037f6cae to fffff800036cbfc0

STACK_TEXT:  
fffff880`03d70b68 fffff800`037f6cae : 00000000`00000019 00000000`00000020 fffff8a0`0e8f25a0 fffff8a0`0e8f27c0 : nt!KeBugCheckEx
fffff880`03d70b70 fffff800`039ace83 : fffff800`038c9600 fffff800`039ab730 fffff800`624e4d43 fffff880`04c5ee90 : nt!ExDeferredFreePool+0x12da
fffff880`03d70c20 fffff800`039aba6e : fffff8a0`15433cc0 00000000`361076d3 fffff8a0`00bef410 00000000`00000000 : nt!CmpFreeKeyControlBlock+0x123
fffff880`03d70c50 fffff800`036d5641 : fffff800`038692d8 fffffa80`03cebb50 00000000`00000000 fffffa80`03cebb50 : nt!CmpDelayDerefKCBWorker+0x33e
fffff880`03d70cb0 fffff800`03962e5a : fffff880`03d6c040 fffffa80`03cebb50 00000000`00000080 fffffa80`03cd7b30 : nt!ExpWorkerThread+0x111
fffff880`03d70d40 fffff800`036bcd26 : fffff880`03b67180 fffffa80`03cebb50 fffff880`03b720c0 fffff800`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03d70d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpFreeKeyControlBlock+123
fffff800`039ace83 e90effffff      jmp     nt!CmpFreeKeyControlBlock+0x36 (fffff800`039acd96)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!CmpFreeKeyControlBlock+123

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

Followup: MachineOwner
---------
Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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   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   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   Tip

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

Thankyou for your reply, I will run DV and post any results in the next 48 hours.
My System SpecsSystem Spec
.


14 Jan 2013   #4

Windows 7 Home Premium 64bit
 
 

Sorry about the late reply, I have done the DV check and have come up with one BSOD. here are the new dump files

Thankyou in advance.
Attached Files
File Type: zip BSOD Log Files.zip (336.3 KB, 2 views)
My System SpecsSystem Spec
14 Jan 2013   #5
Arc

Windows 7 Home Premium 64 Bit SP 1
 
 

Please make it sure that you have enabled DV properly. Follow it, step by step.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
14 Jan 2013   #6

Windows 7 Home Premium 64bit
 
 

Thankyou for your reply, I'll re run DV and post the results.
My System SpecsSystem Spec
15 Jan 2013   #7

Windows 7 Home Premium 64bit
 
 

Here are the results from the DV check

Thanks in advance
Attached Files
File Type: zip BSOD DV File.zip (26.1 KB, 4 views)
My System SpecsSystem Spec
15 Jan 2013   #8
Arc

Windows 7 Home Premium 64 Bit SP 1
 
 

This one is verifier enabled, for sure. But, not showing a driver as a probable cause.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff9800ab9cf98, 2, 0, fffff80003b362b9}

Probably caused by : ntkrnlmp.exe ( nt!ViPendingCompleteAfterWait+49 )

Followup: MachineOwner
---------
So the root of the problem is in somewhere else.

A virus scanner amy sometimes cause such a situation. Uninstall Kaspersky using Kaspersky Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install those, and then run full system scans with both of them, one by one.

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.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
My System SpecsSystem Spec
15 Jan 2013   #9

Windows 7 Home Premium 64bit
 
 

Thanks for your quick reply, will run all the tests and post results. However, it may take me 2-3 days to complete them, until then, thankyou very much for your help so far.

Gabriel
My System SpecsSystem Spec
16 Jan 2013   #10

Windows 7 Home Premium 64bit
 
 

I have run the virus/malware checks and they've come up with a few things detected, however, they wre just a few programs and were perfectly safe.

Then I proceeded to do the ram check, it came back with 13 errors, I've attatched a picture of it.

I have not yet run the GPU and CPU checks, should I or should I just change the ram stick?


Thankyou very much.
Attached Thumbnails
BAD_POOL_HEADER BSOD, not the first time computer has BSOD-imag0371.jpg  
My System SpecsSystem Spec
Reply

 BAD_POOL_HEADER BSOD, not the first time computer has BSOD problems?



Thread Tools



Similar help and support threads for: BAD_POOL_HEADER BSOD, not the first time computer has BSOD
Thread Forum
Solved BSOD with BAD_POOL_HEADER while computer inactive BSOD Help and Support
New built computer bsod's time to time.stop error 0x000000a BSOD Help and Support
BSOD after computer has been up for some time BSOD Help and Support
BSOD, repaired computer for 9th time, still bsod BSOD Help and Support
HELP!! BSOD every time the computer is booted BSOD Help and Support


All times are GMT -5. The time now is 09:53 AM.


Seven Forums Android App Seven Forums IOS App Follow us on Facebook

Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32