Nvlddmkm stopped responding is getting VERY OLD...

[LORD-eX-Bu]

the ati version of this error is caused by using four memory modules on their board.

[$n][pErMan]

I also have all the updates installed and tried different drivers, still get this crash. With older drivers the system blue screened, so this is at least an improvement :o

It worked earlier with 2GB RAM if I remember correctly. $n][pErMan, have you tried it once with 2GB instead of 4GB?
Hmmm... no. I have had 4 gigs for the longest time with no errors before, but that is an interesting idea. Because in Vista 32-bit it only saw 3gigs of my 4gigs of ram and I had been using Vista 32-bit up untill 2 weeks ago... perhaps because it now see's all 4gigs its creating an issue in FSX? I might humor the idea and see what happens, but to be honest, even if it worked, I would not keep 2gigs out of my system. As everything else works perfectly with no silly error, perhaps there is a way to limit the amount of memory FSX can use? Would disabling the "can address 2gb of address space" property in the EXE file itself limit this or is there another way? Also, its interesting ATi's version of this issue has to do with 4 sticks of RAM... I happen to have 4 sticks of ram installed. I could have sworn though Crysis and Sup Com use more memory than FSX and i have no issues with those games...

[slaWter]

[pErMan']Hmmm... no. I have had 4 gigs for the longest time with no errors before, but that is an interesting idea. Because in Vista 32-bit it only saw 3gigs of my 4gigs of ram and I had been using Vista 32-bit up untill 2 weeks ago... perhaps because it now see's all 4gigs its creating an issue in FSX? I might humor the idea and see what happens, but to be honest, even if it worked, I would not keep 2gigs out of my system. As everything else works perfectly with no silly error, perhaps there is a way to limit the amount of memory FSX can use? Would disabling the "can address 2gb of address space" property in the EXE file itself limit this or is there another way? Also, its interesting ATi's version of this issue has to do with 4 sticks of RAM... I happen to have 4 sticks of ram installed. I could have sworn though Crysis and Sup Com use more memory than FSX and i have no issues with those games...

Please report back in case you'll test that. The .exe modification you mentioned is a very good idea, it worked with other games. FSX only uses about 50-60% RAM but that doesn't mean it can't produce an error like this.

[$n][pErMan]

Please report back in case you'll test that. The .exe modification you mentioned is a very good idea, it worked with other games. FSX only uses about 50-60% RAM but that doesn't mean it can't produce an error like this.
I am going to test that now... I never tried this trick in order to DISABLE addressing ability... not sure what might happen but its worth a shot as I refuse to take out any of my ram. I see Sup Com use about 70% of my RAM when playing so I doubt it has anything to do with memory useage, but who knows? Anything is worth a shot at this point. I might also take back my OC on my video card a bit too in FSX and see what happenes if the EXE trick does not work.

[Q]

Do you have dual monitors? I know that I ran into the EXACT same issue and went back to XP before I stumbled over this MS fix...

http://support.microsoft.com/kb/933590

[slaWter]

Could you please explain how to do the .exe trick? Thanks :)

Thanks, Q. I'm gonna test that as well.

[$n][pErMan]

Do you have dual monitors? I know that I ran into the EXACT same issue and went back to XP before I stumbled over this MS fix...

http://support.microsoft.com/kb/933590
Nope, just one monitor.. but 2 are connected, I only use the widescreen however (nothing set for dual view). Did you get the flicker? Or did you get this BS nvlddmkm stopper responding crap? If so, I might give this a try.

Also, changing the EXE, setting compatability to XP SP2, and underclocking my video card did nothing.... game still gives me the damn driver stopped responding BS after roughly 30 minutes of play (sometimes sooner or a little later). This is realyl starting to piss me off.... think I am going to go play Sup Com or something before I get to pissed. microshaft and n****tia are pissing me off ATM... I just want to fly! :mad:

[Bokishi]

Exiting the Addrianne Demo seems to give a stop responding error and then a blue screen (169.28)

[LORD-eX-Bu]

I first encountered this error playing Supreme Commander so eh... you might not have much luck.

[badboy64]

I haven't had 1 yet since I installed nearly a month ago and I am using the 169.28 drivers too on both systems. In fact I also haven't had one my other system which uses 2x8800GT's for over 2 weeks now since I installed the Vista Ultimate. Both systems= no Nvlddmkm Stopped responding issues period.

[$n][pErMan]

Could you please explain how to do the .exe trick? Thanks :)

Thanks, Q. I'm gonna test that as well.
Dual monitor fix do anything for you? Worth noting is after getting pissed of this gay ass error in FSX I went to play Sup Com.... 2 hours solid and no issues in that game (as I expected). FSX has some problem with 169.25 drivers... unless that hotfix for the monitors works (have yet to try)...

[Q]

[pErMan']Nope, just one monitor.. but 2 are connected, I only use the widescreen however (nothing set for dual view). Did you get the flicker? Or did you get this BS nvlddmkm stopper responding crap? If so, I might give this a try.

I got the flicker.... which ended in the nvlddmkm crash.... which THEN (if I kept messing with it) resulted in BSOD. Jolly good times.

[Slammin]

[pErMan']Dual monitor fix do anything for you? Worth noting is after getting pissed of this gay ass error in FSX I went to play Sup Com.... 2 hours solid and no issues in that game (as I expected). FSX has some problem with 169.25 drivers... unless that hotfix for the monitors works (have yet to try)...


If it matters, I get the same thing with FSX and 169.25. I rarely have enough time to actually play for 30 minutes straight but yup, right around 1/2 hr, I get a black screen. I do not get the stopped responding message/popup though but I can tell that is what it is.

I'll try to find a work-around if I see it with the next driver since the only game I spend hours at a time with is online IL-2 and I never have problems with it.

I also fly some pretty long sorties with RedViper (Falcon4) and never encounter this problem. It's only with FSX that I can tell.

[slaWter]

[pErMan']Dual monitor fix do anything for you? Worth noting is after getting pissed of this gay ass error in FSX I went to play Sup Com.... 2 hours solid and no issues in that game (as I expected). FSX has some problem with 169.25 drivers... unless that hotfix for the monitors works (have yet to try)...

Sorry, no time to test it right now. But I'll report back as soon as possible.
Too bad the .exe modification didn't work :(

[$n][pErMan]

I got this error in WiC on Vista 64-bit for the first time.... I then got it 3 more times in a row playing this game. I am really starting to get pissed off at nVidia for such a crap shoot of drivers... might even boot into my old Vista 32-bit as I never had ANY of these damn errors.

[Soccerfly]

:( After having the same problem as numerous people have had with the blessed nvlddmkm error message and with much reading into the situation I stumbled across a possible fix (possible being it may or may not work), I tried the obvious beta driver's from NVIDIA and tried to go that route also tried the Remove the nvlddmkm.sys file route, I didn't uninstall Vista and reinstall XP as many people have done and no I didn't switch to ATI, Being that I am stubborn and have to research and tinker I found a post from another website http://www.laptopvideo2go.com/forum/index.php?showtopic=9243
After unistalling the NVIDIA driver 169.28 and installed this one I have had no probs apart from I cannot open the nvidia adjustment and had to setup through windows


Try it,

I'm not one for knowing my pc specs as to the in and outs :bash: :lame: but this is what I recall that I have
Gateway 5200 with dual core processor
NVIDIA 7600GT
512 mb memory
VISTA 32

FSX with accelleration is the game of choice with great frame rates and plenty of flight time.

Hope this helps

Soccerfly(nana2) (lee63)

[leemik]

I finally got the root of my problem recently.. No matter what I did I got nvlddmkm errors.. some drivers were worse than others..

Then, one day my machine wouldn't post.. found out the error code was a failing stick of RAM.. Totally replaced the RAM with 2 new sticks and the nvlddmkm problem actually went away.. I haven't seen it in a month since i replaced the memory.. same driver, same everything else..

--mike

[haloeighty8]

After 4 months of running Vista 64 problem free.. out of the blue I started getting this dreaded error last week. I've done everything I could to try to get to the bottom of this, short of swapping out the motherboard.

Now, I've seen some who claim this is a failing 680i northbridge that causes this problem. Along, with the error I'm having issues getting the system to boot up.. as in when I power it up it just sits at the bios screen. Until I switch the power supply off for like 30 seconds then back on.. it's boots. But with no video whatsoever. I do see a mouse pointer but that's it.

I'm actually about ready to sell off one of my ultra's and my ram and grab a x38 and a couple gigs of ddr3. Which is most likely what I'm going to do..

[LORD-eX-Bu]

uh, I RMA'd my 680i and it didn't solve the problem at the time.

[haloeighty8]

uh, I RMA'd my 680i and it didn't solve the problem at the time.

Well if that's the case I don't know what else to try? maybe I'll pickup a 780i board and see how that goes. dunno..

[LORD-eX-Bu]

have you tried running your memory at default speed and timings? err... have you tried it with different memory or a different video card?

[haloeighty8]

I tried each card by itself, but I haven't tried different memory. I do have a couple sticks here I may pop them in and see how that goes.

[haloeighty8]

I tried each card by itself, but I haven't tried different memory. I do have a couple sticks here I may pop them in and see how that goes.

btw, the memory that's in at the moment are some of those crucial ballistix which I hear have a tendency to fry on the 680? I ran memtest for like 6 passes and it showed no errors.

btw, sorry about the double post! it's late....

[$n][pErMan]

Anyone got a link to memtest??? I want to try this myself... but I see like 4 different sites for it and I want the right one :)

[[HeX]]

btw, the memory that's in at the moment are some of those crucial ballistix which I hear have a tendency to fry on the 680? I ran memtest for like 6 passes and it showed no errors.

btw, sorry about the double post! it's late....
6 passes of Memtest is a joke. Run 25 passes and provide us with results. Last time I got errors in 17th pass for example :(