Display Driver nvlddmkm stopped responding

[TVeblen]

During the first 4 days of my new W7 install I was getting constant "Display Driver nvlddmkm stopped responding and has recovered" events (Event ID 4101 - Level 3 - Task 0 - 0x8000000000000). The best I can recall these events occurred when changing display settings. These events are occuring much less often now. The only instance in the past day or 2 was trying to start Autocad Lt 2010 (separate, bigger issue).

When I installed W7 it loaded the 186.18 driver. That driver folder still exits in C:\NVIDIA\Display Driver. I installed the latest nVidia driver - 195.62 - right after the motherboard drivers (second thing). The driver version in device manager is 8.17.11.9562. The option to roll back the driver is grayed out. There are no hardware conflicts.

Memtest and Prime95 tests are clean. I have 6GB of 1333 memory "overclocked" to 1333 in bios. This is because the i7-920 is a "fixed" processor and only defaults to 1066 memory.

Originally (day 1-2) the event occured when trying to switch to an aero theme. Today (day 5) I am using a modified aero theme and have no problems. Is it possible that W7 applied a bug fix transparently?

I have researched and there are many possible solutions offered. The most common is to to re-expand the nvlddmkm.sys file in System32. What do you folks here think/suggest I do?

 

[au22ru]

Try to remove one memory module. If it helps, discuss here:

http://www.sevenforums.com/graphic-cards/1348-driver-stopped-responding-recovered.html

Regards
Alex

 

[TVeblen]

I have tried everything regarding memory to no avail. The problem remains.
It's back now with a vengeance. Now the system blue-screens coming out of sleep (screen blinks in and out 4-5 times then crash).
In the past I reset the memory to Auto in Bios, set it at it's lowest speed, taken modules out, switched them, run memtest, and even let Windows Memory Diagnostics Tool give it a go. No change in behavior.
Today I completely uninstalled all nVidia drivers and software, deleted the folder, and rebooted. Windows installed "Nvidia GeForce GTX 260 (MS Corp - WDDM v1.1" device with a v8.15.11.8593 driver (it did this even though I had turned off "auto hardware download and install" feature). It did not crash coming out of sleep but did crash loading AutoCad Lt 2010. I reinstalled the newest nVidia driver 195.62 download. System crashed after blinking during the nVidia install (changing screen res). Changed desktop to Windows Classic and retried. Success. Changed back to Aero desktop - crash coming out of sleep. Nothing solved.

I am going to post over on "Crashes" forum with all my error reports and see what we can determine from that. (I posted this in Video hoping it was a common prob with an easy fix).

 

[Total]

Try this then post back -- start - control panel - admin tools - services -

Scroll down and disable the two Nvidia services ( I attached a picture ) . that should fix your issues ..

 

[TVeblen]

No joy. I stopped and disabled the services. crash coming out of sleep mode. crash running AutoCad 2010.
If I use a basic theme I seem to be able to use sleep mode.

 

[TVeblen]

A Clue?

I just went into the "nVidia Control Panel" > 3D Settings > "Adjust Image Settings With Preview" > and selected "Use My Preference for..." radio button and the driver wigged out before I could move the slider. Display Driver stopped a couple times and recovered before I was able to reselect "Let the 3D application decide" again and close the window with a "nVidia Control Panel has stopped responding" > Close the program option.

 

[Total]

I just went into the "nVidia Control Panel" > 3D Settings > "Adjust Image Settings With Preview" > and selected "Use My Preference for..." radio button and the driver wigged out before I could move the slider. Display Driver stopped a couple times and recovered before I was able to reselect "Let the 3D application decide" again and close the window with a "nVidia Control Panel has stopped responding" > Close the program option.

and you restarted the computer ??

 

[TVeblen]

Issue Solved: Bad video card

I put in a new GeForce 9500GT card and the latest nVidia drivers (195.62) and all my video issues are gone. The GTX260 is being RMA'd as we speak.

 

[dark41]

And we just replaced a 9500GT with 195.62 drivers with another new 9500GT and 196.34 beta drivers. Still gives the "display has recovered" error. I really don't think this is a video card problem, as much as a corrupted drivers by Windows 7/Vista error.

 

[TVeblen]

And you could be right. This TDR issue is so prevalent across both Vista and W7 platforms, with both nVidia and ATI engines, and across every brand of video card that it would be foolish to rule that out. The fact that there is no one solution that works for everyone makes it all the more frustrating.

This is a good read: NVIDIA Statement on TDR Errors - NVIDIA Forums

Who made your card? Some brands have the problem more consistently than others. You could check their forums for clues. I suspect that a video card must perform flawlessly to operate in a W7 environment. The 9500GT card I got was from PNY. When I got my replacement GTX260 and installed it the video problems were gone. It could not be more clear, in my case, that the card was the problem.

The drill:
Check the hardware connections - re-seat the video card and memory, make sure the contacts are clean.
Run Memtest and be sure there are no memory errors.
Run Prime95 for 12 hours or more without errors.
Test the power supply. Be sure it has the ample amperage for your card and the system. You can use a multimeter to measure for a steady 12v to the card's power connectors.
Check for and install an updated BIOS, particularly if it says the new BIOS corrects memory errors or bug fixes.
Uninstall all video software and the drivers. (Some people say to run a cleaner program, some say this is unnecessary). Let W7 install it's own driver. Check for video problems using the windows driver.
Install the latest drivers for your card. Or try older drivers. Always completely remove the old stuff every time.
If you have honestly done all of these diagnostics and the card still does not work than there is not much left to consider other than it must be defective. Although two defective cards in a row would be pretty rare.
If you really think the issue is with the OS you might try a new, clean install.
HTH

 

[dark41]

We might have it working as of today, or at least cut back considerably as we didn't see it in 2 hours and were able to reproduce it in a matter of minutes previously (on a realestate.com.au web page with all sorts of flash ads, just scroll the mouse and slide it around the page).

We've built 15+ systems with the Asus EN9500GT Magic (512MB) video card. This is the only one that errored. After doing most of what you mentioned (except check the 12v rails as I'm sure that's not a problem with a Corsair VX450w, and Prime95 wouldn't prove anything either way other than the system is stable or also has other problems) and a few more fixes that I've seen scattered around the internet (underclocked 1333MHz memory to 1066MHz, changed the Power Management Mode in 3D settings to "Prefer Max Performance", make sure BIOS was set to Plug and Play OS: Yes (actually wasn't included in this BIOS), removing update kb952287, and trying 1 stick of RAM) with nothing solving the problem.

I put everything back to the way it was, then I uninstalled NV drivers and swapped the video card with an ATI 4350, and ran Ccleaner to rid the system of as much NV remains as possible automatically upon booting up again. It ran fine for an hour, so I got brave. I reinstalled his original video card with the original drivers and again ran Ccleaner to rid the system of as much ATI remains as possible automatically. Then we surfed the web, and specifically the realestate.com.au website (as that's where this customer believes they have the most problems and we fairly easily reproduced it earlier). 2 hours without a single crash. At this point I have my fingers crossed that its gone, or slowed down to almost gone.

Everything I've seen is either a work around, or the only way of really getting rid of it was by changing to a video card that uses a different driver. All the more reason that Windows corrupting the drivers makes sense to me (which might well effect all versions of the same driver family for same or similar cards). But again, I won't be sure this is gone until they run it for a few weeks without the error.