nvlddmkm stopped responding and recovered

awott10

Honorable
Dec 29, 2013
25
0
10,530
Specs:
Motherboard: MSI 790FX-GD70
CPU: AMD Phenom II X4 965 (3.4ghz)
Memory: 8GB (2 x 4) DDR3
PSU: 730 Watt
GPU: Galaxy GeForce GTX 670
OS: Vista SP2

I recently upgraded from the geforce 460 to the 670 and when I did I started to have problems with games freezing and the "nvlddmkm has stopped and recovered" error that I have seen so many others have a problem with throughout the years. That is the only change in my system, hardware or software wise.

I'm not sure how to pinpoint the problem. I can play a game and not have a problem for a long time, in others it happens fairly quickly. I ran some GPU performance tests to put it under heavy load, and it failed to get through any before the "nvlddmkm has stopped and recovered" thing would pop up. It happened once just watching a video on youtube using Chrome, though that has not happened since.

Also, I thought I should note, I have read a ton of other forum posts about this problem, many of which mentioned that they could continue playing their game and stuff after 15-20 sec of a black screen. I cannot. Mine fails to the point where I have to kill the process to get back to the desktop.

I have tried many different drivers to no effect, changing the TDR registry settings, removing the factory overclock on my GPU (at least I think I did, I have never messed with overclock settings before), and a host of other small things I can't remember (like changing the Windows theme to classic). Nothing is overclocked that I am aware of unless it came packaged overclocked.

Temperature does not seem to be the issue, as I have not seen it go even close to above 65 celsius when playing any kind of game.

I don't think that it is a PSU problem, as I am fairly certain my 730 watts is plenty for the card and other components, especially as none are overclocked. In terms of voltages, I do not know, I am not knowledgeable enough about them.

I'm not sure whether it is a memory problem. I only say not sure because I do not know enough about how they may interact/effect my GPU. I have had the sticks for a decent amount of time now and have not seen any kind of problems whatsoever. As I mentioned earlier, the only new addition to the system was the GPU.

I just recently updated to the driver framework from Windows, which did not fix it.

I have thought about updating the BIOS, but from what I have read, the only difference between my version of the BIOS and the newest one is an updated AGESA code, which as I understand would not necessarily affect my system at all.

Does anyone have any suggestions? Could my other hardware be causing throttling problems? I don't think they are that outdated/poor enough to do that though...
 

awott10

Honorable
Dec 29, 2013
25
0
10,530
I don't know if this means anything, but I looked at the dump file associated with TDR and it highlights two specific drivers, "nvlddmkm" and "dxgkrnl.sys." I'm not sure what that means exactly. But upon looking at it further, the program specifically points out "dxgkrnl.sys" as the driver responsible for the crash. Those two are paired in quite a few of the crashes.
 

awott10

Honorable
Dec 29, 2013
25
0
10,530
Now on further research, I wonder, could my HDD be at cause for the problem? Could poor data transfer be the reason for the problems? I honestly don't know but would love some feedback. I just looked at the S.M.A.R.T. data for my HDD and the fitness bar is at 0%.... From the short research I have done, that basically means it is on its last legs. So am I looking at replacing that?

The info is here: http://www.hddstatus.com/hdrepshowreport.php?ReportCode=7691614&ReportVerification=074E1253
 

awott10

Honorable
Dec 29, 2013
25
0
10,530
So I have now tried the video card in an entirely different PC and ran a benchmark test to put in on a heavy load - no problems, no errors whatsoever. So I think that would rule out the GPU in terms of causing the issue.

I have also now switched it to a different slot, which had no effect.

And I have switched out my ram, which had no effect.