Nvlddmkm stopped responding is getting VERY OLD...

[kovacevd]

Hmmm, I may have a fix for this afterall. A stupid fix, but a fix none the less. Last night I formatted Vista again, I updated everything in proper order, and rebooting in between. Soon after the last reboot, I got none other than a DSR error, and a BSOD no less. So my friend said, reformat, but DO NOT update Windows. Which I did, and guess what? NO DSR error yet! Stupid, but it might work. I have to find out which update breaks the nvidia drivers >_<

Exactly what i was thinking, But i dont think its Vista updating that breaks it. I Think alot of games out there Break it also, Just like what i noticed, LOTRO Broke it instantly and same with Settlers 6.
Anyway this shouldnt be happenbing, i think its a DX9 Conflict with these DX10 Cards, Something isnt right aboiut them, whenever something Changes in DX Files, like updates, they seems to **** up our cards


Why on earth didnt any of us hear about this error in all the BENCHmarketing BS.
I know this is the only reason i bought these cards cuase of the Benchmarks, But why did not of these sites ever have this error onj there cards ?, Maybe they did, But why wouldnt they tell people about it? **** this feel like smashing everyone

[ZoLoco]

Sigh.. Yepp, here again. And, YES!! Still got that shyte error.

Downloaded the new beta driver from nvidia. 163.67 Haha :(
Started dreamscape, wow!! No errors, thought everything was dandy. But no friggin way!! Bought the new Medal of honor Airborne. How long did ya all think i could play??



5 Mins. 5 ! M I N U T E S!!!

Ok, noticed they had done something about it. You know what they did? They removed the windows pop up window of the error. ROFL.. Bah!!
Still same lockups, freeze and blackscreen waiting. Still same yellow triangle icon warning at bottom screen. Still same ERROR!!!!!!!!!!! Still need to reset (oh yes, resets do good on my OS). Still needs to cltr-alt-del hoping to gain control.. STILL!!!!

Very old, very very very.. Nvidia cant fix it.. :thumbdwn:

[Knacki99]

First time ever i have this problem. Started after installing and a crash in World in Conflict.

Never had this with any driver before. Using 163.69 now.

[Sidric]

First time ever i have this problem. Started after installing and a crash in World in Conflict.

Never had this with any driver before. Using 163.69 now.

I just had the pleasure of seeing my first nvlddkm blue screen ever while in WiC as well. And of course, it happened right in the middle of an intense battle :thumbdwn:

[Smee]

Any updates on this problem?

I removed 2 of my 4 gigs of ram (Vista 64bit) and that seems to have reduced the number of "Nvlddmkm Stopped responding" by about 70% or so.. i definitely think it is memory related.. Tried dozens of different setting with my ram etc.. no luck there.

[Slammin]

Any updates on this problem?

I removed 2 of my 4 gigs of ram (Vista 64bit) and that seems to have reduced the number of "Nvlddmkm Stopped responding" by about 70% or so.. i definitely think it is memory related.. Tried dozens of different setting with my ram etc.. no luck there.


I'd say more like chipset/timing related and I do believe your results too because when I did have the problem, changing ram timings or fsb speed changed the frequency at which the stoppoed responding happened for me.

If it matters, the lower I set my fsb, the less frequent they seemed to happen.

Fortunately, I have not seen this issue in quite some time now.

[GT-Force]

Today, I tried the same thing:

I was using my system at MaxOC BIOS setting for SLI RAM. Today, I "Slowed down" my memory from 1066 to 854 (5:4 FSB:MEM), keeping the voltage at 2.2 V (using eVGA 122-CK-NF68 680i and 4x1GB Corsair Dominator CM2X1024-8500C5D1066 RAM).

Turns out, when I chose a lower frequency, the RAM could run at a lower timing, and guess what: My measured RAM speed is now HIGHER, despite lower running frequency!

What is better? I am yet to see the nvlddmkm error. It used to pop up almost 100% in Trees of Pangaea (when ran Full Screen), and now it doesn't. I also ran 3DMark 2006 and ETQW without a hitch. I even was getting this error while I was doing "normal" (i.e., non-3D) stuff, just browsing etc (Running Vista 32 with 163.69 or 163.71), though not frequently, and it did not happen yet (then again, I have used the computer in this config only for 12 hours or so).

Faster RAM speed, and more stable system by running my memory "slower"? That sounds o.k. to me :)

[sclaws]

I "downgraded" from 4 1GB 1066 sticks to two 2GB 800 sticks about 2wks ago...havent seen the error since, and that includes running dreamscene (which would ALWAYS crap-out within a few hrs). I was also rebooting nightly and no longer need to do so. YMMV.

[DirkGently]

I've been using Vista with an 8800GTX since the day it was released and have just had this problem start occuring. I've made no configuration changes in the last week and installed no new software, and as i recall, no patches have been installed through any automatic updates in at least three days.

My pc use has been the same every day in the last week and yet out of the blue this problem has just cropped up. I'm perplexed to say the least. What is more shocking is the length of time that this problem has existed without any adequate response from Nvidia.

Are we all agreed that the cause of this issue is definately tied to Nvidia driver software? From what i read it seems to be the case so why the hell aren't the well respected hardware sites and pc magazines jumping all over this? I read a dozen of them daily and have never read anything about this issue in any of their articles. Surely they must be aware of the problems existence?

It is shameful that a manufacturer with the market share of Nvidia hasn't addressed a problem of this magnitude or done anything to appease the consumer base that keeps it in business. It is equally shameful that more hasn't been done to advertise these shortcomings in the popular media that would otherwise be a useful tool in putting pressure on Nvidia to address the issue.

I for one think that Nvidia should be forced to respond to their customers complaints with a statement acknowledging that this problem exists with their products and detailing what steps are being taken to resolve it.

The only way anything is going to be done about it is if pressure is brought to bear on Nvidia by shining a spotlight on them and forcing them to act. If they believe their revenue stream will be hit when people flock to the opposition you can bet your life that action will be taken then.

To this end i call for any bloggers and website owners to highlight this issue, and any other Nvidia product problems, by posting about them as often and as widely as possible. Add something to your forum signatures, get up petitions and start shaming Nvidia into taking action. If we can get the bigger websites to look into this, write articles and ask Nvidia representatives for official statements then we may be a step closer to getting our complaints dealt with.

SEVEN WHOLE MONTHS WHERE NVIDIA HAVE DISREGARDED THE PEOPLE WHO MAKE IT POSSIBLE FOR THEM TO EXIST. I BUY A LOT OF PC HARDWARE BUT I'LL NEVER BUY NVIDIA AGAIN.

[Python2]

i am getting the driver NVLDDMKM.dll error, and it either bluescreens or it is "fixed" untill i start another game and it does bluescreen.

specs:
6Gb OCZ 800mhz ram
evga 680i motherboard
evga geforce 8800 gtx superclocked
core 2 duo e6600
163.69 drivers

it most often happens in Company of Heroes: Opposing Fronts, but also in EVE Online. i am installed the 163.69 drivers 2 days ago, and have been having errors constantly ever since. before around march i was having these problems, then i upgraded drivers to 163.44(i think) and it was fine for 7 months, then i decide new drivers sound like a good idea... NVLDDMKM.dll ERROR!!!!! i thought new drivers were designed to have less problems =/

anyone know if i should just go back a few drivers, or is there a fix? cuz my performance increaced, but at the cost of freezing 3/4 through every game of CoH and durring ops in EVE

[Smee]

Ok, I put my other 2 1gb sticks in (4 total again) and underclocked it a bit... No errors yet.. I have played two 2+ hour COH opposing front skirmish's with no problems.. I'll check again after a few more games.

[vmsein]

I've been using Vista with an 8800GTX since the day it was released and have just had this problem start occuring. I've made no configuration changes in the last week and installed no new software, and as i recall, no patches have been installed through any automatic updates in at least three days.

My pc use has been the same every day in the last week and yet out of the blue this problem has just cropped up. I'm perplexed to say the least. What is more shocking is the length of time that this problem has existed without any adequate response from Nvidia.

Are we all agreed that the cause of this issue is definately tied to Nvidia driver software? From what i read it seems to be the case so why the hell aren't the well respected hardware sites and pc magazines jumping all over this? I read a dozen of them daily and have never read anything about this issue in any of their articles. Surely they must be aware of the problems existence?

It is shameful that a manufacturer with the market share of Nvidia hasn't addressed a problem of this magnitude or done anything to appease the consumer base that keeps it in business. It is equally shameful that more hasn't been done to advertise these shortcomings in the popular media that would otherwise be a useful tool in putting pressure on Nvidia to address the issue.

I for one think that Nvidia should be forced to respond to their customers complaints with a statement acknowledging that this problem exists with their products and detailing what steps are being taken to resolve it.

The only way anything is going to be done about it is if pressure is brought to bear on Nvidia by shining a spotlight on them and forcing them to act. If they believe their revenue stream will be hit when people flock to the opposition you can bet your life that action will be taken then.

To this end i call for any bloggers and website owners to highlight this issue, and any other Nvidia product problems, by posting about them as often and as widely as possible. Add something to your forum signatures, get up petitions and start shaming Nvidia into taking action. If we can get the bigger websites to look into this, write articles and ask Nvidia representatives for official statements then we may be a step closer to getting our complaints dealt with.

SEVEN WHOLE MONTHS WHERE NVIDIA HAVE DISREGARDED THE PEOPLE WHO MAKE IT POSSIBLE FOR THEM TO EXIST. I BUY A LOT OF PC HARDWARE BUT I'LL NEVER BUY NVIDIA AGAIN.
I couldn't agree with you more on this issue. I realize that this is an nvidia fan site, but it does seem to me that this issue that affects so many people has been widely neglected by hardware websites with the most traffic. More pressure needs to brought to bear upon nvidia and perhaps Microsoft as well if Vista plays a part in creating this problem. I, for one, have stopped using my EVGA 680i motherboard and replaced it with an ASUS P35 motherboard, and I have sold off my two 8800GTXs which I had running in SLi mode. These I replaced with a single 8800GTX Ultra. All this the result of endless "driver stopped responding" errors with no legitimate fix in sight. I'm sorry to say that it's going to take alot of convincing before I ever go back to an SLi configuration. Nvidia, why can't you fix this?

[JoeJonnyBoy75]

Hello All,

I may have found a solution to this nagging problem, although my symptoms are a little different then some of you guys.
I have a EVGA 680i A1 (P30) Board with a 8800GTS and Vista x64. A friend of mine has an Asus p35 board and a 8800GTX. We've both had sucess with this solution.
I had tried every other methed mentioned on all the forums to no avail.

Anyways I was only ever getting the "driver stopped resonding..." after leaving my computer on for long periods of time (over night). Meaning I could game for hours on day 1 and on day 2 first game loaded, up comes the error. There was the rare time that I had the error on day one but oddly not during gaming.

So Yesterday I disabled DEP and Hardware Signing via the boot manager (bcdedit). Today I haven't had to reboot and I'm still stable. Just finished up a quick couple of TF2 matches.
Now normally I would have seen an error by now, and the game would have stuttered, but as of now the game is running perfectly and no error.

I pray this has finnaly fixed the issue as I hate having to reboot my computer all the time.
I used the following commands to disable DEP and Hardware Signing:

Disable DEP: "bcdedit.exe /set {current} nx AlwaysOff"

Disable Driver Signing: "Bcdedit.exe /set nointegritychecks ON"
or (I don't know what the difference is so I did both)
Disable Driver Signing: "bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS"

Can someone else give this a try and see if they have similar results?

Good luck...

[Lfctony]

I'm sick and tired of this as well. This is all BS. The only driver that doesn't pull this crap is 100.59. Good luck trying to play WiC with that one. I'm trying one last time then I'm going back to Windows XP. I'm very disappointed with Nvidia right now.

[Lfctony]

Crashed AGAIN. Off to XP. Thank you for a wonderful Vista experience Nvidia.

[iwbs]

Does this error occur on 8800s only?....cuz i am running on a 8600gt with vista and haven't got this error for 2 months straight.....

I did have a number of Nvlddmkm stop responding during the first week with this new com, however after that the error just disappear, no matter which driver i'm using:)

[Smee]

Ok, I put my other 2 1gb sticks in (4 total again) and underclocked it a bit... No errors yet.. I have played two 2+ hour COH opposing front skirmish's with no problems.. I'll check again after a few more games.


Well, it wasn't to be.. started crashing like mad after a few complete games.. I write this post from my XP hard drive.. /sigh

[Smee]

Well, it wasn't to be.. started crashing like mad after a few complete games.. I write this post from my XP hard drive.. /sigh

LMAO, Now I'm getting lockups on my new XP install, running the latest Nvidia XP drivers.

Is anyone (Vista or XP) running happily on Company of heroes with Nvidia??

[LORD-eX-Bu]

I gave up on Vista long ago, been running XP for 8 months and couldn't be happier :)

[Nkd]

LMAO, Now I'm getting lockups on my new XP install, running the latest Nvidia XP drivers.

Is anyone (Vista or XP) running happily on Company of heroes with Nvidia??

I know some people dont wanna believe this, Here is a working proof, your card is bad, yes it is.

I have two ultras, One by BFG and one By EVGA superclocked which has gone through 2 rma's and hey refuse to send me a working one, lol.

BFG ultra in the same system has absolutly no issues either in vista or xp.

when i use my evga ultra it locks up in xp with in few minutes and in vista i keep getting the same error as yours(display driver has stopped responding and recovered), all those people having issues in vista should try xp, your games will lock up for sure.

The reason vista doesn't lock up the whole system is because the new WDDM driver model which is out of the kernel, and if your graphics card stops responding to the driver than you start getting that error, and your able to revert back to desktop thanks to the new WDDM driver model after you press ctrl+alt+del, thats only if your plany a game.

With my bfg tech 8800 ultra for a week, no lock ups in xp and no driver errors in vista. using the same system and the same drivers.

So I think we all here who have had this error in vista should intall xp if they can and see if your card freezes than its certainly a defective GPU. I happened to have two ultras and one gave me the same issues and the other didn't.

[LORD-eX-Bu]

mines works fine in XP.

[Nkd]

mines works fine in XP.

well he is getting lock ups in xp, the error in vista, which i got only with the evga ultra, and the bfg tech ultra has no problems what so ever, LORD-eX-Bu if you get nothing wrong in xp, you should try vista again, and I bet you wont get any errors, some cards are fixed by the latest drivers, I have tried lots of different driver sets with the evga card and I get the same results, and I through in the bfg tech ultra, everything is good. Do Not bang ur head and waste your time if you have this issue, IF your card is under warranty just get a new one.

[Nkd]

Nvidia has not come out and acknowledged the problem because I believe its due to some gpu's not being able to respond to the drivers, thats why in vista you get the error and in xp, you get the lock ups. I will be asking my boss to shed some light on this issue, and may be do an article on this issue on our website. I have seen numerous websites with users experiencing this same issue and now I have experienced it with my own computer, where one card has no driver issue or lock ups in and while the other does, all in the same system.

[Nkd]

I have seen a lot of people saying around the net, "turn up the htt voltage, down clock your ram, loosen up the memory timings, lower your vcore" those are just to name the few. I got these loc ups in xp than I jumped to vista and I got this error, all the vista patches installed as instructed at nvidia's website. You should not have to do things stated above to get rid of that error, because that is just pathetic, those things have absolutly nothing to do with your graphic card failing to respond to the drivers. I got the errors on stock setting and nothing was overclocked. While one card works and one card doesn't, for me I dont have to be a rocket scientist to realize its my card. and not my system.

[Buckeye]

I played around with the BIOS settings on my Striker MB last night. It's been set to Auto on the Extreme Tweaker Menu from day 1 of the build. Soon as I jumped the OC up to 5% or so with the A.I. NOS Bam ! not responding errors. The computer would boot just fine and get to the desktop and start to work, then the error.

I played around with this for awhile and ended putting it back to Auto and no errors so far.

Disclamer: I have no idea on how to OC LOL I was just playing around with the BIOS settings and it seems that as soon as I bump OC settings up, RAM or CPU I get this error.