BSOD. Crash while games are at full screen mode.

[CinePro]

Hi guys, I have followed the instructions and here are the files requested.

This crash first started when I was playing League of Legends. since then, everytime I open a game at full screen mode, it crashes after 1 minute and 50 seconds. I already reinstalled League of Legends and also, updated my graphic drivers, but still, nothing changed.

The dump files are attached.
Thanks!

 

[Arc]

The couple of latest drivers by nvidia are buggy as we experienced.

Install the NVIDIA DRIVERS 314.22WHQL only. It works with GT530.

• 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
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

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


Let us know the results.

____________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80096f14e0, fffff88005143700, 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+8ed700 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80096f14e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005143700, 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+8ed700
fffff880`05143700 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`07fe6a48 fffff880`02d2e054 : 00000000`00000116 fffffa80`096f14e0 fffff880`05143700 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`07fe6a50 fffff880`02d01867 : fffff880`05143700 fffffa80`07005000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07fe6a90 fffff880`02d2de63 : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`096f14e0 fffff880`0537ff3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`07fe6b40 fffff880`0538003d : fffffa80`0583b410 00000000`00000080 00000000`00000000 fffffa80`06376410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`07fe6bc0 fffff800`03561bae : fffffa80`05cc05b0 fffffa80`07c57040 fffffa80`051eb040 00000000`00000000 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`07fe6c00 fffff800`032b48c6 : fffff800`0343ee80 fffffa80`07c57040 fffffa80`062cbb50 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`07fe6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8ed700
fffff880`05143700 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+8ed700

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04856000 fffff880`0533b000   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

 

[CinePro]

Hi there Arc. Thank you for your reply. I did everything as you said so but still, while doing Furmark test it crashed again with the Bluescreen error.

 

[Arc]

Hi there Arc. Thank you for your reply. I did everything as you said so but still, while doing Furmark test it crashed again with the Bluescreen error.

So there is a fair chance that the GPU is failing. Try to replace it.

 

[CinePro]

Isn't there anything more that I can do before make such an extreme operation?

 

[Arc]

Isn't there anything more that I can do before make such an extreme operation?

If you want to do more, check the system temperature. Is it hot?
See if there is dust allocation inside the computer and if it is blocking the air vents, fan grills etc.

But, if it is a failing hardware, it will not be salvaged by doing those.