重置了电脑都没有用，而且WiFi频繁消失 终止代码：DPC WATCHDOG VIOLATION Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\062222-13937-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 = 0xfffff803`73c00000 PsLoadedModuleList = 0xfffff803`7482a2b0 Debug session time: Wed Jun 22 22:04:51.572 2022 (UTC 8:00) System Uptime: 0 days 0:51:21.250 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................ Loading User Symbols Loading unloaded module list .............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`73ff7dd0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffff8400`b507fe20=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: fffff803748fb320, 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: 3593 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 66016 Key : Analysis.Init.CPU.mSec Value: 781 Key : Analysis.Init.Elapsed.mSec Value: 127083 Key : Analysis.Memory.CommitPeak.Mb Value: 98 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: 062222-13937-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff803748fb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED TRAP_FRAME: fffff901e864f610 -- (.trap 0xfffff901e864f610) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000004292cf80 rbx=0000000000000000 rcx=fffff901e864f7e0 rdx=fffff901e864f800 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80373ef9b5b rsp=fffff901e864f7a0 rbp=fffff901e864f920 r8=ffff8400b4d89280 r9=0000000000000000 r10=0000fffff803745a r11=ffff73ff22000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KeYieldProcessorEx 0x1b: fffff803`73ef9b5b 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: ffff8400`b507fe18 fffff803`74036fec : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffff8400`b507fe20 fffff803`73e5f203 : 000008f7`8e28f6b2 ffff8400`b4d89180 00000000`00000000 ffff8400`b4d89180 : nt!KeAccumulateTicks 0x1d558c ffff8400`b507fe80 fffff803`73e5ecea : ffff9a08`bbcead40 fffff901`e864f690 fffff803`7763fd00 00000003`00007101 : nt!KeClockInterruptNotify 0x453 ffff8400`b507ff30 fffff803`73e2d885 : ffff9a08`bbcead40 00000000`00000000 00000000`00000000 ffff9c09`200e7f99 : nt!HalpTimerClockIpiRoutine 0x1a ffff8400`b507ff60 fffff803`73ff987a : fffff901`e864f690 ffff9a08`bbcead40 000008e8`ad454e32 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffff8400`b507ffb0 fffff803`73ff9de7 : fffff901`00000000 00001f80`00ff02f4 00000000`00000001 fffff901`e864f7e0 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa fffff901`e864f610 fffff803`73ef9b5b : fffff901`e864f800 fffff803`745ab4c9 00000000`00000010 00000000`00000246 : nt!KiInterruptDispatchNoLockNoEtw 0x37 fffff901`e864f7a0 fffff803`745ab4c9 : 00000000`00000010 00000000`00000246 fffff901`e864f7d0 00000000`00000018 : nt!KeYieldProcessorEx 0x1b fffff901`e864f7b0 fffff803`745a9da5 : fffff901`4292cf80 ffff8400`b4d89180 ffff9a08`cf4efca0 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange 0x2d fffff901`e864f7e0 fffff803`73ea181e : ffff8400`b4d8c240 ffff9a08`bbfd7000 fffff901`e864fae0 ffff8400`00000002 : nt!IopLiveDumpCorralDpc 0x55 fffff901`e864f820 fffff803`73ea0b04 : 00000000`00000000 fffff803`73ee4535 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e fffff901`e864f990 fffff803`73ffb93e : ffffffff`00000000 ffff8400`b4d89180 ffff8400`b4d94440 ffff9a08`c3ded080 : nt!KiRetireDpcList 0x1f4 fffff901`e864fc20 00000000`00000000 : fffff901`e8650000 fffff901`e8649000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e SYMBOL_NAME: nt!KeAccumulateTicks 1d558c MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1766 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1d558c 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 ---------
您好，欢迎询问本站Dump文件显示是由ntkrnlmp.exe引发的异常。ntkrnlmp.exe错误较大的可能性是由于您的设备中安装了不兼容的驱动程序导致的。建议先进行一下"干净启动"，排除第三方应用程序冲突导致的问题https://support.microsoft.com/zh-cn/topic/
