Nvidia - nvlddmkm.sys crash

[dpk33]

Hi,

I've been running my setup for years without any problem. However, for the past two or three days, I've been encountering an error with nvlddmkm.sys, as per WhoCrashed. I have not installed any new software besides drivers or made any hardware changes in the past few weeks.

I noticed recently that Nvidia has been having problems with their drivers, but the driver I'm using is from 2014. I'm particularly puzzled since everything was working fine for months and the problem just seemingly came out of nowhere. Does anyone have an answer or hypothesis to the problem? If there is anything else I am able to provide, please let me know. Thanks.


The WhoCrashed report is as follows:

On Wed 6/24/2015 6:53:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062415-13306-01.dmp
uptime: 00:06:10
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800511A128)
Bugcheck code: 0x116 (0xFFFFFA800A25D4E0, 0xFFFFF8800511A128, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.30
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.30
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 353.30 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR



My specs are:

Intel Core i7 2600k
ASUS P8Z68 Deluxe
2x4gb ram
EVGA GeForce GTX 570 HD
Windows 7 Ultimate 64 bit


Here is a Speccy report:
http://speccy.piriform.com/results/FW1LyffVISKdpKtramunDL0

 

[Burpo]

Simple enough to fix. Go into control panel, device manager, display, properties, driver, Roll back or uninstall driver. Refresh & select an earlier driver. I haven't had a driver issue in yrs. and I have a GTX 570 running Windows 7 Pro. I use mine for video editing, and use CUDA. For me, the last good driver was Sept. 2013. I'm not saying you have to go that far back, but it seems you had a working system, then GeForce Experience updated your driver. I don't allow it to for this very reason.

 

[dpk33]

Simple enough to fix. Go into control panel, device manager, display, properties, driver, Roll back driver. I haven't had a driver issue in yrs because I quit updating mine. I have a GTX 570 running Windows 7 Pro. I use mine for video editing, and need CUDA. The last good driver was Sept. 2013. I'm not saying you have to go that far back, but it seems you had a working system, then GeForce Experience updated your driver. I don't allow it to for this very reason.

I haven't updated the driver since mid 2014, I'm on the same driver now. The problem started completely out of nowhere. I should have included that in the op, my bad.

 

[Burpo]

The driver you're reporting that you use in your OP (353.30) was released 2 days ago. Like I said, GeForce Experience has been updating your drivers automatically since 2014.

http://www.nvidia.com/download/driverResults.aspx/86504/en-us

I'm still using 314.22 for the CUDA support..
Read why here..
https://forums.geforce.com/default/...orce-gtx-560-ti-crashes-with-video_tdr_error/

Alternativley, you may want to try EVGA's Precision fan control software & ramp up fan speeds.. See below..

https://forums.geforce.com/default/...nd-for-tdr-crashes-black-screens-etc/#3993428

 

[dpk33]

The driver you're reporting that you use in your OP (353.30) was released 2 days ago. Like I said, GeForce Experience has been updating your drivers automatically since 2014.

http://www.nvidia.com/download/driverResults.aspx/86504/en-us

I'm still using 314.22 for the CUDA support..
Read why here..
https://forums.geforce.com/default/...orce-gtx-560-ti-crashes-with-video_tdr_error/

Alternativley, you may want to try EVGA's Precision fan control software & ramp up fan speeds.. See below..

https://forums.geforce.com/default/...nd-for-tdr-crashes-black-screens-etc/#3993428

I ended up rolling back to 331.82, but the problem still persists.

On Thu 6/25/2015 12:51:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062415-16177-01.dmp
uptime: 00:01:46
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880107CB2BC)
Bugcheck code: 0x116 (0xFFFFFA800930D010, 0xFFFFF880107CB2BC, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.82
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.82
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR

I can't seem to find 314.22. Either way, I've been fine up until recently. Is it possible that there was a sudden "breaking" of one or more pieces of hardware? I haven't changed any hardware, nor have I installed any new software.

 

[Burpo]

Then you haven't "ended" anything. LIKE I SAID, I'm having no issues using the last good CUDA supported driver 314.22, but others have used work arounds that include speeding up the GPU fans. You'll have to do whatever it takes to resolve this driver issue, and that's what it appears to be. Whether you need to do a clean driver install, or possibly clean your fans & speed them up, it is fixable. The new drivers are more geared towards improving performance on the 700-900 series GPU's. The 500 series isn't even being thought of by Nvidia now. An updated driver caused this. They want you to buy a new card.

314.22
http://www.guru3d.com/files-details/geforce-314-22-beta-driver-download.html

 

[Burpo]

I can't seem to find 314.22. Either way, I've been fine up until recently. Is it possible that there was a sudden "breaking" of one or more pieces of hardware? I haven't changed any hardware, nor have I installed any new software.

I've explained this as clearly as possible & provided links for you to read & understand your problem. You have the GeForce Experience software installed. IT IS UPDATING YOUR DRIVERS! Nvidia's sneaky way of landing new video card sales.

You didn't have a problem until 2 days ago. Coincidence that the driver on your system is 2 days old?
A guide for a clean driver install.
https://forums.geforce.com/default/...-ensure-your-drivers-are-installed-properly-/

 

[dpk33]

Okay so I uninstalled GeForce Experience, display driver and everything else Nvidia related. Driver swept/DDU'd it. Clean installed the 314.22, with NO geforce experience. Still experiencing the same problem.

 

[Burpo]

You haven't done something right, and it seems you don''t like to read or fix the issue at hand.. Buy a new card.. Good luck

 

[VirtualLarry]

Okay so I uninstalled GeForce Experience, display driver and everything else Nvidia related. Driver swept/DDU'd it. Clean installed the 314.22, with NO geforce experience. Still experiencing the same problem.

Then check your RAM, either with a bootable Memtest86+ CD overnight, or use Win7's built-in memory test.

Remove your card, clean it out the best that you can, and make sure the fans still spin freely.

Re-install the card, check card and CPU temps while gaming.

It may be due to a failing / weak PSU too. What brand / model / wattage do you have, and how old is it?

 

[Burpo]

He had no problem until 2 days ago, EXACTLY the time his PC took an update from GeForce Experience.

A simple Windows Restore to previous date & reinstall the older driver should correct the issue.

However if he has EVGA's Precision fan control software installed, all bets are off. FUBAR registry

 

[VirtualLarry]

He had no problem until 2 days ago, EXACTLY the time his PC took an update from GeForce Experience.

A simple Windows Restore to previous date & reinstall the older driver should correct the issue.

However if he has EVGA's Precision fan control software installed, all bets are off. FUBAR registry

If NV's newest drivers are KNOWN to cause TDR problems on 570 cards, wouldn't there be buzz on the internet and a long thread on the GeForce forums dedicated to the issue?

If that's true, then I'll lean towards your theory. But until then, I'm going to assume the the problem is not purely the drivers, but rather some hardware in OP's PC has become marginal.

Edit: Certain drivers are more or less sensitive to marginal hardware. But that doesn't mean that it's purely a driver problem, only that it has exposed a hardware problem.

 

[Burpo]

Op hasn't answered if he has EVGA's fan control software installed. I believe that could cause a problem with the new drivers, and not be widely known on the net. It's only been 2 days & he didn't even know his drivers were updated.

Once Nvidia dropped CUDA support for the 500 series cards, I had no choice but to go back to 314.22. I NEED CUDA. The side effect is I've had no driver crashes/issues since.. GeForce Experience may be nice for updating newer cards, but detrimental for the older ones. Nvidia wants people to replace their older cards, believe that..

 

[VirtualLarry]

Once Nvidia dropped CUDA support for the 500 series cards, I had no choice but to go back to 314.22. I NEED CUDA.

NV dropped CUDA support altogether for 500-series and older cards, in drivers newer than 314.22? Proof? They still sell 400-series lower-end cards in retail, don't they? Would seem that NV through their OEMs and distributors would be guilty of false advertising features if that were true.

 

[VirtualLarry]

I'm still using 314.22 for the CUDA support..
Read why here..
https://forums.geforce.com/default/...orce-gtx-560-ti-crashes-with-video_tdr_error/

Well, after several crash and burns, looks like my GTX 560Ti still crashes and fails even after i rolled back to 314.22.

That's a very short thread, with little supporting technical documentation, and basically just another forum member suggesting to use 314.22 to avoid TDR errors.

Says NOTHING about dropping CUDA support in newer drivers.

And rolling back to that driver version didn't help that person either, just like it didn't help the OP here in this forum.

 

[Burpo]

http://forums.guru3d.com/showthread.php?t=391269

https://forums.geforce.com/default/topic/775543/geforce-drivers/gtx-560-ti-cuda-question/

Proof is my sh*t quit working until i went back to the old driver..

In reference to your above post, I realized I posted the wrong link Larry. I just did a quick search, there are other threads about the problem. I actually use my GTX 570's 448 CUDA cores, and when they changed drivers for the newer hardware, all my programs that used CUDA would not detect or work until I rolled back drivers..

 

[VirtualLarry]

http://forums.anandtech.com/showthread.php?t=2437075

They didn't remove CUDA support. They removed some sort of CUDA-based video-encoding API. Not the same thing.

Edit: Not saying that NV isn't greedy, and trying to force users to upgrade their video cards pre-maturely, though.

Let's get back to the OP though. Just because NV dropped CUDA video-encoding API in newer drivers, it shouldn't have anything to do with the TDR errors, etc., that OP is experiencing. I suggest he start hardware troubleshooting.

 

[Burpo]

Semantics.. :|
That's great.. I like your suggestion. Check every piece of hardware in the PC.

Op started out saying he hadn't changed hardware. software or drivers, yet he listed a driver that was 2 days old as his video driver. He had no clue that drivers were being installed automatically by GeForce Experience. I knew immediately and it only took me an hr to convince him, and then he just starts uninstalling & reinstalling random drivers.

Go ahead, chase hardware Larry..

I would have had this fixed in 20 minutes..

 

[VirtualLarry]

Semantics.. :|
That's great.. I like your suggestion. Check every piece of hardware in the PC.

Op started out saying he hadn't changed hardware. software or drivers, yet he listed a driver that was 2 days old as his video driver. He had no clue that drivers were being installed automatically by GeForce Experience. I knew immediately and it only took me an hr to convince him, and then he just starts uninstalling & reinstalling random drivers.

Go ahead, chase hardware Larry..

I would have had this fixed in 20 minutes..

Okay so I uninstalled GeForce Experience, display driver and everything else Nvidia related. Driver swept/DDU'd it. Clean installed the 314.22, with NO geforce experience. Still experiencing the same problem.

Ok, so he tried your solution, it didn't work, and instead of admitting that your solution may not have been the answer, you berated the OP for not following directions.

You haven't done something right, and it seems you don''t like to read or fix the issue at hand.. Buy a new card.. Good luck

 

[Burpo]

I don't see any be-rating.. I stated a fact. Op also said he couldn't find driver 314.22. I typed 314.22 in a google search & had the driver in front of me instantly, so the op must surely have done everything right.. I'm done here..
You got this right? Your GTX 570 must run sweet..

 

[VirtualLarry]

OP's other thread on this same subject:
https://forums.geforce.com/default/topic/848308/nvlddmkm-sys-crash/

And for the record, I don't own a GTX570, but I've owned a couple of GTX460's, some 430s, and some 630s.

Generally, I find a driver that works, that I like, and I stick with it. It's easier for me, since I don't really play games much, so I don't need to keep updating the drivers for the newest game fixes.

The thing that I don't get is, if all drivers newer than 314.xx cause TDR errors on GTX570 cards, as you've implied, then why is the OP only having the error NOW, even though you've proven to him that GFE has been updating his drivers all along on him.

Still, it seems possible to me that his hardware is marginal, and simply got more marginal, or the newer drivers were more sensitive to marginal hardware.

 

[Burpo]

Actually up to 340.37 drivers work for CUDA encoding (I think), but after checking frame rates, I like this one.. My GTX 570 HAS to work. :\
I'd bet dollars to donuts he has EVGA's Precision Fan software installed, tho he hasn't even said so. You're going to have problems with the software that controls the GPU fans, once drivers start getting changed. He likely has a FUBAR'd mess and is probably re-installing Windows as we speak. It's a shame that people do that instead of following directions to fix their problem. There's a guide I linked about how to uninstall/reinstall Nvidia drivers. Did he read & follow it, or not? Seems he just started uninstalling, DDU'd it, whatever, only compounding his problems.. I started working on PC's in 1981 and I do go with my hunch more often than not. Sometimes I am wrong, but not the majority.. Shrug.. I tried.. Your turn.. Night all

https://forums.geforce.com/default/...nd-for-tdr-crashes-black-screens-etc/#3993428

 

[VirtualLarry]

I'd bet dollars to donuts he has EVGA's Precision Fan software installed, tho he hasn't even said so. You're going to have problems with the software that controls the GPU fans, once drivers start getting changed.

I agree with that. Been there, done that.

I think I have 340.43 beta installed on my GT430. I don't know if I've tried to run any CUDA-based distributed computing on that PC or not. I guess that was just the newest driver out at the time when I put the NV card into that PC.

Edit: Also, for the year or two I used my GTX460 card, I went through a number of drivers, and I had some TDR-type errors, but only if I was overclocked (CPU or GPU), or temp-related (I had a SLI setup for a while).

 

[Ketchup]

Here is another thread on the subject:
http://forums.anandtech.com/showthread.php?t=2436552&highlight=

And the OP has shown an excellent reason why we shouldn't be grabbing all the optional updates Microsoft rolls out. If everything is working, don't mess with it.

dpk33, with a video card that is almost 5 years old, there is no reason to be updating drivers. I would remove anything that "tweaks" you video card, and possibly even the drivers you have. Also, double-check Device Manager, and make sure it is running the driver you installed.

 

[dpk33]

I decided to switch out the card for a GT 220 (I just got the card from a friend just now). Turns out, it was indeed a hardware problem, since the GT 220 worked fine and did not have the aforementioned error.

However, as Larry mentioned, it could be PSU problem. The GT 220 does draw far less power than the GTX 570. I have an Antec Earthwatts 650w from 2009, so that may be an issue. I guess I'm going to test the GTX 570 in another computer and see if it brings up the same problem, just to be sure.

The card never went above 75 degrees while under load (i'd have the error before that was even possible). Also, I do not have EVGA precision software or anything alike installed. I have disabled Windows Updates since 2014, so I'm sure an update would not have been the cause of the problem. I ran memtest for several hours so I assume I'm good on that too.