BSOD happens don't know how to troubleshoot have the SFdebugfiles

Hi Manfredson101. It is a display/graphics failure.

First re-check that everything is properly seated after that partial dismantle you have done.

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: Speccy - Publish Snapshot of your System Specs .

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

Let us know the results.
__________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800fc914e0, fffff8800f9a60dc, 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+9a30dc )

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: fffffa800fc914e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f9a60dc, 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+9a30dc
fffff880`0f9a60dc 803d66e9eeff00  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0f894a49)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`021c8a48 fffff880`0fca9140 : 00000000`00000116 fffffa80`0fc914e0 fffff880`0f9a60dc ffffffff`c000009a : nt!KeBugCheckEx
fffff880`021c8a50 fffff880`0fc7c867 : fffff880`0f9a60dc fffffa80`0ef36000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`021c8a90 fffff880`0fca8f4f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`0fc914e0 fffff880`0fd77f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`021c8b40 fffff880`0fd7803d : fffffa80`0efc4660 00000000`00000080 00000000`00000000 fffffa80`0ef24280 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`021c8bc0 fffff800`0316f2ea : 00000000`02254c2e fffffa80`0ef57060 fffffa80`0c6e6b30 fffffa80`0ef57060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`021c8c00 fffff800`02ec38e6 : fffff800`0304de80 fffffa80`0ef57060 fffff800`0305bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`021c8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9a30dc
fffff880`0f9a60dc 803d66e9eeff00  cmp     byte ptr [nvlddmkm+0x891a49 (fffff880`0f894a49)],0

SYMBOL_NAME:  nvlddmkm+9a30dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52b326bc

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f003000 fffff880`0fc4c000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Dec 19 22:32:52 2013 (52B326BC)
    CheckSum:         00C19112
    ImageSize:        00C49000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You will get all the necessary info in Crash and lockup debug 'How To' - Windows 7 Help Forums

If you think that the issue is really over, please mark this thread as solved.