Nvlddmkm stopped responding is getting VERY OLD...

[$n][pErMan]

FYI.. I just tried WIC in DX10 mode with my RAM Voltage set to 2.25V.... and it crashed after about 25 minutes.... I am not willing to go any higher on the voltage. This is ****ing stupid.... nvidias ****ty drivers have to be partly responsible... I NEVER had this error in Vista 32-bit... and to be honest, I am thinking of switching back to Vista 32-bit from 64-bit :mad:

[LORD-eX-Bu]

contact evga about the problem, msi told me to rma my video card and the problem went away.

[$n][pErMan]

contact evga about the problem, msi told me to rma my video card and the problem went away.
I might have too... I will be pretty pissed if its a very well known issue and they know its a defect but don't come out and say it :mad: Had this card for almost a year now...

[slaWter]

I installed 2x1GB (2.1V) today to test FSX in DX10 preview mode. Just did a 30min flight and it's stable so far. I'll keep you posted.
I'm not going back to 2GB but I really want to know why FSX crashes with this error message.

[conroejoe]

Got the memory today and 2x2GB doesn't help :(
But I've noticed something else. I tried different vdimm settings like Quick209 suggested.

2.10V -> hard lock after around 20min
2.15V -> Nvlddmkm error message during the third flight, after around 45min (all three flights)

I'm now at 2.20V but I don't have anymore time to test that as well. Gonna try it this evening or tomorrow...

Update:
Just did a 20min and a 25min flight without the error. Memory is at 2.20V. So far so good...


Have you guys tried to kick the command rate to 2T with 4 sticks? DDR2 was never meant to run 1T which is why the nvidia boards seem so unstable, people are forcing ddr2 to do what it was never meant to. BTW I have no problems with 4 x 1GB Corsair Dominator 8500 @ 2.1v on a Asus P5k-e (p35).

Try bumping command rate to 2T and lay off the volts before you kill something.

[slaWter]

Never used 1T for DDR2, it's always set at 2T.

[$n][pErMan]

Have you guys tried to kick the command rate to 2T with 4 sticks? DDR2 was never meant to run 1T which is why the nvidia boards seem so unstable, people are forcing ddr2 to do what it was never meant to. BTW I have no problems with 4 x 1GB Corsair Dominator 8500 @ 2.1v on a Asus P5k-e (p35).

Try bumping command rate to 2T and lay off the volts before you kill something.
My memory runs at 2.2V... and is acctually under warranty up to 2.4V :D And mine is running at 2T (Intel Chipset).... does nothing :( I even have it running at a 1:1 ratio (underclocked) and it still does nothing.... also tried running it at stock speeds (+800Mhz) and did nothing to fix the issue either....

I installed 2x1GB (2.1V) today to test FSX in DX10 preview mode. Just did a 30min flight and it's stable so far. I'll keep you posted.
I'm not going back to 2GB but I really want to know why FSX crashes with this error message.
Id like to know why the hell 4GB screws anything DX10 up it seems. I am thinking thats why when I went to 64-bit I have this damn error now. In 32-bit I had 4GB installed, but it only saw and used 2.93GB. Perhaps more stress on the RAM now causing issues? Not a clue here... I am at a loss for figuring this out now. I have tried everything and refuse to use only 2GB. I am thinking next weekend its back to 32-bit Vista for me. :mad: I am not going to RMA my card.. takes to much time and I need my quick gaming fix every other day or so.

*Edit* --> I am going to try something today.. I am going to disable PCI memory remapping in the BIOS and only allow the mother board (and thus the OS) to only see 2.93GB of RAM even though I am currently in a 64-bit OS. This will allow me to use more than 2GB (as I could in 32-bit Vista) but will mask over about 1GB worth of memory. I will then test in Vista 64-bit. If I still get the error I know its some BS with 64-bit nvidia drivers as I saw the same amount of RAm in 32-bit Vista. If I am able to play FSX and WIC in DX10 mode without issue... than there is seriously something ****ed up with 4GB, nVidia and DX10 for some reason.

[Roliath]

Sniperman, love the avatar
And I know exactly what you mean about 64bit Vista.
I've been having nothing but problems with my install too.
I can't even put in my 8GB yet (only 4GB installed atm) because I can't get ANY driver to not crash on me.
Every single driver I have tried has had this dreaded error and it is pissing right the "f**k" off.
I'm still going through and looking over every setting once, twice, three times just to make sure something I'm currently unaware of is causing this.

[$n][pErMan]

Sniperman, love the avatar
And I know exactly what you mean about 64bit Vista.
I've been having nothing but problems with my install too.
I can't even put in my 8GB yet (only 4GB installed atm) because I can't get ANY driver to not crash on me.
Every single driver I have tried has had this dreaded error and it is pissing right the "f**k" off.
I'm still going through and looking over every setting once, twice, three times just to make sure something I'm currently unaware of is causing this.
lol.. thanks. Yea, just to report my trick did not work. It has to be nVidia's ****ty drivers... I have changed no hardware and it litterally worked perfect in Vista 32-bit. I can't figure it out and its pissing me off big time. I will be curious to see how slaWter reports back with just 2GB of memory installed. As it stands now, I might be going back to Vista 32-bit next weekend. Can I play WiC and FSX in DX9 mode in Vista 64-bit? Yes.... but why should I have too on n****tias account? Thank god I made it dual boot with my old 32-bit install.... If anyone has any other ideas I will gladly listen!

[Roliath]

Sniperman, once again....Nice Avatar :)

But yeah I solved my problems, I'm going to dual boot Vista 32bit and XP 64bit.
I can't deal with this Vista 64bit **** anymore. How the hell can this problem have gone on soo damn long without any fix is above me.
That leave 4GB of ram to waste thanks to 32bit memory addressing.
(I have 4x2GB DDR2 800)

EDIT:
I rather use Server 2008 when it comes out as a main OS than vista ultimate 64bit, I literally could not play games for more than 20 minutes (or run 3dmark) without getting this error.
Three Re-Installs, Three different Drive setups (Raid, diff. Raptor, 1TB Sammy), different Ram setups, nothing overclocked all default settings.....Its been more than a headache this time around.
:-(

[slaWter]

Roliath, what's your EVGA 8800 GTX BIOS version?
Maybe it could be fixed via VGA BIOS update. Unfortunately I got warning messages, something about an ID mismatch so I didn't flash the card yet.

$n][pErMan, I need a bit more time with the 2GB test to be sure. Played around 1.5h so far in two sessions and it seems to be stable.

[Roliath]

Roliath, what's your EVGA 8800 GTX BIOS version?
Maybe it could be fixed via VGA BIOS update. Unfortunately I got warning messages, something about an ID mismatch so I didn't flash the card yet.

$n][pErMan, I need a bit more time with the 2GB test to be sure. Played around 1.5h so far in two sessions and it seems to be stable.
I thought about it last night, i'll check into it now.
Currently I'm running 60.80.06.00.01, i'll see what EVGA has as far as BIOS's on that one site with all the roms..
Mvktech something?
I'll figure it out.

found this one at mvktech.net
60.80.0E.00.B1, rev 9
i'll have to give this a shot today, after I do some more research on this BIOS

[slaWter]

Nice, thanks Roliath. Please report back.
With a bit of luck I could get my hands on a G92 GTS this week to test it in FSX... maybe this card doesn't suffer from the same crashes.

[Roliath]

Nice, thanks Roliath. Please report back.
With a bit of luck I could get my hands on a G92 GTS this week to test it in FSX... maybe this card doesn't suffer from the same crashes.
Well I flashed the BIOS, I'm running 32bit Ultimate right now, with my xp cd ready to go if this doesn't work.

First off, i'm using beta drivers (173.65) and I was able to complete the Windows Assessment (wasn't before), 3Dmark06 wouldn't start, and i'm going to try again and test some games out..

It isn't looking that great so far.

EDIT: Crysis locked up within the first few minutes..Trying another driver set before installing XP Pro 64bit.
Vista, you've lost another.
This really pisses me off to no end.

EDIT2: Installing XP Pro now, anyone want to buy a 8800GTX? I'll settle for ATi at this point.

[96Firebird]

Here is yet another person with this problem. However, mine is slightly different. I own an eVGA 8800GT 512MB. I only get the error when I overclock, it never happens on stock clock speeds (600/1800). I can OC safetly up to 700/1900, but anything past that an I get the nvlddmkm has stopped responding error. My temps are fine at around 65C, so I know heat isn't an issue. I am really confused, and will try any method to fix it. I've read so many I don't know where to start.

[slaWter]

Sorry to hear that Roliath :(
Can you please do me a favor and post a link to the BIOS you used to flash the EVGA GTX? Thanks.

[Roliath]

I used this one (http://www.mvktech.net/component/option,com_remository/Itemid,26/func,fileinfo/filecatid,1925/parent,category/).

I also made my own versions with higher clocks (600/1350/2000) and flashed with that one. Xp isn't so bad, I played Crysis for about 40minutes without any crashes. I'm going to dual boot vista64bit and just keep it installed for whenever SP1 comes out and see if there are any changes.

I've frankly had enough of it though, I just don't understand the issue fully yet as to why it happens only this rig and not any of my others.

[slaWter]

I used this one (http://www.mvktech.net/component/option,com_remository/Itemid,26/func,fileinfo/filecatid,1925/parent,category/).


Thanks for the link. But isn't this quite an old one? Submitted on 30 December 2006...

Just did another DX10 test in FSX with 2GB installed (vdimm at 2.10V) and the game crashed after 25min!! So 2GB or 4GB doesn't make a difference!
I'm not gonna try it with a higher vdimm because that didn't help with 4GB.

[Quick209]

Sorry to hear that the RAM voltage didn't help some of you all. I have been running good since the day of that post. Of course I still can't run Crysis 64bit version but of course I haven't met anyone who has yet so I am chalking that one up to maybe something needs fixing in Crysis.

My system actually starting not booting up with 4 gigs installed and had to up the voltage with a single sim just to get it going. Going to post my system specs so everyone can see:

EVGA 680i motherboard P32 Bios
4 Gigs OCZ Reaper 1066MHZ Ram (voltage at 2.225v)
2x XFX GeForce 8800 GT 320MB 320bit throughput (true dual 16x PCIE slots)
Soundblaster XFi Extreme Gamer
2 X 320 SATA HDs
Memorex 4x DvD burner (hey, it is from my old system and I like it, stable and no coasters)
Armor VA8000B Series case (Thing is a heavy beast)
19 inch Viewsonic VA912b LCD

[$n][pErMan]

Sorry to hear that the RAM voltage didn't help some of you all. I have been running good since the day of that post. Of course I still can't run Crysis 64bit version but of course I haven't met anyone who has yet so I am chalking that one up to maybe something needs fixing in Crysis.

My system actually starting not booting up with 4 gigs installed and had to up the voltage with a single sim just to get it going. Going to post my system specs so everyone can see:

EVGA 680i motherboard P32 Bios
4 Gigs OCZ Reaper 1066MHZ Ram (voltage at 2.225v)
2x XFX GeForce 8800 GT 320MB 320bit throughput (true dual 16x PCIE slots)
Soundblaster XFi Extreme Gamer
2 X 320 SATA HDs
Memorex 4x DvD burner (hey, it is from my old system and I like it, stable and no coasters)
Armor VA8000B Series case (Thing is a heavy beast)
19 inch Viewsonic VA912b LCD
Go Figure... I get the nvlddmkm error and can't fix it but am able to run Crysis 64-bit with no issues (played all the way through in DX mode) while you fixed the nvlddmkm error but can;t play 64-bit Crysis.... lol.

I am at a loss though... it must be 64-bit Vista or nvidias drivers... I have tried everything and I keep coming back to my system working flawless in Vista 32-bit and I only get this error in 64-bit.... :( I will see if I can think of anything else to try....

[slaWter]

I'll definitely get a G92 card tomorrow for a test run, I'll report back if it crashes as well. I'm gonna use 4GB (2x2GB) again, apparently it's not memory related.

[$n][pErMan]

I'll definitely get a G92 card tomorrow for a test run, I'll report back if it crashes as well. I'm gonna use 4GB (2x2GB) again, apparently it's not memory related.
Yes... keep us posted! :)

[breathemetal]

i get this all the time with cod4 mp. any fix yet?

[slaWter]

[pErMan']Yes... keep us posted! :)

Wow! Looks like a VGA BIOS update could help for the GTX because I didn't get the error message in FSX with the 8800GTS 512! Two 1h+ flights in DX10, one with 2x2GB and one with 4x2GB and no problems whatsoever! I'm gonna test it again today but FSX usually crashed after 20-30min, this looks really good so far :D

[XxDeadlyxX]

Ok um... a few days ago while playing CoJ DX10 on the Billy mission where there's lightning and you are meant to sneak past (obviously I kill em all tho :D), guys who were killed from my whip had weird artifacts near them around a campfire... then display stopped responding...

After that, even though not in the game, it continued to do it every 5 minutes or so afterwards regardless of what I was doing on the desktop.

After a reboot it was fine and has been fine since... hmmm random.

I've had it happen once or twice before that randomly (can't remember what games), but after a reboot when it was happening it just went away.

And as per sig I've got the culprit system type (8800 4GB x64)