BSOD at random times, idle or in-game (many different errors)

wDanielsson · 23 Jun 2013

Hello!

Im new on this forum and i hope i do this the right way. :)

Ever since i built my computer, (about a year ago) i have gotten at least one bluescreen per week or more.
I have never really cared about it until now. Now, my computer tends to crash and then it gets stuck on the
"bios bootup screen". If i then restart my computer it all goes back to normal but the computer crashes again after 2-5 minutes in windows.

I would love if someone could help me solve this problem.

/William

Arc · 23 Jun 2013

It is a stop 0x116, which is a display related BSOD.

Apply the latest version of nVidia display driver.
You may download it directly, from our forum link Latest NVIDIA ForceWare Video Drivers Windows 7; or you may opt for the Option 2 of Drivers- Download NVIDIA Drivers for “Automatically find drivers for my NVIDIA products” (it requires java installed).

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

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.

Let us know the results.
_______________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800c121010, fffff88008b696c4, 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+9316c4 )

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: fffffa800c121010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88008b696c4, 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+9316c4
fffff880`08b696c4 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03b1fa48 fffff880`08d3d054 : 00000000`00000116 fffffa80`0c121010 fffff880`08b696c4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03b1fa50 fffff880`08d10867 : fffff880`08b696c4 fffffa80`0a8a5000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03b1fa90 fffff880`08d3ce63 : 00000000`ffffd84d 00000000`0000000f fffffa80`0c121010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03b1fb40 fffff880`0796f03d : fffffa80`0b2b0150 00000000`00000080 00000000`00000000 fffffa80`0a8a0010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03b1fbc0 fffff800`03b64ede : 00000000`01f935b3 fffffa80`0a742b50 fffffa80`06cf34a0 fffffa80`0a742b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03b1fc00 fffff800`038b7906 : fffff800`03a41e80 fffffa80`0a742b50 fffff800`03a4fcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b1fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9316c4
fffff880`08b696c4 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+9316c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

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`08238000 fffff880`08ce0000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Feb 10 04:43:08 2013 (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4