My PC was working fine with my R9 280X card and AMD drivers v14.4 under Windows 8 x64. The Catalyst Control Centre (CCC) is set to load on start-up but no CCC notifcation now appears on the task bar. It seems CCC is not loading at start-up although all options are set for it to load. I've unistalled the drivers and CCC and reinstalled them but still have the same problem. CCC works fine when launched manually. Any ideas?
My PC was working fine with my R9 280X card and AMD drivers v14.4 under Windows 8 x64. The Catalyst Control Centre (CCC) is set to load on start-up but no CCC notifcation now appears on the task bar. It seems CCC is not loading at start-up although all options are set for it to load. I've unistalled the drivers and CCC and reinstalled them but still have the same problem. CCC works fine when launched manually. Any ideas?
I have same problems with same drivers in Win10 but in 8.1 works like it should. Do you have AMD Catalyst Control Center in right click menu on the desktop, if you do it's running but not showing on Taskbar. Is there a reason you are using 14.4 drivers instead of newer 14.9 ?
Catalyst Control Center is shown in right click menu - it loads in abput 2 seconds when I select it and shows up in the notifcation area. It works fine once started but isn't loading at start up as it should. I'm using v14.4 since I have Windows 8 x64 - v14.9 is for Windows 8.1 x64. I'll do a clean install of drivers to see if that works. If not, I'll do the Windows 8.1 / AMD Drivers v14.9 update an see if that cures the problem.
"Driver Sweeper" is what I use in safe mode for cleaning up display drivers. There could be some problems with permissions with CCC too, which are not letting it display on Taskbar.
I completely removed all AMD drivers & CCC and reinstalled them but this didn't work.
I found CCC was set to start by command "C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\amd64\CLIStart.exe" MSRun located in the following registry key:
It appears for some reason clistart.exe was being initiated from the wrong place in the registry. I also noticed another autostart program in the same registry location which started working when I moved it. I've no idea why this happened but all is now working.
