BSOD playing league of legends, multiple times

osaifh · 18 Dec 2013

Hi all
Lately, I've been having some problems. When I'm playing league of legends, or similar video games, I often get a BSOD after playing for a while. There is no apparent cause for such events: it just pops up randomly.
Some time ago, like 1 or 2 months, I had the same problem, but the BSOD only happened for a small time after booting up the computer. If I waited 15 minutes before playing, I wouldn't have any problems, even after the computer was working for hours.
Right now it happens always when I'm playing. The usual time it takes for it to BSOD is around 20-30 minutes.
Some times, instead of displaying a BSOD, the computer just freezes, and it outputs a really weird sound, like static sound.
Also, the most often displayed errors in the BSOD are IRQL_less_or_equal and page_in_nonpaged_area.

Do you guys think it could be something related to the PSU? or maybe the drivers?

Arc · 19 Dec 2013

It appears to be an old branded desktop. And, stop 0x116, that means display issue is possible here.

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:

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

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. It is important.

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 .

Let us know the results.
__________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80042624e0, fffff88008b6d68c, ffffffffc000000d, 3}

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+8f068c )

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

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


FAULTING_IP: 
nvlddmkm+8f068c
fffff880`08b6d68c 803dd60cf0ff00  cmp     byte ptr [nvlddmkm+0x7f1369 (fffff880`08a6e369)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07ecda18 fffff880`06f1f140 : 00000000`00000116 fffffa80`042624e0 fffff880`08b6d68c ffffffff`c000000d : nt!KeBugCheckEx
fffff880`07ecda20 fffff880`06ef2569 : fffff880`08b6d68c fffffa80`08045000 00000000`00000000 fffffa80`08040010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07ecda60 fffff880`06f1eeed : fffffa80`042624e0 fffffa80`042624e0 fffffa80`042624e0 fffffa80`08040010 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`07ecdaa0 fffff880`06fc5f13 : fffffa80`042624e0 00000000`00000000 fffffa80`04192110 fffffa80`08040010 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`07ecdad0 fffff880`06ff3ed6 : fffffa80`ffffffff 00000000`000374bf fffff880`07ecdc30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07ecdbb0 fffff880`06fc12aa : fffffa80`08040010 ffffffff`feced300 fffffa80`04192110 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07ecdbf0 fffff880`06fedff6 : 00000000`00000000 fffffa80`04192110 00000000`00000080 fffffa80`08040010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`07ecdd00 fffff800`0376d2ea : 00000000`02666547 fffffa80`07e42b50 fffffa80`03c0cae0 fffffa80`07e42b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07ecdd40 fffff800`034c18e6 : fffff800`0364be80 fffffa80`07e42b50 fffff800`03659cc0 00000024`1b80c000 : nt!PspSystemThreadStartup+0x5a
fffff880`07ecdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8f068c
fffff880`08b6d68c 803dd60cf0ff00  cmp     byte ptr [nvlddmkm+0x7f1369 (fffff880`08a6e369)],0

SYMBOL_NAME:  nvlddmkm+8f068c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52111094

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0827d000 fffff880`08d73000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Aug 18 23:51:08 2013 (52111094)
    CheckSum:         00ACA72F
    ImageSize:        00AF6000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4