PDA

View Full Version : WoW still crashing with nVidia 311.59 drivers



tnili
07-29-2013, 11:54 PM
When I got my G750JX, it crashed almost every time I played in a dungeon. I was using the stock drivers that came with the unit (don't remember the version). I upgraded to 311.59 which are the latest posted on the ASUS support page for this notebook. The crashes have been a lot less regular but it still crashes about once a day. This is still making me grumpy so I would like to do something about it.

I am hesitant about using the nVidia reference drivers because 320.49 apparently requires INF hacks and 326.19 is still in Beta. Has anyone had a similar experience? Did updating to nVidia reference drivers solve the problem?

EpIcSnIpErZ23
07-30-2013, 01:03 AM
Hey tnili, are there any error messages when WoW crashes?

tnili
07-30-2013, 11:34 PM
When this problem happens, WoW exits and a message is displayed in the system tray area saying the video driver stopped responding but recovered successfully. In reality, the system is hosed and you have to reboot to start the game again.

Here is the technical info for ASUS support:

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

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa800edc24d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004de82e0, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 000000000000071c, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+1372e0
fffff880`04de82e0 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9465.0 (debuggers(dbg).130719-2136) x86fre

STACK_TEXT:
fffff880`095c6340 fffff880`0437a952 : 00000000`00000000 00000000`00000001 fffffa80`0eda9010 00000000`00000000 : watchdog!WdDbgReportRecreate+0xcc
fffff880`095c6880 fffff880`04446939 : fffffa80`00000000 fffffa80`13e973f8 fffff880`095c6939 fffffa80`0edc24d0 : dxgkrnl!TdrUpdateDbgReport+0xc2
fffff880`095c68d0 fffff880`0447d85f : fffffa80`0e8ca000 00000000`00000000 00000000`00000001 fffffa80`0e8ca001 : dxgmms1!VidSchiResetEngine+0x455
fffff880`095c69a0 fffff880`044819c9 : fffff880`095c6b00 fffff880`095c6a60 fffffa80`0eda9010 fffffa80`0e8ca000 : dxgmms1!VidSchiResetEngines+0x83
fffff880`095c69e0 fffff880`04445fb5 : 00000000`00000001 fffff880`095c6b69 fffffa80`0eda9010 00000000`00000001 : dxgmms1!VidSchWaitForCompletionEvent+0x3e1
fffff880`095c6aa0 fffff880`0447a646 : 00000000`00000000 fffffa80`0f79fc70 fffffa80`0eeb3100 fffffa80`0eda9010 : dxgmms1!VidSchiScheduleCommandToRun+0x259
fffff880`095c6bd0 fffff803`130b5fd9 : fffffa80`1237c900 fffffa80`0eda9010 fffff880`01366f40 00000000`00e330e0 : dxgmms1!VidSchiWorkerThread+0xca
fffff880`095c6c10 fffff803`1316a7e6 : fffff880`0135b180 fffffa80`1237c900 fffff880`01366f40 fffffa80`0dfcc440 : nt!PspSystemThreadStartup+0x59
fffff880`095c6c60 00000000`00000000 : fffff880`095c7000 fffff880`095c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+1372e0
fffff880`04de82e0 ?? ???

SYMBOL_NAME: nvlddmkm+1372e0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 517d6a3e

FAILURE_BUCKET_ID: 0x141_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x141_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x141_image_nvlddmkm.sys

FAILURE_ID_HASH: {4664cac2-c7ab-571c-719f-1f53c923c833}

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