Windows 10 BSOD Page Fault in non Paged Area

  • Thread starter Thread starter DjCanigia
  • Start date Start date
D

DjCanigia

Hello,
for several months I have occasionally got the blue screen with "Page fault in non paged area" I have tested the ram several times and they have never given me problems, currently I keep them with xmp profile 2 (because with profile one the problem occurs 3 times out of 3) and over the months I have also changed all the components except the processor but the problem remains ...
I did the mini dump with windows debug:
[COLOR=rgba(37, 45, 45, 1)][COLOR=rgba(20, 22, 24, 1)]
Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\theca\Desktop\031721-8593-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
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`2b800000 PsLoadedModuleList = 0xfffff804`2c42a3b0
Debug session time: Wed Mar 17 16:37:21.153 2021 (UTC + 1:00)
System Uptime: 0 days 0:22:09.796
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`2bbf5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc0d`d711dd40=0000000000000050
0: 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: ffffe28a3cc14080, memory referenced.
Arg2: 0000000000000011, value 0 = read operation, 1 = write operation.
Arg3: ffffe28a3cc14080, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2921

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 45129

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 50

BUGCHECK_P1: ffffe28a3cc14080

BUGCHECK_P2: 11

BUGCHECK_P3: ffffe28a3cc14080

BUGCHECK_P4: 2

WRITE_ADDRESS: fffff8042c4fb390: 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
ffffe28a3cc14080

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: wallpaper32.exe

TRAP_FRAME: fffffc0dd711dfe0 -- (.trap 0xfffffc0dd711dfe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff804281d8180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffe28a3cc14080 rsp=fffffc0dd711e170 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=ffffb8feeea00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
ffffe28a`3cc14080 06 ???
Resetting default scope

STACK_TEXT:
fffffc0d`d711dd38 fffff804`2bc7a665 : 00000000`00000050 ffffe28a`3cc14080 00000000`00000011 fffffc0d`d711dfe0 : nt!KeBugCheckEx
fffffc0d`d711dd40 fffff804`2baea4a0 : 00000000`00000000 00000000`00000011 fffffc0d`d711e060 00000000`00000000 : nt!MiSystemFault+0x172315
fffffc0d`d711de40 fffff804`2bc0335e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffffc0d`d711dfe0 ffffe28a`3cc14080 : ffff960d`bad04470 00000000`0000004d ffffe28a`3cc14080 00000000`00000000 : nt!KiPageFault+0x35e
fffffc0d`d711e170 ffff960d`bad04470 : 00000000`0000004d ffffe28a`3cc14080 00000000`00000000 00000000`00000000 : 0xffffe28a`3cc14080
fffffc0d`d711e178 00000000`0000004d : ffffe28a`3cc14080 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff960d`bad04470
fffffc0d`d711e180 ffffe28a`3cc14080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4d
fffffc0d`d711e188 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe28a`35452cf0 : 0xffffe28a`3cc14080


SYMBOL_NAME: nt!MiSystemFault+172315

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.631

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 172315

FAILURE_BUCKET_ID: AV_INVALID_nt!MiSystemFault

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8a33c6b1-a9f1-4efe-025b-a861cc33d6e2}

Followup: MachineOwner
---------

0: kd> lmvm nt
Browse full module list
start end module name
fffff804`2b800000 fffff804`2c846000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\F923DA2D238E7C7CE180B962B19A37811\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\ED9DC31E1046000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: ED9DC31E (This is a reproducible build file hash, not a timestamp)
CheckSum: 00A5F2BD
ImageSize: 01046000
File version: 10.0.19041.631
Product version: 10.0.19041.631
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 10.0.19041.631
FileVersion: 10.0.19041.631 (WinBuild.160101.0800)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.[/COLOR][/COLOR]

I also uploaded the minidump to my drive at this link 031721-8593-01.dmp


What is the problem with me? I'm going crazy for it



Thanks to anyone who can help me!

Continue reading...
 
Back
Top