UPDATE: This instructable is about 5 years old now, but this error still persists. While anything could be causing this, as the steps will show, overheating and driver errors are a dominating problem. Dusting out your computer, and following the "drivers" step would be a good place to start.

This instructable will show you known ways of fixing the dreaded "display driver nvlddmkm stopped responding and has successfully recovered" error. It's been found on operating systems XP, Vista, and Windows 7. I've searched hours and tried many solutions, finally #1 worked for me.

Please note that this also works for other forms "display driver__________ stopped responding and has recovered," however this is the most common. I personally had that, until getting a GTX 260, in which case I got "Display driver nvidia windows kernel mode driver has stopped..."

What is this error? This error occurs when your computer thinks that you graphics card has stopped responding, mainly due to a low frame rate. The program that controls this is called "Timeout detection and recovery." The error is very vague, and doesn't correlate to one problem. Getting this error is like your computer saying "something went wrong with your graphics card, and we're not sure what." It could be you're power supply, ram, temperature, or just the card in general. It happens on all types of cards, and even built in ones, with your motherboard. You will know you have it if your monitor goes black for a few seconds, and comes back, with the popup from the intro picture. If you have only gotten it one time, just ignore it, but if you get it again, you should try the solutions.

Forms of the error

There are a few known forms of this error. Sometimes it will just happen once, normally while watching a video or playing a game, other times it will go berserk, right when you login you will get it every 10 seconds, and may even get the blue screen of death!

Now that you know a little about it, lets continue to the solutions, I'll start with the easiest first, and move up to the more drastic.

Shameless plug: Check out my website at www.coltonboyer.com

Step 1: Solution 1: Power Supply

Make sure that you are on High Performance, in the power options section of the control panel. More specifically, make sure that the PCI express setting is turned OFF. This would fix any issues caused by low power to the video card.

If you are still getting the error, proceed to the next step, this applies to all solutions.

<p>The reasons for this issue are various. Outdated display driver, old or <br>incompatible vedio card, too many programs running at the same time, <br>etc. There are 10 methods to fix this error.</p><p>http://www.drivethelife.com/windows-drivers/how-to-fix-display-driver-stopped-responding-and-has-recovered-on-windows-10-8-7-xp-vista.html</p>
<p>This problem will now be fixed for several HP laptop models by upgrade to GeForce 341.95 Driver.</p><p><a href="http://www.nvidia.com/download/driverResults.aspx/99994/en-us" rel="nofollow">http://www.nvidia.com/download/driverResults.aspx/99994/en-us</a></p><p>Release notes:</p><p><a href="http://us.download.nvidia.com/Windows/341.95/341.95-win8-win7-winvista-desktop-release-notes.pdf" rel="nofollow">http://us.download.nvidia.com/Windows/341.95/341.95-win8-win7-winvista-desktop-release-notes.pdf</a></p>
<p>I tried all the solutions shown here none of them work on W7 64 ultimate did the reg hack still no go. Ran Microsofts fix nope </p>
<p><strong>On an important note:</strong> I recently installed <strong>windows 10</strong> and this error has came along with it. I haven't had a single <strong>Nvlddmkm error</strong> on my previous windows. Is it somehow windows 10 related?</p>
<p>For your information, the reason I upversioned to Win 10 was in the hope that it'd remove this issue. It didn't. I have found that different NVidia drivers create different logs in the Event Viewer. The latest drivers seem to simply show that a reboot has occurred. The older one that I use, and which is less susceptible, did at least mention it was Nvlddmkm. Now I have to assume it still is as the symptoms remain the same.</p>
<p>None of these worked for me, but the following did:</p><p><strong>If you use MSi Afterburner</strong>, try...</p><p>1. Uninstall Afterburner and RivaTuner Statistics Server (keep your settings files)</p><p>2. Download latest NVidia driver</p><p>3. Select &quot;Clean Install&quot;</p><p>4. <strong>***From NVidia control panel***</strong> click &quot;Open Windows Sound settings&quot; and disable all NVidia sound &quot;devices&quot;</p><p>5. Close NVidia control panel and restart your machine</p><p>6. Download and reinstall Afterburner (RivaTuner comes along for the ride)</p><p>7. Restart again</p><p><strong>When next you update your NVidia drivers, uninstall Afterburner first and repeat steps 3 through 7.</strong></p><p>This worked for me. I haven't had a single Nvlddmkm Error in more than 5 months. Hope it helps other people, too. Cheers.</p>
<p>I did what you said from steps 2 to 5. The next thing happened was I got Nvlddmkm error. Anyway thanks though. </p><p>P.S. I don't use MSI Afterburner. </p>
<p>Yeah, I think this Nvlddmkm error thing is really specific, and given what worked for me, it's software-specific. There's a conflict (for me) between NVidia drivers and Afterburner, for example. For you, it's something else. On my pal's PC it turned out to be the RAM. So if you haven't tried Step 7 yet in SirColton's instructable, maybe give it a shot?</p>
<p>Has anyone had this problem on Windows 10? I doubt that it would go away, but I'm curious.</p>
<p>Hi,</p><p>I have recently got the MSI dragon edition gaming rig with win 10 and 8Gb nvidia gtx 980... rarely i encounter the issue.. say like 3 times a week... </p>
<p>I am having this problem on windows 10</p>
<p>i did them and some of procedures in comments...</p><p>i think its a problem with nvidia driver</p><p>recently i install pes 2016 on my x64 windows 10 and when i play it through Nvidia(GT525M) its crashes and give nvidia disply stopped...</p><p>i tried every way from installing a fresh copy of windows to installing windows 8 and 7,editing registry, downgrading and upgrading drivers,DirctX changing...</p><p>but anyway the problem is exist...</p><p>today i figured if i play the game through Integrated graphic(intel hd 3000) i can play 10 hrs without any crash(but in a bad graphic you know that)</p><p>what i have to do know...</p><p>i should mention that i changed my charger adapter and power jack with no chance...</p><p>is it related to DirectX, Nvidia Driver(using many versions from stock in package to latest 358.91), Nvidia High Definition Audio, IDT sound card, Power Supply...</p><p>ANY IDEA???</p>
<p>Sounds like it may be the same problem as I had....the fan. See my post about it. It may be your answer.</p>
<p>I read the threads on this and it seemed that everything kept pointing to the graphics card getting too hot. I decided to disconnect the graphics card from the computer and see if there was a problem with the fan. It turns out it was barely turning (sticking). With the fan disconnected from the graphics card, I sprayed &quot;Fabulous Blaster&quot; brand &quot;Graphite Dry Lube&quot; directly into the guts of the fan until it overflowed. This will make a nice black paint looking mess all over the place, but it cleans up with soap and water fairly easily so be prepared for that. Then I took my pistol grip blower hooked up to my air compressor and blew the whole thing out really good until it was dry. The fan moved better than it did new after I did this. I did have to work the lube in a bit before I stuck it back in the computer but it totally solved the problem. No driver installs rebooting...nothing. I just cleaned the fan and it works fine. Can't say this is the fix-it for everyone, because as has been pointed out in this thread, it could be a multitude of things, but this is how I solved the problem</p>
<p>just putting it in to preformance mode made my pc much faster and 123d works!</p>
<p>I kept getting this error in Windows 10 on start-up. After trying lots of different ways to fix it with none of them working the only way I could prevent it was to disable fast start-up in Power Options &gt; System Settings &gt; Shut-down Settings (go into power options and click 'choose what the power buttons do' in the left panel). </p><p>Hope this helps anyone.</p>
<p>If any of the above fixes it, try disabling the audio device of the motherboard from bios, and try a clean install on nvidia drivers including the high definition audio and physix only. worked form me after a whole year of trying every solution I found on the web.</p>
<p>Cooling is also very important. If you install MSI after burner you can instantly tell if the machine is cooling. Make sure to use a cooling pad if you are using a laptop;. </p>
<p>This is a generic error and there are a lot of things you can try but the error for me was coming from a conflict with the Microsoft Audio drivers and Nvidia Audio drivers. I disabled the Nvidia audio drivers and made Microsoft Audio drivers my default. I made Nvidia card my default video driver and selected it for every instance in Nvidia control panel. </p><p>Fresh installation of operating system</p><p>All windows updates first</p><p>All manufacture drivers</p><p>disabled sleep in power settings</p><p>disabled sleep, hibernation, processor sleep in bios</p><p>Physically cleaned machine</p><p>Checked all system drivers in Device manger</p><p>Constantly checked event logs to trouble shoot changes.</p><p>Error can also be caused by installing wrong video drivers such as for wrong card or wrong operating system. </p><p>If you need a quick fix and don't want to do everything listed here delete and reinstall drivers. Disable Nvidia Audio in Windows Audio Control and Device Manager. </p>
<p>I had this problem only when sharing a screen with Webex. After 5 days and 50 hours and using *all* of these ideas which didn't work, I fixed this by enabling the NVidia nview tool from the control panel. Duh.</p><p>Hope that helps you!!</p>
<p>Here's an update: this fix worked for a bit then it failed again. But I *have* finally fixed the problem: I installed the CUDA package from NVIDIA (to do some GPU machine learning), and along the way it updated my drivers and the problem hasn't happened since, for several weeks. So *now* I think it's finally fixed.</p>
<p>I have a co-worker who experiences the same issue; the crash ONLY happens during webex sharing. We've updated drivers and I've expanded the nvlddmkm.sy_ from the Nvidia folder manually with no luck</p>
<p>will changing the os to windows 8 change.</p>
<p>Greeting all! dear friends i buy a new headphone ( creative 3d rage alpha) because my new device have own sound card i turn off my sound card ( on board-realtek) and VOILA! all my problems dissapear! ALL! no more driver crash no more black screen. . maybe this help and belive me i try every sollution before , my pc : amd a10 7850 kavery , MB asrock fm2a88xextreme6+, Gigabyte gtx 760 - nvidia , 2x4 GB Corsair vangeance and 470w psu.</p>
<p>Remove the Intel Display Driver (If installed) and try to downgrade the Drivers. I had the same issue with all 347.xx updates then i installed 344.75, my issue fixed.</p>
<p>Fixes are as below: </p><p>1. Make sure you are not overheating or overclocking </p><p>2. Update your graphics driver with <a href="http://drivethelife.com/" rel="nofollow">free driver udpate software DriveTheLife </a></p><p>3. Change registry key: </p><p>Use &rdquo;Run&rdquo; and type &rdquo;regedit&rdquo;<br>HKEYLOCALMACHINE &gt; SYSTEM &gt; Currentcontrolset &gt; control &gt; graphicsdrivers. Right click &rdquo;graphicsdrivers&rdquo;, click new &gt;Dword (32-bit) value (If you are using 64bit system, please select Dword (64-bit) value), specify the name as<strong>TdrDelay</strong>and modify the value to<strong>8</strong>.</p><p>4. Nvidia Control Panel -&gt; 3D Settings -&gt; Set PhysX configuration -&gt; Select a Physx processor -&gt; choose your<strong>graphics card</strong>instead of leaving it on auto-select. </p><p></p>
<p>Thanks !!</p>
<p>Thanks !!</p>
<p>Thanks !!</p>
<p>so what are the fixes? i dont see them? </p>
<p>At the top of the page is a button that sez &quot;9 steps&quot; go thru those....</p>
<p>I really don't know what to say ... Just thank you </p>
<p>Confirmed 4 days non stop Battlefield 4 on high to ultra settings.</p>
<p>So i did the windows update, and driver update first, but one thing with driver updates is that I manually combed through the system and uninstalled/deleted anything NVIDIA related.</p><p> I proceeded to install the latest driver 344.11 i believe, and didnt install GEFORCE EXPERIENCE, for i hear it is glitchy with updates.</p><p>I was good, but then proceded to get a blue screen BUT was after a short power outage. So i tried option 1 setting PCIE to OFF. and was able to play Battlefield 4, Modern Warfare 2 and Fable, on high settings with no issue. </p><p>For me i think in the end it was a power supply issue, for a few times while my computer would boot up i would get a message stating that my supply wasnt recognized, i think it is just failing on me, im stationed overseas and get power outages every now and then ( invested in a surge protector now and new supply is on the way). </p><p>So i believe my computer was blue screening due to the PCIE option being on max and when my supply wasnt putting through the right power the card was being treated as insufficient power or something, and shuting itself off to prevent damage. I can somewhat confirm this due to it happening literally right after the short brown-out I had.</p><p>If the OP could confirm this, and if i can last through the weekend playing games constantly, it should be a fix. At least for people with power issues like myself.</p><p> Because nvlddmkm.sys is really just a compuers way of saying &quot;hey something happened, we dont know what, so we shut down to be safe&quot;</p><p>I will post a reply in a few days and give an update.</p>
<div>None of these solutions have helped. And I did not want to buy a new graphics card. So I came up with the solution (after a long search) that you need to put the CPU Core voltage of 1.25 V . And since it works wonderfully. <br>I have a i7 4770K CPU and a NvidiaGeForce GTX 680.</div>
<p>The major problem seems to be in overheating, so changing the voltage should help, at least for CPU temperature. I'm curious if there is much performance loss which lowering the voltage. Thanks for the advice! Amazing that this bug still happens after almost 5 years and 4 lines of new cards.</p>
@safrane --- All versions of DirectX are designed to be backwards compatible and do not overwrite newer versions with older ones. However, some versions have files that are specific to them and these get copied onto your system and can exhibit anomalous behavior, usually caused by something peculiar to your hardware and configuration. Most game installers will safely let you bypass the DirectX installation. For example, if you know the game was designed in DirectX 9 and you have Vista or better, then your Direct X 10 or better trumps theirs and you can safely ignore their DirectX installation unless the game requires drivers specific to your hardware.
DirectX can also cause nvlddmkm errors, recently I installed an older game which for some reason decided to update DirectX on my Win 7 x64 OS, after which nvlddmkm started to TDR crash every 5 minutes even when web browsing only, with MSI Afterburner showing GPU usage spikes of up to 100% and insane power spikes of up to 399%. Tried disabling Aero, clean reinstall drivers with Driver Fusion etc but the problem persisted. I almost considered RMAing the GPU. <br> <br>Thank god I discovered an automatic system restore point (My OS drive is a very small 64GB SSD, and I only had 2 restore points) before I installed that game, named &quot;Installed DirectX&quot;. I was able to successfully revert back to the old configuration and the nvlddmkm error went away, for now at least.
Thanks for this guide. My particular solution was the one related to improving the ventilation. Just cleaned my laptop's heatsinks/airvents with a compressed air can and voila, error is gone! Thanks again!
It seems that memory incompatibility is sometimes the cause of this error. This can often be fixed by flashing your BIOS to a newer version. Until now I've only seen this work on the first generation i5 motherboards (socket 1156) which had a lot of memory incompatibility problems. It might work on other boards as well though. <br> <br>This can be worth a try before buying new RAM if the RAM itself is fine and you don't have other problems. <br> <br>Warning: Do not Flash your bios if your system is very unstable. Take RAM modules which are not functioning properly out of your system before attempting to flash your bios (provided that you have atleast 1 RAM module left of course). Broken or incompatible RAM increases the changes of Flashing going wrong significantly! <br> <br>Test your memory with MemTest86 to find memory issues. <br> <br>Note: Flashing your BIOS is always a little risky. If you make a mistake, the system crashes or you lose power during the Flashing process your motherboard might end up bricked. Make sure you know what you are about to do and try the first 7 or 8 'safe' options above first. <br> <br>Some BIOS Flashing tips: <br> <br>-Disable any overclocking before attempting this. <br>-Clear CMOS after Flashing (check mb manual or google). This is not always required. Do make sure you note any specific bios settings since this will reset them. You might for example want to write down your memory voltages and other specific things you or your computer vendor may have changed for specific hardware. <br>-After resetting your MB settings bij clearing CMOS you might want to reload the 'optimized defaults' or something similar in your BIOS configuration if this option is available. <br>-Run Memtest86 before attemting this and afterwards to check if you're memory is working properly. The tests 5 and 7 are best suited to check for stability by running them about 20 times. <br>-Find a good guide if you are not sure how Flashing works. Preferably one specific to your MB brand.
Power seems to be the main reason for this. If you still have a problem after following #1, make sure your PSU has enough power to drive the card, especially if you're running accelerated graphics across multiple displays. If you do, as a test, only use one display. You might notice less to no more problems.<br><br>My PSU has split rails. I was using a 6pin PCI-E adaptor, connected to 2x HDD power leads. This was coming from the same converter as all my other hardware, but when I used the proper PCI-E lead, it could draw enough power from the second converter and there have been no problems since. You might not have this problem, so your PSU might need to be upgraded to provide more power.
Yeahh!!, ITS WORKS!!!<br> <br> Here your trackback: http://forums.adobe.com/message/2987437<br> <br> and: http://forums.nvidia.com/index.php?showtopic=179747<br> <br> Thanks!!!.
Step 6 solved my problem. One of my 2G RAM chips must have failed. It was the same PNY chip I replaced about 18 months ago. I pulled the chip after one of the many crashes and it was noticeably warmer than the other chip.<br><br>I replaced the chip and the monitor &quot;squigglies&quot; stopped, it stopped freezing on videos and I stopped getting the Nvlddmkm Error! <br><br>My problem was with a Compaq Perserio. Thanks so much for your help. I have been fighting this problem for 6 months!<br><br>
Before replacing parts its worth checking your fans for dust build up on the fans and for dust clogging the ventilation grills and filters. <br>I had done all steps till step 6 without any luck. <br>I had a look at the CPU and Video Card fans and grills and they had dust collected. I cleaned them and whoola, no more Nvlddmkm Error! <br>On a side note my laptop (Dell XPS M1730) was also popping up the blue screen of death twice a day and occasionally the screen would just go blank as well as the Nvlddmkm Error.
Step 6 seems to have fixed my problem, at least I can now boot into windows without safemode ;)
this comment would be way to long if i posted all the info id like to. THIS WORKED !!!! . Followed to step #4 loaded and reloded over 17 games ... no display problem TY :D

About This Instructable