Random BSOD, ntoskrnl.exe+75bc0, BCCode 116

An old computer, and stop 0x116.

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 .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of your PSU.

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

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.
________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009317010, fffff880055d66bc, ffffffffc000000d, 3}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** 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+8ed6bc )

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

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

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

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


FAULTING_IP: 
nvlddmkm+8ed6bc
fffff880`055d66bc 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`041ae9d8 fffff880`04723140 : 00000000`00000116 fffffa80`09317010 fffff880`055d66bc ffffffff`c000000d : nt!KeBugCheckEx
fffff880`041ae9e0 fffff880`046f6569 : fffff880`055d66bc fffffa80`06793000 00000000`00000000 fffffa80`06720410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`041aea20 fffff880`04722eed : fffffa80`09317010 fffffa80`09317010 fffffa80`09317010 fffffa80`06720410 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`041aea60 fffff880`047c9f13 : fffffa80`09317010 00000000`00000000 fffffa80`067f9d50 fffffa80`06720410 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`041aea90 fffff880`047f7ed6 : fffffa80`ffffffff 00000000`01d9315f fffff880`041aebf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`041aeb70 fffff880`047c52aa : fffffa80`06720410 ffffffff`feced300 fffffa80`067f9d50 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`041aebb0 fffff880`047f1ff6 : 00000000`00000000 fffffa80`067f9d50 00000000`00000080 fffffa80`06720410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`041aecc0 fffff800`033232ea : 00000000`0e512a00 fffffa80`067ab610 fffffa80`03cdfb30 fffffa80`067ab610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`041aed00 fffff800`030778e6 : fffff800`03201e80 fffffa80`067ab610 fffff800`0320fcc0 fffff880`019ce0c5 : nt!PspSystemThreadStartup+0x5a
fffff880`041aed40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8ed6bc
fffff880`055d66bc 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+8ed6bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04ce9000 fffff880`057ce000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4