Nvlddmkm stopped responding is getting VERY OLD...

[Nkd]

these errors wont happen at a set time, sometimes I dont get the error for hours but they are most likely to happen while running 3d apps. well I have two cards one gives me errors in the same systems and other doesnt. If someone can get it to go away thats excellent but how you set other components should have nothing to do with your graphic card errors, For Instance: I have never heard an ati user getting the error of this sort. Only detailed explanation we can get is from nvidia, but I believe if you can not get the problem to go away its most likely your GPU than anything else. For me I know its my gpu because two cards based on same core and only one gives me problems.

I would never lay the blame on other components because if there is anyone to blame its nvidia, they are the ones that have to explain this. IF they tell stop overclocking and you will stop getting this error, I would laugh and not buy a g80, how come it doesn't happen with ati cards. One of my system has hd 2900, and overclocked more than 50% and I have never seen that error

well its everybody's opinion and my personal opinion is that when you spend a few hundered dollars on something you should not have to live with these problems and waste your time troubleshooting. for me its simple, same system and two different ultra's one gives me the errors and the other doesn't. I guess my drivers like the bfg card better than evga card, so who's fault is that, lets see probably Nvidia's.

The problem is not just limited to 680i, I have an ip35-pro has no nvidia part in there but the graphic card. I am not going to adjust the voltages when its only one card that gives me problems.

LOL I have to sell my one of my ultra's and evga keeps sending me cards that either freeze or get corruption. first one didnt output any video signal, and the second card locks up in xp and gives me these errors in vista, It also locks up in vista when I am playing games, but I am able to ctrl+alt+dlt out of the desktop, but I keep getting that error after the game locks up until i restart my computer. I should have kept the one I got, I had to downclock that superclocked ultra to make it work, only if I knew that they dont really care if the product they send me works or not, lol. There are several people in their forum that are complaining about rma products. I just bought a paper weight,lol.

[Lfctony]

Well, I've been looking into it. ATI users have atimtag.sys errors as well. It seems its a Vista problem. However this didn't happen with the 100.59s which indicates Nvidia have changed something in the drivers. It's possible the card is used more efficiently, thus the errors have increased with subsequent drivers. I'm back to XP, for now.

[GT-Force]

I have to sell my one of my ultra's and evga keeps sending me cards that either freeze or get corruption. first one didnt output any video signal, and the second card locks up in xp and gives me these errors in vista, It also locks up in vista when I am playing games, but I am able to ctrl+alt+dlt out of the desktop, but I keep getting that error after the game locks up until i restart my computer. I should have kept the one I got, I had to downclock that superclocked ultra to make it work, only if I knew that they dont really care if the product they send me works or not, lol. There are several people in their forum that are complaining about rma products. I just bought a paper weight,lol.

Well well, I have an eVGA 8800 GTX, and having this problem. Yet, I don't think everyone having this problem have an EVGA card.

I think there are some web spreadsheet applications that allow a spreadsheet file to be made public, and once that is done, it can be edited by anyone. Is there anyone here with time to look for this and set it up, then anyone having this problem can go into the spreadsheet and enter their specs (model numbers and brand-names for all hardware components, BIOS settings such as memory timings etc.) in to the corresponding columns, then it may be easier to troubleshoot the components or the component combinations that may be causing this problem. Though, I wouldn't be surprised if we end up having even a more confusing picture in front of ourselves, given the variability of the PC platform.

Looking at all the different posts, suggesting completely different solutions to this problem, it is easy to guess that this one of the PITA problems that is extremely hard to troubleshoot and find the reason for, and provide a fix for it; so I don't really blame nvidia or MS. But then again, they may be the only ones who is receiving enough information (e.g., Vista Problem reports) to make this happen.

[Villa]

Well, I've been looking into it. ATI users have atimtag.sys errors as well.

Thats interesting, I would like to read up on that too. maybe someone might find a solution that would benefit both parties. Could you please provide some links to this, as I have tried Google and going to some ATI forums, but could not find anything.

[Smee]

Thats interesting, I would like to read up on that too. maybe someone might find a solution that would benefit both parties. Could you please provide some links to this, as I have tried Google and going to some ATI forums, but could not find anything.

As would I, I am seriously thinking about a jump back to ATI at this point.

[Slammin]

I'm convinced it's a chipset timing issue. Heck, even the registry treaks suggest the same and since I've upgraded to a new mobo bios, one that just happens to not let me clock my fsb up as high as the previous ones, I have yet to see this error again.

For me at least, it's a non-issue but if I want to reinstall my old bios so that I can overclock my fsb again, I'll be screwed, again.

What I suspect is going to be the final fix is for them to reduce driver performance, unfortunately, or maybe even a vid bios update tha slows things down. I sure hope it doesn't come to either, but since this problem spans across both Vista and XP, it wouldn't seem like something nVidia should take 100% responsibility for.

Driver model, hardware/firmware design, or OS constriction? As another poster said, this one has got to be a PITA for the developers to track down, though since it didn't happen with 100.54 drivers, I would think they could backtrack, though backtracking may mean disabling enhancements that the new drivers provided, so that might not be a good thing either.

I sure hated the error when I had it and certainly hope they fix it for everyone.

[Lfctony]

Thats interesting, I would like to read up on that too. maybe someone might find a solution that would benefit both parties. Could you please provide some links to this, as I have tried Google and going to some ATI forums, but could not find anything.

http://www.repairyourpcnow.com/resources/atikmdag-has-stopped-responding.php

The file name I provided is wrong, sorry about that. Here:
http://www.google.com/search?hl=en&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=atikmdag.sys+has+stopped+responding&spell=1

[Mojoe]

I have had this problem with my old X1900XT, and i have no problem to provoke it on my 8800GTX neither. I just have to set to tight timings on my mem or clock them to high, and i get this problem even if its stabel in all tests, so my guess its a timing issue more than anything else.

[Lfctony]

I attempted to fix my problem by downclocking my system memory to 500mhz from 667, it worked fine for a couple of days then started to happen again. First time it was after an hour in World in Conflict, then it happened again almost instantly after I restarted. So I went back to WinXP. I can't believe I spent $250 on an operating system I can't even use... :(

[Fats_43]

hmmm I get this error every reboot now with new beta drivers 163.75 vista x64.

I've never had this error before :(

[LORD-eX-Bu]

welcome to hell :rofl

[mumstheword]

Wow. this error is relentless. However, after installing the 163.75 drivers, my computer doesn't turn all groggy and slow after the error anymore. This has happened so far in Crysis beta and WiC.

[Lfctony]

Wow. this error is relentless. However, after installing the 167.75 drivers, my computer doesn't turn all groggy and slow after the error anymore. This has happened so far in Crysis beta and WiC.

You mean the 163.75s right?

[mumstheword]

You mean the 163.75s right?

Yeah sorry.

[mumstheword]

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...

Hmm..I just played Crysis and WiC back to back. No problems so far. Anyone else try this?

By the way, I have an 8800gts 320mb, Q6600@3.0ghz and an ATI Xpress 1250 chipset.

[Fats_43]

hmmm fixed my issue by making sure all nvidia files were gone after un install then , re installed drivers from a fresh downloaded version.

Fixed error gone now . wonder what corrupts it.

[ZoLoco]

Tried the bcdedit sollutions, no friggin luck. My 'test' game World of Warcraft stopped after only 3 mins of play. Bam, the crappy error hitted like a smelly rat ass sock...

Guess i can drop my subscription there for a while. :thumbdwn:

All hotfixes installed, tried lesser ram, stock voltage, no OC of any kind, Driver cleaner, safe mode driver install, you name it , ive tried it all. Think i can stop looking for solutions on the net. They seem to only work on superbadasscraysuppedup computers only..... :( Not on my 4000 ass wasted euro system....

Sorry for the language, but this error wont ever be fixed it seems.......

Sigh...

[Fats_43]

arghhhh it's back.... I tried BCE edit nothin works hmmm maybe it's just this version as I've never had it before wierd.

[Lfctony]

I think if it does it once, it causes driver corruption causing subsequent crashes. People who got it once after a long time and now it won't go away, try cleaning your drivers in safe mode and putting new ones.

[Buckeye]

Yeah I did the uninstall driver, reboot in safe mode, driver cleaner thing and that fix'd several problems I was having.

I do not have much of a chance to game anymore so a lot of things just get pushed on the back burnner for me. Just work, work for me atm :)

But it does kind of bug me that Nvidia cannot get not responding issue sorted out, that did hit me a few times. But also why can't the driver installer or uninstall from the control pannel clear out all parts of the driver for us, so we don't have to play these games with driver cleaner etc.

[Fats_43]

Same wonder why we have to go to such extremes to remove a prior driver though :(

Never understood why driver makers can't seem to get a correct un install code.. oh well all fixed for now it seems .. knock on wood

[julesjt]

Well I tried the drivercleaner in safe mode and removed all drivers and folders associated and I still get the freaking error. What is the deal.

I have a MSI 8800 Ultra, 4gb Dominator Mem, quadcore core 2 duo.

I have every freaking hotfix and I installed the latest beta, maybe shouldnt of did the beta drivers but still getting the error.

When is Vista SP1 Beta coming out, it specifically states fixing high GPU issues.

I need to do something I can't play HL2 E2 more then ten minutes at a time.

And I am not going XP and losing DX10 the graphical difference in Crysis are too much for me to ignore DX10. I hate Microsoft!

[Buckeye]

I used both Driver Cleaner and Driver Sweeper from guru3d, it found files that DC did not.

rebooted in safe mode several times and ran both cleaners each time, it's funny how stuff gets missed the first time, go figure. All in all I did that about 4 times just to make sure. Also make sure that when you do boot into non safe mode to "not" let vista install it's default drivers.

[julesjt]

I did make sure all is cleaned and I made sure that Vista didnt install any drivers.

I dont know what else to do. How can they let this go on for this long.

[Dragunov]

I used both Driver Cleaner and Driver Sweeper from guru3d, it found files that DC did not.

rebooted in safe mode several times and ran both cleaners each time, it's funny how stuff gets missed the first time, go figure. All in all I did that about 4 times just to make sure. Also make sure that when you do boot into non safe mode to "not" let vista install it's default drivers.

I use both programs too

first uninstall driver, then reboot in safe mode, first run Driver Sweeper, then run Drivercleaner.net, then reboot, install driver