AnsweredAssumed Answered

Crash BSoD only when plays flash player or youtube video

Question asked by nvangelis on Nov 18, 2017
Latest reply on Nov 19, 2017 by nvangelis

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for atikmdag.sys

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )

 

 

Followup: MachineOwner

---------

 

 

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

 

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)

The device driver is spinning in an infinite loop, most likely waiting for

hardware to become idle. This usually indicates problem with the hardware

itself or with the device driver programming the hardware incorrectly.

If the kernel debugger is connected and running when watchdog detects a

timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()

and detailed message including bugcheck arguments will be printed to the

debugger. This way we can identify an offending thread, set breakpoints in it,

and hit go to return to the spinning code to debug it further. Because

KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck

information in this case. The arguments are already printed out to the kernel

debugger. You can also retrieve them from a global variable via

"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).

On MP machines it is possible to hit a timeout when the spinning thread is

interrupted by hardware interrupt and ISR or DPC routine is running at the time

of the bugcheck (this is because the timeout's work item can be delivered and

handled on the second CPU and the same time). If this is the case you will have

to look deeper at the offending thread's stack (e.g. using dds) to determine

spinning code which caused the timeout to occur.

Arguments:

Arg1: fffffa8004123060, Pointer to a stuck thread object.  Do .thread then kb on it to find

the hung location.

Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.

Arg3: 0000000000000000, Pointer to offending driver name.

Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

 

 

Debugging Details:

------------------

 

 

 

 

FAULTING_THREAD:  fffffa8004123060

 

 

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

 

 

CUSTOMER_CRASH_COUNT:  1

 

 

BUGCHECK_STR:  0xEA

 

 

PROCESS_NAME:  chrome.exe

 

 

CURRENT_IRQL:  0

 

 

LAST_CONTROL_TRANSFER:  from fffff88003c31f63 to fffff80002a90bc0

 

 

STACK_TEXT: 

fffff880`070cc288 fffff880`03c31f63 : 00000000`000000ea fffffa80`04123060 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

fffff880`070cc290 fffff880`03c32112 : fffff880`070cc360 fffff880`040dfa2b fffff880`070cc360 00000000`c0000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37

fffff880`070cc300 fffff880`03ef6f72 : 00000000`00000000 fffff880`040dfa10 fffff880`070cc480 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xbe

fffff880`070cc340 00000000`00000000 : fffff880`040dfa10 fffff880`070cc480 00000000`01c9c380 00000000`00000028 : atikmdag+0x2bf72

 

 

 

 

STACK_COMMAND:  .thread 0xfffffa8004123060 ; kb

 

 

FOLLOWUP_IP:

dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

fffff880`03c31f63 cc              int     3

 

 

SYMBOL_STACK_INDEX:  1

 

 

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

 

 

FOLLOWUP_NAME:  MachineOwner

 

 

MODULE_NAME: dxgkrnl

 

 

IMAGE_NAME:  dxgkrnl.sys

 

 

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

 

 

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

 

 

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

 

 

Followup: MachineOwner

Outcomes