View Full Version : Nvlddmkm stopped responding is getting VERY OLD...
Wow...yesterday I got this error again but it was visible only in the Event Viewer (the system black-screened for a moment, then was unusably sluggish until reboot). It showed as 183 individual, simultaneous error incidents. Damn this error!!!!
Logical
05-29-07, 05:32 PM
Im now running dominator c4d 800mhz ram without any problems.....
I honestly think the memory controller on the 680i boards are shizzle.....:thumbdwn:
ikjadoon
05-29-07, 07:48 PM
Im now running dominator c4d 800mhz ram without any problems.....
I honestly think the memory controller on the 680i boards are shizzle.....:thumbdwn:
I find that it will start after the computer hibernates or goes to sleep. After I "wake" it up, the error comes with a fury. A simple restart will keep me problem-free!
~Ibrahim~
Nightly shutdowns have been my routine with great success....this past wknd tho it stayed on a few days--and the problems started again. Today, no issues after being shutdown last night.
ikjadoon
05-30-07, 10:50 AM
Nightly shutdowns have been my routine with great success....this past wknd tho it stayed on a few days--and the problems started again. Today, no issues after being shutdown last night.
Yup! My problems only start to happen later in the day, but I don't always shutdown at night. What kind of problem does that?
I want to say it is some type of memory issue...
~Ibrahim~
Possible, but hard to prove with its inconsistency. I just installed a cheap auto-shutdown pgm to shutoff the system at 1am, and set my BIOS sleep timer to restart the system at 4am. A band-aid for sure, but takes some of the 'brain' out of it for me.
ikjadoon
05-30-07, 11:24 AM
Possible, but hard to prove with its inconsistency. I just installed a cheap auto-shutdown pgm to shutoff the system at 1am, and set my BIOS sleep timer to restart the system at 4am. A band-aid for sure, but takes some of the 'brain' out of it for me.
Not a bad idea! I might have to try it out!
~Ibrahim~
ikjadoon
05-30-07, 11:57 AM
Did you guys see this:
NVIDIA statement on TDR Error Messages
Some Windows Vista users have reported that their systems are displaying an error message that says: "Display driver stopped responding, but has successfully recovered." This is called a Timeout Detection and Recovery error message.
Timeout Detection and Recovery (TDR) is a new feature of Windows Vista that attempts to detect problematic situations and recover to a functional desktop without forcing a reboot. Hangs can occur when the GPU is processing intensive graphics operations, typically during gameplay, and nothing is being updated on the monitor. To the user it appears that the system is frozen with no resolution to the problem; in previous operating systems users generally had to wait a few seconds and then reboot.
The TDR error message "Display driver stopped responding and has recovered" lets the user know that the NVIDIA display driver (specifically the "nvlddmkm.sys" file) has been re-initialized and the GPU is reset without requiring a reboot. The only visible artifact from the recovery is a screen flicker, the result of a screen redraw. Note that some older Microsoft DirectX applications may render to a black screen at the end of the TDR, requiring the user to restart these applications.
TDRs are not specific to a single driver problem, and can occur for a variety of reasons. When they occur, diagnostic information is collected in the form of a debug report that is sent to Microsoft through the Online Crash Analysis (OCA) mechanism if the user opts to provide feedback.
NVIDIA encourages users to submit their own bug reports via the NVIDIA Vista Quality Assurance Program, using the keyword "TDR" in the description of the problem. The NVIDIA bug report link is here:
https://surveys.nvidia.com/index.jsp?pi=749...8f09e040b4a437a
We understand that many users have expressed frustration with this issue, and we apologize for the inconvenience. Since the NVIDIA v101.41 beta driver release, NVIDIA has been fixing many TDR issues reported by users. Our software team is currently preparing a new driver which will dramatically reduce the number of TDR errors that users have reported on the forums. Thank you for your patience.
More information on TDRs can be found here:
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
.
Found this on nVidia's forums....
Yeah I saw that several weeks ago. I implemented registry changes noted in the MS link, but all that does (I think) is delay the OS's response to the nvlddmkm error...it helps sometimes.
it's interesting if it turns out to be a 680i only issue. I get this issue on my p5n32-e SLI plus and I just got my p5k deluxe and I will be setting it up in the next few days and I'll see if goes away or not.
Slagathor
06-02-07, 10:35 PM
158.45 Beta drivers cause all my games to crash with this error.
Before with the 160's it was just BF2142......
Vapor Trail
06-03-07, 05:25 AM
I get these errors sometimes too.
With BF2142 i actually got a few blue screen crashes (Vista even rebooted). I finally figured out that BF2142 doesn't like 8xQ AA. I created a game profile for BF2142 and set it 4x AA and it hasn't crashed since.... well other than the occasional crash between levels.
$n][pErMan
06-03-07, 01:43 PM
I have never had this error.... untill yesterday playing BF2142 on the 158.45 driver set. I had been using the 100.65's flawlessly without error for months on end without issues. Hopefully it was an isolated error for me, if not it looks like I will be going back (once again) to my trusty 100.65's :(
ikjadoon
06-03-07, 03:15 PM
I get these errors sometimes too.
With BF2142 i actually got a few blue screen crashes (Vista even rebooted). I finally figured out that BF2142 doesn't like 8xQ AA. I created a game profile for BF2142 and set it 4x AA and it hasn't crashed since.... well other than the occasional crash between levels.
You get that, too?!? Are you running 64-bit or 32-bit Ultimate? I get that on BF2 constantly...
Yeah, I've set mine to 8xQ, as well. Thanks for the tip, I'll see if it works!
It CANNOT be a 680i-isolated issue: I have a 650i and it happens constantly. Might be a nForce 6-series issue, however. Or maybe a GPU one, like it is highly speculated to be.
~Ibrahim~
Vapor Trail
06-03-07, 07:07 PM
You get that, too?!? Are you running 64-bit or 32-bit Ultimate? I get that on BF2 constantly...~
32 bit
Yeah, I've set mine to 8xQ, as well. Thanks for the tip, I'll see if it works!
no problem
It CANNOT be a 680i-isolated issue: I have a 650i and it happens constantly. Might be a nForce 6-series issue, however. Or maybe a GPU one, like it is highly speculated to be.
~Ibrahim~
No 680i here and I get Nvlddmkm Stopped responding errors often.
I must say that the 7900GT I had before seems much more stable than the 8800GTS I have now. :(
terror_adagio
06-08-07, 12:55 PM
I can't see how this problem is due to overclocking. With my specs below, I never had this problem with XP. It only started happening when I got Vista installed. And nothing is overclocked.
I've tried: 98.09, 101.70, 158.18, 158.43, 158,45 and games are still crashing.
DarkJedi664
06-08-07, 02:51 PM
It's not a 680i chipset problem as it happens to me STILL on nForce4! And it's not during games, it's on the DESKTOP!!! F#$(ing annoying!
OrangeBlast
06-08-07, 05:55 PM
perhaps we need to make this a sticky.
I never thought this thread would get this big. lol!
ikjadoon
06-08-07, 06:08 PM
perhaps we need to make this a sticky.
I never thought this thread would get this big. lol!
Sticky would be nice, but we also need a list of possible solutions..
~Ibrahim~
I tried to start a 'fix' thread but it got buried...I just bumped it in case anyone wants to try using it.
http://www.nvnews.net/vbulletin/showthread.php?t=90093&highlight=nvlddmkm+fix
Slammin
06-08-07, 08:28 PM
I guess between doing the reg fix, driver, and OC settings, I must have found the magic bullet because I haven't seen this for weeks now.
ikjadoon
06-09-07, 11:35 AM
I tried to start a 'fix' thread but it got buried...I just bumped it in case anyone wants to try using it.
http://www.nvnews.net/vbulletin/showthread.php?t=90093&highlight=nvlddmkm+fix
Nice.I wish that thread developed some more or at least got stickied.
~Ibrahim~
Slagathor
06-13-07, 10:59 PM
Running 158.45 still with no joy, 2142 still dies a painful death......
It's funny, Oblivon runs great, full bore, all eye candy maxed, as do most all my games, cept for EA games, I still think it's DICE/EA thats causing 90% of the problems.....
ikjadoon
06-13-07, 11:27 PM
Running 158.45 still with no joy, 2142 still dies a painful death......
It's funny, Oblivon runs great, full bore, all eye candy maxed, as do most all my games, cept for EA games, I still think it's DICE/EA thats causing 90% of the problems.....
QFTFT!
BF2 crashes daily and BF2142 won't even bloody start! EA is really starting to piss me off.:thumbdwn:
FEAR, 3DMark'06, all the rest run as smooth as butter.
~Ibrahim~
mRYellow
06-15-07, 04:53 AM
BF2 and BF2142 FIX!
For all u guys getting errors pls check this post...PB and Rivatuner (aswell as ATi Tool) clash.
For more info:
http://forums.guru3d.com/showthread.php?t=226934
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.