Nvlddmkm stopped responding is getting VERY OLD...

[wollyka]

Well, so far after a few hours now, I can confirn that it was the OCZ PC2 8500 SLI memory that was BAD! With my old motherboard back in (the original 680i, not the LT), and the new OCZ memory I just bought installed, it works and NO nvlddmkm errors as of yet!!!!!!!! If I put the original ram back in, even with the new RAM, the machine won't even boot! Time to RMA the RAM now.
just to tell u that i have 4 GB of this ram +680i and it works without a problem at 1066MHZ (i manually set the volt to 2.1v)..
but i do get sometimes the nvlddmkm error especially if i am running dreamscene.
XP and XPx64 work without a hitch..

[Peoples-Agent]

Blargh!

Getting this Vista crap off my hard drive ASAP!

I never even had this many problems with Windows 95 or ME, to be an XP successor this is beyond a joke.

Waste of money.

Really wish I had nabbed a warez copy now, I seriously feel robbed.

Be smiling again once this is gone.... lol ...sheesh, cannot believe the troubles.

Seems the only difference in usage right now is a fancy transparent desktop theme. I can't thathom out any other benefit to me in using Vista whatsoever, that's worrying.

[sclaws]

Now running on no drivers...every Vista driver will cause the display to stop responding in a matter of minutes. I've tried every reinstall/uninstall process I know of and have had no luck. I'm hoping for a 'miracle' driver this week, but if not I guess I'll go back to XP as well.

Damnit nVidia. I don't have enough zoloft to deal with this crap right now.

[sclaws]

SLIGHT UPDATE:
Took a tip I read (earlier in this thread I think?)...disabled the Vista sidebar and re-installed 101.70....so far, several hrs of use and no nvlddmkm errors. I fully expect them to return, but considering my computer was next to useless, this is a significant gain--I just hope it lasts.

[Harry_Krishna]

UPDATE - went and exchanged the bad ram, and now have all 4 GIGs in the computer, on the 101.70 drivers, even slightly OC's the system to 2.99mhz, and no errors yet in a whole day! So (crossing fingers!!!!!!!) at this time, my problem turned out to be faulty memory. Might suggest to you others with this problem, to also check your memory.

[Elevon]

I had this problem in XP ,found out the cause was my factory overclocked Leadtek 7800GT card,when I reset the memory and core to 7800GT default speeds had no problems,however in Vista x64 I have no compatible overclocking program so can't reduce the speeds,so I get the problem in most games(only in gaming btw),I'm getting a new video card in a few weeks time.

So try reducing your video card speed if its an OC one, even factory overclocked cards.

[sclaws]

ANOTHER UPDATE:
Nothing is fixed...display driver failed this morning again, and now fails almost immediately upon reboot.

[Ikshaar]

Just got Vista... so now I can join the club of pissed off people.

AMD X2 5400+, 2Gb RAM and 8800GTS, dual monitor, nothing OC.

Playing WoW Test client.. every 5 minutes.

Tried regular and beta drivers.. same :(

[sclaws]

Found this somewhere (evga Geforce forums IIRC) as a possible workaround for this error...havent tried it yet but curious if anyone here has. Its a registry hack that apparently delays how long until the OS attempts a driver restart...no clue if this will work or not, but I may try it this evening. Here it is:

"Doing the registry hack as mentioned earlier in this post seems to have erradicated the problem completely for me. I'm using 8800GTS 640mb, vista ultimate, c2d e6400, 2gig 800mhz ram.

Added these keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers

TdrDdiDelay (REG_DWORD) 20
TdrDelay (REG_DWORD) 20

It didn't take effect until i rebooted, but it seems to have fixed the problem."

[Elevon]

Just got Vista... so now I can join the club of pissed off people.

AMD X2 5400+, 2Gb RAM and 8800GTS, dual monitor, nothing OC.

Playing WoW Test client.. every 5 minutes.

Tried regular and beta drivers.. same :(


It was happening to me in WoW too.

Update to my last post,I'm trying the Gainward ExpertTool software and reduced my factory overclocked card speeds,it seems to be working and no lockups or driver stopped responding in Vista x64 so far,so looking good.

[Slammin]

I'm sure it's a timing issue. I can duplicate the problem as well as make it vanish by changing my PCI bus speed. I guess certain combinations of hardware are more sensitive to the issue/drivers, so I'd guess that they need to relax/adjust some timing issue in the drivers to correct this for everyone.

That registry fix above looks very promising too!

[Trail_of_Dead]

This is encouraging. :)

Indeed.

[Ikshaar]

Problem seems fixed - for me at least - by latest driver 158.18.

[Shocky]

I get this with ATITools spinning cube thing with the latest drivers. :(

EDIT: Nope, just got it with Supreme Commander... "sigh"

[Elevon]

I get this with ATITools spinning cube thing with the latest drivers. :(

EDIT: Nope, just got it with Supreme Commander... "sigh"

UPDATE PART 2:
After some heavy testing with games etc ....with my reduced factory OC 7800GT card (by 10 mhz ) have had no lockups or driver stop responding problems,so I can say it is fixed :).

[Shocky]

UPDATE PART 2:
After some heavy testing with games etc ....with my reduced factory OC 7800GT card (by 10 mhz ) have had no lockups or driver stop responding problems,so I can say it is fixed :).

Umm, yeah.. I don't get this in XP, only vista. It's driver related not hardware.

[Blacklash]

I dual boot and use Vista x64. I haven't had this yet and thank God.

On a side note, driver 158 does rock. I love it, especially for giving me back HDR + AA in "Oblivion".

[Elevon]

Umm, yeah.. I don't get this in XP, only vista. It's driver related not hardware.


I had it in XP too,that's how I knew it was the video card in my case.

[ikjadoon]

I've got this error in every BETA driver. I only get it in WHQL-certified (100.65) when switching from one monitor to two.

~Ibrahim~

[sclaws]

I'm getting it again in 158.18...3 times now at the desktop, and one BSOD on startup!

[jabloomf1230]

Read here:

http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

[MowTin]

Sort of ironic that something that's supposed to help make video display crashes less of a problem actually causes crashes.

So, can we just turn this TDR crap off in the registry?

[sclaws]

I'm so frustrated by this error...tried a registry hack (posted in this thread a few pages back) and it didnt work either--was greeted by the error this morning. I'm going to try to start a new thread about this for anyone who has found working solutions to stopping this error...IMO this thread is too large to be real useful for troubleshooting.

[jabloomf1230]

I'm so frustrated by this error...tried a registry hack (posted in this thread a few pages back) and it didnt work either--was greeted by the error this morning. I'm going to try to start a new thread about this for anyone who has found working solutions to stopping this error...IMO this thread is too large to be real useful for troubleshooting.

That's why I posted the link just above to MS's website. Like UAC and the Vista Boot Manager, isolating hardware drivers so that they don't BSOD the whole OS is a great idea. Unfortunately, the implementation leaves a lot to be desired. "Nvlddmkm Stopped responding" is no more one error than cancer is one disease. It is a catch-all for anything that causes the video driver to get stuck in some kind of loop and stop responding. In XP, the OS would BSOD with that silly "STOP, DRIVER STUCK IN A LOOP" message.

In Vista, the OS has the video driver isolated in memory from the rest of the OS, so if the video driver gets stuck (for any reason), the OS restarts it, often with little symptoms other than a temporary black screen. By fiddling with the time out delay values in the Windows registry, you can reduce the number of these time-outs. But the basic problem lies with bugs in the driver and/or problems with your hardware (weak PSU, bad RAM chip, etc.). My experience has been that the frequency of these errors has dropped substantially between 100.65-->101.41--> 158.18, at least for Vista x64.

[MowTin]

I thought the 158.18's where going to solve those TDR errors. I'm incredibly frustrated by this.

TDU is still giving me this error. I need to fix my xp partition and go back to good ole xp.