BSOD 116 without doing any intensive programming.

lokon · 30 Jan 2015

Hello everyone.
This is my system file generated by DM Log Collector.
I was just looking through my email and had a few WORD documents opened, then I experienced BSOD 116 for the first time.
The screen was flashing black/blank for a few times before the actually BSOD happened. It scared me !!!

Please let me know what's going on. Thank you !

Arc · 02 Feb 2015

Hi.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats including BSODs.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Next, uninstall the display driver using DDU. Install 347.09 WHQL.

When done, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.
____________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8008db64e0, fffff8800740d81c, 0, d}

*** 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+13e81c )

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

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

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

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


FAULTING_IP: 
nvlddmkm+13e81c
fffff880`0740d81c 48ff25cddb5300  jmp     qword ptr [nvlddmkm+0x67c3f0 (fffff880`0794b3f0)]

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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`049e2718 fffff880`07d39cbc : 00000000`00000116 fffffa80`08db64e0 fffff880`0740d81c 00000000`00000000 : nt!KeBugCheckEx
fffff880`049e2720 fffff880`07d39a43 : fffff880`0740d81c fffffa80`08db64e0 fffffa80`06f39510 fffffa80`08aef410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`049e2760 fffff880`0720ff07 : fffffa80`08db64e0 00000000`00000000 fffffa80`06f39510 fffffa80`08aef410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`049e2790 fffff880`0723dd7e : 00000000`ffffffff 00000000`00099f7a fffff880`049e28f0 fffffa80`08aef410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`049e2870 fffff880`07239ca5 : fffffa80`08b02000 ffffffff`feced300 fffffa80`071ed330 fffffa80`06b63010 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`049e28b0 fffff880`07239e5d : fffffa80`08b02000 fffffa80`08aef410 00000000`00000000 fffff880`079c821f : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
fffff880`049e29a0 fffff880`07238d3c : 00000000`0000001c 00000000`00230346 fffffa80`071ed330 fffffa80`08aef410 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
fffff880`049e2aa0 fffff880`07238398 : fffff880`02f68f00 fffff880`07237d00 fffffa80`00000000 fffffa80`000005d4 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`049e2c90 fffff880`07237e96 : 00000000`00000000 fffffa80`06f39510 00000000`00000080 fffffa80`08aef410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`049e2cc0 fffff800`03126166 : 00000000`fffffc32 fffffa80`08ac0620 fffffa80`066e5040 fffffa80`08ac0620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`049e2d00 fffff800`02e61486 : fffff880`02f64180 fffffa80`08ac0620 fffff880`02f6efc0 fffff880`0120f534 : nt!PspSystemThreadStartup+0x5a
fffff880`049e2d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13e81c
fffff880`0740d81c 48ff25cddb5300  jmp     qword ptr [nvlddmkm+0x67c3f0 (fffff880`0794b3f0)]

SYMBOL_NAME:  nvlddmkm+13e81c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54b0548e

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
---------

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`072cf000 fffff880`07cdd000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Jan 10 03:52:06 2015 (54B0548E)
    CheckSum:         009D73FA
    ImageSize:        00A0E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4