链接：https://pan.baidu.com/s/1AkfRHSSem8H-cZu0Jnb3-g 提取码：1hrc Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\徐正真\Documents\WeChat Files\wxid_n5fh0f0k64lm22\FileStorage\File\2022-03\032422-9625-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff804`84200000 PsLoadedModuleList = 0xfffff804`84e2a2d0 Debug session time: Thu Mar 24 16:58:33.713 2022 (UTC 8:00) System Uptime: 1 days 0:02:55.673 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 -v nt!KeBugCheckEx: fffff804`845f7620 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffce07`2585a640=0000000000000113 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 000000000000002b, The subtype of the BugCheck: Arg2: ffffe70fb5dd6820 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2156 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 453609 Key : Analysis.Init.CPU.mSec Value: 624 Key : Analysis.Init.Elapsed.mSec Value: 336045 Key : Analysis.Memory.CommitPeak.Mb Value: 96 Key : DirectX.FatalError.Code Value: 2b Key : DirectX.FatalError.Desc Value: CORRUPTED_LIST FILE_IN_CAB: 032422-9625-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 113 BUGCHECK_P1: 2b BUGCHECK_P2: ffffe70fb5dd6820 BUGCHECK_P3: 0 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe STACK_TEXT: ffffce07`2585a638 fffff804`9bd63ad0 : 00000000`00000113 00000000`0000002b ffffe70f`b5dd6820 00000000`00000000 : nt!KeBugCheckEx ffffce07`2585a640 fffff804`9bb4e838 : ffffe70f`b5dd6820 ffffe70f`b5dd6a01 ffffe70f`b5dd6a01 ffffce07`2585a740 : watchdog!WdLogEvent5_WdCriticalError 0xe0 ffffce07`2585a680 fffff804`9ba9461c : ffffe70f`b5dd6820 ffffe70f`b7a69540 ffffe70f`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState 0xb9a60 ffffce07`2585a6c0 fffff804`9ba941c7 : ffffe70f`b5dd6820 ffffa38d`fc07e8a0 ffffe70f`b5dd6820 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDevice 0xd8 ffffce07`2585a6f0 fffff804`9ba94066 : ffffe70f`b5dd6820 ffffa38d`00000001 ffffe70f`b5dd6820 ffffe70f`b5dd6820 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocksInternal 0x83 ffffce07`2585a800 fffff804`9ba93f78 : ffffe70f`b5dd6820 ffffce07`2585aa80 00000000`000000f4 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocks 0x92 ffffce07`2585a830 fffff804`9ba938cb : 01d83f5d`5754ff9e ffffa38e`739da0c0 00000000`00000000 00000000`00000020 : dxgkrnl!DxgkDestroyDeviceImpl 0x31c ffffce07`2585a9d0 fffff804`84608fb5 : ffffa38e`739da0c0 ffffa38e`739da0c0 00000000`00000000 ffffa38e`755a7ed0 : dxgkrnl!DxgkDestroyDevice 0xb ffffce07`2585aa00 00007ffc`2b874a24 : 00007ffc`24473c9a 000002ba`d079b288 000002ba`d079a300 000002ba`d079b288 : nt!KiSystemServiceCopyEnd 0x25 000000cb`c0efb578 00007ffc`24473c9a : 000002ba`d079b288 000002ba`d079a300 000002ba`d079b288 000002ba`d079a2f0 : 0x00007ffc`2b874a24 000000cb`c0efb580 000002ba`d079b288 : 000002ba`d079a300 000002ba`d079b288 000002ba`d079a2f0 000002ba`d07b77e8 : 0x00007ffc`24473c9a 000000cb`c0efb588 000002ba`d079a300 : 000002ba`d079b288 000002ba`d079a2f0 000002ba`d07b77e8 00007ffc`24461b79 : 0x000002ba`d079b288 000000cb`c0efb590 000002ba`d079b288 : 000002ba`d079a2f0 000002ba`d07b77e8 00007ffc`24461b79 000002ba`d07b7ea8 : 0x000002ba`d079a300 000000cb`c0efb598 000002ba`d079a2f0 : 000002ba`d07b77e8 00007ffc`24461b79 000002ba`d07b7ea8 00000000`00000000 : 0x000002ba`d079b288 000000cb`c0efb5a0 000002ba`d07b77e8 : 00007ffc`24461b79 000002ba`d07b7ea8 00000000`00000000 000000cb`c0efb970 : 0x000002ba`d079a2f0 000000cb`c0efb5a8 00007ffc`24461b79 : 000002ba`d07b7ea8 00000000`00000000 000000cb`c0efb970 000000cb`c0efb9d8 : 0x000002ba`d07b77e8 000000cb`c0efb5b0 000002ba`d07b7ea8 : 00000000`00000000 000000cb`c0efb970 000000cb`c0efb9d8 000002ba`cbc8a680 : 0x00007ffc`24461b79 000000cb`c0efb5b8 00000000`00000000 : 000000cb`c0efb970 000000cb`c0efb9d8 000002ba`cbc8a680 00007ffc`24461b29 : 0x000002ba`d07b7ea8 SYMBOL_NAME: dxgkrnl!DXGDEVICE::DestroyAllDeviceState b9a60 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.19041.1586 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: b9a60 FAILURE_BUCKET_ID: 0x113_2B_dxgkrnl!DXGDEVICE::DestroyAllDeviceState OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f86e2aa1-b3d9-2720-0764-350120287324} Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 000000000000002b, The subtype of the BugCheck: Arg2: ffffe70fb5dd6820 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1812 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1822 Key : Analysis.Init.CPU.mSec Value: 2780 Key : Analysis.Init.Elapsed.mSec Value: 789656 Key : Analysis.Memory.CommitPeak.Mb Value: 96 Key : DirectX.FatalError.Code Value: 2b Key : DirectX.FatalError.Desc Value: CORRUPTED_LIST FILE_IN_CAB: 032422-9625-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 113 BUGCHECK_P1: 2b BUGCHECK_P2: ffffe70fb5dd6820 BUGCHECK_P3: 0 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe STACK_TEXT: ffffce07`2585a638 fffff804`9bd63ad0 : 00000000`00000113 00000000`0000002b ffffe70f`b5dd6820 00000000`00000000 : nt!KeBugCheckEx ffffce07`2585a640 fffff804`9bb4e838 : ffffe70f`b5dd6820 ffffe70f`b5dd6a01 ffffe70f`b5dd6a01 ffffce07`2585a740 : watchdog!WdLogEvent5_WdCriticalError 0xe0 ffffce07`2585a680 fffff804`9ba9461c : ffffe70f`b5dd6820 ffffe70f`b7a69540 ffffe70f`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState 0xb9a60 ffffce07`2585a6c0 fffff804`9ba941c7 : ffffe70f`b5dd6820 ffffa38d`fc07e8a0 ffffe70f`b5dd6820 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDevice 0xd8 ffffce07`2585a6f0 fffff804`9ba94066 : ffffe70f`b5dd6820 ffffa38d`00000001 ffffe70f`b5dd6820 ffffe70f`b5dd6820 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocksInternal 0x83 ffffce07`2585a800 fffff804`9ba93f78 : ffffe70f`b5dd6820 ffffce07`2585aa80 00000000`000000f4 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocks 0x92 ffffce07`2585a830 fffff804`9ba938cb : 01d83f5d`5754ff9e ffffa38e`739da0c0 00000000`00000000 00000000`00000020 : dxgkrnl!DxgkDestroyDeviceImpl 0x31c ffffce07`2585a9d0 fffff804`84608fb5 : ffffa38e`739da0c0 ffffa38e`739da0c0 00000000`00000000 ffffa38e`755a7ed0 : dxgkrnl!DxgkDestroyDevice 0xb ffffce07`2585aa00 00007ffc`2b874a24 : 00007ffc`24473c9a 000002ba`d079b288 000002ba`d079a300 000002ba`d079b288 : nt!KiSystemServiceCopyEnd 0x25 000000cb`c0efb578 00007ffc`24473c9a : 000002ba`d079b288 000002ba`d079a300 000002ba`d079b288 000002ba`d079a2f0 : 0x00007ffc`2b874a24 000000cb`c0efb580 000002ba`d079b288 : 000002ba`d079a300 000002ba`d079b288 000002ba`d079a2f0 000002ba`d07b77e8 : 0x00007ffc`24473c9a 000000cb`c0efb588 000002ba`d079a300 : 000002ba`d079b288 000002ba`d079a2f0 000002ba`d07b77e8 00007ffc`24461b79 : 0x000002ba`d079b288 000000cb`c0efb590 000002ba`d079b288 : 000002ba`d079a2f0 000002ba`d07b77e8 00007ffc`24461b79 000002ba`d07b7ea8 : 0x000002ba`d079a300 000000cb`c0efb598 000002ba`d079a2f0 : 000002ba`d07b77e8 00007ffc`24461b79 000002ba`d07b7ea8 00000000`00000000 : 0x000002ba`d079b288 000000cb`c0efb5a0 000002ba`d07b77e8 : 00007ffc`24461b79 000002ba`d07b7ea8 00000000`00000000 000000cb`c0efb970 : 0x000002ba`d079a2f0 000000cb`c0efb5a8 00007ffc`24461b79 : 000002ba`d07b7ea8 00000000`00000000 000000cb`c0efb970 000000cb`c0efb9d8 : 0x000002ba`d07b77e8 000000cb`c0efb5b0 000002ba`d07b7ea8 : 00000000`00000000 000000cb`c0efb970 000000cb`c0efb9d8 000002ba`cbc8a680 : 0x00007ffc`24461b79 000000cb`c0efb5b8 00000000`00000000 : 000000cb`c0efb970 000000cb`c0efb9d8 000002ba`cbc8a680 00007ffc`24461b29 : 0x000002ba`d07b7ea8 SYMBOL_NAME: dxgkrnl!DXGDEVICE::DestroyAllDeviceState b9a60 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.19041.1586 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: b9a60 FAILURE_BUCKET_ID: 0x113_2B_dxgkrnl!DXGDEVICE::DestroyAllDeviceState OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f86e2aa1-b3d9-2720-0764-350120287324} Followup: MachineOwner ---------
您好！感谢您联系本站，日志显示，您的蓝屏错误与显卡驱动有关，建议您重新安装显卡驱动。请勿发布个人信息，例如你的电子邮件地址、电话号码、产品密钥、密码、信用卡号或可能损害你的隐私的任何其他信息。重视您的反馈，请点击下方''是''或''否''按钮，指出此是否解决了您的问题，以便其他相似提问的本站成员参考。
