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


27 Aug 2010   #1
jalebi

Windows 7 x64 Professional
 
 
Bad_pool_header

I got a BSOD while playing a game and now the computer is having issues booting up. I have managed to boot into safe mode and have created a Windows_NT6_BSOD_jcgriff2 zip file and I've also included my minidump. Please help me diagnose this problem.

OS: Windows 7 Ultimate x64 Retail
OS Age: 2 weeks
PC Age: 2 weeks

EDIT: I forgot to attach the files



My System SpecsSystem Spec
.

27 Aug 2010   #2
richc46

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

STOP 0x00000019: BAD_POOL_HEADER Usual causes: Device driver

Code:
 icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\082810-19000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
Debug session time: Fri Aug 27 19:34:48.152 2010 (GMT-4)
System Uptime: 0 days 1:57:49.822
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa8004093690, fffffa8004093750, 40c0005}
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+5a13 )
Followup: MachineOwner
---------
0: 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: fffffa8004093690, The pool entry we were looking for within the page.
Arg3: fffffa8004093750, The next pool entry.
Arg4: 00000000040c0005, (reserved)
Debugging Details:
------------------
 
BUGCHECK_STR:  0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb00e0
 fffffa8004093690 
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ShippingPC-BmG
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002bab6d3 to fffff80002a78740
STACK_TEXT:  
fffff880`09576848 fffff800`02bab6d3 : 00000000`00000019 00000000`00000020 fffffa80`04093690 fffffa80`04093750 : nt!KeBugCheckEx
fffff880`09576850 fffff880`03667a13 : fffff8a0`09098a70 fffff880`0487a0d1 00000000`5958504b fffffa80`05d25000 : nt!ExDeferredFreePool+0x12c4
fffff880`09576900 fffff8a0`09098a70 : fffff880`0487a0d1 00000000`5958504b fffffa80`05d25000 00000000`00000001 : atikmpag+0x5a13
fffff880`09576908 fffff880`0487a0d1 : 00000000`5958504b fffffa80`05d25000 00000000`00000001 fffff8a0`09098a70 : 0xfffff8a0`09098a70
fffff880`09576910 fffff880`048ad0f0 : fffffa80`05d25000 00000000`00000000 fffff880`095769b0 00000000`00000000 : dxgkrnl!DXGADAPTER::AcquireDdiSync+0xc9
fffff880`09576950 fffff880`048b1205 : fffff8a0`09098a70 00000000`00000000 00000000`00000000 fffff8a0`003ea000 : dxgkrnl!DXGADAPTER::DdiDestroyAllocation+0x50
fffff880`09576980 fffff880`048b054b : fffff8a0`003ea000 00000000`00000000 fffff8a0`00000000 00000000`00000003 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x83d
fffff880`09576a70 fffff880`048b618f : 00000000`00000799 00000000`00000001 fffff880`09576ca0 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`09576ac0 fffff960`001cb336 : 00000000`0956e7d0 ffffffff`c002df00 00000000`fff9e000 00000000`000007d3 : dxgkrnl!DxgkCreateAllocation+0x40b
fffff880`09576bf0 fffff800`02a77993 : fffffa80`043dab60 00000000`00000f68 fffff880`00000000 fffffa80`03d4e2d0 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`09576c20 00000000`7395119a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0956e788 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7395119a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
atikmpag+5a13
fffff880`03667a13 ??              ???
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  atikmpag+5a13
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e
FAILURE_BUCKET_ID:  X64_0x19_20_atikmpag+5a13
BUCKET_ID:  X64_0x19_20_atikmpag+5a13
Followup: MachineOwner
---------
Offending driver per report
Atikmpag.sys
file descriptionProductname:
AMD driver
Company: Advanced Micro Devices, Inc.
File size: Various

Install current driver.
My System SpecsSystem Spec
27 Aug 2010   #3
jalebi

Windows 7 x64 Professional
 
 

I haven't installed any new drivers for a few days at least. Could it have been the game that triggered this problem? I've been playing it (Batman Arkham Asylum) for a few days and nothing has happened till now.

How do I identify the faulty drivers (probably HDD right?) and fix the problem accordingly?

Thanks
My System SpecsSystem Spec
.


27 Aug 2010   #4
richc46

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

You read my post before I was done. Read again.

I did not give you a full report. The driver was reported as bad. If it happens again, repost and I will give you a detail analysis.
My System SpecsSystem Spec
27 Aug 2010   #5
jalebi

Windows 7 x64 Professional
 
 

Quote   Quote: Originally Posted by richc46 View Post
You read my post before I was done. Read again.

I did not give you a full report. The driver was reported as bad. If it happens again, repost and I will give you a detail analysis.
Sorry, the full post didn't display.

I'm not quite understanding if its the video card drivers (ATI) or the CPU drivers (AMD) since your post mentions both. Do I just try and install the newest drivers?

In case it is of any use, my graphics card is an ATI Radeon HD 4850 and my CPU is an AMD Athlon II X3 440 (3.0ghz).

Thanks for your help so far
My System SpecsSystem Spec
27 Aug 2010   #6
reventon

Windows 7 x64, Windows XP SP3, Fedora
 
 

The offending driver is part of the graphics driver package and can be updated from here - Graphics Drivers & Software
My System SpecsSystem Spec
27 Aug 2010   #7
richc46

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

I have a list of drivers and the mfg.
This is the driver that has to be replaced
Atikmpag.sys

According to my information this is the Company that manufactures it

Productname: AMD driver
Company: Advanced Micro Devices, Inc.
If you do have additional drivers that are outdated, by all means update them too.

Thanks for the back up Reventon.
My System SpecsSystem Spec
28 Aug 2010   #8
jalebi

Windows 7 x64 Professional
 
 

I reinstalled the newest ATI drivers but the computer BSODed again overnight. Could it be a compatibility issue with some other hardware?
My System SpecsSystem Spec
28 Aug 2010   #9
reventon

Windows 7 x64, Windows XP SP3, Fedora
 
 

Upload the latest Minidump file from C:\Windows\Minidump please. You will have to copy it to the desktop before zipping it up.
My System SpecsSystem Spec
28 Aug 2010   #10
jalebi

Windows 7 x64 Professional
 
 

Here's the output of a newer test
My System SpecsSystem Spec
Reply

 Bad_pool_header




Thread Tools



Similar help and support threads for2: Bad_pool_header
Thread Forum
Bsod bad_pool_header BSOD Help and Support
Bad_pool_header BSOD Help and Support
Bad_pool_header Drivers
Bad_pool_header Hardware & Devices
Bad_pool_header BSOD Help and Support
Bad_pool_header (19) Hardware & Devices

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 06:06 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App