ATI Catalyst 10.7 Major Crossfire Issue

Posted: August 1st, 2010 | Author: | Filed under: Hardware
Tags: , , , , ,

UPDATE: 10.10 Solves it for good.

NEW HOTFIX DRIVER: 10.8b says it fixed the issue, which might have appeared on 10.6. It’s almost perfect, the games are ok, but when exiting some of them, the core is still in 3d speeds. Here’s a list of some games that I tested. I was close to trying TwL‘s drivers, too…

Today I installed Catalyst 10.7 drivers after skipping 10.6 from hearing some horror stories. I’m with a 4870×2 using Vista64. The installation went smoothly, including the HDMI install. (A year ago the HDMI installer failed on one release, worked on the next month’s release.)

After some testing, there’s a severe problem with the 2d/3d detection, so far with the second core.

With DX9 and OGL games, the second core does not switch between 2d and 3d speeds. On a fresh boot, it stays idle after launching a game. This mismatch makes games really stuttery, especially if they are more demanding. The DX9 games I tested were: Borderlands, Call of Duty Modern Warfare 2, Far Cry 2, Lead and Gold, Mirror’s Edge, Moonbase Alpha, Need for Speed SHIFT, Serious Sam HD.

Mirror’s Edge managed to flip the second core into 3d, but then it got stuck after exiting! I checked Borderlands and it was as smooth as it was before (some areas can dip to ~45fps). Lead and Gold finally has a crossfire profile in the drivers, so now that the second core was in 3d mode, the game was nice and smooth without the huge flicker and ~40fps from before.

DirectX 10/11 games I tested (Battlefield Bad Company 2, Red Faction Guerrilla, Shattered Horizon) work just fine. Launching and exiting flips both cores correctly into 2d/3d. Even after Mirror’s Edge locks the second core into 3D, you could reset it back to idle speed by opening and closing a DX10 game.

If there is no hotfix, it might still be possible to take a specific .dll from 10.5 or 10.6 and put it in the Windows system folder so you can still use the new game profiles of 10.7.

Last Modified: October 22nd, 2010


5 Comments on “ATI Catalyst 10.7 Major Crossfire Issue”

  1. 1 Makoto said at 3:58 pm on August 4th, 2010:

    Interesting, clearly 10.7 are really strange with crossfire. I have HD4850x2 under 7 x64.

    I did not notice this behavior with DX9 games, it sounds like the ATI Tray Tools 2D/3D profile/detection bug with crossfire cards.

    But for DX10/11 games, especially Battlefield bad company 2 both cards runs at only 65% of their load, the 2nd GPU is even switching back to 2D frequencies for few seconds ! While in 10.5a it’s more 99% GPU load, constant clocks and smooth framerate.

  2. 2 kn00tcn said at 12:45 pm on August 6th, 2010:


    wow, interesting… I can’t figure out what’s causing it, since there are people that are fine

  3. 3 cluss said at 8:56 am on August 13th, 2010:

    I think AMD do not any thing at future driver, because this problem is still continued from 10.6 to now…

  4. 4 nnyymm said at 9:37 am on August 22nd, 2010:

    we can’t install 10.7 crossfire profiles while we are still at 10.5 display drivers?

  5. 5 kn00tcn said at 3:00 pm on August 23rd, 2010:

    @nnyymm the profiles installer isn’t just crossfire, and you can install it with any driver from 10.2 and up.

Leave a Reply