Sign in with
Sign up | Sign in
Your question

(MSI GTX 680 Lightning) NVIDIA Windows Kernel Mode Driver stopped responding (Along with nvlddmkm)

Last response: in Graphics & Displays
Share
September 19, 2013 1:07:15 PM

I've been suddenly having problems with my Computer that results in a brief "lag" (Choppy noise, slower mouse movements, processing speed takes a hit, etc.) and then my monitor goes black and detects "No Input". Then a little notification bubble pops up and says

Display Driver NVIDIA Windows Kernel Mode Driver, Version 320.57 stopped responding and has successfully recovered.


Upon checking my Event Viewer I noticed that two things seem to be causing the problem.

1. NVIDIA OpenGL
2. nvlddmkm

This happened one day while I was using my computer (Minecraft) and then when I closed it, I started experiencing the problem. I did not install, nor update anything for the past few days (that includes drivers and Windows update, I set everything to "Notify Me")

What I have tried:

Re-installing NVIDIA drivers, old, new, BETA (In safe mode, Doing in normal boot up doesn't work for me. It shuts down my display and my computer periodically "Beeps")
Rolling Back (As far as 10 days ago.)
Clean Wipe of NVIDIA drivers (Once again, in safe mode)
Underclocking (? I don't know if I did it right...) GPU
UPDATE 09/19 #1: I have tried the registry edit to turn off TDR; Doesn't help, I end up BSOD-ing...
UPDATE 09/19 #1: Cleaning my computer, I noticed no cables loose or anything not seated properly. No burn sent, nor any problem with temperatures.

What I did Notice:

Before the spike, I see that my GPU load floods to 100%
My clock speed (or so GPU-Z says) jumps to 8100MHz (<--- WHHAT?)
I ALWAYS "Lag" in the screen where it "auto locks" your computer when after idling.

PS:

I'm running:

ASUS Sabertooth Z77
i7-3770K (Not OC'd)
MSI Lightning GTX 680
16GB Corsair RAM
Windows 7 x64


Some pictures (or text, in spoilers):

Error Message
Spoiler


Event Log 1
Spoiler
Display driver nvlddmkm stopped responding and has successfully recovered.


Event Log 2
Spoiler
The NVIDIA OpenGL driver detected a problem with the display
driver and is unable to continue. The application must close.


Error code: 3
Visit http://www.nvidia.com/page/support.html for more information.



Can anyone help me?

Thanks!

--

Jopika

UPDATE 09/19 #1 @ 5:30 -7 UTC
a c 83 Î Nvidia
a c 103 Ĉ ASUS
a c 232 U Graphics card
September 19, 2013 1:15:53 PM

327.23 is current driver...update may help

http://www.geforce.com/drivers/results/66884

However, I have seen this error dozens of times and on dozens of machines

here's the explanation .... that's a short exerpt I quoted, read full explanation.

https://forums.geforce.com/default/topic/413110/geforce...

Quote:
As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur.

Things to check or consider initially in your troubleshooting:

Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this here (full credit to DJNOOB for this).
If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.
If the issue is only with a specific game, check for patches.
If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.
Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.
Check that your RAM is running at the correct settings as defined by the manufacturer.
Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.
Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically.
m
0
l
September 19, 2013 3:47:06 PM

JackNaylorPE said:
327.23 is current driver...update may help

http://www.geforce.com/drivers/results/66884

However, I have seen this error dozens of times and on dozens of machines

here's the explanation .... that's a short exerpt I quoted, read full explanation.

https://forums.geforce.com/default/topic/413110/geforce...

Quote:
As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur.

Things to check or consider initially in your troubleshooting:

Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this here (full credit to DJNOOB for this).
If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.
If the issue is only with a specific game, check for patches.
If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.
Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.
Check that your RAM is running at the correct settings as defined by the manufacturer.
Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.
Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically.


Thank you for your post.

However, as I said, I have tried to download MULTIPLE different drivers, the driver that was posted proved to be the "most" stable (It didn't bug every 4 seconds). The download however, did improve it a bit, but did not fix the problem.

UPDATE: I have tried the registry edit to turn off TDR; Doesn't help, I end up BSOD-ing...

m
0
l
Related resources
September 20, 2013 9:24:45 AM

UPDATE:

I have tried to uninstall all of NVIDIA drivers, remove the excess registry values, and then reinstalled them.

No luck so far...
m
0
l
September 23, 2013 10:40:53 PM

I'm not sure if you are running Skype in the background, but I've been having this same exact issue, and I turned it to 'Do Not Disturb'; it lowered the frequency greatly. When I turn it off, its near never. This means jack of course if you don't have Skype.
m
0
l
October 1, 2013 7:53:09 AM

Hi Jopika,

I too had this same error with my rig. I re-installed clean drivers and even RMA'd my GPU with EVGA. But this did not solve it...
Asus Sabertooth Z77
i5 2500k OC'd 4.8Ghz
EVGA GTX680 SC+2
8GB Crucial Ballistix Sport
Corsair TX750M
Windows 8 64-bit

I then noticed a spike in GPU activity before the crash, AND when the temp of the card reached 77 degrees, using EVGA Precision X. So I made a custom fan profile using the program, so that when temperatures reached 75 degrees, the fan speed increased dramatically to keep temps below 75.

This has FIXED the problem and I haven't had a driver crash since.

m
0
l
October 14, 2013 5:40:38 PM

I've recently been getting this issue too: Display driver nvidia windows kernel mode driver, version 327.23 stopped responding and has successfully recovered. I have an EVGA GTX650Ti Boost SC 2GB. My GPU temps almost never go past 70C (I have the temp overlay whenever I play a game). I've just been playing Payday 2 and World of Tanks and it has happened during both games. I've tried reinstalling the GPU driver but it didn't fix anything. I'm running WIN7 x64. Hopefully the more info we can gather on the problem the more we have a chance of fixing this issue.
m
0
l
October 28, 2013 4:10:05 AM

Camel51 said:
I've recently been getting this issue too: Display driver nvidia windows kernel mode driver, version 327.23 stopped responding and has successfully recovered. I have an EVGA GTX650Ti Boost SC 2GB. My GPU temps almost never go past 70C (I have the temp overlay whenever I play a game). I've just been playing Payday 2 and World of Tanks and it has happened during both games. I've tried reinstalling the GPU driver but it didn't fix anything. I'm running WIN7 x64. Hopefully the more info we can gather on the problem the more we have a chance of fixing this issue.


Does the driver crash every time the temperature reaches a certain value, or at random times for you?
m
0
l
November 1, 2013 6:57:27 AM

Had this problem for months on a new Win 8 build - every driver release - even RMA'd my GFX card and still had the problem with the replacement. Tried numerous things including BIOS settings and nothing worked. The drivers would always crash at least a few times a day. Well it's been 3 days with no crashes so it seems I finally found a solution that works!

Open the NIvida control panel & go to Manage 3D settings. Change the Global settings power management mode from adaptive to maximum performance. Do the same for each program in the program settings. Some may already be set to maximum but others wont. My crashes never happened during gaming - only other programs like firefox etc. as the games were already set to maximum.

I know how annoying an issue this was for me so I hope this helps, give it a shot, worked for me!
m
0
l
November 3, 2013 9:47:22 AM

FoxyCoxy said:
Camel51 said:
I've recently been getting this issue too: Display driver nvidia windows kernel mode driver, version 327.23 stopped responding and has successfully recovered. I have an EVGA GTX650Ti Boost SC 2GB. My GPU temps almost never go past 70C (I have the temp overlay whenever I play a game). I've just been playing Payday 2 and World of Tanks and it has happened during both games. I've tried reinstalling the GPU driver but it didn't fix anything. I'm running WIN7 x64. Hopefully the more info we can gather on the problem the more we have a chance of fixing this issue.


Does the driver crash every time the temperature reaches a certain value, or at random times for you?


It seems to be random. It seems to happen more when I have my GPU overclocked but does also happen at stock speeds. My OC'd specs are Power 110% GPU Clock Offset +55mhz mem clock offset +400mhz
m
0
l
November 4, 2013 1:45:30 AM

Camel51 said:
FoxyCoxy said:
Camel51 said:
I've recently been getting this issue too: Display driver nvidia windows kernel mode driver, version 327.23 stopped responding and has successfully recovered. I have an EVGA GTX650Ti Boost SC 2GB. My GPU temps almost never go past 70C (I have the temp overlay whenever I play a game). I've just been playing Payday 2 and World of Tanks and it has happened during both games. I've tried reinstalling the GPU driver but it didn't fix anything. I'm running WIN7 x64. Hopefully the more info we can gather on the problem the more we have a chance of fixing this issue.


Does the driver crash every time the temperature reaches a certain value, or at random times for you?


It seems to be random. It seems to happen more when I have my GPU overclocked but does also happen at stock speeds. My OC'd specs are Power 110% GPU Clock Offset +55mhz mem clock offset +400mhz


Well the card would get hotter when overclocked...so maybe it is down to temperature? Maybe one thing you can try is removing the overclock, and make a custom fan profile that increases fan speed (a lot) when the temps hit 63 degrees. Run a demanding game, which puts a lot of load on the GPU and see if it still crashes?
m
0
l
November 4, 2013 2:45:42 AM

Presler said:
There's an important update in windows update which directly relates to issues with kernel mode drivers. The title of the update is self-explanatory so you don't have to search for it throughout all the updates. Try installing that update and see if it fixes the issue. There are many other performance and reliability updates also available. Try them too later on one by one. I've them all installed since a couple of months and its still going good.


Can u give my a link where i can find that updates?
Because i can't find them

m
0
l
November 5, 2013 10:52:11 AM

Presler said:
http://support.microsoft.com/kb/2685811

Go to control panel->System and security->review your computer's status->Windows update(in bottom left pane of window)->Check for updates->view important updates-> now you should see all the important updates. (if web link did not work)


O, you mean that updates. I had already instal them.
I have tried many options but nothing works for my.
I'm thinking to reinstall windows. Do u think that can be the trick?

m
0
l
December 10, 2013 8:35:36 PM

my english is not good but i had this issue with my asus maximus extreme IV, i updated the bios and i had this issue, so you need to downgrade the bios version, if you need any help contact me, is really easy, my email is marlonesco@gmail.com
m
0
l
December 24, 2013 6:15:16 AM

JackNaylorPE said:
327.23 is current driver...update may help

http://www.geforce.com/drivers/results/66884

However, I have seen this error dozens of times and on dozens of machines

here's the explanation .... that's a short exerpt I quoted, read full explanation.

https://forums.geforce.com/default/topic/413110/geforce...

Quote:
As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur.

Things to check or consider initially in your troubleshooting:

Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this here (full credit to DJNOOB for this).
If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.
If the issue is only with a specific game, check for patches.
If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.
Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.
Check that your RAM is running at the correct settings as defined by the manufacturer.
Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.
Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically.


Jopika said:
JackNaylorPE said:
327.23 is current driver...update may help

http://www.geforce.com/drivers/results/66884

However, I have seen this error dozens of times and on dozens of machines

here's the explanation .... that's a short exerpt I quoted, read full explanation.

https://forums.geforce.com/default/topic/413110/geforce...

Quote:
As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur.

Things to check or consider initially in your troubleshooting:

Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this here (full credit to DJNOOB for this).
If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.
If the issue is only with a specific game, check for patches.
If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.
Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.
Check that your RAM is running at the correct settings as defined by the manufacturer.
Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.
Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically.


Thank you for your post.

However, as I said, I have tried to download MULTIPLE different drivers, the driver that was posted proved to be the "most" stable (It didn't bug every 4 seconds). The download however, did improve it a bit, but did not fix the problem.

UPDATE: I have tried the registry edit to turn off TDR; Doesn't help, I end up BSOD-ing...



hi. im having exactly the same problem. u quoted "Check that your RAM is running at the correct settings as defined by the manufacturer.".i realy didn't understand what u meant . however i just bought a new 2gb ddr3 memory ram and i have already another one like that so im soposed to have 4gb of memory ram but i have windows 7 32 bit so i have only 3.44 usable of ram. some guy told me that its bad if u keep that 32 bit system .could that be the problem ? .
m
0
l
January 5, 2014 4:17:16 AM

Guys sorry for bring up an old thread but I just wanted to let every know who has this proplem from now on, I think ive figured out what cause the proplem with the display driver kernal mode to stop respond.

Its a windows update, in the optional section called "Update for Kernel-Mode Driver Framework version 1.11 for Windows 7 for x64-based Systems (KB2685811)"

I think this is what causes it, Ive reinstalled windows 7 and havent had any proplems with the error whilst playing games like mass efect 2 dragon age 2 ect. and I havent installed that update either.


m
0
l
February 2, 2014 8:24:40 AM

I did something that worked for me, I dont know if it will work for you guys. I went to my NVIDIA Control Panel (Right click desktop or just search it) and then went to Manage 3D settings under the 3D settings tab, then go down to Power Management Mode under Global Settings tab, and select "Prefer Maximum Performance" rather than "Adaptive". This seems to solve the problem, at least for me it did.
m
0
l
February 6, 2014 12:25:09 PM

don't want to beat an old drum but it has been a problem that seems to affect Asus boards...other forums have concluded that enabling XMS profile in bios has completely eliminated this issue... remember that GPU vram overload gets handed off to onboard ram.. without a response que the driver crashes
m
0
l
March 3, 2014 5:53:10 AM

Same issue here since driver version 327 to :(  runing win8 64x on asus p5dwh deluxe (yes its old) and my gpu is ngtx570 tf3 from MSI from what ive come up so far theres no fix for this yet, my guess is nvidia problem and they must fix this.
m
0
l
April 12, 2014 7:02:01 AM

I have the same problem but solved the problem when I uninstalled the graphics card program and installed 332.21. I do not know why but everything works now.

Windows 7
Nvidia GeForce GTX 680
Intel core i5-3570k cpu 3,40 GHZ
Ram 16 GB
m
0
l
April 15, 2014 4:59:19 PM

13082063,0,1634054 said:
I have the same problem but solved the problem when I uninstalled the graphics card program and installed 332.21. I do not know why but everything works now.

Well i detected bad sectors in one of my hdd and remove de disk and had no problems untill last week :(  the same problem again with some artfacts now ive changed OS to win7 made a clean install of both OS and drivers to 335.23 and still cant play games and cant understand what is wrong. :( :( :( 
m
0
l
!