Overclocking in CCC is the worst.. im sorry but its true.. no voltage control.. and a limited oc of the core , if you want to OC higher you have to hack the driver with regedit key to remove the limit.. not so friendly to OC...Originally Posted by Thracks
Why is it our fault that an unsupported overclocking application is breaking your system? We provide supported tools for overclocking in CCC.
Same here anything after 12.4 is a flickering mess.Originally Posted by EyesDilated
I had that same flickering issue trying to update from 12.4 on my unlocked 6950's
I tried 12.6-12.10 and the same thing..ended up reverting back to 12.4 which is running perfectly fine for me
So this is an issue with Afterburner and the way it controls / detects the 2D and 3D clocks? I just tried to overclock my 5850 and had to resort to enabling the unofficial overclock mode on Afterburner; core clock was fine but raising the memory just makes it start doing this. Even resetting the clocks back to default doesn't fix it until reboot (the PC actually rebooted because I let it keep going once.) Thought I maybe stressed the card too much after all the furmark testing.Originally Posted by tsm106
Check the thread in my sig, the 2nd post deals with the flicker you are experiencing. Check the video I made it should look familiar to you.
Read my sig thread and you will understand why it's happening in more detail. But in essence AMD changed the way Powerplay works, or that is how invasive it is and severely impacted its compatibility with unofficial overclock methods. The bypass method works so read it it and give it a try.Originally Posted by Someguy316
Quote:
So this is an issue with Afterburner and the way it controls / detects the 2D and 3D clocks? I just tried to overclock my 5850 and had to resort to enabling the unofficial overclock mode on Afterburner; core clock was fine but raising the memory just makes it start doing this. Even resetting the clocks back to default doesn't fix it until reboot (the PC actually rebooted because I let it keep going once.) Thought I maybe stressed the card too much after all the furmark testing.Originally Posted by tsm106
Check the thread in my sig, the 2nd post deals with the flicker you are experiencing. Check the video I made it should look familiar to you.
Going to go through the Sapphire Trixx thread but that made my PC lock up when I changed the clocks though it could be because I was using CCC to overclock before (was still open with Overdrive disabled.) I have a Sapphire HD 5850 Vapor-X so I can't adjust the voltage on my card with either programs.
Edit: Forgot to mention; I don't really want to get rid of PowerPlay as I leave my PC on.
Oh, I see that part now, thanks; I'll give it a try in a while as I was messing around with my CPU after updating the motherboard BIOS.Originally Posted by tsm106
Read my sig thread and you will understand why it's happening in more detail. But in essence AMD changed the way Powerplay works, or that is how invasive it is and severely impacted its compatibility with unofficial overclock methods. The bypass method works so read it it and give it a try.
Are you kidding me. TSM I both love you and absolutely despise you right now because of how long I've been fiddling around with profiles etc in CCC (Have spent at least 11 hours on it) and now you come and tell me this.
I can confirm that I have not had this problem using CCC. Now if AMD would supply adequet fan ramp rates I wouldnt need any 3rd party softwar:thumb:eOriginally Posted by Thracks
Why is it our fault that an unsupported overclocking application is breaking your system? We provide supported tools for overclocking in CCC.
I don't think so, for me it was mostly to remove any compatibility problems on overclocking.Originally Posted by Crynet
I'm running CCC 12.8 stable with no flickering, but could be different system to system, does disabling CCC at startup resolve flickering in newer drivers
