Nvlddmkm stopped responding is getting VERY OLD...

[Bokishi]

Yeah I been getting them with SLI, so i disabled Aero

[EverGreen]

Its not only with SLi, also the single GPU's who have the same nlvddmkm error, the nvlddmkm is the main driver who's is created when the nvidia drivers will installed after some collecting nfo bout your system, it doesn't depends what you do, even when you go back to the standard Vista nvidia drivers, or change your HW profile.
If Vista run with Ati cards and found no problem then the sollution lays within the nvidia drivers, TDR or not TDR, the 3D section of the card can't be activated, thats why the nvlddmkm driver burst out and make some bsods.
Nvidia did promise us to make more future updates for all cards, the 6x.xx will be next in the row.

[ekovalsky]

I think the TDR errors are multi-factorial, various unrelated problems can culminate in the nvlddmkm error. With single GPU systems, the culprits may include mismatched driver files, instabilities related to overclocking or memory, or otherwise occult incompatibilities between particular memory configurations and the 680i. There may also be Vista issues at play, like UAC; some have had the TDR errors resolve after turning UAC off.

On the other hand, there are systems which are 100% stable with any Nvidia driver in single GPU mode but begin to suffer the nvlddmkm error when switched to SLI mode. In my case this invariably happens with all the 16x.xx drivers, but never with the 158.45 drivers. Since nVidia enabled DX10 SLI functionality when migrating from 15x.xx to 16x.xx drivers, I believe there is still a driver fault involving DX10 SLI code.

Right now I'm fine with the 158.45, but I will be real pissed if Crysis comes out and I cannot take advantage of two 8800 Ultra cards in SLI which I bought to sustain good frame rates running native resolution on a 2560x1600 display.

[Brent101]

On the other hand, there are systems which are 100% stable with any Nvidia driver in single GPU mode but begin to suffer the nvlddmkm error when switched to SLI mode. In my case this invariably happens with all the 16x.xx drivers, but never with the 158.45 drivers. Since nVidia enabled DX10 SLI functionality when migrating from 15x.xx to 16x.xx drivers, I believe there is still a driver fault involving DX10 SLI code.

Right now I'm fine with the 158.45, but I will be real pissed if Crysis comes out and I cannot take advantage of two 8800 Ultra cards in SLI which I bought to sustain good frame rates running native resolution on a 2560x1600 display.

I'm with you on this one. I only get this error with sli enabled. It hasn't bothered me a whole lot and I suppose my patience is based on the fact I don't really have anything to play right now. Come Aug 21, if this error affects Bioshock and all the games that follows it this fall, then I will be pretty upset with Nvidia.

[Slammin]

I just found out something I had found out before, but wasn't sure. Here goes:

I just updated my mobo bios to a newer 1.3beta3 and as I'd run a previous 1.3 beta bios, I already knew a couple of things to expect; lower fsb and lower ram OC. I wasn't willing to accept that before, but as a side note, all TDRs went away back then.

Well, I ran FSX for 40 minutes straight and no TDR, so my guess is that this is in fact some kind of timing issue between system ram and vid ram, and it does get worse when Sli is enabled.

My next test will be to enable Aero, but I won't leave it enabled since it makes my cards run warmer, but I'll leave it on for a day or so just to see how things go.

For reference, with my old bios, I ran my 4 sticks at 3-3-3-6 1T@667Mhz. Right now I'm running 5-5-5-15 2T@810Mhz. Cpu@3510, which is one thing I do like about this bios (let's me run CPU higher with less vcore).

I'll report back tomorrow.


edit:

Well, still more testing to be done, but when I shoot for my max mem and fsb OC, I cannot even open Favorites in IE w/o TDR. When fsb is up, so is memory. I guess the next thing I need to do is try it with fsb up and memory timings relaxed. I've just been leaving my memory at 4-4-4-12 2T for all testing so far, and with that, I've tested fsb from 1066 - 1280 and mem @ 800 - 870 or so. At the high fsb end, again, TDR city. I'll set mem to 5-5-5-15 and try higher fsb again to give a difinitive, but as I always suspected, and makes sense too with the way Vista integrates system memory with vid card mem now, but there is definitely a connection. Of course, it could be running fsb out of spec too, but I'll find out tomorrow.

edit:

Oh well, nothing I do seems to make a difference, really. Back to 158.45.....

edit update:

Installed 163.16 and lowered my NB voltage from 1.55v to 1.40v and so far after trying everything that used to cause TDR, I am TDR free. I don't know if it is the 163.16 or my lowering NB voltage that fixed it, but maybe others here can try it.

[MaUiLoCaL]

At least from my experience this issue has been caused for me by installing extra nV Chipset and Raid drivers via Windows Update. Figured this out through a few installs of Vista. Trial and error you might say.:o

Once I decided to skip these optional updates according to MS...well I haven't seen the issue since.:D

[cabnz]

Is this problem only related to SLI motherboards?

[EverGreen]

Is this problem only related to SLI motherboards?

Nope its related to all mobo's, some brands slips true the mazes and did do their job.

[Zod]

.

[Zod]

159.24 OK. All 16x.xx drivers I've tried so far have this problem. Oblivion just doesn't work: black screen with cursor, then one frame of game, then frozen black screen with cursor ad infinitum.

8800 GTXs in SLI
Q6600
A8n-32X Max
2GB CellShock PC8000
Vista x64

all stock speeds

[Darky46]

System info:
Asus Striker Extreme
Asus Nvidia EN8800GTX/HTDP 768MB DDR3 (PCI-E)
OCZ 2x1GB PC8500 Platinum SLI-Ready Edition XTC DDR2 Dual Channel Kit
Intel Conroe E6300 Core2Duo (Socket 775, 1.86Ghz, 1066Mhz FSB, 2MB)
Coolermaster RealPower 550W *SLI*

I have the same problem whit the blacking out of the screen and the nvlddmkm error message in Vista x64 bit.

If looked it up and tryed a lot of settings but it seems to be a problem whit the memory Voltage and the MHz its running on (1066MHz). If you have the same sort of setup try putting the Mhz back to 800 MHz and the voltage to Automatich Voltage or 1.800 v to 2.300 v, depending on your memory and what it may or can handel.

Hope this helps some people a bit.

Greets,
Darky

[AdamK47]

The only time I received the "driver stopped responding" error was when I was doing stress testing. I run the nVidia Cascades demo, nV Monitor, and two instances of Prime 95. I would get the error anywhere between 2 and 8 hours. Now after several driver revisions, BIOS updates, increased memory from 2 to 4 GB, and the MS patches I can run the stress test indefinitely. This is also with the full memory test and medium test (can't remember the exact names) in Prime 95. Link to system specs. (http://www.anandtech.com/mysystemrig.aspx?rigid=34478)

[ikjadoon]

Is it possible that it could possibly be the memory voltage?

~Ibrahim~

[henrybravo]

The new Vista reliability hotfix is supposed to fix this issue. I haven't heard if it really does, for those that still have this problem.

HB

[M.r Bob]

i finally found what was my problem

i have 2GB 2x1GB OCZ Ram and 1GB OCZ 2X512 ram, I Remove the 1GB OCZ 2X512 and no more problem, i even was getting corruptions graph card and after i remove the 1gb of ram all my problems are gone

[Mojoe]

Think people should take a look at theire ram, all the time i see someone have solved this problem its ram releated.

[Muppet]

I've never had this issue until I installed the 163.11 drivers. I tried all sorts of things to fix it. In the end I had to go back to 158.24, It's a bloody shame I was really liking the 163's there for a while.

[Skinner]

HL2 Episode 2 crashes regular here in Vista 64, but it appears to happen on both vendors, ATI and nVidia.

[Mojoe]

Didnt know that Hl2 ep2 was out ??

[JimBobb]

Same Problem here with 2x XFX 8800GTX and Vista 32 Premium...163.11 Forceware

[Amuro]

Happens to me in Vsita Ultimate x64 with Aero mode on while mousing over the Start menu.

[sclaws]

Think people should take a look at theire ram, all the time i see someone have solved this problem its ram releated.

I wish I could agree but there are also many people like myself who only get the error with certain drivers. If it were hardware I'd expect constant issues regardless installed software. I have no problems with 158.45, but any driver above that is unusable for me so far.

[Muppet]

The new Microsoft hotfix doesn't fix this error. I just installed the 163.11 and fix, but the problem is still there. Damn, I really want to use these drivers. I love how they have Digital Vibrance and SLI fan control working. Ahhhhhh

[Slammin]

Try turning off Aero for now.

[Muppet]

Try turning off Aero for now.
It happens in window every few minutes. But try and play a game and all hell brakes loose. It will happen like every 2 seconds and makes it totally unplayable. Even trying to access the menu is almost impossible when in 3d mode. But like I said it is only with the 163.11 drivers. I have never had this issue until now.