BSOD Apparantly random

I initially believed the problem was only when I played Chess Titans. However, the crash has been happening at seemingly random times. When I try to open two things at once, it can happen. It's as if any multitasking sets it off.

I used SF diagnostic tool to get the memory dumps and they can be found in the attached archive. If any further information is required don't hesitate to ask. Thanks in advance for any assistance provided.

*Edited to include correct attachment.*

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Please do the post #2.

Your upload .....

Attachment 336964

A random upload following the Blue Screen of Death (BSOD) Posting Instructions.....

Attachment 336965

Which gives the sense that you havent followed the instructions.

I've no idea how that happened. To ensure it didn't happen again, I've used the First option in the guideline this time. I did it exactly how it was supposed to be done so this archive should be fine. Thanks in advance.

Uninstall the display driver using Display Driver Uninstaller.

Then install 340.52 WHQL only.

When installed, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Let us know the result. We have to see the situation with a different driver version at first.
_______________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cafd4e0, fffff8800ff4651c, 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+91951c )

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: fffffa800cafd4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800ff4651c, 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+91951c
fffff880`0ff4651c 48ff255dc9ecff  jmp     qword ptr [nvlddmkm+0x7e5e80 (fffff880`0fe12e80)]

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`029d4a48 fffff880`1035e134 : 00000000`00000116 fffffa80`0cafd4e0 fffff880`0ff4651c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`029d4a50 fffff880`10331867 : fffff880`0ff4651c fffffa80`0a1c3000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`029d4a90 fffff880`1035df43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0cafd4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`029d4b40 fffff880`04e8d03d : fffffa80`0b25d310 00000000`00000080 00000000`00000000 fffffa80`09c00410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`029d4bc0 fffff800`0357973a : 00000000`024014af fffffa80`09bea8b0 fffffa80`036f45f0 fffffa80`09bea8b0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`029d4c00 fffff800`032ce8e6 : fffff800`03458e80 fffffa80`09bea8b0 fffff800`03466cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`029d4c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+91951c
fffff880`0ff4651c 48ff255dc9ecff  jmp     qword ptr [nvlddmkm+0x7e5e80 (fffff880`0fe12e80)]

SYMBOL_NAME:  nvlddmkm+91951c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5414a236

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f62d000 fffff880`10301000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Sep 14 01:29:50 2014 (5414A236)
    CheckSum:         00C8E3A6
    ImageSize:        00CD4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

15 minutes? Then take a screenshot of the furmark window at first, then stop it manually.

Let us see the screenshot.