BCCode: 116

Hi agnes88.

Your upload does not contain all the necessary data, but it is apparent that the display driver is failing, because it is too old. You need to update it.

Go to Drivers - Download NVIDIA Drivers ... update your display driver.

As it may not be enough for a branded desktop aging 3 years, so if you receive any more BSOD with the latest version of display driver installed, 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.
Screenshots and Files - Upload and Post in Seven Forums
______________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80084e04e0, fffff88011614f10, ffffffffc000009a, 4}

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+801f10 )

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: fffffa80084e04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88011614f10, 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+801f10
fffff880`11614f10 4883ec28        sub     rsp,28h

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`02cceb88 fffff880`11b23134 : 00000000`00000116 fffffa80`084e04e0 fffff880`11614f10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02cceb90 fffff880`11af6867 : fffff880`11614f10 fffffa80`07472000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ccebd0 fffff880`11b22f43 : fffffa80`ffffd846 00000000`00000000 fffffa80`084e04e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02ccec80 fffff880`03f1203d : fffffa80`07880d50 00000000`00000080 00000000`00000000 fffffa80`0746d010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02cced00 fffff800`0311873a : 00000000`00d0a96d fffffa80`07467060 fffffa80`05505040 fffffa80`07467060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02cced40 fffff800`02e6d8e6 : fffff800`02ff7e80 fffffa80`07467060 fffff800`03005cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02cced80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+801f10
fffff880`11614f10 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+801f10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68

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`10e13000 fffff880`11ac1000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat May 21 09:37:04 2011 (4DD73A68)
    CheckSum:         00C9FFFF
    ImageSize:        00CAE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Well, Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU.

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

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

Code:

BugCheck 116, {fffffa80056d4010, fffff88011a9f798, ffffffffc000000d, 3}

*** 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+9a5798 )

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

First of all you need a better PSU. 300 watts is never enough. Get one of at least 500 watts. You need to do it, whether the computer BSODs or not.

But, the GPU temp is really high. It would be better to get a new GPU for sure.