Forum Discussion

Infoldca's avatar
Infoldca
4 years ago

Apex and Easy Anti Cheat Causing Page Fault BSOD

Product: Apex Legends
Platform:Steam-PC
Please specify your platform model. PC
AMD or Nvidia Model Number RTX 3060 Ti
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? Infoldca
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible. -
Are you using any software with an overlay? Yes
If yes, can you list them here? RivaTunerStatisticServer
If you disable this software, does that have any effect? No
Which Legend were you playing (if applicable)? -
Which Legends were your squad mates using (if applicable)? -
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Storm point though i think it occurs in any map
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. just moving around, a fight was about to happen
Did your squad mates also experience the issue? No
How many matches had you played in a row before the issue occurred? maybe 2 or 3, it occurs randomly
When did this happen? (dd.mm.yy hh:mm) last at 31.5.22 10:21
How often does the bug occur? Occasionally (10% - 49%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? Blue screen of death, windows throws page fault error code
What should be happening instead? i should have been continue playing
Steps: How can we find the bug ourselves? I'm not sure how to replicate the bug as it seems to occur randomly. though since it is related to memory i suspect this had something to do with either easy anticheat, XMP, Windows 11 or a combination of them since thats what i am using.

‌

Product: Apex Legends
Platform:Steam-PC
Please specify your platform model. PC
AMD or Nvidia Model Number RTX 3060 Ti
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? Infoldca
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible. -
Are you using any software with an overlay? Yes
If yes, can you list them here? RivaTunerStatisticServer
If you disable this software, does that have any effect? No
Which Legend were you playing (if applicable)? -
Which Legends were your squad mates using (if applicable)? -
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Storm point though i think it occurs in any map
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. just moving around, a fight was about to happen
Did your squad mates also experience the issue? No
How many matches had you played in a row before the issue occurred? maybe 2 or 3, it occurs randomly
When did this happen? (dd.mm.yy hh:mm) last at 31.5.22 10:21
How often does the bug occur? Occasionally (10% - 49%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? Blue screen of death, windows throws page fault error code
What should be happening instead? i should have been continue playing
Steps: How can we find the bug ourselves? I'm not sure how to replicate the bug as it seems to occur randomly. though since it is related to memory i suspect this had something to do with either easy anticheat, XMP, Windows 11 or a combination of them since thats what i am using.

‌

Hi I have been getting some BSOD with the error message: `page fault in non paged area` since the newest season, it had happen numerous time when I'm playing on a squad. I'm not very sure how to replicate the issue but it seems to persist.

I'm attaching my specs here if that is any interest to the devs:

- CPU: i5 10400f

- Memory: 16GB XMP 3600Mhz

- GPU: RTX 3060 Ti

- Windows 11

Also here is WinDbg result from the minidump:

Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\053122-13109-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 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff807`2c400000 PsLoadedModuleList = 0xfffff807`2d029b90
Debug session time: Tue May 31 22:20:28.339 2022 (UTC + 7:00)
System Uptime: 4 days 0:23:54.451
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff807`2c816b40 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffd87`3b9773e0=0000000000000050
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: ffff9c8d35000038, 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: fffff8072c7d91c8, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 2405

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 45187

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

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

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

    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:  053122-13109-01.dmp

BUGCHECK_CODE:  50

BUGCHECK_P1: ffff9c8d35000038

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8072c7d91c8

BUGCHECK_P4: 2

READ_ADDRESS: fffff8072d105450: 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
 ffff9c8d35000038 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  r5apex.exe

TRAP_FRAME:  fffffd873b977680 -- (.trap 0xfffffd873b977680)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffff9c8000000008 rbx=0000000000000000 rcx=0000046700001000
rdx=00000001a6a00006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8072c7d91c8 rsp=fffffd873b977818 rbp=0000fffffffff000
 r8=fffff8072c7d91b0  r9=fffff8072c7d91b0 r10=fca8fb64276788e9
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MmGetVirtualForPhysical+0x18:
fffff807`2c7d91c8 488b04d0        mov     rax,qword ptr [rax+rdx*8] ds:ffff9c8d`35000038=????????????????
Resetting default scope

STACK_TEXT:  
fffffd87`3b9773d8 fffff807`2c8a09bd     : 00000000`00000050 ffff9c8d`35000038 00000000`00000000 fffffd87`3b977680 : nt!KeBugCheckEx
fffffd87`3b9773e0 fffff807`2c71abd6     : ffffd15f`8040fed0 00000000`00000000 fffffd87`3b9775e0 00000000`00000000 : nt!MiSystemFault+0x20939d
fffffd87`3b9774e0 fffff807`2c8256f5     : ffffd15f`8040fed8 00001fa0`00000001 00000000`000001fd 00000000`00000000 : nt!MmAccessFault+0x2a6
fffffd87`3b977680 fffff807`2c7d91c8     : fffff809`92dc0caf 00000000`00000000 00000467`00001000 00081fd9`00001000 : nt!KiPageFault+0x335
fffffd87`3b977818 fffff809`92dc0caf     : 00000000`00000000 00000467`00001000 00081fd9`00001000 00000000`00001001 : nt!MmGetVirtualForPhysical+0x18
fffffd87`3b977820 00000000`00000000     : 00000467`00001000 00081fd9`00001000 00000000`00001001 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
---------


Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\052722-14671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff801`2f200000 PsLoadedModuleList = 0xfffff801`2fe29b90
Debug session time: Fri May 27 21:55:26.397 2022 (UTC + 7:00)
System Uptime: 8 days 5:54:38.321
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff801`2f616b40 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff881`e62023e0=0000000000000050
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: ffffaedd6efd5a68, 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: fffff8012f5d91c8, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 2280

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 28027

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

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

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

    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:  052722-14671-01.dmp

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffaedd6efd5a68

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8012f5d91c8

BUGCHECK_P4: 2

READ_ADDRESS: fffff8012ff05450: 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
 ffffaedd6efd5a68 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  r5apex.exe

TRAP_FRAME:  fffff881e6202680 -- (.trap 0xfffff881e6202680)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffae8000000008 rbx=0000000000000000 rcx=00001f24ff1e2000
rdx=0000000baddfab4c rsi=0000000000000000 rdi=0000000000000000
rip=fffff8012f5d91c8 rsp=fffff881e6202818 rbp=0000fffffffff000
 r8=fffff8012f5d91b0  r9=fffff8012f5d91b0 r10=4ea93619b59d88e9
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MmGetVirtualForPhysical+0x18:
fffff801`2f5d91c8 488b04d0        mov     rax,qword ptr [rax+rdx*8] ds:ffffaedd`6efd5a68=????????????????
Resetting default scope

STACK_TEXT:  
fffff881`e62023d8 fffff801`2f6a09bd     : 00000000`00000050 ffffaedd`6efd5a68 00000000`00000000 fffff881`e6202680 : nt!KeBugCheckEx
fffff881`e62023e0 fffff801`2f51abd6     : fffffe40`80d71998 00000000`00000000 fffff881`e62025e0 00000000`00000000 : nt!MiSystemFault+0x20939d
fffff881`e62024e0 fffff801`2f6256f5     : fffffe40`80d719a0 00001fa0`00000001 00000000`00000200 00000000`00000000 : nt!MmAccessFault+0x2a6
fffff881`e6202680 fffff801`2f5d91c8     : fffff801`d1220caf 00000000`00000000 00001f24`ff1e2000 00000000`00000000 : nt!KiPageFault+0x335
fffff881`e6202818 fffff801`d1220caf     : 00000000`00000000 00001f24`ff1e2000 00000000`00000000 00000000`00000000 : nt!MmGetVirtualForPhysical+0x18
fffff881`e6202820 00000000`00000000     : 00001f24`ff1e2000 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
---------

WinDbg seems to complain that EasyAntiCheat tries to access non paged area. I have also included the dump file should you guys need it. I apologize that I could not reproduce any steps to reproduce the issue as it seems to occur randomly, I know how frustrating it can be when a user reported a bug without providing reproduce steps. I kindly ask for any assistance regarding this issue, should you guys need anything more I'll be happy to provide more informations.

Thank you.

2 Replies

Replies have been turned off for this discussion
  • XHelperZ's avatar
    XHelperZ
    Hero+
    4 years ago

    C:\Program Files (x86)\EasyAntiCheat
    Delete only EasyAntiCheat.sys

    Starting up the game it should either prompt the EAC menu or the game will boot up normally.

    Issue persists, run the EAC.exe application and use the repair function when Apex Legends is selected.

    Make sure you're also running Apex Legends with Admin privileges.

    Giving EAC Admin priority might also resolve this issue.

    Clean your PC and reseat your RAM if you think it might be related to memory problems, run a memtest to be sure.

    Please provide a DxDiag and maybe the current Win11 version you are using.

    Being behind on updates might result in these kind of issues too.

About Apex Legends Bug Reports - Archive

23,008 PostsLatest Activity: 2 years ago