Re: apex integrity error please help

I havent even got wnything like thag on my pc i did a full hard resert and it still came up on my pc 

captprice345​ So after the full reset, you only installed Apex?

Just did a full reset downloaded my drivers and that’s it and apex and ea up and it does the same thing integrity error 0x8000001Midnight9746​ 

captprice345​ Hmm... that's weird.

Can you provide a DxDiag log?

1. Hit the Windows key
2. Search for "DxDiag" and run it, (it should look like a blue circle with a yellow X):
3. Click the "save all information button" on the DxDiag window:
4. Save the DxDiag log file as a txt file

Bro even on a fresh install of windows this error persist. keyboard and mouse only connected to the pc.

Stock windows install and steam and game. 

Integrity error. 5070ti + 5800x3d

I'm so sick and tired of this error and nothing works. 

diag

BASICCCCCCCC​ Thanks for the DxDiag log!

Everything looks like you should be able to play the game, although at the bottom of the file it does say this several times:

---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1261459314535681008, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: r5apex_dx12.exe
P2: 1.0.0.0
P3: 690a80fd
P4: StackHash_6763
P5: 0.0.0.0
P6: 00000000
P7: PCH_0D_FROM_ntdll+0x0000000000162814
P8: c0000005
P9: 0000000000000008
P10: 

When I looked up "BEX64 error", it popped up several solutions such as:

• Verifying game files, (which you both already did)
• Update and/or reinstall the graphics drivers, (might be what's causing the issue)
• Run the game in compatibility mode, (Right-click on the game's .exe file -> select "Properties" -> go to the "Compatibility" tab -> check the box for "Run this program in compatibility mode" -> select a previous version of Windows that the game is known to work on)
• Running the game as an Administrator, (which I don't think that would make much of a difference, but you could still try it)
• Disabling the "amBX service", (Windows + R -> run "services.msc" -> Find the "amBX" service -> Set the service to "disabled")
• Disabling the Data Execution Prevention (DEP), (Open the Command Prompt in Administrator mode -> "bcdedit.exe /set {current} nx AlwaysOff", (without the quotes) -> Hit enter -> Restart PC) (Although I don't like this one as it turns off a layer of security which performs additional checks on your PC's memory to ensure that no malicious code is running)
  
  

Out of all of these solutions I've found online, I recommend starting with updating the PC's drivers, (and leaving the DEP option for last since it involves turning off a layer of your PC's security, (which I don't know if Apex would get upset if it is disabled or not)).

it says that error several times from thee several times it crashes mid game,

issue persists with the default windows update NVidia driver on a fresh install of windows. 

persists with the latest NVidia driver as of this reply, and the previous release one before that. 

running as admin makes no difference. 

dont see an amBX service to disable. 

and also attempted DEP. 

i will be doing a separate windows 10 install to rule out windows 11. 

however makes no sense why it will keep crashing with this error on a fresh windows install, it must be some sort of hardware incompatibility coming from EA themselves. we just need a member of the apex team to have a look at this.

*update*

using a fresh windows 10 install instead did nothing still got the same error after 30mins of playing. 

thats it tbh im not even sure what this does 

I don’t think there’s going to be a fix anytime soon just going to buy a new pc lol

captprice345​ "DxDiag" stands for "Direct X Diagnostics".

It is a breakdown of your PC's components, (such as what GPU you are using, how many GBs of RAM you have, etc.)

It helps with identifying possible issues with your PC and with Direct X, (such as if there are any outdated drivers).

I'm mainly asking for the DxDiag log so when EA/Respawn looks over this thread, it can help them figure out what is going on.

Lastly, the DxDiag log you had shared matches the one already shared by BASICCCCCCCC​.

So what is there I can do