- Joined
- Feb 21, 2009
- Location
- Arkansas
OK,
I’ve found a correct solution to the nvlddmkm.sys 116 (The TDR error)
(at least for my specific hardware setup)
The nvlddmkm.sys 116 error is the Timeout Detection and Recovery function.
It is a feature of the DirectX graphics kernel subsystem (dxgkrnl.sys)
The symptoms of the error I was getting are the following…
While playing a game, the card would stop responding and either exit with
A BSOD and reboot, or it would crash to the desktop showing the nvlddmkm.sys 116 error as the reason. I tried everything, I even did an RMA on my card and it still
would do this !
How I correctly fixed mine. Here are my system specs.
*----------------------------
Vista x32 Ultimate SP1
ASUS P6T Deluxe OC Palm Edition MB
Intel i7-920 Quad Core CPU
6gb Corsair XMS PC1066 DDR3 1333MHz (6x1024) RAM (all installed))
BFG GeForce GTX 285 OC2 1GB PCIe w/Dual Link DVI VIDEO
Antec TruePower Quattro 850Watt ...(Yellow racing strips
)
Seagate Barracuda 160gb 7200 RPM SATA HD
*----------------------------
The Fix, I did this.
1) Downloaded nVidia nTune and installed it.
2) Select the Adjust GPU Settings under the Performance area.
PLEASE NOTE: I have a single GTX 285 OC2 card, your adjustments
may be different for a different card type.
3) Change “GPU clock settings:” to “Custom clock frequencies”
4) Set Core bus: = 605mhz
5) Set Memory bus: = 1007 mhz
6) ACCEPT the changes
Now, the following may not be required, but I did it on my system
Because if I ever do get the error it helps my system recover better.
Under HKLM/system/CurrentControlSet/Control/GraphicsDriver/DCI
Set and/or create the following as needed.
TdrDdiDelay = 14 (Hex)
TdrDelay = 14 (Hex)
Timeout = 14 (Hex)
As I said, you may not need these at all ! But they helped me.
Make sure you check these settings in nTune before playing each game
as it switches them back to the bad values on my system after a reboot.
That’s it ! 100% fixed.
It looks like this 285 card is factory overclocked to high, and is unstable out of the box!
I’ve only tested this on my specific hardware, it works for me, I hope it will
work for you.
I have also updated the Sticky on this issue.
Good Luck !
Areal Person
I’ve found a correct solution to the nvlddmkm.sys 116 (The TDR error)
(at least for my specific hardware setup)
The nvlddmkm.sys 116 error is the Timeout Detection and Recovery function.
It is a feature of the DirectX graphics kernel subsystem (dxgkrnl.sys)
The symptoms of the error I was getting are the following…
While playing a game, the card would stop responding and either exit with
A BSOD and reboot, or it would crash to the desktop showing the nvlddmkm.sys 116 error as the reason. I tried everything, I even did an RMA on my card and it still
would do this !
How I correctly fixed mine. Here are my system specs.
*----------------------------
Vista x32 Ultimate SP1
ASUS P6T Deluxe OC Palm Edition MB
Intel i7-920 Quad Core CPU
6gb Corsair XMS PC1066 DDR3 1333MHz (6x1024) RAM (all installed))
BFG GeForce GTX 285 OC2 1GB PCIe w/Dual Link DVI VIDEO
Antec TruePower Quattro 850Watt ...(Yellow racing strips
)Seagate Barracuda 160gb 7200 RPM SATA HD
*----------------------------
The Fix, I did this.
1) Downloaded nVidia nTune and installed it.
2) Select the Adjust GPU Settings under the Performance area.
PLEASE NOTE: I have a single GTX 285 OC2 card, your adjustments
may be different for a different card type.
3) Change “GPU clock settings:” to “Custom clock frequencies”
4) Set Core bus: = 605mhz
5) Set Memory bus: = 1007 mhz
6) ACCEPT the changes
Now, the following may not be required, but I did it on my system
Because if I ever do get the error it helps my system recover better.
Under HKLM/system/CurrentControlSet/Control/GraphicsDriver/DCI
Set and/or create the following as needed.
TdrDdiDelay = 14 (Hex)
TdrDelay = 14 (Hex)
Timeout = 14 (Hex)
As I said, you may not need these at all ! But they helped me.
Make sure you check these settings in nTune before playing each game
as it switches them back to the bad values on my system after a reboot.
That’s it ! 100% fixed.
It looks like this 285 card is factory overclocked to high, and is unstable out of the box!
I’ve only tested this on my specific hardware, it works for me, I hope it will
work for you.
I have also updated the Sticky on this issue.
Good Luck !
Areal Person
