Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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

11 Jan 2013   #1
GCFSA

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.


My System SpecsSystem Spec
.
11 Jan 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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
GCFSA

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
GCFSA

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.
My System SpecsSystem Spec
14 Jan 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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
GCFSA

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
GCFSA

Windows 7 Home Premium 64bit
 
 

Here are the results from the DV check

Thanks in advance
My System SpecsSystem Spec
15 Jan 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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
GCFSA

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
GCFSA

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.
My System SpecsSystem Spec
Reply

 BAD_POOL_HEADER BSOD, not the first time computer has BSOD




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD when starting and loading windows in computer, Bad_Pool_Header
Hello, I never had any big issues on this Acer laptop that I have been using for about a year and half up til now. I was using my laptop for about hour then I got back on it a few hours later and I get a BSOD. The BSOD states that it is a BAD_POOL HEADER. The technical information was 0x00000019...
BSOD Help and Support
Computer BSOD from time to time regardless what I'm doing
I have no idea what to do, I'm not so good with computers so I figured out I could get help from here! PS. My PC BSOD's regardless what I'm doing.
BSOD Help and Support
BSOD with BAD_POOL_HEADER while computer inactive
My Windows 7 64bit PC crashes periodically. Sometimes I get BSOD, and other times it reboots. Most often this happens while it is sitting inactive (but not asleep). The ZIP file from last night, 11-08-12 is attached. The BSOD said BAD_POOL_HEADER. The files saved with SF Diagnostic Tool is...
BSOD Help and Support
New built computer bsod's time to time.stop error 0x000000a
it happens time to time and is usually when i open adobe photoshop,aftereffects. Also i cannot seem to open any kind of games on my new computer like fifa 13 ,nfs etc. I have an i7 3770 and 8 gb ddr3 corsair RAM with 1 tb hdd and motherboard is msi B75MA-P45 and geforce gtx560 for graphics card. my...
BSOD Help and Support
BSOD after computer has been up for some time
Currently: Windows 7 Ultimate x64 Not the original OS of the system Full Retail Age of the computer is about 8 months Age of current installation (at the time of posting) is about 7 hours. Hello there I have been getting BSOD for about 5 days or so. I had Windows 7 x64 professional on...
BSOD Help and Support
BSOD, repaired computer for 9th time, still bsod
hi i am sab, i work in china, i moved her couple of years ago. i bought this computer like 1 years ago. it was working fine but from last few months i frequently get BSOD, i went to fix the computer for 9th times, still stucked with same problem. i guess its the language problem, i can't explain...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

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

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

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App