BSOD 116 TDR - GTX 480 W7 x64
  1 / 2    
Could use some ideas here , I’ve already read just about all the articles I could find on 116 TDR BSOD.

I had a 8800 GTS that started to go bad, monitor would get skewed colors in Windows (at first I thought it was drivers), but then I noticed even at bios logo, the colors would be all messed up, to me this said hardware problem. So I opted to replace the card and got a GTX 480

Since installing the new GTX 480, I have been plagued with BSOD 116, alwyas one of the these scenarios
1)Random - Will be doing nothing except running sufing, have a few VM's running
2)Overnight - Arrive at the machine in the AM and the monitors will not wake up.

The only progress I could make was by going to the beta 301.24 (This seemed to stop the overnight BSOD) - but the random ones would still persist. When these do occur, I don’t even see the BSOD, the monitors just go black, most of the time required hard power cycle

I've tried rolling back drivers to: 296.10, 295.73, 266.58 etc..

This morning running on 266.58 (as expected) monitors would not wake up and there was a kernel dump time stamped right about the time I tried to wake it up.

I am trying to see if I have an issue with the PCI-E slot, or power problem, drivers, some contention between other app. I've been collecting full kernel dumps, I have not had time to really go through them yet though.

Machine Specs:
Machine is a Dell Precision 690
W7 Ultimate x64
1KW PSU
Dual Xeon X5355 quad-core
16gb Ram
LSI-9260-8i Raid Controller with: (2 Intel 160 SSD in R0, 2 WD Green 2TB in R1, 2 WD Raptor 10k 150gb in R1)
PCI Sil 3132 SATALnk eSTAT adapter - Connected to Thermaltake BlackX Duet - Externally powered
2 – Dell E248WFP


Standard WinDBG Generic Report on the 266.58 drivers

BugCheck 116, {fffffa801753f160, fffff8800fe1023c, ffffffffc000009a, 4}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -
Probably caused by : nvlddmkm.sys ( nvlddmkm+7b723c )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa801753f160, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fe1023c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP:
nvlddmkm+7b723c
fffff880`0fe1023c 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02c90b88 fffff880`10313000 : 00000000`00000116 fffffa80`1753f160 fffff880`0fe1023c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02c90b90 fffff880`102e6867 : fffff880`0fe1023c fffffa80`1311d000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02c90bd0 fffff880`10312e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`1753f160 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02c90c80 fffff880`103e1ec1 : fffffa80`13382870 00000000`00000080 00000000`00000000 fffffa80`12dfe010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02c90d00 fffff800`03b19e6a : 00000000`0645a009 fffffa80`13136060 fffffa80`0ca9b840 fffffa80`13136060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02c90d40 fffff800`03873f06 : fffff800`039f5e80 fffffa80`13136060 fffff800`03a03cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02c90d80 00000000`00000000 : fffff880`02c91000 fffff880`02c8b000 fffff880`02c90630 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+7b723c
fffff880`0fe1023c 4883ec28 sub rsp,28h

SYMBOL_NAME: nvlddmkm+7b723c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

7: kd> lmvm nvlddmkm
start end module name
fffff880`0f659000 fffff880`102b3d00 nvlddmkm (export symbols) nvlddmkm.sys
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Fri Jan 07 21:07:22 2011 (4D27C6DA)
CheckSum: 00C5F2DA
ImageSize: 00C5AD00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Could use some ideas here , I’ve already read just about all the articles I could find on 116 TDR BSOD.



I had a 8800 GTS that started to go bad, monitor would get skewed colors in Windows (at first I thought it was drivers), but then I noticed even at bios logo, the colors would be all messed up, to me this said hardware problem. So I opted to replace the card and got a GTX 480



Since installing the new GTX 480, I have been plagued with BSOD 116, alwyas one of the these scenarios

1)Random - Will be doing nothing except running sufing, have a few VM's running

2)Overnight - Arrive at the machine in the AM and the monitors will not wake up.



The only progress I could make was by going to the beta 301.24 (This seemed to stop the overnight BSOD) - but the random ones would still persist. When these do occur, I don’t even see the BSOD, the monitors just go black, most of the time required hard power cycle



I've tried rolling back drivers to: 296.10, 295.73, 266.58 etc..



This morning running on 266.58 (as expected) monitors would not wake up and there was a kernel dump time stamped right about the time I tried to wake it up.



I am trying to see if I have an issue with the PCI-E slot, or power problem, drivers, some contention between other app. I've been collecting full kernel dumps, I have not had time to really go through them yet though.



Machine Specs:

Machine is a Dell Precision 690

W7 Ultimate x64

1KW PSU

Dual Xeon X5355 quad-core

16gb Ram

LSI-9260-8i Raid Controller with: (2 Intel 160 SSD in R0, 2 WD Green 2TB in R1, 2 WD Raptor 10k 150gb in R1)

PCI Sil 3132 SATALnk eSTAT adapter - Connected to Thermaltake BlackX Duet - Externally powered

2 – Dell E248WFP





Standard WinDBG Generic Report on the 266.58 drivers



BugCheck 116, {fffffa801753f160, fffff8800fe1023c, ffffffffc000009a, 4}



*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -

Probably caused by : nvlddmkm.sys ( nvlddmkm+7b723c )



Followup: MachineOwner

---------



7: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: fffffa801753f160, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800fe1023c, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.



Debugging Details:

------------------





FAULTING_IP:

nvlddmkm+7b723c

fffff880`0fe1023c 4883ec28 sub rsp,28h



DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT



BUGCHECK_STR: 0x116



PROCESS_NAME: System



CURRENT_IRQL: 0



STACK_TEXT:

fffff880`02c90b88 fffff880`10313000 : 00000000`00000116 fffffa80`1753f160 fffff880`0fe1023c ffffffff`c000009a : nt!KeBugCheckEx

fffff880`02c90b90 fffff880`102e6867 : fffff880`0fe1023c fffffa80`1311d000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec

fffff880`02c90bd0 fffff880`10312e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`1753f160 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3

fffff880`02c90c80 fffff880`103e1ec1 : fffffa80`13382870 00000000`00000080 00000000`00000000 fffffa80`12dfe010 : dxgkrnl!TdrResetFromTimeout+0x23

fffff880`02c90d00 fffff800`03b19e6a : 00000000`0645a009 fffffa80`13136060 fffffa80`0ca9b840 fffffa80`13136060 : dxgmms1!VidSchiWorkerThread+0x101

fffff880`02c90d40 fffff800`03873f06 : fffff800`039f5e80 fffffa80`13136060 fffff800`03a03cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`02c90d80 00000000`00000000 : fffff880`02c91000 fffff880`02c8b000 fffff880`02c90630 00000000`00000000 : nt!KxStartSystemThread+0x16





STACK_COMMAND: .bugcheck ; kb



FOLLOWUP_IP:

nvlddmkm+7b723c

fffff880`0fe1023c 4883ec28 sub rsp,28h



SYMBOL_NAME: nvlddmkm+7b723c



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nvlddmkm



IMAGE_NAME: nvlddmkm.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da



FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys



BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys



Followup: MachineOwner

---------



7: kd> lmvm nvlddmkm

start end module name

fffff880`0f659000 fffff880`102b3d00 nvlddmkm (export symbols) nvlddmkm.sys

Loaded symbol image file: nvlddmkm.sys

Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys

Image name: nvlddmkm.sys

Timestamp: Fri Jan 07 21:07:22 2011 (4D27C6DA)

CheckSum: 00C5F2DA

ImageSize: 00C5AD00

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

#1
Posted 05/09/2012 12:40 PM   
Try nvidia Inspector to force 3D clocks all the time.

Shortcut:
inspector.exe -forcePState:0,0

If it solves the problem you can put this shortcut in Windows startup folder.
Try nvidia Inspector to force 3D clocks all the time.



Shortcut:

inspector.exe -forcePState:0,0



If it solves the problem you can put this shortcut in Windows startup folder.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#2
Posted 05/09/2012 01:16 PM   
[quote name='nvtweakman' date='09 May 2012 - 01:16 PM' timestamp='1336569371' post='1406010']
Try nvidia Inspector to force 3D clocks all the time.

Shortcut:
inspector.exe -forcePState:0,0

If it solves the problem you can put this shortcut in Windows startup folder.
[/quote]


What will this actually accomplish, or help rule out?

Also how would I revert it back, and do I need to update the drivers, or should I leave them at the current 266.58 level?
[quote name='nvtweakman' date='09 May 2012 - 01:16 PM' timestamp='1336569371' post='1406010']

Try nvidia Inspector to force 3D clocks all the time.



Shortcut:

inspector.exe -forcePState:0,0



If it solves the problem you can put this shortcut in Windows startup folder.







What will this actually accomplish, or help rule out?



Also how would I revert it back, and do I need to update the drivers, or should I leave them at the current 266.58 level?

#3
Posted 05/09/2012 01:52 PM   
It causes graphics card to hold a more stable voltage. I would probably try drivers 275.33
It causes graphics card to hold a more stable voltage. I would probably try drivers 275.33

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#4
Posted 05/09/2012 02:47 PM   
The NVIDA installer always fails, so I cant use the "Clean Option" - Does it make a difference if I just update the drivers from Device Manager?
The NVIDA installer always fails, so I cant use the "Clean Option" - Does it make a difference if I just update the drivers from Device Manager?

#5
Posted 05/09/2012 02:51 PM   
Device manager method works half-ass, and is unsupported.

Install failed can usually be solved by removing all nvidia drivers/software/folders and reinstall. You don't have to use clean install, but it is preferrable since you've had so many different versions cluttering up the system.
Device manager method works half-ass, and is unsupported.



Install failed can usually be solved by removing all nvidia drivers/software/folders and reinstall. You don't have to use clean install, but it is preferrable since you've had so many different versions cluttering up the system.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#6
Posted 05/09/2012 03:10 PM   
Unreal what I had to do in order to get the Installer to work. Following what shady did here: http://forums.nvidia.com/index.php?showtopic=201821&st=60&p=1246145&#entry1246145

"Copy the two files from 270.61's DisplayControlPanel to 275.33's DisplayControlPanel. Overwrite."

This was the only way to get the 275.33 (or really any) installer to finish.

I know this is an old release, and it also appears the NVIDIA Control Panel is not installed, but I just want to start to eliminate some of the potential culprits of the 116 TDR BSOD's

I ran nvidiaInspector.exe -forcePState:0,0

Is 275.33 a more stable version? Let me know what you think about upgrading and which release I should be targeting.

[img]http://img854.imageshack.us/img854/2488/20120509155351.png[/img]
Unreal what I had to do in order to get the Installer to work. Following what shady did here: http://forums.nvidia.com/index.php?showtopic=201821&st=60&p=1246145&#entry1246145



"Copy the two files from 270.61's DisplayControlPanel to 275.33's DisplayControlPanel. Overwrite."



This was the only way to get the 275.33 (or really any) installer to finish.



I know this is an old release, and it also appears the NVIDIA Control Panel is not installed, but I just want to start to eliminate some of the potential culprits of the 116 TDR BSOD's



I ran nvidiaInspector.exe -forcePState:0,0



Is 275.33 a more stable version? Let me know what you think about upgrading and which release I should be targeting.



Image

#7
Posted 05/09/2012 07:57 PM   
Typically need to rename the %program files%\nvidia corporation folder when the installer trips up on it.

275.33 is the driver everyone fell back on when they experienced TDRs with r280 and higher.
Typically need to rename the %program files%\nvidia corporation folder when the installer trips up on it.



275.33 is the driver everyone fell back on when they experienced TDRs with r280 and higher.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#8
Posted 05/10/2012 12:06 AM   
[quote name='nvtweakman' date='10 May 2012 - 12:06 AM' timestamp='1336608418' post='1406260']
Typically need to rename the %program files%\nvidia corporation folder when the installer trips up on it.

275.33 is the driver everyone fell back on when they experienced TDRs with r280 and higher.
[/quote]


I removed the entire folder, and even after that, running 275.33, I am still getting 116 TDR's.

Only other thing I recently changed was a version of VM Workstaion which I just downgraded back to what it was before.

Any other apps or drivers I should be looking into?
[quote name='nvtweakman' date='10 May 2012 - 12:06 AM' timestamp='1336608418' post='1406260']

Typically need to rename the %program files%\nvidia corporation folder when the installer trips up on it.



275.33 is the driver everyone fell back on when they experienced TDRs with r280 and higher.







I removed the entire folder, and even after that, running 275.33, I am still getting 116 TDR's.



Only other thing I recently changed was a version of VM Workstaion which I just downgraded back to what it was before.



Any other apps or drivers I should be looking into?

#9
Posted 05/10/2012 12:13 AM   
Here is the best topic on troubleshooting TDRs;
http://forums.nvidia.com/index.php?showtopic=100800

As you will learn, potential causes of TDR are anything from software/driver conflicts to defective hardware.
Here is the best topic on troubleshooting TDRs;

http://forums.nvidia.com/index.php?showtopic=100800



As you will learn, potential causes of TDR are anything from software/driver conflicts to defective hardware.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#10
Posted 05/10/2012 02:42 PM   
i had this problem to with my gtx 460,i tought it was a hardware error or something,but it was the windows,or an update and i've installed an old version of windows 7 x64 ,and turned off windows updates,now i have no problems,with the 275.33 driver.i hope it helps you,sorry for my spelling.
i had this problem to with my gtx 460,i tought it was a hardware error or something,but it was the windows,or an update and i've installed an old version of windows 7 x64 ,and turned off windows updates,now i have no problems,with the 275.33 driver.i hope it helps you,sorry for my spelling.

#11
Posted 05/10/2012 03:01 PM   
faulty memory, unstable chipset, bad power supply.


all of these can cause tdr's.
faulty memory, unstable chipset, bad power supply.





all of these can cause tdr's.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

CPU:Intel i7 920 @ 3.8(D0), Mainboard:Asus Rampage II Gene, Memory:12GB Corsair Vengeance 1600
Video:EVGA Geforce GTX 680+ 4GB, Sound:Creative XFI Titanium Fatal1ty Pro, Monitor:BenQ G2400WD
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1

#12
Posted 05/11/2012 12:52 AM   
Latest update is I restore entire system using Ghost to about 1 month ago, I was able to run a clean install of 275.33.

I am not installing EVGA precisionX or any utilities, so far during the day, no TDR or BSOD.

Tomorrow morning will be interesting because its usually when I try to use the system in the morning the screens are black and the card wont post, required hard reboot.

Strange - but this is almost the type of condition that I am getting. But the card is only 1 week old.
http://forums.nvidia.com/index.php?showtopic=223441
Latest update is I restore entire system using Ghost to about 1 month ago, I was able to run a clean install of 275.33.



I am not installing EVGA precisionX or any utilities, so far during the day, no TDR or BSOD.



Tomorrow morning will be interesting because its usually when I try to use the system in the morning the screens are black and the card wont post, required hard reboot.



Strange - but this is almost the type of condition that I am getting. But the card is only 1 week old.

http://forums.nvidia.com/index.php?showtopic=223441

#13
Posted 05/13/2012 05:14 AM   
No TDR, system was fine this morning, I guess only time will tell though.

I will not be changing from 275.33 or installing anything like EVGA PrecisionX etc.

I suppose this could have been W7 corruption.
No TDR, system was fine this morning, I guess only time will tell though.



I will not be changing from 275.33 or installing anything like EVGA PrecisionX etc.



I suppose this could have been W7 corruption.

#14
Posted 05/13/2012 05:56 PM   
This may sound dumb, but try re-seating your card if you haven't already. Some of the folks that experienced frequent TDR's have found that they had a bad connection with the PCIe slot. Worth a shot anyway.
This may sound dumb, but try re-seating your card if you haven't already. Some of the folks that experienced frequent TDR's have found that they had a bad connection with the PCIe slot. Worth a shot anyway.

EVGA E758 A1 X58 // Core i7 920@4Ghz // OCZ Platinum DDR3 1600 // EVGA GTX 670 SLI // Seasonic X Series Gold 1050w // Corsair 800D // Dual Dell Ultrasharp U2410 displays // Dell Ultrasharp 2408WFP

#15
Posted 05/14/2012 08:20 PM   
  1 / 2    
Scroll To Top