Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20598 Discussions

Error Message: Display driver stopped responding and has recovered

RonaldM_Intel
Moderator
1,524 Views

What are you seeing?

This is an error that it is also known as Time-out Detection and Recovery (TDR). You can read more about it here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff570087(v=vs.85).aspx Timeout Detection and Recovery (TDR)

In a nutshell, the screen turns off and on instantly, and in the bottom right-hand corner the notification "Display driver stopped responding and has recovered" appears.

This behavior can occur in Windows* 7, 8/8.1 or 10.

Example:

Why did you get this error?

Windows* detected an issue with the Display driver, and was forced to terminate the processes linked to it.

What do I do?

Intel released a Display driver which contained a fix to address multiple causes of this error. Released in April 2016 (version 15.40.22.4424), all drivers since that date include this fix. Other causes of the error may exist, that is why we recommend maintaining your drivers up to date.

You can test by installing our latest generic drivers. Try using the http://www.intel.com/content/www/us/en/support/detect.html Intel® Driver Update Utility to get the generic drivers.

Some computer manufacturers design their systems so you can only install drivers provided by them. The following article has a workaround that may help you http://www.intel.com/content/www/us/en/support/graphics-drivers/000005469.html Error Message: Computer Manufacturer Graphics Driver Detected

I already installed the latest driver from https://downloadcenter.intel.com/ downloadcenter.intel.com, and yet the issue still occurs for me.

Contact your computer manufacturer and install their latest driver. Often times, Original Equipment Manufacturers (OEM) customize the generic Intel drivers to match their specifications or requirements.

All OEMs should have access to newer Intel Graphics driver versions that contain this fix.

0 Kudos
0 Replies
Reply