BSOD,help needed as i have no ide what or when to do it

Hi TABU.

A stop 0x116 is a display related issue.

Are you overclocking?

Code:

CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3238

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

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

If the situation does not change after disabling overclocks, try another driver version. 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:
  
  

When the driver is successfully applied, 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, {fffffa800b7c94e0, fffff8800517e694, 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+97e694 )

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: fffffa800b7c94e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800517e694, 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+97e694
fffff880`0517e694 803d6ea7eeff00  cmp     byte ptr [nvlddmkm+0x868e09 (fffff880`05068e09)],0

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`024d3b88 fffff880`02c74140 : 00000000`00000116 fffffa80`0b7c94e0 fffff880`0517e694 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`024d3b90 fffff880`02c47867 : fffff880`0517e694 fffffa80`0aee8000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`024d3bd0 fffff880`02c73f4f : fffff800`ffffd84d ffffffff`fffe7960 fffffa80`0b7c94e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`024d3c80 fffff880`02d4303d : fffffa80`0ab70d50 00000000`00000080 00000000`00000000 fffffa80`0ad66010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`024d3d00 fffff800`0316073a : 00000000`01a05e07 fffffa80`0aae3a00 fffffa80`09757040 fffffa80`0aae3a00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`024d3d40 fffff800`02eb58e6 : fffff800`0303fe80 fffffa80`0aae3a00 fffff800`0304dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`024d3d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+97e694
fffff880`0517e694 803d6ea7eeff00  cmp     byte ptr [nvlddmkm+0x868e09 (fffff880`05068e09)],0

SYMBOL_NAME:  nvlddmkm+97e694

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52f651cf

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`04800000 fffff880`053f9000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Feb 08 21:18:31 2014 (52F651CF)
    CheckSum:         00BC7EE8
    ImageSize:        00BF9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4