THREAD_STUCK_IN_DEVICE_DRIVER_M mavi ekran hatası

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


Loading Dump File [C:\Users\maksu\Desktop\121320-218984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`3ea00000 PsLoadedModuleList = 0xfffff804`3ee461b0
Debug session time: Sun Dec 13 17:16:30.054 2020 (UTC + 3:00)
System Uptime: 0 days 1:01:52.818
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`3ebc3b20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff898c`fbac2ae0=00000000000000ea
1: 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: ffff8b8756a47080, 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:
------------------

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4014

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-G2EFLS9

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 74302

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  ea

BUGCHECK_P1: ffff8b8756a47080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff8b8756a47080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Corsair.Service.CpuIdRemote64.exe

STACK_TEXT: 
ffff898c`fbac2ad8 fffff804`47d70fb5     : 00000000`000000ea ffff8b87`56a47080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff898c`fbac2ae0 fffff804`47d7108e     : ffff898c`fbac2bc0 fffff804`47d4bf9b ffff898c`fbac2bc0 fffff804`4da1396c : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff898c`fbac2b50 fffff804`4d8de5e0     : 00000008`a519e92d fffff804`4da1396c 00000000`00000000 ffff8b87`4eae4000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff898c`fbac2b90 00000008`a519e92d     : fffff804`4da1396c 00000000`00000000 ffff8b87`4eae4000 00000000`00989680 : amdkmdag+0x6e5e0
ffff898c`fbac2b98 fffff804`4da1396c     : 00000000`00000000 ffff8b87`4eae4000 00000000`00989680 00000000`00000001 : 0x00000008`a519e92d
ffff898c`fbac2ba0 00000000`00000000     : ffff8b87`4eae4000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a396c


STACK_COMMAND:  .thread 0xffff8b8756a47080 ; kb

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.18362.1198

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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