Finding source of DirectX 11 Crash with BF4, Total Wars Rome 2, Shogun 2 and Heroes and Generals

vanor

Reputable
Sep 5, 2014
17
0
4,510
September 20th update: Root Cause: Faulty Hardware, product being RMA.

Hi,

Hi tom'sHARDWARE forum community.

I just got a new PC and I suspect a faulty GPU. I wanted to get feedback from the community while I wait for a response from my support ticket with the store where I purchased it.

Here are the component:
CPU
Intel Haswell i7-4790K LGA1150 4.0GHz Processor
Primary Hard Disk
Samsung 840 EVO 1TB SATA 6.0 SSD
Video Card
Asus GeForce GTX 780 Ti 3GB DDR5 Video Card GTX780TI-DC2OC-3GD5
Motherboard
Asus SABERTOOTH Z97 MARK2 LGA1150 DDR3 Motherboard ATX
RAM
Corsair Vengeance 8GB DDR3 1866MHz Memory
Audio Card
Asus XONAR DSX 7.1
Power Supply
EVGA SuperNOVA 1000 G2 1000W 80Plus Gold Power Supply
Cooling
Corsair Hydro Series H60 Intel/AMD High Performance Liquid CPU Cooler
Case
Thermaltake Core V71 Full Tower Case
OS
Microsoft Windows 8.1 PRO 64-bit

I am not overclocking any component

I ran Prime95, IntelBurn, OCCT DirectX 9 and DirectX 11 and FurMark with no problem.

Wolfenstein New Order that uses OpenGL works fine at 1080p max setting.

SSD Caching has been disabled.

3DMark11 Test succeeds if I run it in 720p, it causes an immediate computer crash if I attempt it in 1080p.

Total War: Rome 2 and Shogun 2 -> works fine for battle in Ultra at 1080p. Anytime I try to load the campaign map the computer crashes (not just the game).

Battlefield 4, regular battles at 1080p ultra works fine, whenever the game goes through a transition (getting on the boat in Shangai or jumping off the ships the computer crashes, to bypass the crash I have to set the game to 720p low settings).

Heroes and Generals, Loading New Blood training mission causes an immediate crash.

Infantry battles are fine, still need to test armor and planes (switch side in current war and I haven't unlock those options yet).

GPU Drivers, Windows Drivers and DirectX 11 are all up to date with the latest drivers.

I suspect a faulty GPU (hence why I have raised a support ticket with the store).

That being said since they are not super fast (only one response in a week), I decided to come here for suggestion of what other tests I might want to consider to help diagnose the problem or suggestion on what might be the problem.

Other Note:
Sims 4 works fine so far.
I will be trying Bioshock Infinite and Metro 2033 Redux over the weekend to see how they stable they are.

If you have any suggestions they are welcome.

Thanks in advance.

 

vanor

Reputable
Sep 5, 2014
17
0
4,510
Sorry for the late reply (I expected a quick reply here but not that quick, thanks kapitalistas). Took me a while to pinpoint the dump file location for Windows 8.1 and the error I was getting. They are in windows/livekernelreports/watchdog (base on what I read those are normally graphic related error).

I am in the process of recreating a dump for each event (Battlefield 4, H&G, Total Wars and 3DMARK11).

Here is the dump for 3DMARK11 (definitely graphic related)

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe00162f102a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8014d7b093c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 4

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`5c555a20 fffff801`4d323b88 : 00000000`00000002 ffffe001`62f102a0 00000000`80000000 ffffe001`67c48010 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`5c555a70 fffff801`4d32324d : ffffc000`00000000 ffffc000`19acfd90 00000000`00000002 ffffe001`67811bf8 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`5c555ac0 fffff801`4d318573 : ffffc000`1a0a3b8c ffffe001`67811540 ffffd000`5c555b20 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage2+0x1d9
ffffd000`5c555af0 fffff801`4d323919 : ffffe001`67800100 fffff801`4ce41e78 ffffe001`67804000 ffffe001`67804000 : dxgkrnl!DXGADAPTER::Reset+0x407
ffffd000`5c555b60 fffff801`4ce5afde : fffff801`4ce41c90 ffffe001`67804000 fffff801`bd471000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`5c555b90 fffff801`4ce41d1d : ffffe001`67804000 00000000`00000080 ffffe001`67831880 ffffe001`00000000 : dxgmms1!VidSchiRecoverFromTDR+0x1a
ffffd000`5c555bc0 fffff801`bd540794 : ffffd000`5a94c3c0 ffffe001`67831880 ffffd000`5c555c90 fffff801`bd5c837d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`5c555c00 fffff801`bd5cb5c6 : ffffd000`5a940180 ffffe001`67831880 ffffd000`5a94c3c0 ffffc000`12c12ed0 : nt!PspSystemThreadStartup+0x58
ffffd000`5c555c60 00000000`00000000 : ffffd000`5c556000 ffffd000`5c550000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

FAILURE_BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x117_image_nvlddmkm.sys

FAILURE_ID_HASH: {a93e9c2e-fca7-af48-d0f1-0cc77d4c6965}

Followup: MachineOwner
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
The 2 dumps I got with Heroes and General:

First Dump:
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: ffffe000dcfdd360, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8007880893c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000560, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+15393c
fffff800`7880893c ?? ???

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.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`df347630 fffff800`78379b88 : ffffe000`dcfdd360 ffffe000`dcfdd360 ffffd000`df347739 ffffe000`d61758f0 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`df347680 fffff800`7822a9bb : ffffe000`00000000 ffffe000`d6d8d0a8 ffffe000`d5bef000 ffffe000`0000000b : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`df3476d0 fffff800`7826b98b : ffffe000`d5bef000 00000000`00000000 00000000`00000001 ffffe000`d5bf1001 : dxgmms1!VidSchiResetEngine+0x447
ffffd000`df3477a0 fffff800`78260c12 : ffffd000`df3478d0 ffffe000`d5bef000 00000000`00000102 ffffe000`d5bf1000 : dxgmms1!VidSchiResetEngines+0x83
ffffd000`df3477e0 fffff800`7824dfd5 : ffffe000`d5bef000 ffffe000`d5bf1000 00000000`00000004 00000000`00000004 : dxgmms1!VidSchWaitForCompletionEvent+0x17752
ffffd000`df347890 fffff800`7821d108 : ffffe000`d6652640 ffffe000`d5bf1000 ffffe000`d5bef880 00000000`00000000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
ffffd000`df347980 fffff800`78218dd5 : ffffe000`d6652640 ffffe000`d6652640 ffffd000`df347ac0 ffffe000`d5bf1000 : dxgmms1!VidSchiCompletePreemption+0x28
ffffd000`df3479c0 fffff800`78253d4a : ffffe000`d5bf1000 ffffe000`d5bf1000 ffffe000`d6652640 ffffe000`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x675
ffffd000`df347b70 fffff800`78253d1d : ffffe000`d5bf1000 00000000`00000080 ffffe000`dab43500 ffffe000`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`df347bc0 fffff802`2d946794 : ffffd000`dd74c3c0 ffffe000`dab43500 ffffd000`df347c90 fffff802`2d9ce37d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`df347c00 fffff802`2d9d15c6 : ffffd000`dd740180 ffffe000`dab43500 ffffd000`dd74c3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`df347c60 00000000`00000000 : ffffd000`df348000 ffffd000`df342000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff800`7880893c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

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


Second Dump (created at the same time):
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe000dd0f84d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8007880893c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+15393c
fffff800`7880893c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`df347a20 fffff800`78379b88 : 00000000`00000002 ffffe000`dd0f84d0 00000000`80000000 ffffe000`d6493500 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`df347a70 fffff800`7837924d : ffffc000`00000000 ffffc000`60146220 00000000`00000002 ffffe000`dab65bf8 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`df347ac0 fffff800`7836e573 : ffffc000`60224bf7 ffffe000`dab65540 ffffd000`df347b20 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage2+0x1d9
ffffd000`df347af0 fffff800`78379919 : ffffe000`d5bf0100 fffff800`78253e78 ffffe000`d5bf1000 ffffe000`d5bf1000 : dxgkrnl!DXGADAPTER::Reset+0x407
ffffd000`df347b60 fffff800`7826cfde : fffff800`78253c90 ffffe000`d5bf1000 fffff802`2d877000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`df347b90 fffff800`78253d1d : ffffe000`d5bf1000 00000000`00000080 ffffe000`dab43500 ffffe000`00000000 : dxgmms1!VidSchiRecoverFromTDR+0x1a
ffffd000`df347bc0 fffff802`2d946794 : ffffd000`dd74c3c0 ffffe000`dab43500 ffffd000`df347c90 fffff802`2d9ce37d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`df347c00 fffff802`2d9d15c6 : ffffd000`dd740180 ffffe000`dab43500 ffffd000`dd74c3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`df347c60 00000000`00000000 : ffffd000`df348000 ffffd000`df342000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff800`7880893c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

FAILURE_BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x117_image_nvlddmkm.sys

FAILURE_ID_HASH: {a93e9c2e-fca7-af48-d0f1-0cc77d4c6965}

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

vanor

Reputable
Sep 5, 2014
17
0
4,510
Actually for 3DMARK11 I got 5 dump files, here are the outputs:

Main DUMP:
FAULTING_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

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.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`5c555280 fffff801`4d323b88 : ffffe001`62b34010 ffffe001`62b34010 ffffd000`5c555389 ffffe001`62bd68f0 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`5c5552d0 fffff801`4ce189bb : ffffe001`00000000 ffffe001`62aa94a8 ffffe001`67802000 ffffe001`00000006 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`5c555320 fffff801`4ce5998b : ffffe001`67802000 00000000`00000000 00000000`00000001 ffffe001`67804001 : dxgmms1!VidSchiResetEngine+0x447
ffffd000`5c5553f0 fffff801`4ce4ec12 : ffffd000`5c555520 ffffe001`67802000 00000000`00000102 ffffe001`67804000 : dxgmms1!VidSchiResetEngines+0x83
ffffd000`5c555430 fffff801`4ce3bfd5 : ffffe001`67802000 ffffe001`67804000 00000000`00000008 00000000`00000008 : dxgmms1!VidSchWaitForCompletionEvent+0x17752
ffffd000`5c5554e0 fffff801`4ce0b108 : ffffe001`67804000 ffffe001`67804000 00000000`00000000 ffffd000`5c5556f0 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
ffffd000`5c5555d0 fffff801`4ce3bd09 : ffffe001`67804000 ffffe001`67804000 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiCompletePreemption+0x28
ffffd000`5c555610 fffff801`4ce598d6 : 00000000`00000001 ffffe001`625eb000 ffffd000`5c5556f0 ffffe001`67804000 : dxgmms1!VidSchiPreemptEngineNodes+0xf5
ffffd000`5c555650 fffff801`4ce4ec01 : fffff801`4d6b76c9 ffffd000`5c555790 ffffd000`5c555790 00000000`00000102 : dxgmms1!VidSchiPrepareToResetEngine+0xf6
ffffd000`5c5556a0 fffff801`4ce3bfd5 : ffffe001`625eb000 ffffe001`67804000 00000000`00000008 00000000`00000008 : dxgmms1!VidSchWaitForCompletionEvent+0x17741
ffffd000`5c555750 fffff801`4ce0b108 : ffffe001`67804000 ffffe001`67804000 00000000`00000000 ffffd000`5c555960 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
ffffd000`5c555840 fffff801`4ce3bd09 : ffffe001`67804000 ffffe001`67804000 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiCompletePreemption+0x28
ffffd000`5c555880 fffff801`4ce598d6 : 00000000`00000001 ffffe001`67802000 ffffd000`5c555960 ffffe001`67804000 : dxgmms1!VidSchiPreemptEngineNodes+0xf5
ffffd000`5c5558c0 fffff801`4ce4ec01 : ffffd000`5c555a80 ffffd000`5c555a80 ffffd000`5c555a80 00000000`00000102 : dxgmms1!VidSchiPrepareToResetEngine+0xf6
ffffd000`5c555910 fffff801`4ce06d1b : ffffe001`6298f510 ffffd000`5c555ac0 00000000`00000002 00000000`00000002 : dxgmms1!VidSchWaitForCompletionEvent+0x17741
ffffd000`5c5559c0 fffff801`4ce41d4a : ffffe001`67804000 ffffe001`67804000 ffffe001`6298f510 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x5bb
ffffd000`5c555b70 fffff801`4ce41d1d : ffffe001`67804000 00000000`00000080 ffffe001`67831880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`5c555bc0 fffff801`bd540794 : ffffd000`5a94c3c0 ffffe001`67831880 ffffd000`5c555c90 fffff801`bd5c837d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`5c555c00 fffff801`bd5cb5c6 : ffffd000`5a940180 ffffe001`67831880 ffffd000`5a94c3c0 ffffc000`12c12ed0 : nt!PspSystemThreadStartup+0x58
ffffd000`5c555c60 00000000`00000000 : ffffd000`5c556000 ffffd000`5c550000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

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

Additional Dump -1:
FAULTING_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`5c5554f0 fffff801`4d323b88 : ffffe001`62d734d0 ffffe001`62d734d0 ffffd000`5c5555f9 ffffe001`62b9b5e0 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`5c555540 fffff801`4ce189bb : ffffe001`00000000 ffffe001`68c735c8 ffffe001`625eb000 ffffe001`00000006 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`5c555590 fffff801`4ce5998b : ffffe001`625eb000 00000000`00000001 00000000`00000001 ffffe001`67804001 : dxgmms1!VidSchiResetEngine+0x447
ffffd000`5c555660 fffff801`4ce4ec12 : ffffd000`5c555790 ffffe001`625eb000 00000000`00000102 ffffe001`67804000 : dxgmms1!VidSchiResetEngines+0x83
ffffd000`5c5556a0 fffff801`4ce3bfd5 : ffffe001`625eb000 ffffe001`67804000 00000000`00000008 00000000`00000008 : dxgmms1!VidSchWaitForCompletionEvent+0x17752
ffffd000`5c555750 fffff801`4ce0b108 : ffffe001`67804000 ffffe001`67804000 00000000`00000000 ffffd000`5c555960 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
ffffd000`5c555840 fffff801`4ce3bd09 : ffffe001`67804000 ffffe001`67804000 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiCompletePreemption+0x28
ffffd000`5c555880 fffff801`4ce598d6 : 00000000`00000001 ffffe001`67802000 ffffd000`5c555960 ffffe001`67804000 : dxgmms1!VidSchiPreemptEngineNodes+0xf5
ffffd000`5c5558c0 fffff801`4ce4ec01 : ffffd000`5c555a80 ffffd000`5c555a80 ffffd000`5c555a80 00000000`00000102 : dxgmms1!VidSchiPrepareToResetEngine+0xf6
ffffd000`5c555910 fffff801`4ce06d1b : ffffe001`6298f510 ffffd000`5c555ac0 00000000`00000002 00000000`00000002 : dxgmms1!VidSchWaitForCompletionEvent+0x17741
ffffd000`5c5559c0 fffff801`4ce41d4a : ffffe001`67804000 ffffe001`67804000 ffffe001`6298f510 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x5bb
ffffd000`5c555b70 fffff801`4ce41d1d : ffffe001`67804000 00000000`00000080 ffffe001`67831880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`5c555bc0 fffff801`bd540794 : ffffd000`5a94c3c0 ffffe001`67831880 ffffd000`5c555c90 fffff801`bd5c837d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`5c555c00 fffff801`bd5cb5c6 : ffffd000`5a940180 ffffe001`67831880 ffffd000`5a94c3c0 ffffc000`12c12ed0 : nt!PspSystemThreadStartup+0x58
ffffd000`5c555c60 00000000`00000000 : ffffd000`5c556000 ffffd000`5c550000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

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

Additionnal Dump 2
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: ffffe00162f102a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8014d7b093c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000001438, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 2

BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`5c555760 fffff801`4d323b88 : ffffe001`62f102a0 ffffe001`62f102a0 ffffd000`5c555869 ffffe001`69424010 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`5c5557b0 fffff801`4ce189bb : ffffe001`00000000 ffffe001`62aa94a8 ffffe001`67802000 ffffe001`00000009 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`5c555800 fffff801`4ce5998b : ffffe001`67802000 00000000`00000000 00000000`00000001 ffffe001`67804001 : dxgmms1!VidSchiResetEngine+0x447
ffffd000`5c5558d0 fffff801`4ce4ec12 : ffffd000`5c555a80 ffffe001`67802000 00000000`00000102 ffffe001`67804000 : dxgmms1!VidSchiResetEngines+0x83
ffffd000`5c555910 fffff801`4ce06d1b : ffffe001`6298f510 ffffd000`5c555ac0 00000000`00000002 00000000`00000002 : dxgmms1!VidSchWaitForCompletionEvent+0x17752
ffffd000`5c5559c0 fffff801`4ce41d4a : ffffe001`67804000 ffffe001`67804000 ffffe001`6298f510 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x5bb
ffffd000`5c555b70 fffff801`4ce41d1d : ffffe001`67804000 00000000`00000080 ffffe001`67831880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`5c555bc0 fffff801`bd540794 : ffffd000`5a94c3c0 ffffe001`67831880 ffffd000`5c555c90 fffff801`bd5c837d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`5c555c00 fffff801`bd5cb5c6 : ffffd000`5a940180 ffffe001`67831880 ffffd000`5a94c3c0 ffffc000`12c12ed0 : nt!PspSystemThreadStartup+0x58
ffffd000`5c555c60 00000000`00000000 : ffffd000`5c556000 ffffd000`5c550000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

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


Additional dump file 3
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: ffffe00162f16010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8014d7b093c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 3

BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`5c555780 fffff801`4d323b88 : ffffe001`62f16010 ffffe001`62f16010 ffffd000`5c555889 ffffe001`693bb8f0 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`5c5557d0 fffff801`4ce189bb : 00000000`00000000 00000000`c00000bb ffffe001`625e1000 ffffe001`625e1000 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`5c555820 fffff801`4ce5998b : ffffe001`625e1000 00000000`00000000 00000000`00000001 ffffe001`625e1001 : dxgmms1!VidSchiResetEngine+0x447
ffffd000`5c5558f0 fffff801`4ce4d39c : ffffe001`625e1000 00000000`00000006 00000000`01312d00 ffffe001`625e1000 : dxgmms1!VidSchiResetEngines+0x83
ffffd000`5c555930 fffff801`4ce06ba8 : ffffe001`6298f510 ffffe001`6298f510 ffffd000`5c555ac0 00000000`00000002 : dxgmms1!VidSchiCheckHwProgress+0x1862c
ffffd000`5c5559c0 fffff801`4ce41d4a : ffffe001`67804000 ffffe001`67804000 ffffe001`6298f510 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x448
ffffd000`5c555b70 fffff801`4ce41d1d : ffffe001`67804000 00000000`00000080 ffffe001`67831880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`5c555bc0 fffff801`bd540794 : ffffd000`5a94c3c0 ffffe001`67831880 ffffd000`5c555c90 fffff801`bd5c837d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`5c555c00 fffff801`bd5cb5c6 : ffffd000`5a940180 ffffe001`67831880 ffffd000`5a94c3c0 ffffc000`12c12ed0 : nt!PspSystemThreadStartup+0x58
ffffd000`5c555c60 00000000`00000000 : ffffd000`5c556000 ffffd000`5c550000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

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


Additional Dump 4
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe00162f102a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8014d7b093c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 4

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`5c555a20 fffff801`4d323b88 : 00000000`00000002 ffffe001`62f102a0 00000000`80000000 ffffe001`67c48010 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`5c555a70 fffff801`4d32324d : ffffc000`00000000 ffffc000`19acfd90 00000000`00000002 ffffe001`67811bf8 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`5c555ac0 fffff801`4d318573 : ffffc000`1a0a3b8c ffffe001`67811540 ffffd000`5c555b20 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage2+0x1d9
ffffd000`5c555af0 fffff801`4d323919 : ffffe001`67800100 fffff801`4ce41e78 ffffe001`67804000 ffffe001`67804000 : dxgkrnl!DXGADAPTER::Reset+0x407
ffffd000`5c555b60 fffff801`4ce5afde : fffff801`4ce41c90 ffffe001`67804000 fffff801`bd471000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`5c555b90 fffff801`4ce41d1d : ffffe001`67804000 00000000`00000080 ffffe001`67831880 ffffe001`00000000 : dxgmms1!VidSchiRecoverFromTDR+0x1a
ffffd000`5c555bc0 fffff801`bd540794 : ffffd000`5a94c3c0 ffffe001`67831880 ffffd000`5c555c90 fffff801`bd5c837d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`5c555c00 fffff801`bd5cb5c6 : ffffd000`5a940180 ffffe001`67831880 ffffd000`5a94c3c0 ffffc000`12c12ed0 : nt!PspSystemThreadStartup+0x58
ffffd000`5c555c60 00000000`00000000 : ffffd000`5c556000 ffffd000`5c550000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+15393c
fffff801`4d7b093c ?? ???

SYMBOL_NAME: nvlddmkm+15393c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a

FAILURE_BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x117_image_nvlddmkm.sys

FAILURE_ID_HASH: {a93e9c2e-fca7-af48-d0f1-0cc77d4c6965}

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

 

vanor

Reputable
Sep 5, 2014
17
0
4,510
To be thorough I will be recreating the BF4 and Total Wars Rome 2 crash in the next few hours (I actually have to play BF4 a bit to get to crash location) and post those dumps as well to confirm same error code being reported (symptoms are the same so quite likely but what to confirm through test).
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
mmm Total Wars 2 doesn't generate a dump files. For that one the fan speed veers up, computer screen goes blank but the computer doesn't actually crash just seems to loop and loose display output (was in that state for 2 minutes before I manually restarted it).

I will recreate the BF4 crash event in the next hour (that one is a bit longer to recreate since I am no longer at the in game sequence were it crashes).

 

vanor

Reputable
Sep 5, 2014
17
0
4,510
Ok will try removing and re-installing display drivers. Will provide an update when it is done.

BF4 is generating same series of 5 dumps that 3DMARK11 was generating.

Will update after drivers uninstall and reinstall.
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
I am in the process of updating drivers.
I will do full uninstall and re-install and test of the following drivers until they either all fail or one works:
I will redo the 3DMARK11 test with

331.82
332.21
334.89
335.23
337.88
340.52

I am starting with 331.82 since that is the one that ASUS lists on it's driver software for the GTX 780 ti (I downloaded the drivers from NVIDIA)
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
Some improvement, managed to make it through 3DMARK11 1080 Benchmark Test 1 before crashing on Benchmark Test 2 (used to crash on test 1).

I did not instrall GEFORCE Game experience this time around with the drivers to avoid being asked to update the drivers.

Only 3 dump files this time around:

[First dump]
*******************************************************************************
* *
* 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: ffffe00181290010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8000c407e64, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000001264, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+152e64
fffff800`0c407e64 ?? ???

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.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`22046760 fffff800`0c000b88 : ffffe001`81290010 ffffe001`81290010 ffffd000`22046869 ffffe001`80d44490 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`220467b0 fffff800`0c0aa9bb : ffffe001`00000000 ffffe001`80e2f0a8 ffffe001`7f788000 ffffe001`0000000c : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`22046800 fffff800`0c0eb98b : ffffe001`7f788000 00000000`00000000 00000000`00000001 ffffe001`7ab7c001 : dxgmms1!VidSchiResetEngine+0x447
ffffd000`220468d0 fffff800`0c0e0c12 : ffffd000`22046a80 ffffe001`7f788000 00000000`00000102 ffffe001`7ab7c000 : dxgmms1!VidSchiResetEngines+0x83
ffffd000`22046910 fffff800`0c098d1b : ffffe001`81298a40 ffffd000`22046ac0 00000000`00000002 00000000`00000002 : dxgmms1!VidSchWaitForCompletionEvent+0x17752
ffffd000`220469c0 fffff800`0c0d3d4a : ffffe001`7ab7c000 ffffe001`7ab7c000 ffffe001`81298a40 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x5bb
ffffd000`22046b70 fffff800`0c0d3d1d : ffffe001`7ab7c000 00000000`00000080 ffffe001`7f76c500 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`22046bc0 fffff803`1deec794 : ffffd000`2064c3c0 ffffe001`7f76c500 ffffd000`22046c90 fffff803`1df7437d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`22046c00 fffff803`1df775c6 : ffffd000`20640180 ffffe001`7f76c500 ffffd000`2064c3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`22046c60 00000000`00000000 : ffffd000`22047000 ffffd000`22041000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+152e64
fffff800`0c407e64 ?? ???

SYMBOL_NAME: nvlddmkm+152e64

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75

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

Additional dump 1
*******************************************************************************
* *
* 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: ffffe0018136d4d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8000c407e64, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 000000000000028c, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+152e64
fffff800`0c407e64 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`220466e0 fffff800`0c000b88 : ffffe001`8136d4d0 ffffe001`8136d4d0 ffffd000`220467e9 ffffe001`80ddc8f0 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`22046730 fffff800`0c0aa9bb : 00000000`00000000 00000000`c00000bb ffffe001`7f788000 ffffe001`7f788000 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`22046780 fffff800`0c0eb98b : ffffe001`7f788000 00000000`00000000 00000000`00000001 ffffe001`7f788001 : dxgmms1!VidSchiResetEngine+0x447
ffffd000`22046850 fffff800`0c0df39c : ffffe001`7f788000 00000000`00000000 00000000`01312d00 ffffe001`7f788000 : dxgmms1!VidSchiResetEngines+0x83
ffffd000`22046890 fffff800`0c0c6d18 : ffffd000`00000002 00000000`00000102 00000000`00000002 ffffe001`7ab7c000 : dxgmms1!VidSchiCheckHwProgress+0x1862c
ffffd000`22046920 fffff800`0c098b99 : ffffffff`ff676980 00000000`00000000 ffffd000`22046ac0 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x278
ffffd000`220469c0 fffff800`0c0d3d4a : ffffe001`7ab7c000 ffffe001`7ab7c000 ffffe001`81273c70 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x439
ffffd000`22046b70 fffff800`0c0d3d1d : ffffe001`7ab7c000 00000000`00000080 ffffe001`7f76c500 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
ffffd000`22046bc0 fffff803`1deec794 : ffffd000`2064c3c0 ffffe001`7f76c500 ffffd000`22046c90 fffff803`1df7437d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`22046c00 fffff803`1df775c6 : ffffd000`20640180 ffffe001`7f76c500 ffffd000`2064c3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`22046c60 00000000`00000000 : ffffd000`22047000 ffffd000`22041000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+152e64
fffff800`0c407e64 ?? ???

SYMBOL_NAME: nvlddmkm+152e64

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75

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

Additional dump 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe00181327010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8000c407e64, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+152e64
fffff800`0c407e64 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 2

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

STACK_TEXT:
ffffd000`22046a20 fffff800`0c000b88 : 00000000`00000002 ffffe001`81327010 00000000`80000000 ffffe001`813298f0 : watchdog!WdDbgReportRecreate+0x10c
ffffd000`22046a70 fffff800`0c00024d : ffffc001`00000000 ffffc001`bb3d0890 00000000`00000002 ffffe001`7fb8bbf8 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd000`22046ac0 fffff800`0bff5573 : ffffc001`bb861749 ffffe001`7fb8b540 ffffd000`22046b20 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage2+0x1d9
ffffd000`22046af0 fffff800`0c000919 : ffffe001`7ab70100 fffff800`0c0d3e78 ffffe001`7ab7c000 ffffe001`7ab7c000 : dxgkrnl!DXGADAPTER::Reset+0x407
ffffd000`22046b60 fffff800`0c0ecfde : fffff800`0c0d3c90 ffffe001`7ab7c000 fffff803`1de1d000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd000`22046b90 fffff800`0c0d3d1d : ffffe001`7ab7c000 00000000`00000080 ffffe001`7f76c500 ffffe001`00000000 : dxgmms1!VidSchiRecoverFromTDR+0x1a
ffffd000`22046bc0 fffff803`1deec794 : ffffd000`2064c3c0 ffffe001`7f76c500 ffffd000`22046c90 fffff803`1df7437d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`22046c00 fffff803`1df775c6 : ffffd000`20640180 ffffe001`7f76c500 ffffd000`2064c3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`22046c60 00000000`00000000 : ffffd000`22047000 ffffd000`22041000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+152e64
fffff800`0c407e64 ?? ???

SYMBOL_NAME: nvlddmkm+152e64

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75

FAILURE_BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x117_image_nvlddmkm.sys

FAILURE_ID_HASH: {a93e9c2e-fca7-af48-d0f1-0cc77d4c6965}

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



Moving onward to test with 332.21...

 

vanor

Reputable
Sep 5, 2014
17
0
4,510
So far result with 3DMARK11 and different drivers:
331.82 Test 1, no tesselation ok, test 2 tesselation crashes at start).
332.21 Test 1, ok, test 2 works for 4-5 seconds crashes).
340.52 Test 1 -> crashes

340.52 is less stable the then other.

I still have to test 334.89, 335.23 amd 337.88

To remove I uninstall the nVidia Drivers and PhysX, restart computer, then reinstall only those two component (custom install) selecting a clean install and restarting computer followed by the test.

Result of the other tests to follow shortly
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
Well from nvidia.com

Drivers 331.82 passes test 1, fails at the beginning of test 2
Drivers 332.21 is the most stable passes test 1 and survives 11 second of test 2.
Drivers 334.89, 335.23, 337.88 and 340.52 all fails on test 1.

Will retry wit the drivers directly from the Asus website...
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
Well the Asus website is just using 331.82 (it seems fully identical to the one from nvidia.com).

Whether it is or not, it crashes at the start of test 2 just like nvidia.com.

332.21 is the least "unstable" I will install it and test it with H&G, BF4 and Total War: Rome 2 to see if it crashes at the same location then 340.52 fails.

Still unacceptable crash with 3DMARK11, the GTX 780ti should have no problem with the 1080 tests.

I still suspect a GPU issue. Any other suggestion of what I might test?
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
Don't understand what got you upset here.

My GPU is Asus GeForce GTX 780 Ti 3GB DDR5 Video Card GTX780TI-DC2OC-3GD5 and I did install the driver from ASUS from their website "http://dlcdnet.asus.com/pub/ASUS/vga/nVidia/NVDriver_Vista_Win7_Win8_Win8_1_64_VER331_82.zip".

If you meant something else, then you could have clarified it.

Either way I still appreciate the help you gave me so far. I learned a lot about reading windows 8 dumps so it was worth it for me even if the problem isn't resolved yet.

If anyone else as a suggestion or can clarify what kapitalistas meant and that I misinterpreted it is welcomed.




I installed y you are mad. But thanks anyway for your previous help. If anyone else as a suggestion, or could explian
 

vanor

Reputable
Sep 5, 2014
17
0
4,510


I really don't understand this one I have a GTX not an ATI (AMD). AMD drivers are for ATI not GTX (NVIDIA).

I have been testing only with NVIDIA drivers and ASUS, AMD/ATI drivers are irrelevant to my GPU. Anyway thanks for your initial help.

Anyway: Rome Total War still crashes with ASUS GTX 780 ti drivers 332.21.

I am going to try Rome 2 beta 15 patches to see if it makes any difference.

Will update once I've tested it.


 

vanor

Reputable
Sep 5, 2014
17
0
4,510
Prologue Campaign still crashes. Regular Campaign seems to work (actually need to test with other drivers version since I was focusing on Prologue Campaign crash only).

Testing BF4 to see if there is a change in stability with 332.21
 

vanor

Reputable
Sep 5, 2014
17
0
4,510
BF4 less seems less stable with 332.21, now having crash in location that was previously working fine.

Reverting back to 340.52 drivers for comparison (as well as testing Rome regular campaign map vs prologue)
 

getwrecked

Reputable
Oct 13, 2014
12
0
4,510
Ok Listen Up.
I searched for a VERY long time for a fix to this problem.
Basically its NOT the graphic card at all.
I replaced my graphic card with a completely new one of the same model (R9 280X)
I even replaced my RAM just to check if that would work.
The problem is to do with the OS, look IDK why but it is.
I rolled back drivers with no success, I changed hardware with no success.
The problem lies in the OS.
So if you re install Windows 7 (Put old files on a external HDD), then install all old driver as per usual. I GUARANTEE a 100% Fix.
Please reply to this.