1. Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Display driver atikmdag stopped responding and has recovered

Discussion in 'AMD / ATI' started by Kofoed, Mar 13, 2009.

  1. Kofoed

    Joined:
    Mar 9, 2009
    Messages:
    187 (0.09/day)
    Thanks Received:
    3
    Location:
    Denmark
    Hello all! :) after i played a game a few minutes i get the following error: "Display driver atikmdag stopped responding and has recovered"
    But when i disable crossfire everything works fine, atlast for more time than with crossfire on, without crossfire on i can actually complete a game. But with crossfire it keep chrashing after a few minutes.
    Has anyone got a solution for this? i tryed both card one by one, slotby slow, works fine. Could it be my crossfire bridge? or any other software componemts?
    so annjoying that i could :banghead:
    Anyways, please help :laugh:
    As you see in system spec my card is ATI RADEON HD 3870 Crossfire.

    What i tried?
    Reinstall driver
    Reinstall windows
    updating directx
    Not overclocked card.
    No overheat
     
    Last edited: Mar 13, 2009
  2. Castiel

    Castiel

    Joined:
    May 5, 2008
    Messages:
    3,319 (1.43/day)
    Thanks Received:
    310
    Do you have the latest Catalyst drivers?
     
  3. Kofoed

    Joined:
    Mar 9, 2009
    Messages:
    187 (0.09/day)
    Thanks Received:
    3
    Location:
    Denmark
    Yeah, i have tried with older driver that worked before, and the newest driver.
     
  4. 95Viper

    95Viper

    Joined:
    Oct 12, 2008
    Messages:
    4,373 (2.02/day)
    Thanks Received:
    1,581
    Location:
    στο άλφα έως ωμέγα
  5. Kofoed

    Joined:
    Mar 9, 2009
    Messages:
    187 (0.09/day)
    Thanks Received:
    3
    Location:
    Denmark
    Okay thanks. I don't know the timing, just picked one of the bios with the same clocks :laugh:

    Okay, this issue is still not solved i just got my secondary card replaced as it was blacked totally out, but this does not solve my problem. Still get the error.
     
    Last edited: Mar 20, 2009

Currently Active Users Viewing This Thread: 1 (0 members and 1 guest)

Share This Page