AMD CCC 13.12 Bad Pool Header

polarissucks01

Honorable
Sep 22, 2012
53
0
10,630
Ever since updating the Catylist control Centre to 13.12 I keep getting BSOD and they say bad pool header. Did a check disk, a system file check and a memory test. All came back clean. Istalled no other drivers besides 13.12. Anyone else hear about this. Any other possible issues?


On Sun 12/22/2013 4:14:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122113-6156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x19 (0x3, 0xFFFFE00004907320, 0x300000000000000, 0xFFFFE00004907320)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12/22/2013 4:14:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x14CA6)
Bugcheck code: 0x19 (0x3, 0xFFFFE00004907320, 0x300000000000000, 0xFFFFE00004907320)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Thanks,
 
Solution
Here is from a Microsoft user.

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

Dont forget to upload any further DMP files (especially those when verifier is running)

If you are overclocking anything reset to default before running these tests.
In other words STOP!!! If you dont know what this means you probably arent

1-Memtest. (yes I do know you have run a memory check just not this one for 6-8passes)
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember...

Blaise170

Honorable
Here is from a Microsoft user.

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

Dont forget to upload any further DMP files (especially those when verifier is running)

If you are overclocking anything reset to default before running these tests.
In other words STOP!!! If you dont know what this means you probably arent

1-Memtest. (yes I do know you have run a memory check just not this one for 6-8passes)
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.

2-Driver verifier
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Here is the procedure:
Go to Start and type in "verifier" (without the quotes) and press Enter
Select "Create custom settings (for code developers)" and click "Next" (or Type "verifier /standard /all" (no quotes) if you want to verify all of them (this will slow your computer down))
Select "Select individual settings from a full list" and click "Next"
Select everything EXCEPT FOR "Low Resource Simulation" and for win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Further Reading
http://support.microsoft.com/kb/244617

About Driver Verifier
Driver Verifer information driver verifier Windows Vista - Microsoft Search
Driver Verifier issues within Vista/ Windows 7 http://support.microsoft.com..default.aspx?+verifier1&res=20
Driver Verifier Special Pool Feature http://support.microsoft.com/kb/188831
MS MVP- Windows Expert-Consumer 2009-2013,MCC 2013
Wanikiya & Dyami--Team ZigZag
 
Solution

AdamG

Distinguished
Dec 21, 2013
85
11
18,545
I got bad_pool_header before aswell, had left my RAM timed at mboards default timing and not set it correctly manually, caused me solid year or two of bad pool header blue screens, after fixing the timing I was able to avoid the issue but the damage was done to the ram modules and they needed to be rma'd, I'm sure this could probably happen with a bunch of different scenarios and I'm not advanced in the technical aspects like bug codes, but I figured since I just signed up and seen this thread I'd reply my experience with that same blue screen message, probably not likely relevant to your situation though. I had nothing but trouble with catalyst software tbh, is primarily why I went intel this time around, just bunk pricing in comparison did make me wish I went AMD again, lol =P