If you’ve got an AMD (ATI) graphics card and you keep getting the message “The Display Driver Has Stopped Responding” in Windows 10 it can be very frustrating. The screen goes blank for a second, the message pops up and any application you were using likely crashes – especially frustrating if you’re in a game. This simple guide will hopefully help remove the problem and get you back to a nice stable system.
To update to the latest display driver for your graphics hardware by using Windows Update, click the link specific to your version of Windows and follow the steps in that article: Update a driver for hardware that isn't working properly in Windows 7 Update a driver for hardware that isn't working properly in Windows Vista. On my Windows 10 machine I play Minecraft and most of the time when I come out of full screen I get the (Display Driver has stopped responding and has recovered). It then Minecraft turns to a white screen. Metadatics 1 5 5 – powerful audio metadata editor. If anyone can help me out that would be great! System Stats. OS: Windows 10. RAM: 6.00GB RAM. Display Driver: Intel(R) HD Graphics 4400. Windows 10 - Display Driver Stopped Responding and Has Recovered. Question asked by [email protected] on Nov 11, 2015 Latest reply on Nov 11, 2015 by raym.
Causes of Display Driver Has Stopped Responding on Windows 10
It seems this is wholly driver related. I’ve mainly seen this problem using AMD (ATI) graphics cards and it seems to happen at completely random times. Having done a little research, the problem can happen on more than Windows 10 machines and on more than just AMD graphics cards too but we’re going to focus on the AMD family, specifically the Radeon 7800 and Windows 10.
How to fix Display Driver Has Stopped Responding on Windows 10
In short, we’re going to do the following:
Display Driver Stopped Working Windows 10
- Download Display Driver Uninstaller
- Boot Windows 10 into Safe Mode
- Clean out all AMD drivers using Display Driver Uninstaller
- Boot back into Windows 10
- Allow Windows 10 to use it’s preferred drivers
So let’s get started.
Download Display Driver Uninstaller
Display Driver Uninstaller is an application released by Wagnard Mobile that is designed specifically to remove any trace of display driver software and utilities. It currently works for AMD, Nvidia and Intel cards but in this guide, we’re focusing specifically on AMD.
- Visit The Official Website for Display Driver Uninstaller and download the utility
- Save it somewhere you can get to it easily, on your Desktop for example
- Once downloaded, run and extract the file to c:ddu
Boot Windows 10 into Safe Mode
Although Display Driver Uninstaller will run in normal Windows 10 mode, it’s reccomended you run it in Safe Mode. Windows 10 Safe mode allows the operating system to boot up with a minimal set of drivers running – meaning when you uninstall something like, oh I don’t know – your graphics card drivers – you won’t find any files locked and prevent a nice clean uninstall.
- From normal Windows 10 mode, press the Windows Key and type msconfig and press Enter
- Within msconfig, select the Boot tab and choose the following options at the bottom of the screen:
- Safe Boot
- Network (Network mode isn’t strictly required, but I always use it just in case I need to access something whilst in Safe Mode)
- Click OK, the system will then ask you if you’d like to reboot – select Restart
- The system will now reboot into Windows 10 Safe Mode
Clean out all AMD drivers using Display Driver Uninstaller
Once you’re in Windows 10 Safe Mode, locate and launch the Display Driver Uninstaller file you downloaded.
- Open C:DDU in Explorer
- Launch the Display Driver Uninstaller.exe file
- Ensure that AMD is selected in the top right drop down for Select Graphic Driver
- Click on Clean and Restart (Highly Recommended)
- The utility will now go through your system and clean out any trace of the AMD display drivers and built in utilities
- Once it’s completed it will ask you to reboot, choose OK
- Windows 10 will now boot back into normal mode
Boot back into Windows 10
- Once Windows 10 has rebooted and you’ve logged in (if necessary) you will be back in normal Windows 10 mode
- You may notice that your screen looks strange, this is because it’s using generic graphics drivers and not AMD
Allow Windows 10 to use it’s preferred drivers
Chocolat 3 2 1. Now Windows is back into Windows 10 normal mode and the system is running on generic graphics card drivers, you need to install drivers you know are stable. I would recommend you download the latest Windows 10 Updates which should now include your AMD graphics drivers.
- Press Windows & I (The Windows key and the I key together) – this launches Settings
- Click the Update & Security icon
- Click Check for Updates
- Windows should now detect the AMD graphics driver and potentially an audio driver for HDMI
- Click the Install Now button and allow Windows 10 to update the AMD drivers to it’s recommended version
- Once the installation is complete, reboot your PC
Once complete, go into your Radeon settings and check the Software version to make sure you’ve got the older drivers installed.
Summary of how to fix the Your Display Driver Has Stopped Responding error
Essentially by following this guide you are cleaning any of the AMD drivers you have downloaded that are now not working correctly and causing the Your Display Driver Has Stopped Responding error and have replaced them with the latest AMD drivers that Windows 10 officially supports through it’s Windows Update functionality. If you would rather manually use an older version of the drivers that you have downloaded, install these before running the Allow Windows 10 to use it’s preferred drivers section of the guide. I personally have started using the Windows 10 version of the drivers that Windows Update provides and haven’t had a single re-occurrence of the problem. I’ve also stopped updating the drivers as I’d rather have a stable system than features and settings enabled for cards much newer than mine that may actually be the cause of the problem.
Update – 10th June 2016
Keka 1 1 2 for mac free download. Having had a stable system with no crashes for a few weeks (rather than a few crashes every session) I was curious if I would experience the issues again if I updated the drivers cleanly. I went through the clean install procedure again and this time installed the current latest WHQL driver (16.15.xxxx). Within 10 minutes of running the new driver, I got the Your Display Driver Has Stopped Responding message again so it’s definitely connected to newer drivers.
I re-followed this guide and reverted to the Windows Update version again (15.30.xxxx) and we’re stable again.
I hope you’ve found this guide helpful and look forward to any suggestions or questions in the comments.
-->Find information on known issues and the status of the rollout for Windows 10, version 2004 and Windows Server, version 2004. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.
Windows 10, version 2004 is available for users with devices running Windows 10, versions 1903 and 1909, who manually seek to “Check for updates” via Windows Update. We are now starting a new phase in our rollout. Using the machine learning-based (ML-based) training we have done so far, we are increasing the number of devices selected to update automatically to Windows 10, version 2004 that are approaching end of service. We will continue to train our machine learning through all phases to intelligently rollout new versions of Windows 10 and deliver a smooth update experience. The recommended servicing status is Semi-Annual Channel. |
Windows 10, version 2004 is now available Find out how to get the update > | What’s new for IT pros Explore the latest features and and servicing innovations in Windows 10 > | Wondering how to deploy feature updates remotely? Get tips and best practices > |
![Driver for display windows 10 Driver for display windows 10](https://i.ytimg.com/vi/wJIFnWh2my8/maxresdefault.jpg)
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
Summary | Originating update | Status | Last updated |
Dragging with the mouse in some apps might cause issues for some IME users Users of the Microsoft IME for Chinese and Japanese might receive an error or the app might stop responding or close. See details > | N/A | Resolved KB4571744 | September 03, 2020 02:00 PM PT |
Certain WWAN LTE modems might not be able to connect after waking from sleep Affected WWAN LTE modems might show no internet and be unable to connect. See details > | N/A | Mitigated | August 31, 2020 12:27 PM PT |
Issues when using Microsoft IME for Japanese or Chinese languages Users of the Microsoft IME for Japanese or Chinese languages might have issues. See details > | N/A | Mitigated | August 31, 2020 12:27 PM PT |
Issue with older drivers for Nvidia display adapters (GPU) You might have issues if you are using an Nvidia display adapter (GPU) and drivers with a version below 358.00. See details > | N/A | Resolved KB4568831 | July 31, 2020 10:00 AM PT |
Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present Devices with apps or drivers using certain versions of aksfridge.sys or aksdf.sys might have issues updating or starting See details > | N/A | Resolved KB4568831 | July 31, 2020 10:00 AM PT |
Difficulty connecting to more than one Bluetooth device Windows 10 devices with certain Realtek drivers might be unable to connect to more than one Bluetooth device. See details > | N/A | Resolved KB4568831 | July 31, 2020 10:00 AM PT |
Variable refresh rate not working as expected on devices with Intel iGPU Enabling VRR on affected devices will not enable the VRR for games using Direct X 9. See details > | N/A | Resolved KB4568831 | July 31, 2020 10:00 AM PT |
Errors or issues during or after updating devices with Conexant ISST audio drivers Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004. See details > | N/A | Investigating | August 06, 2020 03:26 PM PT |
Errors or issues during or after updating devices with certain Conexant audio drivers Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen. See details > | N/A | Investigating | August 06, 2020 03:26 PM PT |
Issue details
Windows 10 Display Driver Keeps Crashing
August 2020
Details | Originating update | Status | History |
Certain WWAN LTE modems might not be able to connect after waking from sleep After waking from sleep or hibernation, certain WWAN LTE modems might show no internet in the Network Connectivity Status Indicator (NCSI) in the notification area and might be unable to connect to the internet. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected WWAN LTE modems drivers installed from being offered Windows 10, version 2004 until the issue has been resolved. If your organization is using Update Compliance, the safeguard ID is 28428232. Workaround: To mitigate this issue if you are already on Windows 10, version 2004, you can enable then disable Airplane mode. To do this, you can select the Start button, type airplane mode and select it. In the settings dialog, toggle Airplane mode on then off again. You should now be able to connect as expected. Affected platforms:
Next steps: We are working on a resolution and estimate a solution will be available in late September. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until the safeguard is removed. Back to top | N/A | Mitigated | Last updated: August 31, 2020 12:27 PM PT Opened: August 31, 2020 11:42 AM PT |
Issues when using Microsoft IME for Japanese or Chinese languages Users of the Microsoft IME for Japanese or Chinese languages might experience issues when attempting various tasks. Input may have issues, you may receive unexpected results or you may be unable to enter text. Affected platforms:
Next steps: For more information on issues, workaround steps and currently resolved issues, please see KB4564002. Back to top | N/A | Mitigated | Last updated: August 31, 2020 12:27 PM PT Opened: August 31, 2020 12:12 PM PT |
July 2020
Details | Originating update | Status | History |
Dragging with the mouse in some apps might cause issues for some IME users Users of the Microsoft IME for Chinese and Japanese in some apps such as Microsoft Excel, might receive an error or the app might stop responding or close when attempting to drag with the mouse. Affected platforms:
Resolution: This issue was resolved in KB4571744. Back to top | N/A | Resolved KB4571744 | Resolved: September 03, 2020 02:00 PM PT Opened: July 14, 2020 09:06 AM PT |
May 2020
Details | Originating update | Status | History |
Issue with older drivers for Nvidia display adapters (GPU) Nvidia and Microsoft have found incompatibility issues with certain versions of Nvidia display adapter drivers and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Nvidia display driver versions might receive a stop error with a blue screen or other issues during or after installing the update to Windows 10, version 2004. The affected drivers are any version lower than 358.00. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Nvidia display drivers drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 24803238. Affected platforms:
Workaround: To mitigate this issue, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows Server, version 2004 is offered. Back to top | N/A | Resolved KB4568831 | Resolved: July 31, 2020 10:00 AM PT Opened: May 27, 2020 12:09 AM PT |
Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present An incompatibility issue was found with apps or drivers using certain versions of aksfridge.sys or aksdf.sys and Windows 10, version 2004 (the Windows 10 May 2020 Update). When an affected version of aksfridge.sys or aksdf.sys is present, Windows 10, version 2004 might fail to install or might fail to start after updating. Affected file versions are up to 1.8.0.* for aksfridge.sys or up to 1.51.* for aksdf.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with an affected version of aksfridge.sys from being offered Windows 10, version 2004 or Windows Server, version 2004. If your organization is using Update Compliance, the safeguard ID is 24858586. Affected platforms:
Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows Server, version 2004 is offered. Back to top | N/A | Resolved KB4568831 | Resolved: July 31, 2020 10:00 AM PT Opened: May 27, 2020 12:09 AM PT |
Difficulty connecting to more than one Bluetooth device Realtek and Microsoft have found incompatibility issues with certain versions of drivers for Realtek Bluetooth radios and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Realtek Bluetooth radio drivers might be unable to connect or pair with more than one Bluetooth device at a time after updating. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Realtek Bluetooth radio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25692458. Affected platforms:
Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows Server, version 2004 is offered. Back to top | N/A | Resolved KB4568831 | Resolved: July 31, 2020 10:00 AM PT Opened: May 27, 2020 12:22 AM PT |
Variable refresh rate not working as expected on devices with Intel iGPU Intel and Microsoft have found incompatibility issues when using a monitor with Variable refresh rate (VRR) plugged into an Intel integrated graphics processing unit (iGPU) display adapter and Windows 10, version 2004 (the Windows 10 May 2020 Update). Enabling VRR on affected devices will not enable the VRR for games using Direct X 9. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004. If your organization is using Update Compliance, the safeguard ID is 26251417. Affected platforms:
Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 is offered. Back to top | N/A | Resolved KB4568831 | Resolved: July 31, 2020 10:00 AM PT Opened: May 27, 2020 12:13 AM PT |
Errors or issues during or after updating devices with Conexant ISST audio drivers Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant ISST audio driver and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant ISST audio driver might receive an error or experience issues while installing the update or after the device has updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version lower than 7.231.3.0. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25178825. Affected platforms:
Workaround: To mitigate this issue, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | N/A | Investigating | Last updated: August 06, 2020 03:26 PM PT Opened: May 27, 2020 12:22 AM PT |
Errors or issues during or after updating devices with certain Conexant audio drivers Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53, 8.65.56.51, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard IDs are 25702617, 25702660, 25702662, and 25702673. Affected platforms:
Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | N/A | Investigating | Last updated: August 06, 2020 03:26 PM PT Opened: May 27, 2020 12:20 AM PT |