Apex legends BLEU SCREEN.. PAGE FAULT IN NONPAGED AREA

@Vell51rus 

This is potentially a hard drive issue.

Bluescreen issues are outside of the scope of support we provide here as they generally indicate an issue outside of our games.

Some general troubleshooting steps:

• Make sure all available Windows Updates and hardware driver updates are installed
• Run System File Checker to ensure the integrity of your Windows System files: http://support.microsoft.com/kb/929833
• Perform a clean boot before starting the game: http://support.microsoft.com/kb/929135

Thanks.

Hey

With all my respect sir but this problem happened to many people and only with apex

I played many other games without any issues

And i googled this to find some people got the same problem

And run a test to my harddrive it's work fine.. But the im installing apex legends in the location of my windows 

Has happened to me twice now, this is a real bug, but if they wont acknowledge it it wont ever be fixed. 

@TroublegoatsCreate new topic and inform them cuz they said it's not there problem u see...

We all have hardwares problems.. With same time in same game..with the same  bleu sreen code error...

And guess what

I think u got the crash in stormmap

With season 13, my computer has been constantly crashing, and I don't see a pattern to what is causing the crashes, other than it only happens while I am playing Apex Legends. Every time I get a blue screen, the error is a Page Fault in a Non Paged Area. I originally thought this was a driver issue as I had recently updated my graphics driver, but the issue persisted after rolling them back as far as Nvidia allowed. Is anyone having similar issues, and is there anything else I can provide to help determine if this is an Apex issue?

My PC is an Acer Predator Helios 300 laptop with an Nvidia RTX 2060 GPU running driver version 471.41, an Intel i7 processor, and 16GB of RAM.

Just joined this HQ to say I have the exact same problem. I have the same specs as OP (except the CPU, I have an i5) and just now my PC crashed due to this.
I had 8GB of RAM back then and I had at least three BSOD's before upgrading to 16GB RAM (Literally upgraded my RAM because of Apex Legends). These BSOD's only happened this season.
Wishing EA/Respawn could look into this~ seems like a virtual memory paging issue that only happens when I play Apex Legends.

@PrinceXuxhizYessss virtual memory triggers the BSOd... For me i changed the memory virtual from automatic management to disk local C... And rebooted my pc long time ago.. But still im not sure if the bsod will happen or not..

I'm having the exact same problem. Only been happening in this new season.

Signs are pointing to EasyAntiCheat.

Also replied in the Reddit too - https://www.reddit.com/r/apexlegends/comments/usap9z/page_fault_in_nonpaged_area/

I used WinDbg to analyse the memory.dmp file from my crash... Pasting some of it below:

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

* *

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

SYMBOL_NAME: EasyAntiCheat+20caf

MODULE_NAME: EasyAntiCheat

IMAGE_NAME: EasyAntiCheat.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 20caf

FAILURE_BUCKET_ID: AV_R_(null)_EasyAntiCheat!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {de037a2f-1007-fb78-fc0b-814c5461dfd3}

Followup: MachineOwner

---------

1: kd> lmvm EasyAntiCheat

Browse full module list

start end module name

fffff807`cee90000 fffff807`cf9b2000 EasyAntiCheat (no symbols)

Loaded symbol image file: EasyAntiCheat.sys

Image path: \??\C:\Program Files (x86)\EasyAntiCheat\EasyAntiCheat.sys

Image name: EasyAntiCheat.sys

Browse all global symbols functions data

Timestamp: Tue May 17 09:38:38 2022 (62835F0E)

CheckSum: 00B23996

ImageSize: 00B22000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Information from resource tables:

Hi, I got the same problem several times from season 13, never happened before.

my specs are

CPU:Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 3.70 GHz
RAM:64.0 GB
GPU:1080ti

Windows 11 Pro ver 21H2
OS build 22000.675

dump file is like this.

1: 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: ffffb0fffffffd08, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80631fd91c8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify timestamp for EasyAntiCheat.sys

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 2468

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 44881

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

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

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1

FILE_IN_CAB: 052822-11937-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffb0fffffffd08

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80631fd91c8

BUGCHECK_P4: 2

READ_ADDRESS: fffff80632905450: 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
ffffb0fffffffd08

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: python.exe

TRAP_FRAME: fffffe03ef11f680 -- (.trap 0xfffffe03ef11f680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffae0000000008 rbx=0000000000000000 rcx=0000ffffffff0000
rdx=0000005fffffffa0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80631fd91c8 rsp=fffffe03ef11f818 rbp=0000fffffffff000
r8=fffff80631fd91b0 r9=fffff80631fd91b0 r10=f627ee1932f288e9
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MmGetVirtualForPhysical+0x18:
fffff806`31fd91c8 488b04d0 mov rax,qword ptr [rax+rdx*8] ds:ffffb0ff`fffffd08=????????????????
Resetting default scope

STACK_TEXT:
fffffe03`ef11f3d8 fffff806`320a09bd : 00000000`00000050 ffffb0ff`fffffd08 00000000`00000000 fffffe03`ef11f680 : nt!KeBugCheckEx
fffffe03`ef11f3e0 fffff806`31f1abd6 : fffff769`8045dfb8 00000000`00000000 fffffe03`ef11f5e0 00000000`00000000 : nt!MiSystemFault+0x20939d
fffffe03`ef11f4e0 fffff806`320256f5 : fffff769`8045dfc0 00001fa0`00000001 00000000`000001f5 00000000`00000000 : nt!MmAccessFault+0x2a6
fffffe03`ef11f680 fffff806`31fd91c8 : fffff80a`995f0caf 00000000`00000000 0000ffff`ffff0000 00000000`00000000 : nt!KiPageFault+0x335
fffffe03`ef11f818 fffff80a`995f0caf : 00000000`00000000 0000ffff`ffff0000 00000000`00000000 00000000`00000000 : nt!MmGetVirtualForPhysical+0x18
fffffe03`ef11f820 00000000`00000000 : 0000ffff`ffff0000 00000000`00000000 00000000`00000000 00000000`00000000 : EasyAntiCheat+0x20caf

SYMBOL_NAME: EasyAntiCheat+20caf

MODULE_NAME: EasyAntiCheat

IMAGE_NAME: EasyAntiCheat.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 20caf

FAILURE_BUCKET_ID: AV_R_(null)_EasyAntiCheat!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {de037a2f-1007-fb78-fc0b-814c5461dfd3}

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

Is there memory handling error or something in EasyAntiCheat?