Bluescreen Thread Stuck in Device Driver

HominiLupus schrieb:

Bitte den BSOD mit Stack Trace posten.

Zum Vergrößern anklicken....

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


Loading Dump File [C:\Windows\Minidump\032217-4437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
Machine Name:
Kernel base = 0xfffff803`5c491000 PsLoadedModuleList = 0xfffff803`5c790000
Debug session time: Wed Mar 22 12:33:34.293 2017 (UTC + 1:00)
System Uptime: 0 days 0:24:03.931
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {ffff820144fc16c0, 0, 0, 0}

*** 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+3f )

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

4: 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: ffff820144fc16c0, 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:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.953 (rs1_release_inmarket.170303-1614)

SYSTEM_MANUFACTURER: ASUS

SYSTEM_PRODUCT_NAME: All Series

SYSTEM_SKU: All

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2801

BIOS_DATE: 11/11/2015

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z97-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: ffff820144fc16c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: 44fc16c0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: f9e

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: TRIXX.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-IU4BAMO

ANALYSIS_SESSION_TIME: 03-23-2017 12:53:11.0007

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER: from fffff80562ad2d1f to fffff8035c5df7c0

STACK_TEXT:
ffffc180`1b429af8 fffff805`62ad2d1f : 00000000`000000ea ffff8201`44fc16c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffc180`1b429b00 fffff805`62ad2dde : ffffc180`1b429bd8 fffff805`66891958 ffffc180`1b429bd8 ffffc180`1b429cc0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f
ffffc180`1b429b70 fffff805`66835ac0 : ffff8201`44428000 00000000`00000000 ffffc180`1b429cc0 fffff805`66891944 : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffc180`1b429bb0 ffff8201`44428000 : 00000000`00000000 ffffc180`1b429cc0 fffff805`66891944 00000000`00002710 : atikmdag+0x55ac0
ffffc180`1b429bb8 00000000`00000000 : ffffc180`1b429cc0 fffff805`66891944 00000000`00002710 00000000`00000028 : 0xffff8201`44428000


STACK_COMMAND: .thread 0xffff820144fc16c0 ; kb

THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17

THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff805`62ad2d1f cc int 3

FAULT_INSTR_CODE: c48b48cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 58ba59cf

IMAGE_VERSION: 10.0.14393.953

FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME: 2017-03-22T11:33:34.000Z

OSBUILD: 14393

OSSERVICEPACK: 953

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-03-04 07:09:56

BUILDDATESTAMP_STR: 170303-1614

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.953

ANALYSIS_SESSION_ELAPSED_TIME: b37e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys

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

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

Zum Vergrößern anklicken....