如何解决最近的频繁蓝屏？错误代码50

旗紋 幡門 0 信誉分
2024-04-10T21:45:50.2066667+00:00

以下为WinDbg查看Dump文件的结果，不知能否看出问题所在，非常感谢：

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

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : 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.032 seconds

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

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

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\041024-8718-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 (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0xfffff806`5c200000 PsLoadedModuleList = 0xfffff806`5ce2a730

Debug session time: Wed Apr 10 15:07:10.199 2024 (UTC + 8:00)

System Uptime: 0 days 4:43:32.967

Loading Kernel Symbols

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

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

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

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

Loading User Symbols

PEB is paged out (Peb.Ldr = 0000002b`7c025018).  Type ".hh dbgerr001" for details

Loading unloaded module list

......

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff806`5c5fd890 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff8782`19d3eb80=0000000000000050

7: kd> !analyze -v

*******************************************************************************

*                                                                             *

* 
  ```dockerfile
                     Bugcheck Analysis                                    *
  ```* 
  ```sql
                                                                          *
  ```*******************************************************************************

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: fffff0065ce53940, memory referenced.

Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.

```python
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: fffff8065c43bf59, If non-zero, the instruction address which referenced the bad memory

address.


Debugging Details:

------------------

KEY_VALUES_STRING: 1

```scala
Key  : AV.Type

Value: Read

Key  : Analysis.CPU.mSec

Value: 3343

Key  : Analysis.Elapsed.mSec

Value: 9319

Key  : Analysis.IO.Other.Mb

Value: 9

Key  : Analysis.IO.Read.Mb

Value: 0

Key  : Analysis.IO.Write.Mb

Value: 26

Key  : Analysis.Init.CPU.mSec

Value: 812

Key  : Analysis.Init.Elapsed.mSec

Value: 450587

Key  : Analysis.Memory.CommitPeak.Mb

Value: 95

Key  : Bugcheck.Code.LegacyAPI

Value: 0x50

Key  : Bugcheck.Code.TargetModel

Value: 0x50

Key  : Dump.Attributes.AsUlong

Value: 8

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Failure.Bucket

Value: AV_R_(null)_Npfs!NpCommonCleanup

Key  : Failure.Hash

Value: {255b6694-3299-dd29-fe63-b7b3422f7a57}
```BUGCHECK_CODE:  50

BUGCHECK_P1: fffff0065ce53940

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8065c43bf59

BUGCHECK_P4: 2

FILE_IN_CAB:  041024-8718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8

  Kernel Generated Triage Dump

READ_ADDRESS: fffff8065cefb390: 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

 fffff0065ce53940 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffff878219d3ee20 -- (.trap 0xffff878219d3ee20)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=00000000000000c6 rbx=0000000000000000 rcx=fffff8065c200000

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8065c43bf59 rsp=ffff878219d3efb0 rbp=0000000000000000

 r8=0000000000000001  r9=0000000000000070 r10=0000000000000001

r11=ffff878219d3f040 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl nz ac pe nc

nt!PspReturnQuota+0x49:

fffff806`5c43bf59 488b1f          mov     rbx,qword ptr [rdi] ds:00000000`00000000=????????????????

Resetting default scope

STACK_TEXT:  

ffff8782`19d3eb78 fffff806`5c63bf7d     : 00000000`00000050 fffff006`5ce53940 00000000`00000000 ffff8782`19d3ee20 : nt!KeBugCheckEx

ffff8782`19d3eb80 fffff806`5c424660     : fffff806`5c525850 00000000`00000000 ffff8782`19d3eea0 00000000`00000000 : nt!MiSystemFault+0x1d8afd

ffff8782`19d3ec80 fffff806`5c60d798     : ffff8782`19d3ee80 00000000`00000000 00000000`00000000 fffff806`5c200000 : nt!MmAccessFault+0x400

ffff8782`19d3ee20 fffff806`5c43bf59     : ffffaa89`24a40730 fffff806`5c44545e ffffaa89`24a40080 fffff806`5c4130d8 : nt!KiPageFault+0x358

ffff8782`19d3efb0 fffff806`5c8462e7     : ffffaa89`24b0a568 ffffaa89`24b0a050 ffffaa89`0fe99220 ffffaa89`24b0a030 : nt!PspReturnQuota+0x49

ffff8782`19d3f010 fffff806`5c846048     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpFreeObject+0x247

ffff8782`19d3f070 fffff806`5c445c07     : 00000000`00000000 00000000`00000000 ffff8782`19d3f1b9 ffffaa89`24b0a080 : nt!ObpRemoveObjectRoutine+0x88

ffff8782`19d3f0d0 fffff806`5c445b2e     : 00000000`00000000 ffffffff`ffffffff 00000000`00400201 ffffffff`5ffffffd : nt!ObfDereferenceObjectWithTag+0xc7

ffff8782`19d3f110 fffff806`5c45d589     : ffffaa89`1fcaaa43 ffff8782`19d3f1b9 ffffffff`ffffffff ffff8782`19d3f1c9 : nt!HalPutDmaAdapter+0xe

ffff8782`19d3f140 fffff806`5c45d007     : ffffaa89`1fcaa8e0 00000000`00000002 ffffaa89`24aaca30 ffff8782`19d3f2b8 : nt!IopfCompleteRequest+0x569

ffff8782`19d3f220 fffff806`688eeaa8     : 00000000`00000000 ffff8782`00000000 ffffaa89`00000000 ffffaa89`24aaca30 : nt!IofCompleteRequest+0x17

ffff8782`19d3f250 fffff806`688ee927     : 00000000`00000000 ffffaa89`163a5c70 00000000`00000103 00000000`00000000 : Npfs!NpCommonCleanup+0x148

ffff8782`19d3f300 fffff806`5c435cf5     : ffffaa89`163b75d0 fffff806`5c435ed2 ffffaa89`163b75d0 00000000`00000000 : Npfs!NpFsdCleanup+0x27

ffff8782`19d3f330 fffff806`59264a76     : ffffaa89`163b75d0 00000000`00000000 00000000`00000000 ffffaa89`248e7080 : nt!IofCallDriver+0x55

ffff8782`19d3f370 fffff806`5c435cf5     : ffffaa89`24aaca30 fffff806`5c435bbd ffffaa89`0fef7400 ffff8782`19d3f589 : FLTMGR!FltpDispatch+0xd6

ffff8782`19d3f3d0 fffff806`5c843607     : 00000000`00000000 ffffaa89`24aaca30 00000000`00000000 00000000`00040082 : nt!IofCallDriver+0x55

ffff8782`19d3f410 fffff806`5c84b6ff     : ffffaa89`248e7080 00000000`00000001 00000000`00000000 ffffaa89`24aaca00 : nt!IopCloseFile+0x177

ffff8782`19d3f4a0 fffff806`5c8ed885     : ffffaa89`248c1708 fffff806`5c445ef9 ffffaa89`24781070 00000000`00000000 : nt!ObCloseHandleTableEntry+0x51f

ffff8782`19d3f5e0 fffff806`5c7e908d     : ffffaa89`248c16d0 ffffaa89`24a40080 ffffffff`ffffff01 ffffaa89`248e74d8 : nt!ExSweepHandleTable+0xd5

ffff8782`19d3f690 fffff806`5c885ef0     : ffffffff`ffffffff ffffaa89`248e7080 ffff8782`19d3f6e0 fffff806`5c7f4604 : nt!ObKillProcess+0x35

ffff8782`19d3f6c0 fffff806`5c88da4e     : ffffaa89`248e7080 ffffbe08`abd78730 ffff8782`19d3f8e9 00000000`00000000 : nt!PspRundownSingleProcess+0x204

ffff8782`19d3f750 fffff806`5c907f48     : ffffaa89`00000000 fffff806`5c417701 00000000`00000000 0000002b`7c030000 : nt!PspExitThread+0x5f6

ffff8782`19d3f850 fffff806`5c4c872d     : 00000000`00000000 00000000`00000001 00000000`00000101 00000000`00000010 : nt!KiSchedulerApcTerminate+0x38

ffff8782`19d3f890 fffff806`5c602ee0     : 000001ef`f9833820 ffff8782`19d3f950 ffff8782`19d3fb00 00000000`00000002 : nt!KiDeliverApc+0x60d

ffff8782`19d3f950 fffff806`5c61161f     : ffffaa89`24a40080 0000002b`7c27f918 00000000`00000000 000001ef`f98350b8 : nt!KiInitiateUserApc+0x70

ffff8782`19d3fa90 00007ffd`0c870a74     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f

0000002b`7c27fa78 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`0c870a74

SYMBOL_NAME:  Npfs!NpCommonCleanup+148

MODULE_NAME: Npfs

IMAGE_NAME:  Npfs.SYS

IMAGE_VERSION:  10.0.19041.4170

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  148

FAILURE_BUCKET_ID:  AV_R_(null)_Npfs!NpCommonCleanup

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {255b6694-3299-dd29-fe63-b7b3422f7a57}

Followup:     MachineOwner

---------
Windows 10
Windows 10
在个人计算机和平板电脑上运行的 Microsoft 操作系统。
56 个问题
Windows
Windows
Microsoft 操作系统系列，可跨个人计算机、平板电脑、笔记本电脑、手机、物联网设备、独立混合现实头戴显示设备、大型协作屏幕和其他设备运行。
135 个问题

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Hania Lian 8,226 信誉分 Microsoft 供应商
    2024-04-12T06:24:05.0233333+00:00

    您好。

    “PAGE_FAULT_IN_NONPAGED_AREA （50） npfs.sys”错误表示npfs.sys文件有问题，该文件是系统关键文件的一部分。这是一种系统错误，通常是由于硬件问题、过时的驱动程序或损坏的系统文件而发生的。

    检查RAM是否存在错误：“PAGE_FAULT_IN_NONPAGED_AREA”错误通常是由RAM中的错误引起的。使用 Windows 内存诊断工具检查它，如果出现问题，请进行更换。

    更新驱动程序：如果您的计算机驱动程序已过时，可能会导致此错误。确保所有驱动程序都已更新。您可以在设备管理器中执行此操作，也可以通过访问每个制造商的网站来了解您的硬件组件并下载最新的驱动程序。

    进行干净启动：如何在 Windows 中执行干净启动 - Microsoft 支持

    运行检查磁盘：硬盘驱动器上也可能存在错误，从而导致该问题。运行“检查磁盘”以查找并修复硬盘驱动器上的错误。以管理员身份打开命令提示符，键入 chkdsk /f /r 并按 Enter，然后重新启动计算机。

    还原系统：如果上述解决方案都无法解决问题，您可以尝试还原系统。这会将您的系统回滚到错误开始发生之前的某个点。为此，请单击“开始”并在搜索栏中键入“恢复”，选择“恢复选项”，然后选择“打开系统还原”。

    Bug 检查 0x50 PAGE_FAULT_IN_NONPAGED_AREA - Windows drivers | Microsoft Learn

    如果答案有帮助，请点击”接受答案“并投赞成票。

    0 个注释