PDA

View Full Version : Nvlddmkm stopped responding is getting VERY OLD...


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 [35] 36

hokeyplyr48
02-01-09, 02:13 PM
I've never had this up until a month ago when my screen started going black and it would say nvlddmkm stopped responding. I noticed my drivers were out of date, so I updated them hoping that would fix the problem but it kept happening. So I reformatted my computer and reinstalled vista hoping that would resolve any conflicts that were occurring and it did it for the first couple days. Then it magically went away for about a month, then yesterday it randomly came back. Why is it so intermittent? Does it mean there's a hardware problem? like my graphics card is dying?

Jurassic Pork
02-06-09, 08:01 AM
Hi. I'm trying to collect all of the data about this stupid nvlddmkm error and put it all into one place so people won't be spending that much time scouring all over Google for the solutions. This website is at http://www.nvlddmkm.com please let me know if there should be anything that I should add to the website. Thanks!
-Nick

BTW I still have yet to fix this error for my computer as well.

fantastic idea, well done.

sticker
02-12-09, 12:14 PM
I had this problem too...

Changed my RAM, and updated my BIOS - problem seems to be gone!

Just wanted to post my situation for others

Tr1cK
02-12-09, 12:27 PM
I still get this.

I have tried all kinds of different clocks on my system and video card, all the way to stock. I've tried numerous drivers, BIOS, and firmwares. I think my next step is new motherboard.

Evil_Homer
02-19-09, 02:24 PM
I have never had this error with my GTX 280 until last night after installing the new 182.06. Playing crysis wars last night I would get stuttering all of a sudden followed by a black screen for about 30 seconds then crash to desktop with this error. Grrrr......

Delbert
02-19-09, 03:41 PM
Never had this in XP.
get this in Win 7 ( beta ) as soon as i overclock the Gfx card.

wysiwyg
03-05-09, 07:50 AM
im getting the error after about an hours play in GTA IV with Vista 32

using a GTX 295 dedicated to video and 8800 GT dedicated for physx

tomb18
03-05-09, 09:30 AM
I never had this error until I installed the 182 series of drivers. Now it occurs frequently and many times in a row. You would think that this would have been fixed by now. Does ATI suffer from this problem???

slaWter
03-05-09, 01:05 PM
I never had this error until I installed the 182 series of drivers. Now it occurs frequently and many times in a row. You would think that this would have been fixed by now. Does ATI suffer from this problem???

ATI has a similar problem, different file name though :p

Tr1cK
03-05-09, 01:47 PM
This stems from system instability. My motherboard has been slowly losing its overclocking ability and this has become more of an issue. Change my clocks down and stability is here.

Seems in my case that my motherboard didn't want to run my 1000mhz RAM at anything above 800. The longer I've ran the board the more frequent the video driver would restart. Evidently my board didn't like running the RAM at 1000 from the start but more slightly more tolerant.

|MaguS|
03-11-09, 10:07 PM
Im getting this error with OpenGL apps on my HTPC. I can run Direct3D Progams all day long without issue but if I play Doom 3 or XMBC with the OpenGL Plugin I get a crash. I have tried multiple drivers but its the same with them all.

I thought its what Tr1ck stated but being that it only crashes under OpenGL, I don't think its the same issue.

Cyant
03-18-09, 06:50 PM
Fixed my "Nvlddmkm stopped responding" problem by RMA'ing my GTX295+. Now I have a GTX295 w/Backplate (factory installed) and have no problem whatsoever.

Oced to 675 / 1566 / 1269 @ 1.088v

Isola
03-22-09, 09:52 AM
nvlddkm back with 185 beta drivers....

silencer51
03-24-09, 01:10 PM
Well a few minutes ago I had my first BSOD in at least 2 years and my first for Vista 64bit...

Guess what... Nvlddmkm STOP error. Before that I was sorting images through Windows Explorer and Windows Image Preview when all of a sudden, Winamp gets stuck, my monitor turns off and back on and I have a nice BSOD in front of me. :(

I've never had this problem with any Nvidia cards before, actually I never get crashes on my systems (I'm a stability minded nerd).

What could the problem be?

AdamK47
03-24-09, 06:06 PM
I havent seen this error in a long long time. I built my Core i7 / GTX 280 SLI system back in November and can honestly say I haven't seen this error at all... unless it was caused by me forcing SLI on something that doesn't like it.

Nu3gaWhat
03-29-09, 03:29 AM
, my monitor turns off and back on and I have a nice BSOD in front of me. :(



That just happened to me, while playing ArmA. Was playing for like 4 hours before it happened. :(

GTX260 216 178.24WHQL (custom res broken in the newer drivers I tried :( )

six_storm
04-28-09, 12:14 AM
I installed Windows 7 RC on my gaming rig tonight and of course, the freakin NVIDIA drivers crash with Left 4 Dead. :( NVIDIA (or whoever is to blame ;) ) needs to get this crap worked out before Windows 7 gets released.

Grechie
04-28-09, 03:57 AM
only occurs to me if i play DX10 games with AA, i get sound crackling, and then boot to desktop, ultimatly lame. everything stock.

six_storm
04-28-09, 06:01 PM
Does this issue come from the stability of the drivers? What's going on with this?

Hopefully now that I've downclocked my video card, I won't get more crashes but who knows . . .

Greg
05-11-09, 12:00 PM
I'd just like to pop back and say that I fixed my problem by warrantying my video card. The replacement works flawlessly.

It is obvious from reading all the posts in this thread, countless other forum threads and my own experience that this issue is merely a symptom for a variety of different issues including overheating, hardware and software problems. There is no conspiracy by nVidia to hide the issue. If you experience it (particularly with a brand new card), and after troubleshooting don't find a solution, try to RMA it, you might be one of the few percent with a dud.

Sazar
05-11-09, 03:37 PM
I installed Windows 7 RC on my gaming rig tonight and of course, the freakin NVIDIA drivers crash with Left 4 Dead. :( NVIDIA (or whoever is to blame ;) ) needs to get this crap worked out before Windows 7 gets released.

I got a bsod while watching a movie last night on my HTPC.

:(

Arrowhead
05-13-09, 04:29 PM
RMA your cards. I was struggling with this problem for over a year on my XFX 8800 GTS 640. I got an RMA, they ran an initial test and tried to tell me that the card was fully functional and that they would just send it back. I got on the phone with them and convinced them to run more tests. Sure enough, they ran it all weekend and found the card to be faulty! I got a new 9600GT back, and it seems to be working flawlessly.

I think a lot of cards out there have tiny faults which cause this error to occur. Insist on an RMA and don't let them send it back to you without testing it extensively to find the fault.

Misfire
05-16-09, 05:24 PM
Yeah i suppose this is a good indicator that your video card is dying. Last week I started getting this error consistently when opening up a game. checked my temps and they werre fine, then opened up ATITool and artifacts everywhere!

Time to RMA

ptal78
06-08-09, 05:41 AM
It works for me.

I have stuffed around with this for too long. After a complete reinstall of vista 64bit I installed one application every two days. Dot Net was found to cause the pausing/freezing/crashing that caused me so much grief and blamed NVlddmkm. Maybe it is just a bug or something but if Dot Net 3.5SP1 causes such problems then Microsoft has something to answer for.

Phil

silencer51
06-22-09, 08:19 PM
Okay, now this thing is starting to get on my nerves.

I have only recently encountered this problem with my GTX 295.

I've tried multiple drivers of the 185, 186 and 190 family.

I even tried doing a fresh Vista x64 install.

Guess what?

I can't play any game whatsoever. Most crash to the desktop within minutes and I get the dreaded "Display driver nvlddmkm stopped responding and has successfully recovered." error message (oddly enough, I would get a BSOD before).

Any ideas? Should I RMA the card? :(:thumbdwn::thumbdwn::thumbdwn::thumbdwn: