BSOD Playing GW2 , Blade and soul ,launching google chrome

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.

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.

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
Take the built in 15 minutes benchmark test.

Let us know the results.
__________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006f96280, fffff8800f5c393c, 0, 2}

*** 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+15393c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006f96280, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f5c393c, 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+15393c
fffff880`0f5c393c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0fcea6b0)]

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`03d5b4f8 fffff880`1015b134 : 00000000`00000116 fffffa80`06f96280 fffff880`0f5c393c 00000000`00000000 : nt!KeBugCheckEx
fffff880`03d5b500 fffff880`1015ae3e : fffff880`0f5c393c fffffa80`06f96280 fffffa80`0c377810 fffffa80`0c357010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03d5b540 fffff880`0f40ff13 : fffffa80`06f96280 00000000`00000000 fffffa80`0c377810 fffffa80`0c357010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03d5b570 fffff880`0f43ded6 : fffffa80`ffffffff 00000000`00009e47 fffff880`03d5b6c0 00000000`00000005 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03d5b650 fffff880`0f423ce9 : fffffa80`0c37a000 ffffffff`feced300 00000000`00000005 fffffa80`0c37a000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`03d5b690 fffff880`0f421184 : 00000000`00000001 fffff8a0`0a1d2010 fffffa80`0c37a000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`03d5b790 fffff880`0f41e927 : 00000000`00000000 fffffa80`07096000 00000000`00000013 fffff8a0`0a1d2010 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`03d5b7d0 fffff880`0f4387d9 : 00000000`00000000 fffff8a0`0ef54bf0 fffffa80`00000000 fffffa80`06f6b6f0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
fffff880`03d5b9a0 fffff880`0f438514 : fffff880`009ecf40 fffff880`0f437f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03d5bb90 fffff880`0f438012 : 00000000`00000000 fffffa80`0704e490 00000000`00000080 fffffa80`0c357010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03d5bbc0 fffff800`0335b73a : 00000000`02a0c0e3 fffffa80`0c379b50 fffffa80`069879e0 fffffa80`0c379b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03d5bc00 fffff800`030b08e6 : fffff880`009e8180 fffffa80`0c379b50 fffff880`009f2fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03d5bc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+15393c
fffff880`0f5c393c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0fcea6b0)]

SYMBOL_NAME:  nvlddmkm+15393c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

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

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f470000 fffff880`100fe000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4