Forum Discussion

Gforsie's avatar
4 years ago
Solved

BEX64 Apex Legends crash

I upgraded my PC with a new motherboard, cpu and ram (and an extra ssd), all other components stayed the same (e.g. graphics card). One of the reasons I upgraded was because I noticed me being bottlenecked by my CPU when playing games like Apex (which up to that point didn't cause me any issues, other than some framerate/connectivity stuff).

Here is my list of components:

  • Motherboard: MPG X570 Gaming Pro Carbon
  • CPU: AMD Ryzen 9 5900X 12 Core
  • Memory: 2x Corsair CMW32GX4M2E3200C16 (32gb total)
  • GPU: NVIDIA GeForce RTX 2060 Super

One of the first things I tried was to play Cyberpunk 2077 and Apex after I got my PC. Cyberpunk 2077 ran fine at a considerably higher framerate and fidelity.

However everytime I try to start Apex the EasyAntiCheat starts and when the Apex exe tries to run it crashes with no apex_crash file being created in Documents. However the Application event log creates two entries, one being an error and one being a information.

Error log:

Faulting application name: R5Apex.exe, version: 1.0.0.0, time stamp: 0x6177d9ae
Faulting module name: R5Apex.exe, version: 1.0.0.0, time stamp: 0x6177d9ae
Exception code: 0xc0000409
Fault offset: 0x0000000000d883cc
Faulting process id: 0x3c7c
Faulting application start time: 0x01d7d0e7345b8119
Faulting application path: E:\Games\Origin Games\Apex\R5Apex.exe
Faulting module path: E:\Games\Origin Games\Apex\R5Apex.exe
Report Id: 2d5e59a2-0790-498b-b6df-8ff5f5d80730
Faulting package full name:
Faulting package-relative application ID:

Information log:

Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: R5Apex.exe
P2: 1.0.0.0
P3: 6177d9ae
P4: R5Apex.exe
P5: 1.0.0.0
P6: 6177d9ae
P7: 0000000000d883cc
P8: c0000409
P9: 0000000000000007
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_R5Apex.exe_bd1619108abdc5ade391a93e9bce561adc6bb081_af34d796_ae2684d0-e49e-4c77-b357-cd2562fdaad7

Analysis symbol:
Rechecking for solution: 0
Report Id: 2d5e59a2-0790-498b-b6df-8ff5f5d80730
Report Status: 4
Hashed bucket:
Cab Guid: 0

I opened the .dmp file created by the crash and according to it the exception that was thrown is the following:

Security check failure or stack buffer overrun - code c0000409 (first/second chance not available)
For analysis of this file, run !analyze -v
r5apex!GetDenuvoTimeTicketRequest+0x12ef5c:

It looks like a Denuvo request from inside the r5apex.exe (not inside the EasyAntiCheat.exe) is causing this issue. Since the new patch just dropped I was hoping that would fix the issue. It didn't.

Here is a list of things I tried this past week to resolve this:

  • Updating windows
  • Updating NVIDIA drivers
  • Disable all in-game overlays from various programs (Origin, Steam, Nvidia, etc.)
  • Run Origin as admin
  • Run r5apex.exe as admin
  • Run EasyAntiCheat_launcher.exe as admin
  • Repair EasyAntiCheat
  • Uninstall/Reinstall EasyAntiCheat
  • Repair the game
  • Removing certain files (GFSDK_Aftermath_Lib.x64.dll, r5apex.exe, EasyAntiCheat_launcher.exe + /EasyAntiCheat + /__Installer/customcomponent/EasyAntiCheat, etc..) then repairing
  • Uninstall/Reinstall the game
  • Move the game to a different hard drive
  • Removing all overclocks (only memory was slightly overclocked)
  • Use various combinations of launch arguments: -novid, +fps_max unlimited, etc.
  • Check my memory (no errors)
  • Check my hard drives (no errors)
  • DisableData Execution Prevention with admin cmd (bcdedit.exe /set {current} nx AlwaysOff), rebooting
  • Removing and/or Adding EasyAntiCheat.exe and/or r5apex.exe to the Windows Defender firewall exceptions (both private/public)
  • Clean boot (disable all startups, etc.)
  • Reinstalling all VC++ x86/x64 installations
  • Uninstalling all VC++ x86/x64 installations, uninstallling Apex, rebooting, reinstalling Apex
  • Uninstalling all VC++ x86/x64 installations, uninstallling Apex, rebooting, installing all VC++ x86/x64 installations using the latest microsoft installers (2008, 2010, 2012, 2013, 2015-2019), rebooting, reinstalling Apex
  • Uninstalling my NVIDIA drivers, rebooting, installing the NVIDIA Studio drivers and when that didn't work then reinstalling regular NVIDIA drivers

Nothing so far has helped and this list is a rather comprehensive one I've gathered over the past week from many sources regarding potential issues on Apex, Origin, BEX64, etc.

I have had no other issues doing anything else with my PC (working, playing, etc.). Only Apex seems to misbehave.

The only thing I have not yet tried is to install the Steam version of Apex (since I read running the Steam version might work (better) while Origin doesn't and vice versa, though it can also create different issues you didn't have before).

... Help?

  • Hello @EA_Atic ,

    I have now tried to start Apex from Steam. It started. I did not however link my Origin Account when prompted. I simply quit the game after it started up. Then I started the Origin version up ... and it worked too.

    I guess there was some error in the process between the EasyAntiCheat and the r5Apex.exe that didn't go through on the Origin version, so once it went through on the Steam version the hiccup on the Origin version also resolved itself ... somehow.

    Anyway, case closed.

4 Replies

  • Hey there! @Gforsie Thanks for the super detailed post. 🙂 

    Have you tried running another windows account with Admin rights and what version  of windows do you have installed including patch version? 

    /Atic 

  • Hello @EA_Atic,

    I have Windows 10 Pro. Version "10.0.19043 Build 19043"

    I have set up a local admin account, logged off my regular account, logged into the test admin account, ran Origin as Admin, ran Apex, same issue, same Event Log messages. I think I might try out the Steam version unless you have other suggestions.

  • Hello @EA_Atic ,

    I have now tried to start Apex from Steam. It started. I did not however link my Origin Account when prompted. I simply quit the game after it started up. Then I started the Origin version up ... and it worked too.

    I guess there was some error in the process between the EasyAntiCheat and the r5Apex.exe that didn't go through on the Origin version, so once it went through on the Steam version the hiccup on the Origin version also resolved itself ... somehow.

    Anyway, case closed.