Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Eigene Dateien\Desktop\Bluescreens\021421-11921-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`57a00000 PsLoadedModuleList = 0xfffff806`5862a390
Debug session time: Sun Feb 14 00:31:15.832 2021 (UTC + 1:00)
System Uptime: 0 days 0:00:56.519
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`57df5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9387`bb5bd740=00000000000000ea
11: 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: ffffb90c09bde0c0, 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
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3342
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on MATISSE
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 60303
Key : Analysis.Memory.CommitPeak.Mb
Value: 91
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: ffffb90c09bde0c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffb90c09bde0c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9387`bb5bd738 fffff806`61a4324d : 00000000`000000ea ffffb90c`09bde0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9387`bb5bd740 fffff806`61a4332e : ffff9387`bb5bd820 fffff806`61a173bb ffff9387`bb5bd820 fffff806`68c1ac94 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff9387`bb5bd7b0 fffff806`68ae0d80 : 00000000`21d28979 fffff806`68c1ac94 00000000`00000000 ffffb90c`0930e000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff9387`bb5bd7f0 00000000`21d28979 : fffff806`68c1ac94 00000000`00000000 ffffb90c`0930e000 00000000`00989680 : amdkmdag+0x70d80
ffff9387`bb5bd7f8 fffff806`68c1ac94 : 00000000`00000000 ffffb90c`0930e000 00000000`00989680 00000000`00000001 : 0x21d28979
ffff9387`bb5bd800 00000000`00000000 : ffffb90c`0930e000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aac94
STACK_COMMAND: .thread 0xffffb90c09bde0c0 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.804
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
Treiber sind komplett aktuell, ich könnte natürlich auch mal nen älteren Treiber nutzen um zu schauen ob das was ändern würde. Ist doch aber trotzdem komisch dass die Graka selbst nach langen Stresstests usw. keine Fehler zeigt, naja.
