Nvlddmkm stopped responding is getting VERY OLD...

[slaWter]

****! Nvlddmkm error message after 75min in FSX with the G92 card :(
I don't know what to test anymore, it seems like a silly driver bug! At least it's possible to play a bit longer with the G92 card compared to the GTX...
Back to DX9!

[XxDeadlyxX]

Hmm been playing CoJ DX10 this morning for about 2 hours in a row... no problems at all...

Seems to be more common for some than others.

[$n][pErMan]

****! Nvlddmkm error message after 75min in FSX with the G92 card :(
I don't know what to test anymore, it seems like a silly driver bug! At least it's possible to play a bit longer with the G92 card compared to the GTX...
Back to DX9!
Damn ... that really sucks man. Must be nVidias crappy set of drivers then... how else can you explain this error?!?! :(

[quad_fx]

hey guys,

first let me list my system specs so you know what you're reading about.

asus l1n64-sli ws (680a SLI chipset) motherboard (brand new, fresh from asus rma dept.)
amd athlon fx-74 CPU's (2 of them)
4gb (1gb x 4) ocz ddr2 800 RAM
nvidia bfg geforce 8800 gtx (16x PCIe)
thermaltake toughpower 850w PSU
first array: (3) WD 500 GB drives - RAID 5
second array: (3) WD 320 GB drives - RAID 5
no overclocking on any of this hardware (aside from bfg's out-of-the-box OC)

i've read through this incredibly extensive thread, hopefully to find a solution at the end, but it appears that's not the case. i'm having the same problem all of you are experiencing, but only with FSX (Acceleration). as you read, my board is BRAND NEW, due to my raid controller malfunctioning a few weeks ago (causing the loss of 400 GB of data). with that in mind, i had been experiencing this error, prior to my board failing, only after i had upgraded my nvidia drivers to the latest version (169.25). i was in the process of troubleshooting it when my board failed, so when i got it back monday (5 days ago), i was hoping to put this beast back together and hope the problem had left with my bad board. i installed vista ultimate x64 sp1, and again the latest non-beta drivers from nvidia (STILL 169.25). as soon as i got everything re-installed i fired up FSX and made it about 50 miles from the runway before i got that cursed error. strange thing is, i fired it back up and flew for about 45 minutes with no problems. i left for an hour or so, came back, and barely made it off the runway before i got the error again. point i'm tyring to make is, this error is not consistent on my end, nor does it occur in any other games (Crysis, Bioshock). i'm skeptical to try any of the voltage changes that i've read about, as it doesn't seem to produce much luck. if you have any (other) suggestions, or things you think i could try on my system to help the community solve this issue, let me know.

[slaWter]

I agree, the error is not consistent, it's totally random but with the G92 card and a newer VGA BIOS I could fly 1h+ three times in a row. With the G80 and an older VGA BIOS FSX usually crashed earlier.
I didn't have this error with older drivers, it started around 2 months ago. It seems to be a driver issue :( A new driver combined with a new VGA BIOS seems to be more stable but still not flawless.

quad_fx, did you try FSX in DX9 mode? It's stable for me.

Overall I'm happy with 1h+ FSX gameplay because that's what I need, I don't fly long distances.

[Greg]

Just for interest, if you think you're getting this error because your video card is overheating, try saving your bios with nvFlash and viewing it with NiBiTor. Here's what good and bad bioses look like:
http://img263.imageshack.us/img263/5964/romcompareno9.th.jpg (http://img263.imageshack.us/my.php?image=romcompareno9.jpg)

[quad_fx]

i'll try some extensive flights in dx9 and see what i come up with. i'll report back the results later tonight or tomorrow.

[tisdale36]

When I built my system (680I, 8800GTX, 2g @ 800...) I had XP. I used it for a month or so, bought Vista, used it for a while with no problems. I played BF2142 at max everything. No problemos. It seems like after a Windows Update I started getting this "nvlddmkm" error. I wish I could say for certain if I was using DX10 or 9.0c. My computer locks up a bunch. The only way to get my system stable is to underclock my card. When my system boots it has squiggly lines (worms) all in the display, does ya'lls do that? Has anyone heard of or thought of a class action law suit? I paid $700 dollars for a card that is useless.

[Roliath]

Small update, I just sold my GTX.
I got fed up trying to figure this issue out.

I just bought an ATI 3870x2, and i'll just wait until the new Nvidia cards comes out.

[sucko_the_clown]

Sold my 8800 ultra because of this problem. It ended up being a bios issue that caused the TDR error. I had to rma it to bfg to get the bios flashed. It was the 2nd time I had to RMA this card, so it was time to get something else (eVGA 8800 GTS 512). I haven't had one single problem with this card and it runs alot cooler to.

[$n][pErMan]

When I built my system (680I, 8800GTX, 2g @ 800...) I had XP. I used it for a month or so, bought Vista, used it for a while with no problems. I played BF2142 at max everything. No problemos. It seems like after a Windows Update I started getting this "nvlddmkm" error. I wish I could say for certain if I was using DX10 or 9.0c. My computer locks up a bunch. The only way to get my system stable is to underclock my card. When my system boots it has squiggly lines (worms) all in the display, does ya'lls do that? Has anyone heard of or thought of a class action law suit? I paid $700 dollars for a card that is useless.
I get no display corruption... sounds like your card has a clear defect.

On the class action idea though, I would be all for it. The fact that some BIOS's for some people fix it leads me to believe there is a clear defect with all cards and the BIOS flash just masks over the error (perhaps by disabling some features). I dont know... all I know is however it seems to be driver related in some way. As I have stated, I have ZERO issues in Vista 32-bit... I could play WiC and FSX in DX10 till no end without a crash. In Vista 64-bit I can't play more than 15min in FSX before it ****s itself and about 25min in WiC before it also crashes. Yet I can play Crysis 10DX till no end without any error. In my honest opinion it seems driver related... but in being a part of this thread for some time now I have come to found each of us have had a slightly different issue with this error which is making it a bitch to track down.

BTW.. congrats on the ATi card Roliath... let us know how it runs... I have heard ATi has a similar issue so if it works flawless and runs good for you... my next card might honestly be an ATi card as I am just fed up with nVidia as of late.... and I have been using nVidia cards sense the GeForce 2 Ti series....

[Roliath]

[pErMan']
BTW.. congrats on the ATi card Roliath... let us know how it runs... I have heard ATi has a similar issue so if it works flawless and runs good for you... my next card might honestly be an ATi card as I am just fed up with nVidia as of late.... and I have been using nVidia cards sense the GeForce 2 Ti series....

I just don't understand how my other rigs (less powerful all around) don't have this issue. I'll be getting the ATI 3870x2 on tuesday, and I might pick up another board and see about running them in crossfire.

Not sure yet, because I'm also not impressed too much with the TRUE120 so I might go watercooling.

Hell I should just bring my dual quad box from work home and just use that and be done with games... :-(

EDIT:
I'll say this though, I was testing BIOS's(tried out an XFX bios) on the GTX and I noticed that on my fresh install of 64bit I wasn't getting any TDR errors however I did get some artifacts that I believe were driver related.
At times 3dmark06 would run without issue, other times it would lock up and BSOD pointing to nv4 driver. Its a toss up at this point, hell it may be related to my chipset. But at this point i'm far beyond messing with hardware/drivers/bios's as I feel a someone who spends hundreds even thousands on a Rig should not have to deal with this and not have an official response from M$ or NV. 1 Year and counting and I cannot believe this issue
is still around and there are no known "good" fixes for this.
I am extremely happy that my Dual Quad rig for my home is not built nor ordered yet as I am extremely leaning towards ATi on that build and this TDR issue has completely made me rethink my build (next 6~8 months).

I've heard that ATi has issues with OpenGL apps, but i'll take a hit in performance if it provides stability. Going fast doesn't mean squat if you falling apart getting there.

[quad_fx]

hey guys,

sad to hear that many loyal nvidia fans (such as myself) are now looking towards ati because of this frustrating error. you would honestly think nvidia would have resolved this by NOW.

anyway, my buddies and i have been flying around on my rig in dx9 literally all night, probably 4 hours, and did not have one problem. that leads me to believe that this is definitely dx10 related, and agree that it's probably a driver issue. i would go to vista 32-bit after hearing how sniperman had such good luck with it, but having 4GB of memory, i can't allow more than a gig of it to go to waste simply because i can't run FSX in dx10. i guess for now i'll just have to deal with the (now, after experiencing dx10) crappy water and clouds in dx9. i'll continue to monitor this thread in case any new information arises. thanks for your help fellas, and for the man that does find the solution, i've got a beer with your name on it.

[$n][pErMan]

hey guys,

sad to hear that many loyal nvidia fans (such as myself) are now looking towards ati because of this frustrating error. you would honestly think nvidia would have resolved this by NOW.

anyway, my buddies and i have been flying around on my rig in dx9 literally all night, probably 4 hours, and did not have one problem. that leads me to believe that this is definitely dx10 related, and agree that it's probably a driver issue. i would go to vista 32-bit after hearing how sniperman had such good luck with it, but having 4GB of memory, i can't allow more than a gig of it to go to waste simply because i can't run FSX in dx10. i guess for now i'll just have to deal with the (now, after experiencing dx10) crappy water and clouds in dx9. i'll continue to monitor this thread in case any new information arises. thanks for your help fellas, and for the man that does find the solution, i've got a beer with your name on it.
Ya, you are about at the same point as me... sucks man :( As much of a bitch as this error is... you better make it a keg... lol. :p

[slaWter]

Man I hope the GX2 improves the situation. I don't expect a perfect solution for this issue but hopefully it's on par with the G92 GTS.

Roliath, enjoy your X2!

quad_fx, good to see DX9 is stable for you as well. If you don't like the clouds and the water in DX9 you could use FEX (http://www.flightenvironment.com/). Looks much better than the DX10 stuff.

[$n][pErMan]

Man I hope the GX2 improves the situation. I don't expect a perfect solution for this issue but hopefully it's on par with the G92 GTS.

Roliath, enjoy your X2!

quad_fx, good to see DX9 is stable for you as well. If you don't like the clouds and the water in DX9 you could use FEX (http://www.flightenvironment.com/). Looks much better than the DX10 stuff.
Thing is... the error should not exist at all... even on newcards we should not have to settle for "it happens less often" we should settle for nothing less than a fully functioning piece of hardware :(

[Roliath]

[pErMan']Thing is... the error should not exist at all... even on newcards we should not have to settle for "it happens less often" we should settle for nothing less than a fully functioning piece of hardware :(
Exactly, the only thing that makes this thread worth reading now is just to look at your avatar..

[quad_fx]

Man I hope the GX2 improves the situation. I don't expect a perfect solution for this issue but hopefully it's on par with the G92 GTS.

Roliath, enjoy your X2!

quad_fx, good to see DX9 is stable for you as well. If you don't like the clouds and the water in DX9 you could use FEX (http://www.flightenvironment.com/). Looks much better than the DX10 stuff.

wow, slawterman, i have no idea why i haven't ran across this little jewel (fex) before, being the FSX enthusiast that i am. i have to tell this really brightened my day up looking at those screenshots, and i didn't even hesitate before buying it, lol. i can't wait to get this up and see how it looks. thanks again for the recommendation, i'll let you guys know how it works out.

EDIT: stunningly beautiful, i'm in love with this program. forget dx10, it may look good, but this looks just as good if not better, and i can change how it looks! highly recommended

EDIT 2: i know this isn't an fsx forum, but i know several of you play the game, so do any of you know if you can use FEX and Active Sky X on the same FSX installation, or will it cause problems?

[Isola]

Damn damn damn damn

No way to play Company of heroes with any forceware driver and 8800GTx...
Nvlddmkm error keeps appearing.

Very boring.

No problems with others directx10 games like crysis or world in conflict..

>_<

[tisdale36]

ROLIATH, did you get your ATI card? Does it work? If I can get a refund of $650 for this P.O.S. EVGA nvidia 8800 GTX SC I will definately go ATI and never return to Nvidia for life. I think that if EVGA does not give me a full refund I am going to seek a lawyer because this is rediculous and my card is advertised to work great with Vista and DX10. Also, I dual booted my pc and used XP and it stilled locks up using XP and DX 9c. I would like to try my card on someone elses pc that is using a 7600 and XP and has no problems but i am worried that if I put the driver on his pc that it will "copulate" him too.
Sean
:captnkill: (nana2)
Lick the banana

[tisdale36]

ISOLA, the only way to play is to underclock your card, I set factory overclocked EVGA 8800 GTX core clock to 461 and the memory clock to 810 using ntune, you will need to use diefferent settings. Maybe underclock by 10 - 15%. Try it and tell me if it locks up after a period of time. I am able to play BF2142 at max settings sometimes indefinately. Look forward to hearing from you.
Sean
:captnkill: (lee63)
Ball lick

[Isola]

the problem is that only company of heroes gives me "NVLDDKM stoppe dresponding".....i have stock frequencies and low temperatures no reasons to underclock my card only for Company of heroes but damn that game rocks:rw:

i expect microsoft fix for this problem and something from Nvidia,this is a serious issue.I have an XFX 8800gtx manufactured card.

[Furiøùs]

I never got this problem until i changed to the 780i chipset. The first board that did it was the Asus P5N-T Deluxe, i couldnt play for a few minutes before it would either drop out crysis to desktop or Bluescreen in FSX with Nvlddmkm has stopped responding etc. I thought my Windows XP was corrupt, so im on Windows Vista Ultimate x64 and its doing it again with a eVGA 780i and its still doing it, but i can play for an hour or so and then it will. Not sure what the culprit is, but its definately getting on my nerves. It's done this so far with the 174.12's and the 169.18 or somethin, whatever the latest WHQL off of nVidia's website.

[Roliath]

ROLIATH, did you get your ATI card? Does it work? If I can get a refund of $650 for this P.O.S. EVGA nvidia 8800 GTX SC I will definately go ATI and never return to Nvidia for life. I think that if EVGA does not give me a full refund I am going to seek a lawyer because this is rediculous and my card is advertised to work great with Vista and DX10. Also, I dual booted my pc and used XP and it stilled locks up using XP and DX 9c. I would like to try my card on someone elses pc that is using a 7600 and XP and has no problems but i am worried that if I put the driver on his pc that it will "copulate" him too.
Sean
:captnkill: (nana2)
Lick the banana

It Just came in today!

I had a 6200LE overnighted to me as I found out that my ATI card had been delayed. So on a Brand spanking new 74GB raptor, I loaded Ultimate 64bit. Using 169.25 drivers (might be off a revision, the whql ones on their site) two hours into moving files, making backups, the driver stopped responding on me..........

So it was not only my 8800GTX!

This "pissed" me off to see this card do the same so I just turned the rig off.

I have dinner planned tonight so I may not have enough time to do any testing tonight. I don't work tomorrow so I will post results tomorrow. I have HIGH hopes for the ATi card.

Also I'm contemplating on ordering a new mobo using another chipset, I just honestly don't know. If the ATi card doesn't work out for me, I may just do what I was planning and just order a Dell Precision 690 which was the whole plan anyways.. :(

[Knacki99]

the problem is that only company of heroes gives me "NVLDDKM stoppe dresponding".....i have stock frequencies and low temperatures no reasons to underclock my card only for Company of heroes but damn that game rocks:rw:

i expect microsoft fix for this problem and something from Nvidia,this is a serious issue.I have an XFX 8800gtx manufactured card.

Yeah CoH is crashing quite a bit with this error. Tried various drivers, 169.61, 174.16, 169.32 & 169.39. Added an extra fan and now it seems rather stable with 169.39. No probs with other games I might mention, eh? Even before the extra fan...

So when SP1 comes with appropriate drivers I hope this will be gone.