通过

如何解决ntkrnlmp.exe蓝屏

luo jin 0 信誉分
2025-12-11T10:21:34.4366667+00:00 
************* 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.000 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: 46

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


Loading Dump File [E:\Users\luojin\Desktop\新建文件夹\121125-7656-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 26100 MP (10 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`eb200000 PsLoadedModuleList = 0xfffff802`ec0f4e70
Debug session time: Thu Dec 11 17:48:14.159 2025 (UTC + 8:00)
System Uptime: 0 days 1:37:19.874
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
PEB is paged out (Peb.Ldr = 00000006`d64f7018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`eb6f9280 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff300`4b5df6b0=000000000000001a
7: 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
PEB is paged out (Peb.Ldr = 00000006`d64f7018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003453, The subtype of the BugCheck.
Arg2: ffff9109103ed080
Arg3: 00000000007ad7ae
Arg4: 0000000000000003

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 968

    Key  : Analysis.Elapsed.mSec
    Value: 11942

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1a

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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: 0x1a_3453_nt!MiDeleteFinalPageTables

    Key  : Failure.Hash
    Value: {5341b5a0-5b02-2da1-51b3-df124a48f6f9}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    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: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    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  : WER.System.BIOSRevision
    Value: 5.32.0.0


BUGCHECK_CODE:  1a

BUGCHECK_P1: 3453

BUGCHECK_P2: ffff9109103ed080

BUGCHECK_P3: 7ad7ae

BUGCHECK_P4: 3

FILE_IN_CAB:  121125-7656-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9109028b2040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
fffff300`4b5df6a8 fffff802`eb65cf6a     : 00000000`0000001a 00000000`00003453 ffff9109`103ed080 00000000`007ad7ae : nt!KeBugCheckEx
fffff300`4b5df6b0 fffff802`ebad7bb3     : ffff9109`103ed080 ffff9109`103ed540 ffff9109`028b2040 00000000`00000000 : nt!MiDeleteFinalPageTables+0x20a
fffff300`4b5df780 fffff802`ebae1493     : ffff9109`103ed080 00000000`00000000 ffff9109`028b2040 ffff9109`103ed258 : nt!MmDeleteProcessAddressSpace+0x73
fffff300`4b5df7d0 fffff802`eba4ac9a     : ffff9109`103ed080 ffff9109`103ed050 00000000`00000000 ffff9109`103ed080 : nt!PspProcessDelete+0x183
fffff300`4b5df880 fffff802`eb457928     : 00000000`00000000 00000000`00000000 fffff300`4b5dfa50 ffff9109`103ed080 : nt!ObpRemoveObjectRoutine+0x11a
fffff300`4b5df8e0 fffff802`ebc9f25f     : ffff9109`103ed080 ffff9108`ef602ae0 fffff300`4b5dfa50 ffff9108`ef602ae0 : nt!ObfDereferenceObjectWithTag+0x108
fffff300`4b5df920 fffff802`eb504ddc     : ffff9109`028b2040 ffff9109`028b2000 ffff9108`ef602a00 ffff9109`00000004 : nt!PspProcessRundownWorkerSingle+0x3f
fffff300`4b5df950 fffff802`eb687c2a     : ffff9109`028b2040 ffff9109`028b2040 fffff802`eb5047f0 ffff9108`ef602ae0 : nt!ExpWorkerThread+0x5ec
fffff300`4b5dfb30 fffff802`eb8a0b24     : fffff802`7a3aa180 ffff9109`028b2040 fffff802`eb687bd0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff300`4b5dfb80 00000000`00000000     : fffff300`4b5e0000 fffff300`4b5d9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!MiDeleteFinalPageTables+20a

MODULE_NAME: nt

IMAGE_VERSION:  10.0.26100.6584

STACK_COMMAND: .process /r /p 0xffff9108ef4c4040; .thread 0xffff9109028b2040 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  20a

FAILURE_BUCKET_ID:  0x1a_3453_nt!MiDeleteFinalPageTables

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5341b5a0-5b02-2da1-51b3-df124a48f6f9}

Followup:     MachineOwner
---------
Windows 家庭版 | Windows 11 | 性能和系统故障
0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. DaveM121 813.6K 信誉分 独立顾问
    2025-12-11T10:56:24.89+00:00

    请上传您拥有的所有 minidump 文件，我会检查这些文件，看看能否找到系统崩溃的潜在原因。

    非常重要 - 请勿上传大型的 Memory.dmp 文件。

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

    打开 Windows 文件资源管理器。

    导航至 C:\Windows\Minidump 文件夹。

    将所有 minidump 文件复制到桌面，然后将它们压缩成 zip 文件。

    将 zip 文件上传到云端（例如 OneDrive），然后选择共享并获取共享链接。

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

    0 个注释

你的答案

提问者可以将答案标记为“已接受”，版主可以将答案标记为“已推荐”，这有助于用户了解答案是否解决了提问者的问题。