Asus laptop (N73Jn) getting BSOD playing LOL

sigby · 13 Nov 2014

Hi!

I'm having trouble with my laptop. I'm getting BSOD when playing League of Legends - previously I’ve had similar problems when playing Diablo 3.
It doesn’t happen every time I play but just from time to time.

I recently did a complete reinstallation of the pc hoping that it might solve the problem - unfortunately it didn’t.

I’ve read somewhere that the N73 series sometimes gets BOSD because of driver issues, but I don’t know how to find out what causes the crashes. Can anyone help me troubleshooting and fixing this issue?

Thanks!

Best regards, Morten

(I have attached a zip-file as recommended in the sticky)

koolkat77 · 14 Nov 2014

Welcome.

Go through this thread: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\SIGBY-PC-13-11-2014_211116,31\110914-71136-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305d890
Debug session time: Sun Nov  9 20:04:00.749 2014 (UTC + 6:00)
System Uptime: 0 days 0:41:56.096
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80046914e0, fffff8800f36a93c, 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
---------

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

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

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`022b4498 fffff880`0ff02134 : 00000000`00000116 fffffa80`046914e0 fffff880`0f36a93c 00000000`00000000 : nt!KeBugCheckEx
fffff880`022b44a0 fffff880`0ff01e3e : fffff880`0f36a93c fffffa80`046914e0 fffffa80`09370270 fffffa80`093b3410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`022b44e0 fffff880`0ffa9f13 : fffffa80`046914e0 00000000`00000000 fffffa80`09370270 fffffa80`093b3410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`022b4510 fffff880`0ffd7ed6 : fffffa80`ffffffff 00000000`00027578 fffff880`022b4650 fffffa80`093a4d50 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`022b45f0 fffff880`0ffc3d2c : 00000000`00000000 ffffffff`feced300 00000000`00000001 fffff880`0ffd3fe1 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`022b4630 fffff880`0ffc2cfd : fffffa80`093a4c50 00000000`00000000 00000000`80000011 fffffa80`093b3410 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0xcc
fffff880`022b4700 fffff880`0ffbd95f : 00000000`ffffd9fa 00000000`000222a4 fffffa80`093cb230 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x2a1
fffff880`022b4750 fffff880`0ffc04ad : fffff8a0`00000000 fffff880`0ffbbca9 00000000`00000000 fffff8a0`040c6e01 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x4c3
fffff880`022b48a0 fffff880`0ffb88c1 : 00000000`00000000 fffffa80`09922000 00000000`00000021 fffffa80`0993bb40 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x14d
fffff880`022b4910 fffff880`0ffd27d9 : 00000000`00000000 fffff8a0`093c41f0 fffffa80`00000000 fffffa80`09ab1010 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd09
fffff880`022b4ae0 fffff880`0ffd2514 : fffff880`031d9f40 fffff880`0ffd1f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`022b4cd0 fffff880`0ffd2012 : 00000000`00000000 fffffa80`0459bad0 00000000`00000080 fffffa80`093b3410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`022b4d00 fffff800`0312b73a : 00000000`fffffc32 fffffa80`093a6610 fffffa80`03e50890 fffffa80`093a6610 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`022b4d40 fffff800`02e808e6 : fffff880`031d5180 fffffa80`093a6610 fffff880`031dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`022b4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

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

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

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f217000 fffff880`0fea5000   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:42:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

sigby · 15 Nov 2014

Hi,

thanks for your reply.
Iv'e tried some of the first suggestions in the thread you linked to (reinstallation of NVIDIA drivers and I am running the second of the two stress tests at the moment). I haven't had any BSODs since I reinstalled the drivers. I have however not played a lot since then either, so I can't say for sure if it has worked.
I'll return with updates - espacially if I get further BSODs.

Update: I ran the furmark test until temp. stabilized at 64 degrees C and i ran the Prime95 test for 7 hours without any errors.