i always encounter this problem. "Page_fault_in_nonpaged_area (0x50)"

Question

Even doing browser. my PC Suddenly freeze then black screen showing Page_fault_in_nonpaged_area (0x50)

how to solve this problem? i dont have extra money now to buy new ram

this minidump i analyze

*******************************************************************************
*                                                                             *
*                        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: ffffce2ef7183cc0, memory referenced.
Arg2: 0000000000000000, 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: fffff803b40a5da2, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.PTE
    Value: Invalid

    Key  : AV.Page.Virtual
    Value: 0xffffce2ef7180000

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1843

    Key  : Analysis.Elapsed.mSec
    Value: 8140

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    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: AV_nt!ObpLookupObjectName

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

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

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

    Key  : Failure.Hash
    Value: {474528e0-febc-e870-edfc-c0a99a0c8f3c}

    Key  : Faulting.IP.Type
    Value: Paged

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

BUGCHECK_P1: ffffce2ef7183cc0

BUGCHECK_P2: 0

BUGCHECK_P3: fffff803b40a5da2

BUGCHECK_P4: 2

FILE_IN_CAB:  052826-13281-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff950bcd852080

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffce2ef7183cc0

READ_ADDRESS: fffff803b47c54d8: Unable to get MiVisibleState
 ffffce2ef7183cc0 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ROUTE.EXE

IP_IN_PAGED_CODE: 
nt!ObpLookupObjectName+cb2
fffff803`b40a5da2 394310          cmp     dword ptr [rbx+10h],eax

STACK_TEXT:  
fffffa87`cbc4f168 fffff803`b3b0e960     : 00000000`00000050 ffffce2e`f7183cc0 00000000`00000000 fffffa87`cbc4f3d0 : nt!KeBugCheckEx
fffffa87`cbc4f170 fffff803`b3a43e96     : ffff950b`c687fd90 ffff8000`00000000 ffffce2e`f7183cc0 0000007f`fffffff8 : nt!MiSystemFault+0x850
fffffa87`cbc4f260 fffff803`b3eb80cb     : ffff950b`bb481660 00000000`00000004 ffff950b`cb489c70 fffff803`b3ac799e : nt!MmAccessFault+0x646
fffffa87`cbc4f3d0 fffff803`b40a5da2     : ffffce8f`eb278720 fffff803`00000001 ffff950b`c687fd80 00000000`00000000 : nt!KiPageFault+0x38b
fffffa87`cbc4f560 fffff803`b40a3c43     : ffff950b`cb489a01 fffffa87`cbc4f798 00000000`00000040 ffff950b`9e59cb10 : nt!ObpLookupObjectName+0xcb2
fffffa87`cbc4f710 fffff803`b416821f     : ffff950b`00000000 ffff950b`c3671270 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x223
fffffa87`cbc4f850 fffff803`b41673f9     : 0000008d`2cb5f1e0 00000000`00100001 0000008d`2cb5f1f8 0000008d`2cb5f1e8 : nt!IopCreateFile+0xe0f
fffffa87`cbc4f920 fffff803`b3ebc555     : fffffa87`cbc4faa0 00000000`000000be fffffa87`cbc4faa0 00000000`00007742 : nt!NtCreateFile+0x79
fffffa87`cbc4f9b0 00007ff8`da822744     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000008d`2cb5f168 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`da822744


SYMBOL_NAME:  nt!ObpLookupObjectName+cb2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.8457

STACK_COMMAND: .process /r /p 0xffff950bcbc88080; .thread /r /p 0xffff950bcd852080 ; kb

BUCKET_ID_FUNC_OFFSET:  cb2

FAILURE_BUCKET_ID:  AV_nt!ObpLookupObjectName

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {474528e0-febc-e870-edfc-c0a99a0c8f3c}

Followup:     MachineOwner

Answer 1

Hi, thank you for reaching out to Microsoft Q&A.

Your Minidump files just indicate RAM (Memory) Corruption, and there is no specific cause of the crash listed.

To force Windows to generate minidump files and identify any faulting drivers, enable Driver Verifier and let your PC crash 3 times. After that, disable Driver Verifier and upload the newly created minidump files. Make sure you create a system restore point before making any changes to your device.

See "Driver Verifier- tracking down a misbehaving driver" (Related article for your reference)

https://yourwindowsguide.com/2025/09/driver-verifier-what-it-is-why-its-useful-and-how-to-use-it.html

This article was written by a trusted Microsoft MVP, Sumit. Watch out for any ads.

---

Standard Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.'

Answer 2

The PAGE_FAULT_IN_NONPAGED_AREA (0x50) bug check indicates that invalid system memory was referenced. The dump shows a read access (Arg2 = 0) to an invalid page table entry (AV.PTE = Invalid), with the fault occurring in nt!ObpLookupObjectName, which is part of the Windows kernel.

From the documentation, typical causes include:

• Faulty system service or driver code
• Antivirus software
• Corrupted NTFS volume
• Faulty or failing hardware (often RAM, cache, or video RAM)

Because replacing RAM is not an option, focus on software and configuration causes first.

Steps to troubleshoot and mitigate:

1. Check Event Viewer
   • Open Event Viewer → Windows Logs → System.
   • Look for critical or error events that occurred at the same time as the blue screen.
   • Note any driver or service names that appear repeatedly.
2. Update or roll back drivers and system services
   • If a specific driver or system service is mentioned on the blue screen or in Event Viewer, update it from the vendor site.
   • If the problem started after a recent driver or Windows update, roll back that driver or use System Restore/Windows recovery options to revert to a previous state.
3. Check antivirus software
   • Temporarily disable or uninstall third‑party antivirus and see if the issue stops.
   • If disabling resolves the problem, contact the antivirus vendor for an updated version.
4. Check disk and file system (NTFS)
   • Run chkdsk /f /r on the system drive.
   • A restart is required for system partitions; allow the scan to complete.
   • This detects and repairs disk and NTFS corruption that can cause 0x50.
5. Test system memory (without replacing it)
   • Run Windows Memory Diagnostics:
     • Open Control Panel → search for “Memory” → select “Diagnose your computer's memory problems”.
     • Let the test run and then check the results in Event Viewer → System log → MemoryDiagnostics-Results.
   • If errors are reported, reseat RAM modules if possible (power off, remove and reinsert), and test again.
6. Check for faulty hardware or recent changes
   • If any hardware was added recently (e.g., GPU, storage, peripherals), remove or disconnect it and test.
   • Run any hardware diagnostics provided by the PC or motherboard manufacturer.
7. Use Driver Verifier (advanced)
   • Driver Verifier can help identify misbehaving drivers:
     • Run verifier from an elevated command prompt.
     • Configure it to check only non‑Microsoft drivers to reduce risk.
     • If Driver Verifier triggers a new blue screen, analyze the new dump to see which driver is reported.
   • Disable Driver Verifier once testing is complete, as it adds overhead.
8. Analyze multiple dumps
   • If more dumps are available, compare them:
     • Look at MODULE_NAME, FAULTING_MODULE, and stack traces.
     • If the same third‑party driver or module appears repeatedly, focus on updating, disabling, or removing that component.

If these steps identify a specific driver, service, antivirus, or disk issue and it is corrected, the PAGE_FAULT_IN_NONPAGED_AREA (0x50) bug checks should stop without requiring new RAM.

---

References:

• Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA