Nvlddmkm stopped responding is getting VERY OLD...

[$n][pErMan]

For the first time ever... I got this error on my GTX 285. It happened in Cryostasis... I took a shot in the dark and figured it must have been the PhysX causing it. So I kept the same exact video drivers... but installed the latest PhysX drivers... and boom... error never showed up again :) *knocks on wood*

[Grechie]

i was getting this error with SLI 9800GTX's and even TRI SLI 9800GTXs, fixed it by increasing the voltage going to the northbridge(sli) and south bridge(for tri) on my 790i

Running 2 GTX295s now for some reason havent needed to touch voltage AT all....

[silencer51]

Well I think I've found the culprit. Its BOINC - I always run seti@home however it seems the latest BOINC versions still run a background service even after you 've quit the BOINC manager...

I uninstalled BOINC and played Crysis Warhead & Prototype for an hour without problems...

[mstrling]

I've started getting this error as well. I've skimmed over several pages in this thread, but one thing I've noticed is most of the equipment referenced is newer than what I have.

Here's the thing: My system is three years old. I put it together myself, and when it was new, I had XP Media Center 2005 installed on it. The card is a 7600GT, the processor is a Pentium D930. Nothing is overclocked. 1GB of RAM (2x512). It was decent three years ago, and it still serves what I need.

Last year I had to upgrade to Vista 32 bit. I didn't have any issues until maybe two months ago. I started to get this message. Now I don't get a blue screen because Vista always successfully recovers.

So far the problem only shows up when I play Runescape, which is not exactly hardware intensive.

I keep the nVidia drivers up to date, and I have Vista SP2 installed.

It's interesting that it's not just the latest hardware that this is happening on. My system certainly does not get very warm at all, so what could it be? A Vista problem? An nVidia problem? It just seems so random.

[DarkOneX]

Grrrr, I haven't got this in a long time and recently I started playing Urban Terror again, haven't played it for like 8 years, it's a like a 10 year old game lol and it happens often while playing this! I haven't had it happen with anything else yet but I can't make it NOT happen while playing this. Sometimes it will happen multiple times in a row just after starting to play, but other times I actually played for like 1 to 3 hours straight and never happened, it's so random. I was using the latest 19X drivers but went back trying drivers all the way back to 180.XX and happened with every one of them so I'm assuming it's something with this game that's triggering it. I am also not overclocked on CPU or video either anymore so can't be due to that.

[DarkOneX]

Fixed it by taking out 2 2GB sticks of RAM, leaving me with 2 2GB sticks, so I'm guessing it had something to do with all 4 mem slots full on my mobo. Also doing that fixed an issue in NFS Shift where when I went in the dirt/grass or hit other cars, it got mega choppy. As soon as I took that 4GB out and fired it up again, now it runs smooth as silk and I've been playing since the weekend all games with no issues. Sux though I've down to half the RAM I had, though I don't really need 8GB heh but it was nice.

[AdamK47]

Most of the time when I've had this problem it was related to me overclocking my memory too far, or lowering the timings too much. I haven't had this problem in ages. It's been well over a year. People like to blame nVidia for the problem, but they really should look at their system first. Other programs may run without a problem, but the nVidia drivers seem to be very finicky when it comes to memory stability. Exposing problems no other software encounters.

[Mr Bigman]

This is getting old.

I don't overclcok right now and i still get this bsod at times.

it would do it for a few days than not for weeks and come back so why is this happening and i am using the 190 drivers.

Could it be evga precision? or just cuz im running sli on an intel chipset?

Whatever it is its annoying bigtime and all my stuff is fully uptodate.

[trivium nate]

i haven't gotten this error in forever i have dual cards in sli with latest drivers idk but i haven't gotten it in a while

[wysiwyg]

had Nvlddmkm stopped responding while playing operation flashpoint dragon rising on windows 7 :(


Edit: saw this further down in the event viewer= "The NVIDIA Display Driver Service service has reported an invalid current state 32"

any ideas why ?

[LovingSticky]

I have not seen this error for ages, but started getting it in 2D / Win 7 Aero (!) with latest 191.07 WHQL drivers and 195.39 Beta. Had to revert back to 190.62 WHQL.

[wysiwyg]

i have not seen the error code on any other game or time since my post so put it down to a game fault

[LovingSticky]

Well, this error is definitely configuration-specific, and is probably very hard to debug for NVIDIA, if they do not see it. I have not seen it for about 2 years, till now.

[LovingSticky]

I think I found source of this problem (at least in my particular case). Had previous version of UK drivers installed manually and working great, but let Windows Update install automatically latest WHQL (US) release. This messed-up whole system and probably caused those BSODs.

After booting into Safe Mode, uninstalling drivers, rebooting, running Driver Sweeper, rebooting again, and installing WHQL (UK) release manually, everything seems to be working fine.