您好，我的电脑的蓝屏日志如下：Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\051122-14312-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 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff801`41000000 PsLoadedModuleList = 0xfffff801`41c2a290 Debug session time: Wed May 11 14:45:30.609 2022 (UTC 8:00) System Uptime: 0 days 0:42:10.297 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................................... Loading User Symbols Loading unloaded module list ........... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`413f7d50 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffae00`97e7fe20=0000000000000133 3: 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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: fffff80141cfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4108 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 162961 Key : Analysis.Init.CPU.mSec Value: 624 Key : Analysis.Init.Elapsed.mSec Value: 148670 Key : Analysis.Memory.CommitPeak.Mb Value: 99 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: 051122-14312-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff80141cfb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED TRAP_FRAME: ffffe982f684f610 -- (.trap 0xffffe982f684f610) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000004373de1c rbx=0000000000000000 rcx=ffffe982f684f7e0 rdx=ffffe982f684f800 rsi=0000000000000000 rdi=0000000000000000 rip=fffff801412f9b4b rsp=ffffe982f684f7a0 rbp=ffffe982f684f920 r8=ffffae0097b68280 r9=0000000000000000 r10=0000fffff801419a r11=ffff9dffa3200000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KeYieldProcessorEx 0x1b: fffff801`412f9b4b 5b pop rbx Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffae00`97e7fe18 fffff801`41436eec : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffae00`97e7fe20 fffff801`4125f393 : 0000075e`0e0703bc ffffae00`97b68180 00000000`00000000 ffffae00`97b68180 : nt!KeAccumulateTicks 0x1d52fc ffffae00`97e7fe80 fffff801`4125ee7a : ffffc502`8eb03d40 ffffe982`f684f690 fffff801`4362fd00 00000003`00007101 : nt!KeClockInterruptNotify 0x453 ffffae00`97e7ff30 fffff801`4122da15 : ffffc502`8eb03d40 00000000`00000000 00000000`00000000 ffffc2a4`851ce789 : nt!HalpTimerClockIpiRoutine 0x1a ffffae00`97e7ff60 fffff801`413f97fa : ffffe982`f684f690 ffffc502`8eb03d40 0000074f`2e31487c 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffae00`97e7ffb0 fffff801`413f9d67 : ffffe982`00000000 00001f80`003f0274 00000000`00000001 ffffe982`f684f7e0 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffe982`f684f610 fffff801`412f9b4b : ffffe982`f684f800 fffff801`419ab4e9 ffffc502`997ea318 ffffae00`97b68180 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffe982`f684f7a0 fffff801`419ab4e9 : ffffc502`997ea318 ffffae00`97b68180 ffffc502`997ea660 ffffe982`f684faf4 : nt!KeYieldProcessorEx 0x1b ffffe982`f684f7b0 fffff801`419a9dc5 : ffffe982`4373de1c ffffae00`97b68180 ffffc502`ac9cd950 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange 0x2d ffffe982`f684f7e0 fffff801`412a19ae : ffffae00`97b6b240 ffffc502`8edd4000 ffffe982`f6840400 ffffae00`00000002 : nt!IopLiveDumpCorralDpc 0x55 ffffe982`f684f820 fffff801`412a0c94 : 00000000`00000000 fffff801`412e46c5 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffffe982`f684f990 fffff801`413fb8be : ffffffff`00000000 ffffae00`97b68180 ffffae00`97b73440 ffffc502`ac47d280 : nt!KiRetireDpcList 0x1f4 ffffe982`f684fc20 00000000`00000000 : ffffe982`f6850000 ffffe982`f6849000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e SYMBOL_NAME: nt!KeAccumulateTicks 1d52fc MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1682 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1d52fc FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner ---------
欢迎咨询本站！Chen。没有看到具体的问题所在，通常是驱动的问题。建议到设备供应商的官网更新一下bios，覆盖安装一下所有的驱动，请勿使用第三方的驱动安装程序。完成后执行一下干净启动，排除其他干扰：https://support.microsoft.com/zh-cn/help/929135.先卸载设备中全部的第三方反病毒软件与系统优化软件(例如360、联想电脑管家、360桌面、腾讯电脑管家、腾讯桌面、鲁大师，代理，加速器，虚拟机等)。然后鼠标右键单击开始菜单→运行（RUN）→输入：msconfig（按下Enter键）点击上面的“服务”勾选下面的“隐藏所有Microsoft服务”（请务必勾选）点击“全部禁用”。然后鼠标右键单击开始菜单→任务管理器，（点击底部“详细信息”），点击顶部”启动”，鼠标右键单击“状态”显示为“已启动”的项，选择“禁用”。（禁用所有启动项。）然后鼠标右键单击开始按钮（图标的按钮）→"WindowsPowerShell(I)（管理员)(A）”→输入：（WIndows11中可能显示Windows终端（管理员））sfc/SCANNOW（按下Enter键）Dism/Online/Cleanup-Image/ScanHealth（按下Enter键）Dism/Online/Cleanup-Image/CheckHealth（按下Enter键）DISM/Online/Cleanup-image/RestoreHealth（按下Enter键）完成后重启电脑，再次输入：sfc/SCANNOW（按下Enter键）
