Buggar i Catalyst lösningar och worarounds.

Här är en bra tråd där man listar kända buggar i Catalyst, man får också lösningar till en del.
http://hardforum.com/showthread.php?t=1559534

1. OpenGL Extension Limit
2. PowerPlay Downclocking
3. DXVA GUI Artifacting
4. 6400k Glitch
5. Cursor Corruption
6. ATi Overdrive Idle Clockspeed
7. CCC Profiles are Not Properly Applied
8. Cursor Lag
9. Slow Display Mode Switching

--- Klipp från tråden ------------------------------------------------------------------------------------------------
Current standings:
- 9 Bugs Total
- 3 Resolved Bugs
- 3 Moderate Unresolved Bugs
- 3 Critical Unresolved Bugs

1. OpenGL Extension Limit
Quote:
Symptoms:
Older OpenGL games (such as those based on the Quake III engine) crash immediately upon launch.

Causes:
AMD’s has recently added more OpenGL extensions. The drivers don’t enable an extension limit for these older games, they can’t handle the increased count, and crash.

Workarounds:
a. Rename the game's executable to quake3.exe. This may force Catalyst Control Center to detect the game and set an OpenGL extension limit.
b. Catalyst 10.4 was one of the last driver revisions before they increased the number of extensions. Place atioglxx.dll from Catalyst 10.4 into the same folder as the executable of the game you’re having trouble with. It should load the older DLL from the game folder and run correctly.

Official fix:
This may have been resolved in 11.1a (though it isn't noted in the changelog), and remains resolved in 11.2

Quake III, Return to Castle Wolfenstien, and Alice are all confirmed working. If you still have a game that requires a fix listed in the Workarounds section, let me know.

2. PowerPlay Downclocking
Quote:
Symptoms:
a. GPU clockspeed is set below normal 2D clocks when a hardware accelerated video is playing or paused (includes DXVA accelerated and Flash video).
b. GPU clockspeed will not scale up to 3D clocks when such a video is playing or paused.
c. Being stuck below 2D clockspeeds leads to a massive performance hit.
d. Secondary displays flicker or jitter every time you open or close such a video.

Causes:
When the HD5000 series was first released, PowerPlay scaled vRAM clockspeed. It was discovered shortly thereafter that secondary displays flicker or jitter momentarily while vRAM clockspeed stabilizes at a new value. To remedy the flickering, recent drivers are supposed to keep the vRAM at full 3D clocks at all times. (If the clockspeed never changes, the secondary displays don't flicker). Core clock is still allowed to scale up and down normally.

Unfortunately, they forgot to handle one of the PowerPlay states. Specifically, the one that kicks-in when you launch any kind of hardware accelerated video. The card reverts to its old behavior and sets the lower vRAM clockspeed defined in its video BIOS for that PowerPlay state. The change in clockspeed causes displays to flicker momentarily. Performance drops harshly in 3D applications because the card isn't allowed to use 3D clockspeeds with that video open.

Workaround:
The only current way to work-around this driver bug is to modify the BIOS on your graphics card. The basic procedure involves dumping your current BIOS with ATi WinFlash, editing UVD Clock manually using Radeon BIOS Editor (Match UVD clocks and voltage to 3D clocks for your card), then flashing the modified BIOS back to your card with ATi WinFlash again.

I've gone ahead and pre-modified the BIOS for the HD5850 and HD5870. These are for reference model cards ONLY; if you have a non-reference design, you'll have to modify your video BIOS yourself.

Reference HD 5850 pre-mod BIOS - Updated 1/25/2011
Reference HD 5870 pre-mod BIOS - Updated 1/25/2011

- These BIOS are directly from ATi, they already have the DisplayPort voltage fix.
- UVD clock has been modified to full 3D clocks. This resolves issues with hardware accelerated video causing monitors to flicker, as well as 3D performance issues.

Official fix:
None. Unresolved as of Catalyst 11.2

3. DXVA GUI Artifacting
Quote:
Symptoms:
You may experience artifacting within the Windows Media Center user interface while playing a DXVA accelerated video on some ATI cards.

Causes:
Specific cause is unknown. The bug was introduced in the most recent few driver releases (confirmed in 10.9 and 10.10 on an HD4200).

Workaround:
Use older video drivers. Catalyst 10.4a are known not to have this issue.

Official fix:
Resolved as of 11.1, though the fix is not noted in any changelog

4. 6400k Glitch
Quote:
Symptoms:
You may notice a reddish hue to your monitor(s) after updating to Catalyst 10.10. This reddish hue may stick even after downgrading to older drivers or updating to newer ones.

Causes:
Catalyst 10.10 sets your display's color temperature to 6400k instead of 6500k, this is warmer (meaning redder) than normal. This setting does not get reset back to its normal value by most drivers updates.

Workaround:
If you are still experiencing this problem on or after Catalyst 10.10, open up Catalyst Control Center and navigate through the following menus...
Graphics > Desktops & Displays > Right click the smaller monitor representation near the bottom of the window > Configure > Color
Once there, change the Temperature slider from 6400k back to to 6500k. Your display should look normal again.

Official fix:
Officially resolved in Catalyst 10.10 hotfixes, and all drivers since.

May still require that you manually reset color temperature if you updated from Catalyst 10.10.

5. Cursor Corruption
Quote:
Symptoms:
The mouse cursor may become corrupt (enlarged, garbled, etc).

Causes:
Specific cause is unknown.

Workaround:
Keeping the Windows Magnifier open in the background will, oddly, fix cursor corruption. Unfortunately, it must stay running. As soon as it's closed, the corruption comes back
A reboot will always return the cursor to normal, but having to reboot constantly is hardly a solution...

Official fix:
Officially resolved in Catalyst 10.12 (Note that Cursor Corruption is still present in 10.12a, as they are actually older than 10.12)

Update 1: ATi's fix for cursor corruption has created a new problem for some users, slow mouse response in the top/bottom right corners of their monitor(s). See Bug #8 for details.
Update 2: Cursor corruption is BACK in Catalyst 11.2. Now we have the cursor corruption bug AND the slow mouse response bugs at the same time...

6. ATi Overdrive Idle Clockspeed
Quote:
Symptoms:
If you use anything but default clockspeeds in ATi Overdrive, your card begins to idle at 157MHz core, 300MHz RAM. These clockspeeds are too low, and can cause secondary monitors to flicker or corrupt in other ways.

Causes:
Appears to be a conflict between PowerPlay idle states, the newly defined idle clocks assigned by the driver (AMD's attempted fix for another driver bug), and ATi Overdrive causing those newly defined idle states to be overridden.

Workaround:
1. Catalyst Control Center > Graphics > ATi Overdrive.
2. Set your desired 3D clockspeed and apply it.
3. Your card's idle clock will have dropped to 157 / 300. Ignore that for now.
4. Options > Profiles > Profile Manager.
5. Name the profile "OverdriveFix" and make sure "ATi Overdrive" is checked.
6. Save the profile, but DO NOT apply it yet.
7. Navigate to "C:\Users\%username%\AppData\Local\ATI\ACE\Profiles\"
8. Right click "OverdriveFix.xml" and select "Edit"
9. Edit the clockspeeds and voltages as appropriate for your card.

10. Save the XML file.
11. Catalyst Control Center > Options > Profiles > Activate Profile > OverdriveFix
12. If only the core clock changed, repeat step 11 (apply the profile again).
13. Your idle clockspeed should now be correct. 400/1000 for the HD5850, or 400/1200 for the HD5870.

Official fix:
None. Unresolved as of Catalyst 11.2

7. CCC Profiles are Not Properly Applied
Quote:
Symptoms:
When you apply a previously saved Catalyst Control Center profile, not all aspects of the saved profile are loaded. Any setting related directly to your monitors may be effected, including resolution, relative position, primary monitor selection, and color correction settings.

Causes:
This occurs when you reconnect your displays to different heads on your graphics card. The driver has a "memory problem," and remembers the head each monitor was attached to at the time of installation. You will continue to have issues with profiles until each display is returned to its original head.

Workarounds:
1. Swap cables around until you find the original combination of monitors and heads again.
2. Apply the profile a second time, the remaining settings should switch to those defined in the profile.
3. Uninstall the driver, run Driver Sweeper, reinstall the driver. You'll have to remake all your profiles from scratch, but they'll work correctly again.

Official fix:
None. Unresolved as of Catalyst 11.2

8. Cursor Lag
Quote:
Symptoms:
The mouse cursor lags, stutters, or appears to run at a lower frame-rate when it's in the top (or bottom) right hand corner of the display.

Causes:
ATi's fix for the mouse cursor becoming corrupt when moved across displays through these areas (Bug #5) seems to be the cause. The cursor no-longer becomes corrupt, but the fix is causing lag in very specific areas on the display.

Workaround:
Some users are reporting that disabling the cursor shadow has helped significantly or completely solved the cursor lag.
Reverting to older drivers will just replace this bug with the corrupt cursor problem.

Official fix:
Unresolved as of Catalyst 11.2

9. Slow Display Mode Switching
Quote:
Symptoms:
Upon requesting a mode switch, each attached display will turn black one at a time (you may still see the mouse cursor). The displays will remain black for up to 5 minutes, then suddenly come back at the requested mode.
Once this has occurred once, it will happen on every subsequent mode switch until the computer is restarted.

Logging out, locking the computer, logging in, changing resolution, switching between Extended Desktop and Eyefinity, changing refresh rates, etc. all count as a mode switch. These will all take excessive amounts of time once this glitch manifests.
Note: Symptoms may not be immediately apparent. Mode switching may work correctly for quite some time before the bug kicks in.

Causes:
Unknown, but may have something to do with ATi's fix for cursor corruption.

Workaround:
None known, besides rebooting the computer or reverting to a driver older than 11.1(a)

Official fix:
Unresolved as of Catalyst 11.2
---Klipp slut --------------------------------------------------------------------------------------------------------------