THREAD_STUCK_IN_DEVICE_DRIVER_M mavi ekran hatası

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: ffffd58d9cb1f640, 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:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6109

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 50669

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 83

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  ea

BUGCHECK_P1: ffffd58d9cb1f640

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffffd58d9cb1f640

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MSIAfterburner.exe

STACK_TEXT:
fffff10b`5e44b768 fffff807`55c4289d     : 00000000`000000ea ffffd58d`9cb1f640 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff10b`5e44b770 fffff807`55c4297e     : fffff10b`5e44b850 fffff807`55c1727b fffff10b`5e44b850 fffff807`619017e0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
fffff10b`5e44b7e0 fffff807`617ccf30     : 00000017`07ecbf9b fffff807`619017e0 00000000`00000000 ffffd58d`89058000 : dxgkrnl!TdrTimedOperationDelay+0xce
fffff10b`5e44b820 00000017`07ecbf9b     : fffff807`619017e0 00000000`00000000 ffffd58d`89058000 00000000`00989680 : amdkmdag+0x6cf30
fffff10b`5e44b828 fffff807`619017e0     : 00000000`00000000 ffffd58d`89058000 00000000`00989680 00000000`00000001 : 0x00000017`07ecbf9b
fffff10b`5e44b830 00000000`00000000     : ffffd58d`89058000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a17e0


STACK_COMMAND:  .thread 0xffffd58d9cb1f640 ; kb

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.685

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

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

OS_VERSION:  10.0.19041.1

IMAGE_VERSION:  10.0.19041.685