Enabling today.
Inspiring tomorrow.

 How to troubleshoot “Display driver stopped responding and has recovered”, ATIKMDAG.sys type errors

Article Number: 27116

​​This article provides information on the possible causes an ATIKMDAG.sys type error may occur and how to troubleshoot the system to prevent the error from reoccurring.


Issue Description:

During startup or use of an application, (most commonly a game / video application) the system or application will freeze, crash or exit to the desktop / a blue screen (BSOD). Additionally, an error message appears stating that the “Display driver stopped responding and has recovered” and may reference one of the following driver files:

  • ATIKMDAG.sys
  • ATI2DVAG.sys
  • ATI2CQAG.dll
  • ATIVPK.sys
  • AMD2DVAG.sys
  • AMDKMDAG.sys
  • AMDVPK.sys



Issue Cause:

The issue occurs when the Timeout Detection and Recovery (TDR) feature available in Windows Vista® and Windows 7 detects that the graphics card (GPU) has not responded within a predetermined period of time and reinitializes it with the Windows Display Driver Model (WDDM) to prevent the need to reboot. There is no single cause for a TDR event to be triggered.

Additional Details about TDR events can be found on Microsoft’s website.



There are several factors that can cause the TDR event to be triggered. The following troubleshooting steps can help rule out / resolve the cause of the issue:

Note! If you do not feel comfortable performing any of the steps provided in these instructions, you should have your system checked by an expert.


Related Topics