• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

"Bad Pool Header" BSOD after installing CCC

M

Mohonri

Supreme [H]ardness
2FA
Joined
Jul 29, 2005
Messages
5,773
So I'm setting up a Radeon 5450. When I installed the 12.3 drivers, I got a page fault BSOD every time I got to the desktop. 12.2 drivers refused to install, and 12.1 (and earlier) drivers give me a "BAD_POOL_HEADER" BSOD on boot.

If I install only the driver, without CCC, it seems to work, but Windows doesn't detect a monitor attached to the DVI port. So I kinda need CCC. I read that there might be a hardware problem with my RAM (and I'm running memtest right now--no errors yet)

Has anyone else run into this, and been able to solve it?
 
yeah definitely sounds ram related or os related.. had a similar problem with my ram though not with CCC specifically(different program) all 4 sticks tested fine, pulled out 2 of them and magically worked fine with the program. but since i don't use that program anymore i put them back in and they have been fine for almost 3 years now, never could find the exact reason but it was something it didn't like about those two sticks.

you could try pulling 1 or 2(depending on how many you have) and see if that solves it or not or try alternating them.
 
Did you ever find a solution to this problem? I'm trying to update Catalyst from 11.12 to 13.4 and I get a BAD_POOL_HEADER BSOD shortly after reaching the desktop. System seems perfectly stable under 11.12. A few months ago I tried a 12.something version of Catalyst and the result was exactly the same. Posted the problem on the AMD forums (http://forums.amd.com/game/messageview.cfm?catid=454&threadid=167592&forumid=11), only suggestion so far is to turn off the overclock which has been stable for years. Thanks!
 
Yeah, eventually I stuck with an older driver (6.14.10.7267) and it seems to be working.
 
You must log in or register to reply here.
Back
Top