积极答复者
Win10蓝屏，麻烦帮看一下dump代码
问题
-
Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`38c00000 PsLoadedModuleList = 0xfffff807`39048170
Debug session time: Thu Nov 28 11:58:22.506 2019 (UTC + 8:00)
System Uptime: 0 days 6:03:56.387
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`38dc14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8709`a98845a0=00000000000000ea
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffff9007356944c0, 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 this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on HAHAHA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 158
Key : Analysis.Memory.CommitPeak.Mb
Value: 63
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: ea
BUGCHECK_P1: ffff9007356944c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff9007356944c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8709`a9884598 fffff807`42d40db5 : 00000000`000000ea ffff9007`356944c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8709`a98845a0 fffff807`42d40e8e : ffff8709`a9884688 fffff807`42d1beab ffff8709`a9884688 ffff8709`a98846d0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff8709`a9884610 fffff807`484224da : 00000032`d796f16d ffff8709`a98846d0 00000000`00000000 ffff9007`343cb000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff8709`a9884650 fffff807`48417583 : ffff8709`00000402 fffff807`484bd380 00000000`a9060001 ffff8709`a9884728 : atikmdag+0x724da
ffff8709`a9884710 fffff807`484bd212 : ffff8709`a98847f1 00000000`00000000 00000000`000007d0 00000000`00000063 : atikmdag+0x67583
ffff8709`a9884750 fffff807`484be632 : 00000000`000007d0 00000000`0001629a 00000000`0000001f ffff9007`34fe3c54 : atikmdag+0x10d212
ffff8709`a9884840 fffff807`484c0d5a : ffff9007`357c65f4 00000000`00000000 ffffb6d6`8fbd54c1 fffff807`38c3b644 : atikmdag+0x10e632
ffff8709`a9884890 fffff807`484c08bb : ffff9007`357c65f4 ffff8709`a9884a60 00000000`00000001 fffff807`4965ee95 : atikmdag+0x110d5a
ffff8709`a98848d0 fffff807`496bf241 : ffff9007`357c65f4 00000000`00000000 00000000`00000001 fffff807`38c3ade5 : atikmdag+0x1108bb
ffff8709`a9884930 fffff807`4976eb84 : ffff9007`356944c0 00000000`00000000 ffff9007`34460000 fffff807`38d07a4a : atikmdag+0x130f241
ffff8709`a9884960 fffff807`484a5c2f : ffff9007`356fb390 ffff8709`000002fd ffff8709`a9884be8 ffff8709`a9884b20 : atikmdag+0x13beb84
ffff8709`a9884ad0 fffff807`484a9125 : ffff9007`34fdae60 ffff8709`a9884b79 ffff9007`356fb390 0c29736c`000aad60 : atikmdag+0xf5c2f
ffff8709`a9884b00 fffff807`484a516d : 00000000`00000008 00000000`00000000 ffff9007`34fd8000 00000000`000000ef : atikmdag+0xf9125
ffff8709`a9884be0 fffff807`38d2a7a5 : ffff9007`356944c0 fffff807`484a5158 ffff9007`34fdae60 00000404`ad9bbffe : atikmdag+0xf516d
ffff8709`a9884c10 fffff807`38dc8b2a : ffffe500`f2556180 ffff9007`356944c0 fffff807`38d2a750 a71d6df4`000a7d38 : nt!PspSystemThreadStartup+0x55
ffff8709`a9884c60 00000000`00000000 : ffff8709`a9885000 ffff8709`a987f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
STACK_COMMAND: .thread 0xffff9007356944c0 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
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
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffff9007356944c0, 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 this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on HAHAHA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 12
Key : Analysis.Memory.CommitPeak.Mb
Value: 65
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: ea
BUGCHECK_P1: ffff9007356944c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff9007356944c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8709`a9884598 fffff807`42d40db5 : 00000000`000000ea ffff9007`356944c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8709`a98845a0 fffff807`42d40e8e : ffff8709`a9884688 fffff807`42d1beab ffff8709`a9884688 ffff8709`a98846d0 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff8709`a9884610 fffff807`484224da : 00000032`d796f16d ffff8709`a98846d0 00000000`00000000 ffff9007`343cb000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff8709`a9884650 fffff807`48417583 : ffff8709`00000402 fffff807`484bd380 00000000`a9060001 ffff8709`a9884728 : atikmdag+0x724da
ffff8709`a9884710 fffff807`484bd212 : ffff8709`a98847f1 00000000`00000000 00000000`000007d0 00000000`00000063 : atikmdag+0x67583
ffff8709`a9884750 fffff807`484be632 : 00000000`000007d0 00000000`0001629a 00000000`0000001f ffff9007`34fe3c54 : atikmdag+0x10d212
ffff8709`a9884840 fffff807`484c0d5a : ffff9007`357c65f4 00000000`00000000 ffffb6d6`8fbd54c1 fffff807`38c3b644 : atikmdag+0x10e632
ffff8709`a9884890 fffff807`484c08bb : ffff9007`357c65f4 ffff8709`a9884a60 00000000`00000001 fffff807`4965ee95 : atikmdag+0x110d5a
ffff8709`a98848d0 fffff807`496bf241 : ffff9007`357c65f4 00000000`00000000 00000000`00000001 fffff807`38c3ade5 : atikmdag+0x1108bb
ffff8709`a9884930 fffff807`4976eb84 : ffff9007`356944c0 00000000`00000000 ffff9007`34460000 fffff807`38d07a4a : atikmdag+0x130f241
ffff8709`a9884960 fffff807`484a5c2f : ffff9007`356fb390 ffff8709`000002fd ffff8709`a9884be8 ffff8709`a9884b20 : atikmdag+0x13beb84
ffff8709`a9884ad0 fffff807`484a9125 : ffff9007`34fdae60 ffff8709`a9884b79 ffff9007`356fb390 0c29736c`000aad60 : atikmdag+0xf5c2f
ffff8709`a9884b00 fffff807`484a516d : 00000000`00000008 00000000`00000000 ffff9007`34fd8000 00000000`000000ef : atikmdag+0xf9125
ffff8709`a9884be0 fffff807`38d2a7a5 : ffff9007`356944c0 fffff807`484a5158 ffff9007`34fdae60 00000404`ad9bbffe : atikmdag+0xf516d
ffff8709`a9884c10 fffff807`38dc8b2a : ffffe500`f2556180 ffff9007`356944c0 fffff807`38d2a750 a71d6df4`000a7d38 : nt!PspSystemThreadStartup+0x55
ffff8709`a9884c60 00000000`00000000 : ffff8709`a9885000 ffff8709`a987f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
STACK_COMMAND: .thread 0xffff9007356944c0 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
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
---------
6: kd> !blackboxbsd
Version: 168
Product type: 1
Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progrees: FALSE
Power button timestamp: 0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d5a56d4408866f
Last reference time checksum: 0x5bb87fcb
Last update boot id: 11
Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0xc5
Last boot id: 11
Last successful shutdown boot id: 10
Last reported abnormal shutdown boot id: 10
Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info other error count: 0
Power button last press time: 0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0
6: kd> lmvm dxgkrnl
Browse full module list
start end module name
fffff807`42d00000 fffff807`43074000 dxgkrnl (pdb symbols) C:\ProgramData\Dbg\sym\dxgkrnl.pdb\B9A4B09FD13CC1B55C45BB0AFDB029921\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: B1B2A7DF (This is a reproducible build file hash, not a timestamp)
CheckSum: 0037704F
ImageSize: 00374000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
答案
-
你好，
根据您提供的信息，可以看到有关的信息：
image name:dxgkrnl.sys
Error:THREAD_STUCK_IN_DEVICE_DRIVER (ea)
Stack text: ffff8709`a9884960 fffff807`484a5c2f : ffff9007`356fb390 ffff8709`000002fd ffff8709`a9884be8 ffff8709`a9884b20 : atikmdag+0x13beb84
Related file: atikmdag.sys
这个BSOD错误通常是由外部显卡驱动程序在硬件之间产生冲突引起的。卸载您的显卡驱动，然后到厂商的官网，重新下载安装显卡的驱动程序。
同时可以到控制面板中，程序和功能选项中，查看是否有相关显卡驱动的控制软件，可以卸载掉。
希望对您有帮助，如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。
针对Windows 2008/2008R2的扩展支持将于2020年结束，之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》，把握良机完成云迁移并实现业务现代化。
- 已标记为答案 肥磅 2019年11月30日 2:24
- 已编辑 Carl FanMicrosoft contingent staff, Moderator 2020年1月17日 9:40
全部回复
-
你好，
根据您提供的信息，可以看到有关的信息：
image name:dxgkrnl.sys
Error:THREAD_STUCK_IN_DEVICE_DRIVER (ea)
Stack text: ffff8709`a9884960 fffff807`484a5c2f : ffff9007`356fb390 ffff8709`000002fd ffff8709`a9884be8 ffff8709`a9884b20 : atikmdag+0x13beb84
Related file: atikmdag.sys
这个BSOD错误通常是由外部显卡驱动程序在硬件之间产生冲突引起的。卸载您的显卡驱动，然后到厂商的官网，重新下载安装显卡的驱动程序。
同时可以到控制面板中，程序和功能选项中，查看是否有相关显卡驱动的控制软件，可以卸载掉。
希望对您有帮助，如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。
针对Windows 2008/2008R2的扩展支持将于2020年结束，之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》，把握良机完成云迁移并实现业务现代化。
- 已标记为答案 肥磅 2019年11月30日 2:24
- 已编辑 Carl FanMicrosoft contingent staff, Moderator 2020年1月17日 9:40
-
是不是在用 AIDA 64 提供的显卡跑分工具测评的时候会出问题？
Alexis Zhang
http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
本帖是回复帖，原帖作者是楼上的 "肥磅"
| Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
| Information from resource tables:
