dpc_watchdog_violation 蓝屏问题 频繁蓝屏，ntkrnlmp.exe

      重新搞了完全内存转储，上传新的dmp文件https://1drv.ms/u/s!Ag_FhimUVq78kdZ8GjZA1EnIIix1uw?e=doJBgA下面是win dbg的分析日志Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\jose\Desktop\082122-8953-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`6fa00000 PsLoadedModuleList = 0xfffff805`7062a250
Debug session time: Sun Aug 21 10:10:46.263 2022 (UTC + 8:00)
System Uptime: 0 days 8:29:05.031
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`6fdf88c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffce01`9747fc90=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: 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: fffff805706fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5405

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 33035

    Key  : Analysis.Init.CPU.mSec
    Value: 608

    Key  : Analysis.Init.Elapsed.mSec
    Value: 6582

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 93

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    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:  082122-8953-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff805706fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff9983bc416ee0 -- (.trap 0xffff9983bc416ee0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffe201fb004080
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8056fc345d0 rsp=ffff9983bc417070 rbp=0000000000000003
 r8=0000000000000000  r9=00000000000000e1 r10=fffff8056fd3a370
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiIpiSendRequestEx+0xb0:
fffff805`6fc345d0 8b87802d0000    mov     eax,dword ptr [rdi+2D80h] ds:00000000`00002d80=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

STACK_TEXT: 
ffffce01`9747fc88 fffff805`6fe2a998     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`706fb320 : nt!KeBugCheckEx
ffffce01`9747fc90 fffff805`6fc50fed     : 000001d7`b15756d8 ffffce01`971d9180 00000000`00000246 00000000`001dd442 : nt!KeAccumulateTicks+0x1dcbc8
ffffce01`9747fcf0 fffff805`6fc51591     : 00000000`001db600 00000000`0011c790 ffffce01`971d9180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffce01`9747fd40 fffff805`6fc4b403     : ffffce01`971d9180 00000000`00000000 fffff805`706317a0 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffce01`9747fe80 fffff805`6fc53e02     : ffff9983`bc416ee0 ffff9983`bc416f60 ffff9983`bc416f00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffce01`9747ff30 fffff805`6fcd9405     : 00000047`1ec94368 ffffe201`ca504e60 ffffe201`ca504f10 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffce01`9747ff60 fffff805`6fdfa36a     : ffff9983`bc416f60 ffffe201`ca504e60 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffce01`9747ffb0 fffff805`6fdfa8d7     : 00000000`c41af9ef ffffce01`971dc088 ffff9983`bc417011 00000000`00000003 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9983`bc416ee0 fffff805`6fc345d0     : 00000000`00000000 ffff9983`bc417129 00000000`00000001 fffffe80`0000818a : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9983`bc417070 fffff805`6fc534ac     : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000090 : nt!KiIpiSendRequestEx+0xb0
ffff9983`bc4170b0 fffff805`6fc531eb     : 00000000`00000004 00000000`00000000 ffffce01`971d9180 00000000`00000002 : nt!KxFlushEntireTb+0x1bc
ffff9983`bc417100 fffff805`6fd103be     : 00000000`00000000 00000000`00000000 fffff480`e8581800 00000000`00000000 : nt!KeFlushTb+0x7b
ffff9983`bc417160 fffff805`6fc1f621     : 00000000`00000000 00000000`00000000 fffffb80`072a4a30 fffffb80`072a4a30 : nt!MiFlushEntireTbDueToAttributeChange+0x3a
ffff9983`bc417250 fffff805`6fc736d5     : fffff805`70650b80 00000000`00000002 00000000`000000e1 00000000`00000000 : nt!MiChangePageAttributeBatch+0x91
ffff9983`bc4172c0 fffff805`6fc70458     : 00000000`00000002 ffffe201`f8bac9c0 00000000`00000000 ffffffff`ffffffff : nt!MiGetPageChain+0xd75
ffff9983`bc417500 fffff805`6fc6f9a8     : ffff9983`bc417690 fffff805`6fc55e94 00000000`00000000 00000000`00000000 : nt!MiResolvePrivateZeroFault+0x6e8
ffff9983`bc417630 fffff805`6fc6ed7d     : 00000000`c0000016 00000000`00000002 00000000`00000000 00000000`00000002 : nt!MiResolveDemandZeroFault+0x208
ffff9983`bc417720 fffff805`6fc6ce69     : ffff9983`bc417950 000001d0`0000001c 00000000`c0000016 00000000`00000000 : nt!MiDispatchFault+0x22d
ffff9983`bc417860 fffff805`6fe06a5e     : ffffe201`f1ecc080 ffffe201`f1ecc080 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x189
ffff9983`bc417a00 00007ffd`25b89db9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
000000cb`69ffeed0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`25b89db9


SYMBOL_NAME:  nt!KeAccumulateTicks+1dcbc8

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1889

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1dcbc8

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner      您好，A&K，前来提供帮助。您的dump文件显示了系统内核的问题，这是一个很普通的错误，可能是驱动程序导致的，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。
        您好，A&K，前来提供帮助。您的dump文件显示了系统内核的问题，这是一个很普通的错误，可能是驱动程序导致的，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。好的，
        不一定是硬件问题，但显卡及内存等硬件更有可能出问题，请先重新安装驱动程序来确认一下。
        好的，谢谢！我先回退了显卡的驱动，会和杀毒软件有关吗？我使用的MacAfee此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        如果有杀毒软件的话，可以暂时关闭一下看看，使用Windows安全中心即可。
       
        不客气，
        你好，今天出现了新的错误类型，ntoskrnl.wrong.symbols.exe，现在上传dmp文件，可以再看看是什么问题吗？谢谢https://1drv.ms/u/s!Ag_FhimUVq78kdZ-hEBICYdSEU9tAg?e=qcfNzl此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。