通过

如何解决蓝屏报错 PAGE_FAULT_IN_NONPAGED_AREA 失败操作FLTMGR.SYS

亚 刘 0 信誉分
2025-11-14T18:15:34.37+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.29457.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\111525-8375-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 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff804`23400000 PsLoadedModuleList = 0xfffff804`240298a0
Debug session time: Sat Nov 15 02:10:05.765 2025 (UTC + 8:00)
System Uptime: 0 days 0:40:26.521
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 = 0000002e`06c39018).  Type ".hh dbgerr001" for details
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`2381d780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffaf04`847e1750=0000000000000050
11: 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 = 0000002e`06c39018).  Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffb8, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
	bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the processor decided the fault was due to a corrupted PTE.
	bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
	- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8042058b4da, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 1687

    Key  : Analysis.Elapsed.mSec
    Value: 14724

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29457.1000

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 0x1008

    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: AV_W_(null)_FLTMGR!FltpGetFileName

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8042058b4da

    Key  : Failure.Exception.IP.Module
    Value: FLTMGR

    Key  : Failure.Exception.IP.Offset
    Value: 0x3b4da

    Key  : Failure.Hash
    Value: {53a02e9e-a0ff-8b73-2a08-a179b2e9ba0a}

    Key  : WER.System.BIOSRevision
    Value: 1.9.0.0


BUGCHECK_CODE:  50

BUGCHECK_P1: ffffffffffffffb8

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8042058b4da

BUGCHECK_P4: 2

FILE_IN_CAB:  111525-8375-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe70d48211080

READ_ADDRESS: fffff80424105450: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffb8 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  wuauclt.exe

STACK_TEXT:  
ffffaf04`847e1748 fffff804`238ea0a1     : 00000000`00000050 ffffffff`ffffffb8 00000000`00000002 ffffaf04`847e19f0 : nt!KeBugCheckEx
ffffaf04`847e1750 fffff804`23743636     : ffffaf04`847e1b60 00000000`00000002 ffffaf04`847e1950 00000000`00000000 : nt!MiSystemFault+0x189ff1
ffffaf04`847e1850 fffff804`2382e141     : ffffd70d`cd71e130 fffff804`23a8a5d4 ffffe70d`3436a030 ffffaf04`847e1b20 : nt!MmAccessFault+0x2a6
ffffaf04`847e19f0 fffff804`2058b4da     : ffffe70d`5e503e00 fffff804`23641969 00000000`0000000e ffffe70d`2e98c604 : nt!KiPageFault+0x341
ffffaf04`847e1b80 00000008`00000010     : 00000002`00000005 ffffd068`00a12184 ffffe70d`50571e50 00000000`00000000 : FLTMGR!FltpGetFileName+0x15a
ffffaf04`847e1c20 00000002`00000005     : ffffd068`00a12184 ffffe70d`50571e50 00000000`00000000 00000000`00004000 : 0x00000008`00000010
ffffaf04`847e1c28 ffffd068`00a12184     : ffffe70d`50571e50 00000000`00000000 00000000`00004000 ffffe70d`50571ef8 : 0x00000002`00000005
ffffaf04`847e1c30 ffffe70d`50571e50     : 00000000`00000000 00000000`00004000 ffffe70d`50571ef8 ffffe70d`50571ec3 : 0xffffd068`00a12184
ffffaf04`847e1c38 00000000`00000000     : 00000000`00004000 ffffe70d`50571ef8 ffffe70d`50571ec3 fffff804`2058cdc5 : 0xffffe70d`50571e50


SYMBOL_NAME:  FLTMGR!FltpGetFileName+15a

MODULE_NAME: FLTMGR

IMAGE_NAME:  FLTMGR.SYS

IMAGE_VERSION:  10.0.22000.2124

STACK_COMMAND: .process /r /p 0xffffe70d4ba020c0; .thread 0xffffe70d48211080 ; kb

BUCKET_ID_FUNC_OFFSET:  15a

FAILURE_BUCKET_ID:  AV_W_(null)_FLTMGR!FltpGetFileName

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {53a02e9e-a0ff-8b73-2a08-a179b2e9ba0a}

Followup:     MachineOwner
---------
Windows 家庭版 | Windows 11 | Windows 更新
0 个注释

2 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Igor Leyko 109.6K 信誉分 独立顾问
    2025-11-14T18:57:50.3266667+00:00

    你好

    我叫伊戈尔。我很高兴帮助别人，我会尽力帮助你。我只是一个试图提供可能对他人有帮助的见解和信息的同路用户。

    这是单个转储吗？所有转储都指向 FLTMGR 吗？

    如果是，请以管理员身份运行命令提示符并运行

    FLTMC 过滤器

    命令。然后使用 https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/allocated-altitudes 列表检查所有过滤器并尝试卸载非Microsoft工具。

    如果没有，请将多个内存小型转储共享到 OneDrive 进行分析。

    https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/how-to-post-crash-dumps-after-blue-screen-of-death/5b11c5c7-5903-45b8-8348-0fbee6b2ba6e

    0 个注释
  2. Igor Leyko 109.6K 信誉分 独立顾问
    2025-11-14T19:01:45.9266667+00:00

    正确的命令 fltmc filters

    0 个注释

你的答案

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