Windows 10: BSOD - page fault in nonpaged area

Hello. Hoping you can help. I was getting a page fault in nonpaged area BSOD's on my 10 year old but still competent system so replaced motherboard, ram and processor. Sadly the issue has followed me!


So the new components are i3-10100f, nvidia gtx 980, 32gb ram, gigabyte mobo. Old components are a samsung 250gb SSD which is only a few years old and passes all the tests with flying colours and a corsair 500w psu.


I've done so many fresh windows installs over the last few months I lost count.


Thankfully today I finally got some log files- attached. I got this BSOD whilst restarting due to changing pagefile size; for some reason "let windows manage it" meant it was only 4gb which goes against the conventional wisdom so I tried upping it. I have since tried 16gb and no pagefile with no clear impact either way.



dumpstack.log file:

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


DLOGFILE00010000DUMP
Dump stack initialized at UTC: 2021/02/28 18:57:05, local time: 2021/02/28 18:57:05.
Starting get secondary dump callbacks size.
Finish get secondary dump callbacks size.
Dump Type: 6, Total Dump Size: 683090520, Secondary Dump Size: 209496.
Starting write of dump header.
Finish write of dump header.
Starting write of kernel bitmap dump header.
Finish write of bitmap dump header.
Starting write of memory dump data.
Dumping physical memory to disk: 0%
Dumping physical memory to disk: 5%
Dumping physical memory to disk: 10%
Dumping physical memory to disk: 15%
Dumping physical memory to disk: 20%
Dumping physical memory to disk: 25%
Dumping physical memory to disk: 30%
Dumping physical memory to disk: 35%
Dumping physical memory to disk: 40%
Dumping physical memory to disk: 45%
Dumping physical memory to disk: 50%
Dumping physical memory to disk: 55%
Dumping physical memory to disk: 60%
Dumping physical memory to disk: 65%
Dumping physical memory to disk: 70%
Dumping physical memory to disk: 75%
Dumping physical memory to disk: 80%
Dumping physical memory to disk: 85%
Dumping physical memory to disk: 90%
Dumping physical memory to disk: 95%
Dumping physical memory to disk: 100%
Finish write of bitmap dump data. Total pages:166449 Pages written:166449
Starting invoking secondary dump callbacks.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling TRIAGEDUMPDATA secondary callback.
Return from TRIAGEDUMPDATA secondary callback.
Writing TRIAGEDUMPDATA secondary callback data.
Writing TRIAGEDUMPDATA secondary callback data done.
Calling CRASHDUMP secondary callback.
Return from CRASHDUMP secondary callback.
Writing CRASHDUMP secondary callback data.
Writing CRASHDUMP secondary callback data done.
Calling USBXHCI secondary callback.
Return from USBXHCI secondary callback.
Writing USBXHCI secondary callback data.
Writing USBXHCI secondary callback data done.
Calling nvlddmkm.sys secondary callback.

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


[end]


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



minidump file analysed with debugging tools for windows:





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


Loading Dump File [C:\bsod fixes\022821-6031-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 8 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`48000000 PsLoadedModuleList = 0xfffff800`48c2a390
Debug session time: Sun Feb 28 18:57:05.475 2021 UTC + 0:00
System Uptime: 0 days 0:00:06.129
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
7: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffffffffffffc7, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff800486a9b5b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, reserved

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


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-16NHEJE

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 21

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 50

BUGCHECK_P1: ffffffffffffffc7

BUGCHECK_P2: 2

BUGCHECK_P3: fffff800486a9b5b

BUGCHECK_P4: 2

READ_ADDRESS: fffff80048cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80048c0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80048c0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffc7

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff20acf19f670 -- .trap 0xfffff20acf19f670
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff20acf19f934 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800486a9b5b rsp=fffff20acf19f800 rbp=0000000000000008
r8=0000000000000001 r9=000000000000000b r10=0000000000000000
r11=fffff20acf19f7d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!_PnpGetObjectProperty+0x10f:
fffff800`486a9b5b 8945bf mov dword ptr [rbp-41h],eax ss:ffffffff`ffffffc7=????????
Resetting default scope

LOCK_ADDRESS: fffff80048c44bc0 -- !locks fffff80048c44bc0
Cannot get _ERESOURCE type

Resource @ nt!PiEngineLock 0xfffff80048c44bc0 Available
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff80048c44bc0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

STACK_TEXT:
fffff20a`cf19f3c8 fffff800`4841ebbb : 00000000`00000050 ffffffff`ffffffc7 00000000`00000002 fffff20a`cf19f670 : nt!KeBugCheckEx
fffff20a`cf19f3d0 fffff800`4820c960 : fffff20a`cf19f968 00000000`00000002 fffff20a`cf19f6f0 00000000`00000000 : nt!MiSystemFault+0x1f43ab
fffff20a`cf19f4d0 fffff800`48403c5e : fffff20a`cf19f750 ffff8004`547a6e70 fffff800`4800c320 fffff20a`cf19f970 : nt!MmAccessFault+0x400
fffff20a`cf19f670 fffff800`486a9b5b : fffff20a`cf19f9f8 ffff8004`547a6e70 00000000`00000008 ffff8004`5077cdb0 : nt!KiPageFault+0x35e
fffff20a`cf19f800 fffff800`48756abf : fffff20a`cf19f9f8 00000000`00000000 ffff8004`547a6e70 00000000`00000001 : nt!_PnpGetObjectProperty+0x10f
fffff20a`cf19f8d0 fffff800`4868435c : ffff8004`547a6e70 fffff20a`00000004 00000000`00000007 ffffdc02`0180600a : nt!PiUEventDeviceNeedsInstall+0x147
fffff20a`cf19f960 fffff800`4870a3e8 : ffff8004`547a6dd0 ffffdc02`bc8aec00 00000000`00000000 00000000`00000000 : nt!PiUEventNotifyUserMode+0x1f0
fffff20a`cf19f9f0 fffff800`48225975 : ffffdc02`c22da0c0 ffffdc02`c22da0c0 ffffdc02`bc8aec40 ffffdc02`beb33a00 : nt!PnpDeviceEventWorker+0x298
fffff20a`cf19fa70 fffff800`48317e25 : ffffdc02`c22da0c0 00000000`00000080 ffffdc02`bc8b0200 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
fffff20a`cf19fb10 fffff800`483fd0d8 : fffff800`44f4c180 ffffdc02`c22da0c0 fffff800`48317dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff20a`cf19fb60 00000000`00000000 : fffff20a`cf1a0000 fffff20a`cf199000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!_PnpGetObjectProperty+10f

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 10f

FAILURE_BUCKET_ID: AV_INVALID_nt!_PnpGetObjectProperty

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d41636d0-8f74-c44f-ded9-84564e2015b0}

Followup: MachineOwner

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


[end]


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


And finally, in safe mode I ran sfc / scannow which told me it had found errors and corrected them, and gave me a log file I will post below due to length limitations.



Can anyone help me- did sfc /scannow solve the problem? Will I still get BSOD's?

:)

 

Page Fault in Nonpaged Area

I'm getting the BSOD due to the Page Fault in Nonpaged Area on my Windows 10 PC; it only happens when I navigate to certain websites, and it appears to be browser independent. I've run the Memory Diagnostic Tool, the System File Checker, and Chkdsk- no
errors have been found. Any suggestions? Thanks!

 

How do we all dealt with "Page fault in nonpage area"?

Hi

These links may give you a better insight.

http://www.channelpro.co.uk/advice/9919/how-to-fix-page-fault-in-non-paged-area-bsod-crash-1

Type....Nonpaged Area in search box.^ and select how to fix........ first in list.

http://turbofuture.com/computers/What-Is-Page-Fault-In-Nonpaged-Area

 

page fault in nonpaged areas win 10

Hi,

my computer starting showing a new BSOD stating "page fault in nonpaged areas" .The computer keeps on restarting and every time I get the same BSOD.

When i inserted the bootable usb ,I selected the setup option and again the BSOD (page fault in nonpaged areas) appears .

I can't even restart in safe mode because again I get the BSOD.

earlier my computer was stuck in an infinite automatic repair loop and suddenly when I turned it ON the next time I got the BSOD (page fault in nonpaged areas)..

So please help me fast..