Posted: December 19th, 2013 | Author: kn00tcn | Filed under: Hardware, Software, Tips/Tutorials
Tags: annoyance, ATI, catalyst, CCC, drivers, fix
Looks like the Catalyst version isn’t being correctly stored for some users on the recent 13.12 WHQL release. This has happened before and it’s absolutely nothing to be alarmed about. The only time this would even matter is when a game or application is using this number as a version check such as Battlefield 4, but that is a problem in itself as you’ll notice that this number is merely a registry string.
As a user, all you need to do to change the number is to go into the registry like the example shown above. You can see how you can put any text in there. Many applications in turn read that string and I say it’s poor practice on their part.
The correct driver version number to look at is the packaging version. You can even see the date in its numbers! This is the only true way to tell if your driver has been installed. You could also simply look at the dates of the driver .DLL files. I can’t believe how many people are falling for this in forums, they’re wasting a whole day reinstalling things, it’s ridiculous. Few people seem to bother with any real (not to mention FAST and EASY) troubleshooting, ironic when they do it right with hardware issues. You don’t replace the tower if a component is acting funny, software is no different.
By the way, the Nvidia Forceware driver is the same. It also uses a string for the basic number that many applications read.
Last Modified: December 19th, 2013
Posted: February 14th, 2013 | Author: kn00tcn | Filed under: Hardware, Tips/Tutorials
Tags: annoyance, ATI, CAPs, CCC, drivers, fix, profiles
So a few months ago, maybe when 12.10 CAP 1 came out, you may have noticed some of the AMD pre-defined crossfire profiles do not appear anymore in CCC (and you know they used to be there). What seems to be happening is that CCC is falling back to the CAP that came with the currently installed driver, which is located in the system folders of Windows.
This is certainly a problem for legacy users stuck on a driver branch and default CAP made in April 2012. Hawken for example only appeared in later CAPs and you need to tell CCC to load the profile since it doesn’t match the game exe.
So what’s the solution? Might as well overwrite the driver CAP with the latest one since we know that’s what CCC is loading.
Let’s start with renaming atiapfxx.blb in your system folders of Windows: C:\Windows\SysWOW64 and C:\Windows\System32. Just put an -old at the end or something so that you can rename back if there is a problem.
Install the latest CAP then go to its folder, something like C:\Program Files (x86)\ATI Technologies\Application Profiles\. Copy atiapfxx.blb and paste it into the two system folders from earlier.
Restart your system and now your CCC will display the new profiles again.
There was a related bug posted on forums where ALL pre-defined profiles were missing for some users of newer cards. I’m not sure if this method can also fix that issue as I’ve never ran into it.
Last Modified: February 14th, 2013