Solved Unexpected BSOD results in crash dump

[swk87]

Hi everyone, I recently had a crash dump file in c:\windows\minidump.

I am uploading it here for those who may wish to review it. However, I cannot specify what the cause of the this problem may have been.

 

[Arc]

Click on button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

We need to see those files before we suggest anything with this issue.
____________________________________________

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800d33f4e0, fffff88005000f38, 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+7a3f38 )

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: fffffa800d33f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005000f38, 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+7a3f38
fffff880`05000f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`04eda230)]

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`06c06a48 fffff880`052cc134 : 00000000`00000116 fffffa80`0d33f4e0 fffff880`05000f38 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06c06a50 fffff880`0529f867 : fffff880`05000f38 fffffa80`0fd2c000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06c06a90 fffff880`052cbf43 : fffffa80`ffffd846 00000000`00000000 fffffa80`0d33f4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`06c06b40 fffff880`0539c03d : fffffa80`0d2a3430 00000000`00000080 00000000`00000000 fffffa80`0fcf1010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`06c06bc0 fffff800`03316b8a : 00000000`04537f53 fffffa80`0fce3a00 fffffa80`0c9e69e0 fffffa80`0fce3a00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`06c06c00 fffff800`030698e6 : fffff800`031f4e80 fffffa80`0fce3a00 fffff800`03202cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06c06c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7a3f38
fffff880`05000f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`04eda230)]

SYMBOL_NAME:  nvlddmkm+7a3f38

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54d3b001

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