Game Crashes directly after launching. Analyzing the crash dmp states that r5apex.exe tries to execute code from address 0xffffffffffffffff. I had the same two patches ago. It got fixed with the next patch but now its back again after the last patch some minutes ago. Respawn pls fix!
System Info (everything up to date):
Windows 10
AMD Ryzen 5900x
Nvidia GTX 1070ti
Output from WinDbg:
CONTEXT: (.ecxr)
rax=2cafd2c44cebf15d rbx=2cafd2c44cebf15d rcx=2cafd2c44cebf15d
rdx=fe0202be97f2757f rsi=a2338330d3cf6d26 rdi=2cafd2c44cebf15d
rip=ffffffffffffffff rsp=000001f8179a7740 rbp=2cafd2c44cebf15d
r8=72586dba17f99523 r9=01d4cac3fa782013 r10=f5842d7ea732df31
r11=2cafd2c44cebf15d r12=2cafd2c44cebf15d r13=2cafd2c44cebf15d
r14=2cafd2c44cebf15d r15=2cafd2c44cebf15d
iopl=0 nv up ei pl nz na po cy
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010207
ffffffff`ffffffff ?? ???
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: ffffffffffffffff
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: ffffffffffffffff
Attempt to execute non-executable address ffffffffffffffff
PROCESS_NAME: r5apex.exe
EXECUTE_ADDRESS: ffffffffffffffff
FAILED_INSTRUCTION_ADDRESS:
+0
ffffffff`ffffffff ?? ???
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: ffffffffffffffff
IP_ON_HEAP: ffffffffffffffff
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.
STACK_TEXT:
000001f8`179a7740 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffffff`ffffffff
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: r5apex.exe!unknown_error_in_process
MODULE_NAME: r5apex
IMAGE_NAME: r5apex.exe
FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_AVRF_c0000005_r5apex.exe!unknown_error_in_process
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.0.0
FAILURE_ID_HASH: {7fa0bc25-af75-e133-b28c-1d9a2938f594}
Followup: MachineOwner
---------
Have you tried increasing the page file size?
Typically if it tries to access an invalid address your page file is too small.
This is what I personally recommend:
1. Press the Windows logo key + the Pause/Break key to open System Properties.
2. Select Advanced system settings and then select Settings in the Performance section on the Advanced tab.
3. Select the Advanced tab, and then select Change in the Virtual memory section.
4. Clear the Automatically manage paging file size for all drives check box.
5. Select Custom size, and then set the "Initial size" and "Maximum size" values for the paging file. We recommend that you set the initial size to 1.5 times the amount of RAM in the system. (Max size should be set to 2.0x the ram size, if that doesn't fix it use 3.0x the ram size)
6. Select OK to apply the settings, and then restart the system. If you continue to receive "out-of-memory" error messages, increase the "initial size" of the page file.
Please let me know if that fixes it for you, otherwise I'm going to do some more digging... again.
@XHelperZI have tried that but it crashed with the same error. I have 32GB RAM in my PC and even with 20+ GB available it crashes. I cannot see a reason why it would try to use the page file. If u need more infos from me or want me to test stuff we can communicate over instant messaging if u want. Discord, Steam, Origin, what ever.
I was using Steam. I redownloaded Apex form Origin and the version from Origin is working!
Suddenly the issue could be Denuvo related...
I've reached out to a Dev, currently awaiting response.
I thought Denuvo is used as copyright protection tool but Apex is free to play. Does Apex use it against hacking?
Some people on Reddit were able to fix it by disabling/removing unverified drivers from windows. That fix did not work for me but I only had one unverified driver anyways. Haven't tried disabling other drivers so far.
