ntkrnlmp.exe导致win10电脑蓝屏死机。求助大神

Question

我的电脑经常在空闲模式（就是我鼠标键盘没有进行任何操作）下蓝屏，蓝屏界面显示DPC WATCHDOG VIOLATION，已断断续续有一年半左右，也使用windbg导出了崩溃日志，求大神解答，不胜感激！

下面是我做过的尝试，但是并没什么卵用：

1、重启电脑

2、更换内存条

3、关闭CPU超频

4、更新系统

崩溃日志如下：

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\052823-10828-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
Machine Name:
Kernel base = 0xfffff801`10a00000 PsLoadedModuleList = 0xfffff801`1162a2b0
Debug session time: Sun May 28 10:39:13.524 2023 (UTC + 8:00)
System Uptime: 0 days 0:34:44.891
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:
fffff801`10dfbca0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa380`fa3ffe20=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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff801116fb320, 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: 1952

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5174

    Key  : Analysis.IO.Other.Mb
    Value: 15

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 18

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  052823-10828-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff801116fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  AdskIdentityMa

STACK_TEXT:  
ffffa380`fa3ffe18 fffff801`10e43814     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`116fb320 : nt!KeBugCheckEx
ffffa380`fa3ffe20 fffff801`10c813c3     : 00000587`91349651 ffffa380`fa3aa180 00000000`00000000 ffffa380`fa3aa180 : nt!KeAccumulateTicks+0x1bfbf4
ffffa380`fa3ffe80 fffff801`10c80eaa     : ffffe38f`f5f03d40 ffff9f8d`983e75f0 00007ffe`771dc000 00000000`00000001 : nt!KeClockInterruptNotify+0x453
ffffa380`fa3fff30 fffff801`10d3e965     : ffffe38f`f5f03d40 00000000`00000000 00000000`00000000 ffff36ec`26d89adc : nt!HalpTimerClockIpiRoutine+0x1a
ffffa380`fa3fff60 fffff801`10dfdc3a     : ffff9f8d`983e75f0 ffffe38f`f5f03d40 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffa380`fa3fffb0 fffff801`10dfe407     : ffff9f8d`983e7590 00000000`00000000 ffffa380`fa3aa180 fffff801`10dfe414 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9f8d`983e7570 fffff801`10cde397     : ffffffff`ffffffd2 fffff801`10f1e601 00000000`00000010 00000000`00040282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9f8d`983e7700 fffff801`10f1e5fd     : 00000000`00000000 ffffe381`08873080 00000000`00000000 00000000`0000fff0 : nt!KeYieldProcessorEx+0x17
ffff9f8d`983e7730 fffff801`10f1e4c4     : 00000000`00000009 ffff9f8d`983e77f8 ffff9f8d`983e77f0 ffffa380`fa3aa180 : nt!KiSendHeteroRescheduleIntRequestHelper+0xed
ffff9f8d`983e77c0 fffff801`10e2459a     : ffffa380`ffffffff 00000000`00000000 ffffa380`fa74e180 00000000`00000000 : nt!KiSendHeteroRescheduleIntRequest+0x74
ffff9f8d`983e77f0 fffff801`10c1beef     : ffffe381`00000003 fffff801`00000001 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0x2080da
ffff9f8d`983e78a0 fffff801`10cda572     : 00000000`000000ca 00000000`00000000 ffffe381`00000001 0000016e`2f090000 : nt!KiCommitThreadWait+0x14f
ffff9f8d`983e7940 fffff801`110881ef     : 0000016e`2cca4908 00000000`00000000 ffffe381`0696c000 ffff9f8d`00000002 : nt!KeDelayExecutionThread+0x122
ffff9f8d`983e79d0 fffff801`10e0f4f5     : 0000004f`2a4feef0 00000000`00000000 ffffffff`ffffd8f0 00000000`00000000 : nt!NtDelayExecution+0x5f
ffff9f8d`983e7a00 00007ffe`7ebad6e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000004f`2a4feda8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`7ebad6e4


SYMBOL_NAME:  nt!KeAccumulateTicks+1bfbf4

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1bfbf4

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner

Answer 1

Hello

In general this stop code is caused by faulty driver code that under certain conditions, does not complete its work within the allotted time frame.

Cast the address of the nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK to display information about it:

dt nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK fffff801116fb320

Use the !dpcs command to display the queued DPCs:

!dpcs

Or use some basic troubleshooting techniques:

If a driver is identified in the bug check message, to isolate the issue, disable the driver. Check with the manufacturer for driver updates.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x133.

Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example for Windows 10, you can get information about required hardware at Windows 10 Specifications.