View Full Version : Nvlddmkm stopped responding is getting VERY OLD...
I just experienced two of these errors now. I installed the 158 drivers a couple of days ago and for some reason errors started to happen tonight as I'm booting into Windows. Never experienced it before now.
jabloomf1230
04-23-07, 12:21 AM
I just experienced two of these errors now. I installed the 158 drivers a couple of days ago and for some reason errors started to happen tonight as I'm booting into Windows. Never experienced it before now.
The most interesting aspect of this error is that with the default registry settings for the delays, if your game's frame rate slows to below 10 FPS, you may generate this error. Other than changing the registry settings (as explained in the MS article), you can also try reducing the load on the GPU to increase frame rates. Cutting the resolution is an obvious choice, but most games give you a variety of ways to improve frame rates.
The most interesting aspect of this error is that with the default registry settings for the delays, if your game's frame rate slows to below 10 FPS, you may generate this error. Other than changing the registry settings (as explained in the MS article), you can also try reducing the load on the GPU to increase frame rates. Cutting the resolution is an obvious choice, but most games give you a variety of ways to improve frame rates.
Mine was actually occuring during the period where Windows was loading (after logging in). It happened twice in a row last night during this period. I even played a game and did not experience the issue again.
However, I did a very small tweak that has so far worked. I raised the opacity of the Aero interface. It's still transparent, but not as much as it was before when I was experiencing the error (I forgot I lowered this value a couple of days ago). Since increasing the opacity, I have not experienced the error again during the Windows boot. Probably won't work for everyone but I'm just tossing out what my personal fix was.
After the registry tweak and the 158.19 driver, I have not had this error once since. I used Vista most of the weekend playing STALKER and updating various files and utilities in Vista and all was well. Hopefully things are looking up.
Blacklash
04-24-07, 02:23 AM
I got my first one of these today. :(
alkolkin
04-26-07, 05:08 PM
Believe it or not, I have fixed it on my Vista 32 bit. Just turn of UAC and everything works perfectly (at least it has for the last half hour.) NO more interruptions to the DirectX 10 demos, or to DreamScene content, or to videos.
My setup is as follows:
Asus Striker Extreme
PNY 8800 GTX Driver version 7.15.11.5818 - 158.15
2 GB Corsair Dominator memory
OC the CPU to 3.00 MHz
RAID 0
Creative X-Fi gamer
:captnkill:
Peoples-Agent
04-27-07, 10:37 AM
Believe it or not, I have fixed it on my Vista 32 bit. Just turn of UAC and everything works perfectly (at least it has for the last half hour.) NO more interruptions to the DirectX 10 demos, or to DreamScene content, or to videos.
My setup is as follows:
Asus Striker Extreme
PNY 8800 GTX Driver version 7.15.11.5818 - 158.15
2 GB Corsair Dominator memory
OC the CPU to 3.00 MHz
RAID 0
Creative X-Fi gamer
:captnkill:
Doesn't turning off UAC actually phuck Windows up in some way though?
i.e problems deleting files and stuff afterwards, even when trying to enable again.
I get this message everytime my PC boots up, but it fixes itself near enough instantly and can use PC without interuption, how strange.
Turning off UAC is fine, but it doesn't solve the problem.
Read here:
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
Can someone post the suggested values for this. Without that it isn't of much use.
Read here:
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
I don't see any of those keys in the registry...does that mean I have to enter them all in manually...or is there a REG file I can download to do it ?
I don't see any of those keys in the registry...does that mean I have to enter them all in manually...or is there a REG file I can download to do it ?
bump to that.
Since adding these registry keys I have not had this error reappear, and it was happening so often that I couldnt use my computer. You will have to manually add the two keys below.
In the following registry path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers
ADD:
TdrDdiDelay (REG_DWORD) 20
TdrDelay (REG_DWORD) 20
I didn't create this info but got the tip in an evga forum, and for me it seems to have done the trick. Hope this helps, but of course YMMV.
Since adding these registry keys I have not had this error reappear, and it was happening so often that I couldnt use my computer. You will have to manually add the two keys below.
In the following registry path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers
ADD:
TdrDdiDelay (REG_DWORD) 20
TdrDelay (REG_DWORD) 20
I didn't create this info but got the tip in an evga forum, and for me it seems to have done the trick. Hope this helps, but of course YMMV.
Is this 20 hex? 0x20? or 20 decimal
Is this 20 hex? 0x20? or 20 decimal Decimal is what I used.
Since adding these registry keys I have not had this error reappear, and it was happening so often that I couldnt use my computer. You will have to manually add the two keys below.
In the following registry path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers
ADD:
TdrDdiDelay (REG_DWORD) 20
TdrDelay (REG_DWORD) 20
I didn't create this info but got the tip in an evga forum, and for me it seems to have done the trick. Hope this helps, but of course YMMV.
It didn't work for me. It still crashes but now it just recovers more slowly. I think those keys just specify that "time out" period. So, if the cause of your errors are period where the frame rate drops down really low then increasing the time out period will help. But that's not the only cause of errors.
I found a long thread about this issue on nvidia forums. It's obvious that there are MULTIPLE CAUSES.
1. Overheating GPU (Fan not at 100%)
2. Burnt RAM
3. Unstable overclock
4. Unstable driver for that game/app
5. UAC
6. PSU power to vid card issues
If there are two causes of problems on your system then trying each solution in succession will never work. Let's say I have an unstable overclock AND driver version that often locks up with my favorite game. Well, if I undo the overclock I'll still have the error because of my unstable drivers but I may conclude that the overclock was not the cause of the problem. Later I may try new drivers but I'll still have the problem because of my unstable overclock and I'll conclude that it's not that drivers.
The key is to try to undo the overclock AND try different drivers. In other words if there are possibly multiple problems causing the same errors you have to try multiple solutions simultaneously.
Slammin
05-23-07, 11:12 AM
MowTin,
I think you are absolutely correct. I have noticed that more than one thing can cause the problem as well. Right now, I'm experimenting with bios voltage setting for my SB. So far, it looks like when I do have the problem, increasing SB voltage decreases the frequency of the problem, or shortens the duration of the freeze ups. If this doesn't pan out, I'll go play with my NB voltage settings, but so far, I am able to observe a definite reaction when playing with SB voltage.
Logical
05-24-07, 12:35 AM
I found a long thread about this issue on nvidia forums. It's obvious that there are MULTIPLE CAUSES.
1. Overheating GPU (Fan not at 100%)
2. Burnt RAM
3. Unstable overclock
4. Unstable driver for that game/app
5. UAC
6. PSU power to vid card issues
If there are two causes of problems on your system then trying each solution in succession will never work. Let's say I have an unstable overclock AND driver version that often locks up with my favorite game. Well, if I undo the overclock I'll still have the error because of my unstable drivers but I may conclude that the overclock was not the cause of the problem. Later I may try new drivers but I'll still have the problem because of my unstable overclock and I'll conclude that it's not that drivers.
The key is to try to undo the overclock AND try different drivers. In other words if there are possibly multiple problems causing the same errors you have to try multiple solutions simultaneously.
I think that there are different causes that are leading to the same error. In some cases it has been a driver issue or a graphics card issue in others it seems that it is memory related.
I first got this error a few days ago after having my system run shweet for the last 2 month and thought it might have been a problem with the mcp - spp bus but was wrong as i have since changed my motherboard and still i get the error. It occurs mostly when i am playing games sometimes from system boot up it can take upto 2 hours before i get the error but once i do get it, i cannot play a game or run a demo without getting the error again almost immediantly, and so i have to power off for at least a minute and then again after 20 mins - 2 hours gameplay i get it again.
I have disabled sli memory in bios and now have it running at 800mhz at 1.85 v and noticed the PCI-E bus speed went down to 1.2v from 1.4 and so far it seems ok (needs more game testing)....if this fails i will install xp and see if i can recreate the error on there.
Also may i add that brother has an identical system to me except he has the corsair 800mhz dominator ram and he has never seen this error yet, hmmmmm.........
Will let you know how i get on....
TrixTeH,
Some people have heat issues that didn't exist during the winter. Has it been hotter lately than the past 2 months when you were running smooth?
The fact that your errors seem to come after playing for some time suggests a heat issue. Maybe that's why after letting it cool off it works fine for another two hours.
What's your high load temp?
Logical
05-24-07, 12:37 PM
No its not an heat issue in my case m8. I keep an eye on temps and tbh they have hardly ever changed since ive had the system......
Idle CPU = 44 degree c
Idle GPU = 57 degree c
Idle system temp = 29 degree c
Under load cpu = 53 degree c
GPU = 67 degree c
system temp = 33 degree c
My temps are pretty low compared to what ive seen from systems with a similar spec.
TBH turning my pc off for a min points me in the direction that it is RAM related......still gotta test it out at 800mhz though.
If i still get the error at 800mhz and the lower voltages im gonna run memtest for a few hours...
Logical
05-24-07, 11:50 PM
Ok after having my system underload all day, I haven't had 1 error with the memory set to 800mhz at 1.85v and the pci-e bus at 1.2v.
I am going to run memtest all night with the memory at 1067mhz and the voltages back up....if i get errors then im exchanging my memory for some 800mhz dominator as i dont see the point in me paying extra for something i cant use...imo the memory controller on the 680i board is phucked.....
Slammin
05-25-07, 11:35 AM
I've also noticed that if I set my bios strap to 1333, the error is relentless!
Logical
05-25-07, 01:09 PM
Ran memtest all night for 9 hours at 1067 mhz at 2.2v and the PCI-e at 1.4v and the test came back with zero errors.....
Im very confused and i have a theory that the EPP's on the Dominator ram arent doing there job.
Ive set the memory back to 1067 with the voltages back up....if i get the error now then its definately time to change RAM.......
Logical
05-25-07, 05:54 PM
As soon as i ran a game at 1067 mhz @ 2.2v and the PCI-e bus at 1.4 i am getting the error....
Tomorrow i will change the ram to 800mhz dominator, which will run faster than my current c5d mem because of the lower timings.
Dropping my cpu OC and reseting all bios setting back to default cleared this up for me (knock on wood).
It sucks that I can't OC because of this.
ikjadoon
05-29-07, 12:18 AM
Dropping my cpu OC and reseting all bios setting back to default cleared this up for me (knock on wood).
It sucks that I can't OC because of this.
I think this error has multiple causes, but many, I believe, are on the driver-side. There are people who have stock systems with this problem, etc..
~Ibrahim~
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.