ntkrnlmp.exe 导致电脑蓝屏每次都是在玩守望先锋几小时后

348 阅读 0 评论 56 点赞

      dmg文件下载链接：https://pan.baidu.com/s/18O7fyUdLX67kCOXM_K5MEw 提取码：2e7b 以下是 WinDbg分析Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\102422-12265-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`48200000 PsLoadedModuleList = 0xfffff800`48e2a270
Debug session time: Mon Oct 24 21:16:55.559 2022 (UTC + 8:00)
System Uptime: 0 days 19:33:41.219
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`485f90f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff8600`6014be20=0000000000000133
2: 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: fffff80048efb320, 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                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2234

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 2234

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

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

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

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

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

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

    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: 102422-12265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80048efb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Overwatch.exe

FAULTING_THREAD: 0000000000000017

STACK_TEXT:
ffff8600`6014be18 fffff800`486597fe     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff8600`6014be20 fffff800`484d2973     : 000014f9`d5a1afca ffff8600`60200180 00000000`00000000 ffff8600`60200180 : nt!KeAccumulateTicks+0x18462e
ffff8600`6014be80 fffff800`484d245a     : ffffa682`3d7240e0 ffff8487`40247a20 fffff800`56a2d800 00000000`00006001 : nt!KeClockInterruptNotify+0x453
ffff8600`6014bf30 fffff800`48408a45     : ffffa682`3d7240e0 ffff8600`6014bf40 00000000`00000010 ffffe66f`ce03b8ef : nt!HalpTimerClockIpiRoutine+0x1a
ffff8600`6014bf60 fffff800`485fab9a     : ffff8487`40247a20 ffffa682`3d7240e0 000014e8`9ffd41b8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8600`6014bfb0 fffff800`485fb107     : ffffa682`4b403000 00000000`00000000 ffff8487`40247bb8 fffff800`485fb114 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8487`402479a0 fffff800`4841bfdd     : 00000000`00000010 00000000`00000286 ffff8487`40247b50 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8487`40247b30 fffff800`4852a779     : ffffa682`3dac7210 00000000`000008a8 00000000`00000f44 00000000`00400a02 : nt!KeYieldProcessorEx+0xd
ffff8487`40247b60 fffff800`4843489e     : ffff8600`60203240 ffffa682`489c19bf ffff8487`40247cb0 ffff8487`00000002 : nt!ExpGetPoolTagInfoTarget+0x149
ffff8487`40247bb0 fffff800`48433b84     : ffff8600`60200180 01d88baf`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x30e
ffff8487`40247d20 fffff800`48600165     : 00000000`00000000 ffff8600`60200180 00000000`00000000 00000000`00001928 : nt!KiRetireDpcList+0x1f4
ffff8487`40247fb0 fffff800`485fff50     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffff8487`48c9fa90 fffff800`485ff61e     : ffffa682`56406080 ffffa682`5c87a2e0 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffff8487`48c9fac0 00007ff8`45b0e092     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee
000000f2`d7dffc10 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`45b0e092

STACK_COMMAND: ~23 ; .cxr ; kb

SYMBOL_NAME: nt!KeAccumulateTicks+18462e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2130

BUCKET_ID_FUNC_OFFSET: 18462e

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner
---------      您电脑的型号是什么呢？？可以到您电脑制造商的官网，下载所有最新版本的驱动更新一下。（蓝牙+芯片组+网卡+声卡+显卡+BIOS）（建议不要使用第三方软件更新驱动）如果您不了解您电脑的型号，您可按查找》输入“系统信息”（SystemInformation）》在主页的SystemSummary（系统摘要）下，截图或拍张照片上传上来吗？？（以方便我帮您查找您电脑制造商的最新驱动下载链接，然后发那链接给您。）
        你好，我刚刚在玩了一小时守望先锋后又蓝屏了一次。这是dmp下载地址以及系统信息截图：链接：https://pan.baidu.com/s/1kJPAcgfun_31dXnXskkAPQ提取码：r5ea
        您好！您可到以下的连接，下载所有最新版本的驱动更新一下，然后重启电脑：（蓝牙+芯片组+网卡+声卡+显卡+BIOS）（建议不要使用第三方软件更新驱动）https://www.asus.com.cn/Motherboards-Components.
        你好，我会在下班后尝试更新驱动。你能否从我发的dmp日志文件中找出蓝屏出现的原因？我担心驱动不是真正问题所在此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        您好！之前那dmp文件显示驱动所导致，通常蓝屏80%是因驱动所导致，而20%是因硬件损坏所导致，您更新了驱动之后观察一两天看看如何。此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。

点赞(56) 打赏

本文分类：操作系统
本文标签：ntkrnlmp.exe 导致电脑蓝屏每次都是在玩守望先锋几小时后 win10更新以后蓝屏 2020win10更新后一直蓝屏 win10更新以后一直蓝屏 win10更新后不断蓝屏
浏览次数：348 次浏览
发布日期：2022-11-12 03:33:06
本文链接：https://yunkanjia.com/system/ntkrnlmp-exe-dao-zhi-dian-nao-lan-ping-mei-ci-dou-shi-zai-wan-shou-wang-xian-feng-ji-xiao-shi-hou.html

上一篇 > 电脑经常蓝屏重启，什么原因导致的？
下一篇 > 指纹和密码无法使用

ntkrnlmp.exe 导致电脑蓝屏 每次都是在玩守望先锋几小时后

微信扫一扫：分享

process_name: system image_name: ntkrnlmp.exe 导致蓝屏重启

explorer不断重启

蓝屏：system_thread_exception_not_handled

更新windows11 后不断蓝屏

微信扫一扫：分享

ntkrnlmp.exe 导致电脑蓝屏每次都是在玩守望先锋几小时后