Sign in with
Sign up | Sign in
Your question

An odd Catalyst Control Center problem

Tags:
  • Radeon
  • Catalyst
  • Graphics
Last response: in Graphics & Displays
Share
January 14, 2012 4:46:10 PM

As the title says, I have an odd problem with CCC.

It will not open, but it is running, and I can change some settings with the sidebar menu in the bottom right, but when I try and open CCC it just gives me the hourglass for about 15 seconds and then disappears. A quick check of processes with the Task Manager shows that it is clearly running, the window just never pops up.

I have re-installed both CCC and my drivers several times, making sure to re-boot between each step of the cleaning process. I've tried multiple solutions from around the web, from looking for the CCC GAC tokens (which aren't there), to, again, completely uninstalling and using driver cleaner and CCleaner to make sure they are completely off my comp.

Nothing else is wrong, CCC's main window just refuses to load.

I'm running with 2x5770's Crossfired, which is one of the reasons I wanted it to open, as Crossfire has turned itself off somehow. I'm also using the 11.12 drivers from AMD.

Any help is very much appreciated, and thanks in advance.

More about : odd catalyst control center problem

January 14, 2012 4:55:07 PM

Downloading, I'll see if this helps.
m
0
l
January 14, 2012 5:23:49 PM

Well, it re-enabled Crossfire, but the window still won't open. So very odd.
m
0
l
January 15, 2012 2:02:42 AM

I have had that problem sometimes with my cf 5770's.

However usually if i reboot it fixed the problem. You could try using 11.11 Drivers.

I havent switched to the 11.12 yet as 11.11 is working fine for me. Also make sure your running driver sweeper after you uninstall the 11.12 Drivers
m
0
l
January 16, 2012 1:42:47 AM

It's not the drivers or crossfire that's got me confused, it's CCC's refusal to open up it's main window.

I did get a .net error when I tried one of the other options in it, specifically when I tried to open up the About...

Maybe it's a .net problem.
m
0
l
!