- 惠普社区
- >
- Vader 的帖子
最新主题
2022-06-09
00:01:09
您好,今天晚上我又遇到这个故障,,不过幸运的是找到了dump文件,您能帮忙分析一下吗 Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 2200...
查看更多...
您好,今天晚上我又遇到这个故障,,不过幸运的是找到了dump文件,您能帮忙分析一下吗 Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff806`0cc00000 PsLoadedModuleList = 0xfffff806`0d829b90
Debug session time: Wed Jun 8 23:06:01.722 2022 (UTC + 8:00)
System Uptime: 0 days 0:10:28.518
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff806`0d016b40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff982`bd18e7c0=0000000000000116
15: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffa78906d87010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff806c7750600, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2546
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 23417
Key : Analysis.Init.CPU.mSec
Value: 999
Key : Analysis.Init.Elapsed.mSec
Value: 149671
Key : Analysis.Memory.CommitPeak.Mb
Value: 116
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 060822-13421-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffa78906d87010
BUGCHECK_P2: fffff806c7750600
BUGCHECK_P3: 0
BUGCHECK_P4: d
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffa78906d87010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 000000000000000d
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff982`bd18e7b8 fffff806`437087ae : 00000000`00000116 ffffa789`06d87010 fffff806`c7750600 00000000`00000000 : nt!KeBugCheckEx
fffff982`bd18e7c0 fffff806`43707e3d : fffff806`c7750600 ffffa789`06d87010 fffff982`bd18e8d9 00000000`00000006 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffff982`bd18e800 fffff806`70f14e29 : 00000000`00000006 ffffa789`068de000 01d87b49`445d5a07 00000000`009cb80f : dxgkrnl!TdrIsRecoveryRequired+0x19d
fffff982`bd18e830 fffff806`70f97144 : ffffa789`068de000 00000000`00000001 ffffa789`068de000 00000000`00000000 : dxgmms2!VidSchiReportHwHang+0x5e9
fffff982`bd18e940 fffff806`70f65abb : 00000000`00000000 00000000`00000000 00000000`00009c5d 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x31654
fffff982`bd18e9c0 fffff806`70edb949 : 00000000`00000000 ffffa789`068de000 fffff982`bd18eaf9 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x37b
fffff982`bd18ea90 fffff806`70f7d215 : ffffa789`04095000 ffffa789`068de000 ffffa789`04095010 ffffa789`049f2010 : dxgmms2!VidSchiScheduleCommandToRun+0x2f9
fffff982`bd18eb60 fffff806`70f7d1ca : ffffa789`068de400 fffff806`70f7d100 ffffa789`068de000 ffffa788`ee588000 : dxgmms2!VidSchiRun_PriorityTable+0x35
fffff982`bd18ebb0 fffff806`0ce579d5 : ffffa789`00dc6040 fffff806`00000001 ffffa789`068de000 00000000`00400000 : dxgmms2!VidSchiWorkerThread+0xca
fffff982`bd18ebf0 fffff806`0d01abf4 : ffffcb01`30498180 ffffa789`00dc6040 fffff806`0ce57980 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff982`bd18ec40 00000000`00000000 : fffff982`bd18f000 fffff982`bd189000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: atikmpag+10600
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}
Followup: MachineOwner
2022-06-05
10:56:51
您好,按照您的建议更新了一下amd的集显驱动(大版本号30),但今天早上又出现了黑屏的现象,强制重启开机后,AMD驱动自动回退到了上次安装的版本(大版本号22)。
2022-06-01
20:24:26
我购买的是暗影精灵6锐龙版,R7-4800H, 2060TI版本,去年购买了一台外接显示器(惠普 24mh)。连接之后经常出现使用外接屏幕看视频时,本机屏幕黑屏,外接屏幕图像停留在最后一帧(且发出噪音,应该也是音频的最后输出)。笔记本无法操作,只能强制重启。(期间更新过系统,和bios、驱动等,未有改善)