win11 专业版ntkrnlmp.exe导致蓝屏

Question

win11 专业版ntkrnlmp.exe导致蓝屏

陈弦笙 0

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToChakraJsProvider : false

-- Configuring repositories

  ----> Repository : LocalInstalled, Enabled: true

  ----> Repository : UserExtensions, Enabled: true

Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.016 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 45

Microsoft (R) Windows Debugger Version 10.0.27920.1001 AMD64

Loading Dump File [C:\Windows\Minidump\100525-21718-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 22621 MP (24 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0xfffff8036ee00000 PsLoadedModuleList = 0xfffff8036fa13580

Debug session time: Sun Oct 5 15:57:45.470 2025 (UTC + 8:00)

System Uptime: 0 days 5:53:34.219

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:

fffff8036f21de70 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcb01a3d2b9f0=0000000000000133

1: kd> !analyze -v

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

...............

                   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: fffff8036fb1d340, 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: 4000

Key  : Analysis.Elapsed.mSec

Value: 45017

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 26

Key  : Analysis.Init.CPU.mSec

Value: 328

Key  : Analysis.Init.Elapsed.mSec

Value: 275863

Key  : Analysis.Memory.CommitPeak.Mb

Value: 104

Key  : Analysis.Version.DbgEng

Value: 10.0.27920.1001

Key  : Analysis.Version.Description

Value: 10.2506.23.01 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2506.23.1

Key  : Bugcheck.Code.LegacyAPI

Value: 0x133

Key  : Bugcheck.Code.TargetModel

Value: 0x133

Key  : Dump.Attributes.AsUlong

Value: 0x1808

Key  : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key  : Dump.Attributes.ErrorCode

Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage

Value: 0

Key  : Failure.Bucket

Value: 0x133_DPC_nt!KeAccumulateTicks

Key  : Failure.Hash

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

Key  : Hypervisor.Enlightenments.ValueHex

Value: 0x1497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent

Value: 1

Key  : Hypervisor.Flags.ApicEnlightened

Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable

Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint

Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested

Value: 0

Key  : Hypervisor.Flags.CpuManager

Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi

Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled

Value: 1

Key  : Hypervisor.Flags.Epf

Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks

Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable

Value: 1

Key  : Hypervisor.Flags.MaxBankNumber

Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl

Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush

Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing

Value: 1

Key  : Hypervisor.Flags.Phase0InitDone

Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos

Value: 0

Key  : Hypervisor.Flags.RootScheduler

Value: 0

Key  : Hypervisor.Flags.SynicAvailable

Value: 1

Key  : Hypervisor.Flags.UseQpcBias

Value: 0

Key  : Hypervisor.Flags.Value

Value: 4853999

Key  : Hypervisor.Flags.ValueHex

Value: 0x4a10ef

Key  : Hypervisor.Flags.VpAssistPage

Value: 1

Key  : Hypervisor.Flags.VsmAvailable

Value: 1

Key  : Hypervisor.RootFlags.AccessStats

Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened

Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor

Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading

Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync

Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled

Value: 0

Key  : Hypervisor.RootFlags.IsHyperV

Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened

Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt

Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened

Value: 1

Key  : Hypervisor.RootFlags.Nested

Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor

Value: 1

Key  : Hypervisor.RootFlags.Value

Value: 1015

Key  : Hypervisor.RootFlags.ValueHex

Value: 0x3f7

Key  : Stack.Pointer

Value: ISR

Key  : WER.System.BIOSRevision

Value: 5.17.0.0

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8036fb1d340

FILE_IN_CAB: 100525-21718-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808

Kernel Generated Triage Dump

FAULTING_THREAD: 17

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffcb01a3d2b9e8 fffff8036f0c7dc5 : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx

ffffcb01a3d2b9f0 fffff8036f0c7491 : 0000476fb43d19b8 000000000014b78e 000000000014b78d 0000000000000000 : nt!KeAccumulateTicks+0x3d5

ffffcb01a3d2ba50 fffff8036f0c3bbf : 0000000000000018 0000000000001388 000000000014b700 00000000000c592a : nt!KiUpdateRunTime+0xd1

ffffcb01a3d2bc00 fffff8036f0c47a8 : 0000000000000000 0000000000000000 ffffcb01a3d11180 0000000000000000 : nt!KiUpdateTime+0x63f

ffffcb01a3d2bea0 fffff8036f0c406a : fffff8036fa60370 0000000000000001 0000000000000001 0000000000000002 : nt!KeClockInterruptNotify+0x228

ffffcb01a3d2bf40 fffff8036f12438c : 0000003164abfd2a ffffa88c4673d480 ffffa88c4673d530 fffff8036f21fe1b : nt!HalpTimerClockInterrupt+0x10a

ffffcb01a3d2bf70 fffff8036f22007a : ffffdb0c52e472a0 ffffa88c4673d480 0000000080000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x9c

ffffcb01a3d2bfb0 fffff8036f220947 : ffffdb0c58919f08 fffff8036f220954 0000000048fe21ad ffffdb0c52e47418 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffffdb0c52e47220 fffff8036f042e40 : ffffdb0c58919f08 fffff8036f1d6847 ffffdb0c52e47508 ffffa88c466baad2 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffdb0c52e473b0 fffff8036f1d6847 : ffffdb0c52e47508 ffffa88c466baad2 000000030000000e ffffa88c00000000 : nt!KeYieldProcessorEx+0x20

ffffdb0c52e473c0 fffff8036f0448cc : 0000000000000000 00000000490247bd ffffcb0100000000 ffffdb0c52e47540 : nt!KiSwapDirectoryTableBaseTarget+0x57

ffffdb0c52e47410 fffff8036f045b84 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExecuteAllDpcs+0x42c

ffffdb0c52e47950 fffff8036f222e7e : 0000000000000000 ffffcb01a3d11180 ffffa88c4677b080 ffffa88c7f336080 : nt!KiRetireDpcList+0x1b4

ffffdb0c52e47c00 0000000000000000 : ffffdb0c52e48000 ffffdb0c52e41000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

STACK_COMMAND: ~23 ; .cxr ; kb

SYMBOL_NAME: nt!KeAccumulateTicks+3d5

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.5983

BUCKET_ID_FUNC_OFFSET: 3d5

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

2 个答案

你的答案

Answer 1

DaveM121 802.2K 独立顾问

请上传您拥有的任何 minidump 文件，我会检查这些文件，看看它们是否能提供任何有关系统崩溃潜在原因的见解，请不要上传较大的 Memory.dmp 文件。

请注意，我无法从百度云盘下载，请使用其他云服务进行上传，如 OneDrive 或 www.lanzv.com

打开 Windows 文件资源管理器。

导航到 C:\Windows\Minidump

将所有 minidump 文件复制到您的桌面，然后将其压缩。

将 zip 文件上传到云（OneDrive、www.lanzv.com 等），然后选择共享这些文件并获取共享链接。

然后将链接发布到 zip 文件，以便我们帮您查看。

陈弦笙 0 信誉分

2025-10-06T08:50:56.2466667+00:00

100125-11046-01.txt请把txt改成dmp
DaveM121 802.2K 信誉分独立顾问

2025-10-06T08:58:27.0333333+00:00

那个 minidump 文件只是显示了一般错误，并没有列出导致崩溃的具体原因。

您的电脑是否只崩溃过一次？或者，如果这个问题持续存在，您是否还有其他 minidump 文件可以上传以供分析？
陈弦笙 0 信誉分

2025-10-06T09:40:27.69+00:00

所有崩溃都是DPC_WATCHDOG_VIOLATION (133)，我会继续留意后续的minidump文件，及上传
DaveM121 802.2K 信誉分独立顾问

2025-10-06T09:42:05.67+00:00

好的，如果您有新的 minidump 文件，我会在这里。
陈弦笙 0 信誉分

2025-10-11T16:02:48.05+00:00

这是今天的蓝屏文件
陈弦笙 0 信誉分

2025-10-11T16:03:32.4233333+00:00

101125-17281-01.txt Header 1 Header 2

Cell 1 Cell 2

Cell 3 Cell 4
陈弦笙 0 信誉分

2025-10-13T11:18:36.07+00:00

101325-15093-01.txt
陈弦笙 0 信誉分

2025-10-13T11:18:59.0066667+00:00

101325-17156-01.txt
陈弦笙 0 信誉分

2025-10-13T11:19:38.6566667+00:00

101325-15234-01.txt

Answer 2

陈弦笙 0

请将txt格式改成dmp

101125-17281-01.txt Header 1	Header 2
Cell 1	Cell 2
Cell 3	Cell 4

通过

win11 专业版ntkrnlmp.exe导致蓝屏

2 个答案

你的答案