下面是DMP文件,希望能找到解决方案: Loading Dump File [C:\Windows\Minidump\070122-18750-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 22621 MP (8 procs) Free ARM 64-bit (AArch64) Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.4.arm64fre.ni_release_svc_oem.220531-1755 Machine Name: Kernel base = 0xfffff803`abe00000 PsLoadedModuleList = 0xfffff803`acadad10 Debug session time: Fri Jul 1 15:37:33.566 2022 (UTC 8:00) System Uptime: 2 days 17:17:54.990 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................................................ .................. Loading User Symbols Loading unloaded module list ................................................ For analysis of this file, run !analyze -v nt!KeBugCheck2 0x1dc: fffff803`ac052a2c 91010260 add x0,x19,#0x40 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff803acb19338, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 13358 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 17485 Key : Analysis.Init.CPU.mSec Value: 1452 Key : Analysis.Init.Elapsed.mSec Value: 11059 Key : Analysis.Memory.CommitPeak.Mb Value: 88 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.KiBugCheckData Value: 0x133 Key : WER.OS.Branch Value: ni_release_svc_oem Key : WER.OS.Timestamp Value: 2022-05-31T17:55:00Z Key : WER.OS.Version Value: 10.0.22621.4 FILE_IN_CAB: 070122-18750-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff803acb19338 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: ffffee829c6b2df0 -- (.trap 0xffffee829c6b2df0) Unable to read trap frame at ffffee82`9c6b2df0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff803`af902350 fffff803`ac053c40 : fffff803`af902930 fffff803`ac053c40 fffff803`ac010100 ffff8c8f`d2a9f080 : nt!KeBugCheck2 0x1dc fffff803`af902930 fffff803`ac05468c : fffff803`af902cf0 fffff803`ac05468c 00001b4c`0e1fd038 fffff803`ac054a08 : nt!KeAccumulateTicks 0x670 fffff803`af9029a0 fffff803`ac057270 : fffff803`aca40800 00000000`00e590bf fffff803`a8410000 00000000`0002625a : nt!KiUpdateTime 0x22c fffff803`af902d50 fffff803`ac017488 : 00000000`00000000 fffff803`a8418b80 00000000`00000000 00000000`00000000 : nt!KeClockInterruptNotify 0x3b0 fffff803`af902e10 fffff803`ac082c3c : fffff803`af902e60 fffff803`ac082c3c 0000041a`de270fdf 00000000`00000009 : nt!HalpTimerClockInterrupt 0x128 fffff803`af902e60 fffff803`ac06f25c : fffff803`af902f90 fffff803`ac06f25c fffff803`aca4aec0 fffff803`aca4aec8 : nt!KiCallInterruptServiceRoutine 0xa4 fffff803`af902ea0 fffff803`ac0084d4 : 0d0d0100`0b000001 00000001`00000100 00000000`00000000 00000000`00000001 : nt!KiPlayInterrupt 0x654 fffff803`af902ff0 fffff803`ac06f640 : 00000000`00000000 ffffee82`9c6b2d70 00000000`00000000 00000000`00000000 : nt!KxSwitchStackAndPlayInterrupt 0x1c ffffee82`9c6b2d80 fffff803`ac0028dc : ffffee82`9c6b2f30 fffff803`ac0028dc 00000003`00000013 00000013`00000000 : nt!KiProcessInterrupt 0x168 ffffee82`9c6b2df0 00000000`00000000 : 7072544b`08000000 00000000`00000000 ffffee82`9c6b2f40 fffff803`ac135014 : nt!KiKernelSp0InterruptHandler 0x5c SYMBOL_NAME: nt!KeAccumulateTicks 670 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.105 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 670 FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OS_VERSION: 10.0.22621.4 BUILDLAB_STR: ni_release_svc_oem OSPLATFORM_TYPE: arm64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Followup: MachineOwner ---------

您好,欢迎询问本站请上传您的本次蓝屏的dmp文件到百度网盘或者其他文件共享平台这个文件一般在C:\Windows\Minidump文件夹下


链接:https://pan.baidu.com/s/1X2kQBgp0V9bUTFvuZR27JA?pwd=77ca提取码:77ca谢谢此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


Dump文件显示是由ntkrnlmp.exe引发的异常。ntkrnlmp.exe错误较大的可能性是由于您的设备中安装了不兼容的驱动程序导致的。建议先进行一下"干净启动",排除第三方应用程序冲突导致的问题https://support.microsoft.com/zh-cn/topic/

点赞(17) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部