The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    "Display Driver AMD Stopped Responding Has Successfully Recovered"

    Discussion in 'Alienware 17 and M17x' started by helloimjared, Sep 30, 2012.

  1. helloimjared

    helloimjared Notebook Guru

    Reputations:
    5
    Messages:
    59
    Likes Received:
    0
    Trophy Points:
    15
    Sorry for the double post. The original wasn't posted in the m17x sub forum. I forgot their was one.



    When browsing the internet (Youtube & Stickam), I get the message: "Display Driver AMD Stopped Responding Has Successfully Recovered"

    I have never received this message while playing Starcraft II,League of Legends, BF3, or Sniper Elite V2.

    My screen flashes then turns black and finally recovers.

    Could this just be a problem when browsing the internet? Because that's when it only happens. Shock-wave player occasionally crashes too. I use Chrome.

    So could the Shock-wave crash be causing the AMD error???



    Does anyone know why this is happening?

    My specs are in my sig!
    Thanks


    Fix:



    I disabled the Google home brew of flash in chrome and I am now strictly running on the real Macromedia Flash player.


    It was a fix I found on some site and it worked.:thumbsup:
     
  2. ADegtyarev

    ADegtyarev Notebook Guru

    Reputations:
    36
    Messages:
    74
    Likes Received:
    0
    Trophy Points:
    15
    This was happening to me as well, but only while I was playing graphically and computationally intensive games like crysis 2 and batman arkham city. What I did was I downgraded my drivers from ccc 12.7 to 12.6 and this removed all problems for me. Though I am not sure what drivers you are currently on.
     
  3. Prasad

    Prasad NBR Reviewer 1337 NBR Reviewer

    Reputations:
    1,804
    Messages:
    4,956
    Likes Received:
    10
    Trophy Points:
    106
    What driver are you using? Have you tried another?
     
  4. helloimjared

    helloimjared Notebook Guru

    Reputations:
    5
    Messages:
    59
    Likes Received:
    0
    Trophy Points:
    15
    Not quite sure. But the fix I tried seemed to solve the problem. I was browsing all last night and did not receive the error. :)

    Fix that seemed to work:

    I disabled the Google home brew of flash in chrome and I am now strictly running on the real Macromedia Flash player.
     
  5. Alienware-Luis_Pardo

    Alienware-Luis_Pardo Guest

    Reputations:
    1,141
    Messages:
    1,459
    Likes Received:
    8
    Trophy Points:
    56
    To check your driver version open the Catalyst Control Center, click Preferences --> About Catalyst Control Center...

    It will say something like:

    Version 20 12.0806.1213....

    This would be the 12.8 Catalyst.

    As it has been suggested, you could try a different driver version. Make sure to remove all traces of your current driver if you do.

    Video Driver Clean Installation
     
  6. dmorman

    dmorman Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    Had the same problem. Previously, Adobe Flash and Shockwave had caused crashes and other problems. When I uninstalled and reinstalled Flash and Shockwave, the problem disappeared.
     
  7. darkdomino

    darkdomino Notebook Deity

    Reputations:
    203
    Messages:
    833
    Likes Received:
    2
    Trophy Points:
    31
    this error is known as a TDR error, and in older versions of windows you would have gotten a blue screen of death (BSOD) ... Windows 7 has a failsafe system that, if the display driver takes too long to respond, the operating system restarts the adapter instead of crashing the entire operating system. If you get multiple TDRs within a certain time frame, you will get a BSOD.

    These errors could mean two things: hardware damage or bad drivers (more likely) ... Roll back your drivers and see if the problem persists. If it does, you may have hardware issues.
     
  8. Alienware-L_Porras

    Alienware-L_Porras Company Representative

    Reputations:
    3,658
    Messages:
    6,874
    Likes Received:
    969
    Trophy Points:
    281