BSOD 0x00000116, sometimes horizontal white lines on rebot

[sansseraph]

Good evening all,

I've been troubleshooting this for months...

This BSOD has been mostly random, but can be more often reproduced during act transitions in Diablo III, although it seems to have thrown it less often recently. Sometimes it can happen after browsing in chrome or watching videos online, where square artifacts will appear, and it will black screen then blue screen. White horizontal lines are sometimes present on reboot but if I safely restart before booting all the way, I can have a clean boot with no artifacts, and then likely have a few hours of use or more.

Through endless browsing of other threads, I seem to have narrowed it down to either the PSU or my GTX 580 being faulty. I've tried testing out the GTX 580 for a while in games and watching videos simultaneously in a friend's machine with a Corsair 850W TX vs. my Thermaltake 850W and it was doing perfectly for a bit, but there are days where I can do that on my machine as well with no issues. I did switch the cables to the auxiliary ports on my PSU going to the card instead of the ones coming out from inside the PSU -- this seemed to help marginally. I've toyed with all sorts of drivers, the most stable being 314.22.

EVGA rejected my attempt at a RMA, so before I buy a new PSU hoping it's not the card, if someone could analyze the attached report alongside my listed system specs, I would appreciate that greatly!

Thanks so much for your time,
David

 

[Arc]

Hi sansseraph.

A stop 0x116 is a display/graphics related issue. You rightly identified the problem.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Also, is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
_____________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007273010, fffff880051406ac, 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+9336ac )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007273010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880051406ac, 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+9336ac
fffff880`051406ac 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0554ea48 fffff880`05315140 : 00000000`00000116 fffffa80`07273010 fffff880`051406ac ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0554ea50 fffff880`052e8867 : fffff880`051406ac fffffa80`08571000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0554ea90 fffff880`05314f4f : 00000000`ffffd84d fffff800`00b96080 fffffa80`07273010 fffff880`053e3f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0554eb40 fffff880`053e403d : fffffa80`081e0560 00000000`00000080 00000000`00000000 fffffa80`083ff010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0554ebc0 fffff800`0397673a : 00000000`0364952b fffffa80`0820cb50 fffffa80`069fb6f0 fffffa80`0820cb50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0554ec00 fffff800`036cb8e6 : fffff800`03855e80 fffffa80`0820cb50 fffff800`03863cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0554ec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9336ac
fffff880`051406ac 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+9336ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

5: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0480d000 fffff880`052b8000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4