BSOD 116 TDR error (attached minidumps) HELP!

Guru's, I'm in need of some serious help! I am having very frequent BSOD's (specifically 116 TDR errors) whilst playing games & only when playing games. These vary from loading up the game (to be specific not the opening sequences or menu but the actual game) 1 second in or 10 minutes in.

I have created a thread on the Windows Seven Forums but there seem to be A LOT of unsolved threads and responses from the guys on there seem to be slow.

Link below is for my drop box which contains a zip with all my minidumps and .txt files for information.

https://www.dropbox.com/s/wm9ypf0rnaik7c0/HOME-PC-25_11_2015_223810_29.zip?dl=0

My systems specs to the left are up to date.

Things I have tried
Several different driver versions (clean installations). Only PhysX and main GPU driver installed.
Update all component drivers
Disabling SLI (this does seem to make the crashes less frequent but BSOD still happen)
GPU's in different PCIe slots
Replaced the motherboard!
use 1 stick of ram, swap out and use the other stick of ram
sfc /scannow found no issues
check the SSD for errors
Fresh install of windows 7
Malwarebytes scan found no malware/issues


Things on my list to try
Memtest
Furmark
Update mobo BIOS (although I'm sure this is up to date as mb only installed last week and drivers were taken from MSI website)
Test PSU (don't have a multi meter?). Possible swap PSU out for another.
Driver verifier (although I have manual checked in device manager for updates)
Underclock my GPU's?

I currently have reset CPU clock to stock, was at 4ghz and stable for a year+. GPU's are not overclocked but have been previously for a year+ and were always stable.
Card temps idle at 28c. Under load top out at 60c.
CPU temps idle at 35c. Tops out at 60c.

Just for further info these BSOD's stared randomly I cannot remember updated or adding any software before they started (apart from a gsync monitor about a week before). They are BLACK screens not blue with text. The sound loops and I have to hard restart my system manually. Also upon replacing my motherboard I had non of these BSOD's for 5 days before they started again. I'm sure you can imagine my disappointment...

That's all I got.... if anyone can help I will be forever thank full because short of seeking some professional help and trying the remaining things I have listed I'm at a loose end.

 

I'd update the mobo bios and swap out the PSU for starters.

 

What is going on more than likely is your fan on your PSU is not ramping up and the PSU is powering off to keep from over heating. I ran into a similar problem a little over a year ago with an SLI set up with my PSU set to hybrid fan function.

So, if you have your PSU set to hybrid, set it to normal. Even in normal it will be silent, so noise won't be an issue. If you are fortunate like me, that it is all it is.

 

Thanks, I'll look at the mb bios tonight. All case and GPU fans/LED's stay on with the crash. Which makes me think it isn't the PSU?

 

Sorry Sota I didn't see your reply before posting. How do I set my PSU to normal/hybrid?

 

To be honest...I am not sure. My Seasonic has a switch on the upper right corner to switch between normal and hybrid. If you have the C-Link attached, look in the software and see if you can find a way to cut the fan to a normal fan curve.

Those PSU's fans don't spin until 40% usage by default. Sounds like a very similar issue I had, only I am not sure where to direct you to with that particular PSU...though the issue should be alleviated if you can enable it in the provided software. If there is not a way, then I would suggest another PSU. Seasonic is always my first choice, but Seasonic makes Corsair PSUs if you prefer to stick with them.

Here is a link to the Corsair forums discussing this issue:

http://forum.corsair.com/v3/showthread.php?t=123484

 

Thanks Sota, I'll have a look through the forums for some more insight. Thanks again

EDIT: Forums discuss RM850's manufactured in 2013. I bought mine 2014. I will double check the serial no. when I get home to make sure I didn't get one included in the bad batch.

 

A PSU shutdown would not give you BSODs and TDRs, it would simply turn off or hard restart your PC.

Run a memtest, update the MB BIOS, check that your videocards are on the latest BIOS as well, try underclocking both the CPU and the videocard (disable SLI for now; I'd even pull one videocard out as this will limit the load on PSU and CPU both).

But my prime suspect here would be the RAM modules.

I myself have the same issue since September which I was able to somewhat limit in occurance by setting the RAM to "enhanced stability" mode in BIOS. As I don't see much point in splashing out on new DDR3 at the moment I'm sitting it out waiting for Broadwell-E. These issues can be really frustrating as they prompt you to basically change all the components until you'll find the faulty one.

Here's something else you can try: since you're saying that the issue disappeared for 5 days after the MB swap you may want to try to clean whatever electrical contacts you have access to. These usually include the contact pads on the CPU/MB socket (depending on where the pins are), the contacts on RAM modules and the contacts on any PCI/PCIE expansion card you have. The simplest way of cleaning them would be to use a pencil eraser on them and then simply clean the remains of the eraser with a soft cloth or napkin. Sometimes this helps as these contacts can oxidize with time and that would give errors which may lead to BSODs/hangs.

 

They are my thoughts also on the PSU. As the system stays on it just loses display signal and gives the 116 error when I restart the PC. Although, Newegs PSU checker does put my system requirements at 825watts so I am aware I'm borderline on the power supply.

I plan on running the memtest tonight so can report back on it's findings tomorrow. As I said I have tried both sticks individually and crashes still occurred - what causes RAM corruption? Surely it has to be a very unfortunate case if both sticks stared with errors at the same time. I will check with memtest non the less as being thorough with my troubleshooting at this stage is a must to avoid going over old ground again and again.

I will give the contacts a gentle clean also. Thanks for taking the time to offer some help.

 

Try raising the PCH (Northbridge)voltage a little to give the pcie a little extra voltage see if that helps

 

0x116 is gpu specific.. try higher vccsa voltage 0.020 or 0.040v offset

 

Can I do this through MSI afterburner by just unlocking the voltage and using the slider? When I get home I will post some pics of HWinfo showing all voltages & temps for clarity.

Yes before my original mobo went back I tried various configs i.e top card on its own, top card in bottom slot, bottom card top slot etc etc.. and yes tried a different SLI bridge last night. Unfortunately the crashes still occur in every scenario.

 

Thanks Illnino is this the same as what TJ has mentioned?

 

For those not wanting to download and view the files in my OP. I have copied one of my minidumps which are the same each time.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Home\Desktop\New folder\112415-5226-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`03050730
Debug session time: Tue Nov 24 23:53:31.596 2015 (UTC + 0:00)
System Uptime: 0 days 0:05:22.439
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 Use !analyze -v to get detailed debugging information.
 BugCheck 116, {fffffa800d203010, fffff8800508f0c8, ffffffffc000009a, 4}
 *** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+8420c8 )
 Followup: MachineOwner
---------
 3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800d203010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800508f0c8, 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+8420c8
fffff880`0508f0c8 48ff2579b2ebff  jmp     qword ptr [nvlddmkm+0x6fd348 (fffff880`04f4a348)]
 DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 CUSTOMER_CRASH_COUNT:  1
 BUGCHECK_STR:  0x116
 PROCESS_NAME:  System
 CURRENT_IRQL:  0
 STACK_TEXT:  
fffff880`03583a48 fffff880`02c5d134 : 00000000`00000116 fffffa80`0d203010 fffff880`0508f0c8 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03583a50 fffff880`02c30867 : fffff880`0508f0c8 fffffa80`10d41000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03583a90 fffff880`02c5cf43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0d203010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03583b40 fffff880`0536c03d : fffffa80`0d485010 00000000`00000080 00000000`00000000 fffffa80`10bfd410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03583bc0 fffff800`03116b86 : 00000000`013eddd4 fffffa80`10d83060 fffffa80`0cd4a720 fffffa80`10d83060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03583c00 fffff800`02e6e0e6 : fffff880`02f65180 fffffa80`10d83060 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03583c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
 FOLLOWUP_IP: 
nvlddmkm+8420c8
fffff880`0508f0c8 48ff2579b2ebff  jmp     qword ptr [nvlddmkm+0x6fd348 (fffff880`04f4a348)]
 SYMBOL_NAME:  nvlddmkm+8420c8
 FOLLOWUP_NAME:  MachineOwner
 MODULE_NAME: nvlddmkm
 IMAGE_NAME:  nvlddmkm.sys
 DEBUG_FLR_IMAGE_TIMESTAMP:  5646c8c8
 FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
 BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
 Followup: MachineOwner
---------
 3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800d203010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800508f0c8, 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+8420c8
fffff880`0508f0c8 48ff2579b2ebff  jmp     qword ptr [nvlddmkm+0x6fd348 (fffff880`04f4a348)]
 DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 CUSTOMER_CRASH_COUNT:  1
 BUGCHECK_STR:  0x116
 PROCESS_NAME:  System
 CURRENT_IRQL:  0
 STACK_TEXT:  
fffff880`03583a48 fffff880`02c5d134 : 00000000`00000116 fffffa80`0d203010 fffff880`0508f0c8 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03583a50 fffff880`02c30867 : fffff880`0508f0c8 fffffa80`10d41000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03583a90 fffff880`02c5cf43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0d203010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03583b40 fffff880`0536c03d : fffffa80`0d485010 00000000`00000080 00000000`00000000 fffffa80`10bfd410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03583bc0 fffff800`03116b86 : 00000000`013eddd4 fffffa80`10d83060 fffffa80`0cd4a720 fffffa80`10d83060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03583c00 fffff800`02e6e0e6 : fffff880`02f65180 fffffa80`10d83060 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03583c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
 FOLLOWUP_IP: 
nvlddmkm+8420c8
fffff880`0508f0c8 48ff2579b2ebff  jmp     qword ptr [nvlddmkm+0x6fd348 (fffff880`04f4a348)]
 SYMBOL_NAME:  nvlddmkm+8420c8
 FOLLOWUP_NAME:  MachineOwner
 MODULE_NAME: nvlddmkm
 IMAGE_NAME:  nvlddmkm.sys
 DEBUG_FLR_IMAGE_TIMESTAMP:  5646c8c8
 FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
 BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
 Followup: MachineOwner
---------
 

Increased the voltages & power limit via afterburner but the crashes remain. I have just tried the cards individually - top card crashed straight away and I had to manually restart. Took that out and put the bottom card in the top slot on it's own and I got a different Bugcheck. Computer didn't shut down but it did restart on its own. That is the first time it has done that. minidump below.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Home\Desktop\112615-5428-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols


Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`0329b730
Debug session time: Thu Nov 26 19:03:14.115 2015 (UTC + 0:00)
System Uptime: 0 days 0:02:11.286
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4e7d75, 2, 0, fffff88004d0ec3f}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+464c3f )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000004e7d75, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004d0ec3f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003305100
 00000000004e7d75 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+464c3f
fffff880`04d0ec3f 8b410c          mov     eax,dword ptr [rcx+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  witcher3.exe

TRAP_FRAME:  fffff80000ba0840 -- (.trap 0xfffff80000ba0840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000004e7d69
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004d0ec3f rsp=fffff80000ba09d0 rbp=fffff80000ba0a00
 r8=fffff80000ba0a58  r9=fffff80000ba0a50 r10=0000000000000000
r11=fffff80000ba0960 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x464c3f:
fffff880`04d0ec3f 8b410c          mov     eax,dword ptr [rcx+0Ch] ds:4010:00000000`004e7d75=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c71e9 to fffff800030c7c40

STACK_TEXT:  
fffff800`00ba06f8 fffff800`030c71e9 : 00000000`0000000a 00000000`004e7d75 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba0700 fffff800`030c5e60 : fffffa80`4d52564e fffff880`000002c2 fffffa80`0dd16000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba0840 fffff880`04d0ec3f : fffff880`04d0db25 00000000`00000000 fffff800`00ba0080 00000000`00000001 : nt!KiPageFault+0x260
fffff800`00ba09d0 fffff880`04d0db25 : 00000000`00000000 fffff800`00ba0080 00000000`00000001 fffff880`04d0db25 : nvlddmkm+0x464c3f
fffff800`00ba09d8 00000000`00000000 : fffff800`00ba0080 00000000`00000001 fffff880`04d0db25 00000000`00000000 : nvlddmkm+0x463b25


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+464c3f
fffff880`04d0ec3f 8b410c          mov     eax,dword ptr [rcx+0Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+464c3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5646c8c8

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+464c3f

BUCKET_ID:  X64_0xD1_nvlddmkm+464c3f

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

 

Basically want to give the pcie lanes a little more voltage, may or may not help but worth a try

 

Are you using an anti-static strap while handling your gear? I sometimes see these kind of problems where the system was originally built without using one.

As you've been overclocking it's almost certain you've got damaged hardware. At least you got a year out of it. Good luck on the fix.

 

No its in uefi bios..

VCCSA is Cpu system agent voltage, responsible for memory, multi gpu, pcie.

 

The system was built and not physically changed for the best part of the year, so I doubt it was a static easy. I'm also fairly confident it isn't a hardware problem. The only OC the CPU and memory ever had were through MSI OC genie which I believe to be safe bets. I would be surprised if the GPU's have both given up at the exact same time. Also, wouldn't I be getting a Bug Check 124 code if it was hardware related?

Thanks for the comment, but it wasn't really advice nor was it really helpful?

Everything is pointing towards a driver issue but it's almost like a false positive. I believe the Nvidia driver is crashing but what is causing it to crash is what I need to ascertain.

Tonight's further testing has concluded it is definitely more stable with one card (doesn't matter which they both crash as frequent and in-frequent as one another).

HWinfo in the link -----> http://imgur.com/a/yi5nj

 

Hi TJ, all voltages are set to auto in the bios I'll take a look now and maybe increase it manually. I have noticed that the intel turbo mode is set to on? I assume this can control the voltage when on auto? In the images I linked above, the CPU is set to 3.5ghz but it is 'turbo-ing' to 3.7ghz on the desktop and maxing at 3.9ghz in a game. I will try turning the turbo feature off firstly then look into increasing voltage.