Nvlddmkm stopped responding is getting VERY OLD...

[ragingWS6]

It all has to do with RAM. I have ADATA 4GB kit DDR2-6400 with 4-4-4-12 timings. The kit says 1.9-2.1V as far as voltage. I had 2GB Corsair XMS26400C4 that required 2.1V voltage in before. I never changed the voltage thinking the range was fine. Well, I started getting the TDR errors. Went into the BIOS, changed the voltage to 1.9V and the problem was solved. Check RAM timings and overclocks and try things a little more conservatively and see if you get better results. This has been working for me for the past 2 weeks with the 175.63 installed. I have also pushed my PCI-E clocks to 110 and this helped as well.

[slaWter]

RAM is not always the solution... I've tried multiple RAM combinations with 3 different kits.
I think it was more to do with VGA BIOS.

[ragingWS6]

RAM is not always the solution... I've tried multiple RAM combinations with 3 different kits.
I think it was more to do with VGA BIOS.

You are correct, RAM isn't always the solution. I need to reword that post. I meant it OFTEN is.

[Roliath]

This thing came up again :-(
with 175.80's for me.
gonna try a different driver set, but this GX2 has been a pain to get working correctly in games.

from interlaced videos, and interlaced gaming (constantly having to alt-tab, to get the video to sync). If only consoles were as powerful as pc's, than we wouldn't have to deal with this crap.
:-(


EDIT: 177.26's aren't any better

[$n][pErMan]

Anyone getting these errors with the new GTX280???

[slaWter]

[pErMan;1696862']Anyone getting these errors with the new GTX280???

So far so good.

I didn't get this error for weeks now with different cards (8800GTX, GX2 and the 280). It got much better with newer drivers.
Do you still get this error?

[dotslasher]

I just recently started getting this error.

It started happening when I installed the newer 175.xx and 177.xx drivers.

The first time it happened was when I wanted to open a pdf file in acrobat reader. It took 1 minute or something and then the screen turn black and I got the aformentioned error.

Now it's been happening to me with all drivers I have tested so far. 177.35/39/40/41 and with the 175.16/19 set as well.
It also happens when I go afk and my screensaver kicks in.

any advice?

[$n][pErMan]

So far so good.

I didn't get this error for weeks now with different cards (8800GTX, GX2 and the 280). It got much better with newer drivers.
Do you still get this error?
To be honest... I have not played a DX10 game in awhile... been playing Mass Effect and Civ BTS. I might fire some FSX up in DX10 mode and see what happens.... I ussually got that damn error within an hour on that game :( Using 175.16 driver set.

[slaWter]

[pErMan;1697728']To be honest... I have not played a DX10 game in awhile... been playing Mass Effect and Civ BTS. I might fire some FSX up in DX10 mode and see what happens.... I ussually got that damn error within an hour on that game :( Using 175.16 driver set.

FSX is the only DX10 app I play these days but it's finally stable.
Good luck!

[Alaa]

That "Nvlddmkm" gives me bsod randomly!

[David power]

I was getting that issue allot in vista x64, the screen would flicker and then after a while it would crash, sometimes vista would fix the issue before a crash which was nice,,,,

I havent seen it in a while actually, I miss you Nvlddmkm crash,,,, why did you leave me,

[nekrosoft13]

I havent seen it in a while actually, I miss you Nvlddmkm crash,,,, why did you leave me,

you want it back?

[$n][pErMan]

you want it back?
He can have mine.... I dont want it.

[David power]

[pErMan;1698821']He can have mine.... I dont want it.

Lets see,

I built a new pc and since then I have come across so many problems that I haven’t actually got around to playing games,

when the Nvlddmkm error stopped it was like saying good by to a child when they go to college for the first time, I sort of got attached to my errors and crashes, now I have most of them gone and I realised I don’t really want to play games, I just want to build and play with hardware.

I have my COD4 issue to fix at the moment, I thought it was an OC issue but it looks like its back, :)

I found driver sweeper to be a great help here actually.

[ragingWS6]

Well, it came back to me this past week. I was gaming playing COD4 when hello flickering screen then nvlddmkm.sys BSOD! So, I started checking things out. In order to try and resolve this I have:

swapped out my RAM (2GB Corsair XMS2-6400C4 for 4GB ADATA Vitesta)
swapped out my PSU (box has a Silverstone 1200W in it now...so I don't think power is my problem)
tried single card configs...only thing that works (and it works with either card as long as they are underclocked to 560/885 or lower)
Tried onboard sound versus the X-FI card
Dropped CPU to stock clocks and stock voltages
Tried a multitude of different drivers for the MB and video cards...no dice
upped the PCI-E clocks to 110...helped to extend the stability of the system

The cards are running cool (hitting 65C under load) and the CPU doesn't break 48C under load. It is usually at 39C at idle. This is at 1.34V. Tried the VDROOP mod without help.

I am thinking the 680i board is the issue for me. I am trying to get with EVGA to get mine RMA'd here and see if it helps. The board is barely over a year old and it fits under the 2-year warranty of the board.

EDIT: EVGA wants to RMA both my 8800GTXs. So, I am going to do that and see what happens.

[slaWter]

EDIT: EVGA wants to RMA both my 8800GTXs. So, I am going to do that and see what happens.

That could actually help because I still think it could be VGA BIOS related. Good luck.
680i is the reason for a lot of problems but not for this one.

[$n][pErMan]

That could actually help because I still think it could be VGA BIOS related. Good luck.
680i is the reason for a lot of problems but not for this one.
Keep us posted... I am willing to RMA mine if it works. Better yet... if it works... could you save the VGA BIOS file and give it to me so I can flash my own card? :)

[ragingWS6]

Ok....so I did just a little testing yesterday....

I was running 60.80.0A.00.01 on the card in PCI-E1. I was running 60.80.07.00.11 on the card in slot PCI-E2. So, I went out to mvktech and downloaded nvflash and the latest EVGA 8800 GTX SC bios they had (60.80.0A.00.15). I put it on both cards. Run DriverCleaner.NET in safe mode and reinstalled the 177.39s. Then, I ran 3dMark06 looping. With 1 card in alone, it would run about an hour and a half and then give an nvlddmkm.sys BSOD. With both in SLI, it was about 40 minutes. SO, I decided to get the 60.80.13.00.13 of the normal 8800 GTX and mod the timings to boot at 621/1000 instead of 575/900. Same results....

So, I started thinking...why haven't I thrown them in one of my other systems? So, I took my DVR system and uninstalled CCC and the HD 2400 and took the box down. I took one of the 8800 GTXs and threw it in. I installed the 177.39s (of course running DriverCleaner first) and 3dMark06. The system has a Corsair 550W PSU so a single card in it is just fine. Well, after about 2 hours guess what was on the screen? BSOD nvlddmkm.sys! That was on Vista Ultimate x86 SP1.

I always wondered if SP1 was the issue, so I took the other card and threw it in my HTPC that is running Vista Business x86 without SP1. DriverCleaner yet again after I removed CCC and the HD 3650. This system has an Antec 560W, so again, power not an issue. Installed 177.39s and 3dMark06. Ran about 2 hours and, of course, guess what was on the screen? The damn BSOD!

So, it looks like it is both my cards. It obviously isn't a BIOS issue on the cards. Want to hear the worst part? I registered both my cards after the 30 day period and I have had them for a year and 5 days, so EVGA denied my warranty claim. The would have honored it if i would have submitted the RMA 6 days earlier.:( That is a major blow to my wallet. :(

So, I am either going to buy a single GTX 260 OC (will buy the 2nd later on) or 2 XFX 9800 GTX XXX boards. I was also contemplating selling the 680i board and buying 2 4870s and an Intel X48 board.

[$n][pErMan]

Ok....so I did just a little testing yesterday....

I was running 60.80.0A.00.01 on the card in PCI-E1. I was running 60.80.07.00.11 on the card in slot PCI-E2. So, I went out to mvktech and downloaded nvflash and the latest EVGA 8800 GTX SC bios they had (60.80.0A.00.15). I put it on both cards. Run DriverCleaner.NET in safe mode and reinstalled the 177.39s. Then, I ran 3dMark06 looping. With 1 card in alone, it would run about an hour and a half and then give an nvlddmkm.sys BSOD. With both in SLI, it was about 40 minutes. SO, I decided to get the 60.80.13.00.13 of the normal 8800 GTX and mod the timings to boot at 621/1000 instead of 575/900. Same results....

So, I started thinking...why haven't I thrown them in one of my other systems? So, I took my DVR system and uninstalled CCC and the HD 2400 and took the box down. I took one of the 8800 GTXs and threw it in. I installed the 177.39s (of course running DriverCleaner first) and 3dMark06. The system has a Corsair 550W PSU so a single card in it is just fine. Well, after about 2 hours guess what was on the screen? BSOD nvlddmkm.sys! That was on Vista Ultimate x86 SP1.

I always wondered if SP1 was the issue, so I took the other card and threw it in my HTPC that is running Vista Business x86 without SP1. DriverCleaner yet again after I removed CCC and the HD 3650. This system has an Antec 560W, so again, power not an issue. Installed 177.39s and 3dMark06. Ran about 2 hours and, of course, guess what was on the screen? The damn BSOD!

So, it looks like it is both my cards. It obviously isn't a BIOS issue on the cards. Want to hear the worst part? I registered both my cards after the 30 day period and I have had them for a year and 5 days, so EVGA denied my warranty claim. The would have honored it if i would have submitted the RMA 6 days earlier.:( That is a major blow to my wallet. :(

So, I am either going to buy a single GTX 260 OC (will buy the 2nd later on) or 2 XFX 9800 GTX XXX boards. I was also contemplating selling the 680i board and buying 2 4870s and an Intel X48 board.

Screw that dude... get yourself an ATi card after that kind of customer service :thumbdwn: I have yet to play a DX10 lately that I had the issue on to see if my situation has improved but if not... ATi will be my next jump.

[Swift-R]

sorry, double post

[Swift-R]

This isn't happening with xp or xp x64 right?

[Lfctony]

Just got it again in Crysis. It's been a while... It might be the 177.41s... :(

[Roliath]

This isn't happening with xp or xp x64 right?

I believe this issue doesn't exist in XP, if the cause of this were to happen in XP the computer would just blue screen instead.

[ragingWS6]

No, it doesn't. So, if anyone wants a few EVGA 8800 GTX S/Cs for $175 a pop and is ONLY going to run XP, I have 2

[noko]

This whole issue has plague me since both Vista 64 and 8800 GTX. I am sick of it! Appears this will never go away with this setup. Using an Intel setup, previously an ULI setup and I thought it was related to my old configuration. Nothing changed, a complete rebuild and same problem. This to me it is Vista/driver/8800 or G80 related, maybe just G80 related and not fixable. I don't know how many hours I've wasted in trying beta after beta drivers when all the official drivers where even worst. :thumbdwn: