BSOD Newbie!

Hi Scooby1.

A stop 0x116 is a display/graphics related issue.

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.

The computer seems to me old, for more or less 3 years. 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 the PSU.

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

The display driver that is installed is not very stable. But I am not seeing any update for your GeForce 6200 with TurboCache . If you know, please update it.

Let us know the results.

Edit: Is it nForce? And th GPU driver is a part of it?
__________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80042d3010, fffff8800f2232b0, 0, 2}

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+14c2b0 )

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: fffffa80042d3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f2232b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+14c2b0
fffff880`0f2232b0 4055            push    rbp

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.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`02db59c8 fffff880`04cba140 : 00000000`00000116 fffffa80`042d3010 fffff880`0f2232b0 00000000`00000000 : nt!KeBugCheckEx
fffff880`02db59d0 fffff880`04cb9e4a : fffff880`0f2232b0 fffffa80`042d3010 fffffa80`0633bd50 fffffa80`06249410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02db5a10 fffff880`04d60f13 : fffffa80`042d3010 00000000`00000000 fffffa80`0633bd50 fffffa80`06249410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02db5a40 fffff880`04d8acf1 : 00000000`ffffffff 00000000`00005a96 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02db5b20 fffff880`04d89437 : 00000000`00000102 00000000`00000000 00000000`00005a96 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02db5b50 fffff880`04d5c2d2 : ffffffff`ff676980 fffffa80`06249410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02db5bf0 fffff880`04d88ff6 : 00000000`00000000 fffffa80`06355b90 00000000`00000080 fffffa80`06249410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02db5d00 fffff800`02d6d2ea : 00000000`fffffc32 fffffa80`05faab50 fffffa80`039eb6f0 fffffa80`05faab50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02db5d40 fffff800`02ac18e6 : fffff800`02c4be80 fffffa80`05faab50 fffff800`02c59cc0 fffff880`02db5e40 : nt!PspSystemThreadStartup+0x5a
fffff880`02db5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+14c2b0
fffff880`0f2232b0 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+14c2b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  510a2100

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f0d7000 fffff880`0fde1000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Jan 31 13:15:04 2013 (510A2100)
    CheckSum:         00CEDB22
    ImageSize:        00D0A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Welcome, mate.

Let us know for any further issue.