Regarding the issue of APEX not starting.

Ive been losing my mind over this same issue. Just CTD's all the time when playing at random times. Same exact error in my Event Viewer and it looks like the Driver for Easy Anti Cheat is the issue. Here's my output from running the "fsutil bypassIo state c:\" command: 

C:\Windows\System32>fsutil bypassIo state c:\
BypassIo on "c:\" is not currently supported
    Status:  506 (At least one minifilter does not support bypass IO)
    Driver:  EasyAntiCheat_EOSSys
    Reason:  The specified minifilter does not support bypass IO.
    Storage Type:   NVMe
    Storage Driver: Not BypassIo Compatible

Would also really love some solution to this. 

I am also having the same EAC related CTD, every two games it crashing in the middle or end of the third game. No crashlog or error message except for a BypassIO error in event viewer shown below. 

File System Filter 'EasyAntiCheat_EOSSys' (Version 10.0, ‎2025‎-‎03‎-‎28T13:10:53.000000000Z) does not support bypass IO.
Supported features: 0x4.

I also can't run the EAC setup file, it just shows command prompt for 1 millisecond then disappears even if I run it as administrator. I've tried pretty much everything, re downloading the game, uninstalling EAC and reinstalling it entirely and even tried the manual repair option EAC has on their website (https://www.easy.ac/en-US/support/articles/eac-windows-service). the only thing I haven't done is disable BypassIO on the drives which I shouldn't have to do. 

Unfortunately, I can't move the game to a different drive because both of my drives are BypassIO compatible, I'm not sure if this is a EA problem or a EAC problem.

Not really sure what else to try.

Artificialprayer​, HighwayTwo​, aartsA​, & Big_Ronnie_C​ In Windows Defender, (which is also called "Windows Security" on Windows 11), do you have the "core isolation" security setting enabled in the "device security" tab:

Navigation: Windows Defender/Security > Device Security > Core Isolation > Core Isolation Details > Memory Integrity

If you do have the "core isolation" security setting enabled, turn it off, restart your PC, and then see if you can play the game:

Note: While the "core isolation" security setting is very important, the game won't run on some PCs because of it. The solution for this was found by E9ine_AC​, as on my PC, I'm still able to run the game with the "core isolation" security setting enabled.

This doesn't seem to be my problem, as Core Isolation was already off for me. Although this may fix the issue with crashing on launch for whoever has that issue, but it doesn't seem to be the cause of crashing with the bypassIO related error in event viewer. 

My crash happens 2-3 games into the initial launch, I've just been restarting my game after every 2 games to make sure I don't crash in the middle of the third one.

aartsA​ Can you upload a DxDiag log? I might be able to figure out what's going on by looking at that log.

I know for some users, the issue was due to having certain Nvidia GPUs and drivers, (so players had to roll back to a previous driver).

This is my DxDiag. I was running apex on a 572.83 NVIDIA Driver previously, and updated to the current 576.02 yesterday evening, Both still gave me the same event viewer error. 

I know on the trello it mentions a DXGI_ERROR_DEVICE_REMOVED crash with nvidia gpus paired with certain cpus. I am not getting this crash fortunately. 

aartsA wrote:

I know on the trello it mentions a DXGI_ERROR_DEVICE_REMOVED crash with nvidia gpus paired with certain cpus. I am not getting this crash fortunately. 

I had mentioned the Trello post as it was something that could possibly be related. However, in that Trello post, have you tried any of the possible workarounds?, (especially the part about rolling back your GeForce Game Ready Driver to 561.09)?

If you have already tried the possible workarounds, another thing you could try is to repair your system's files:

• Open the Command Prompt in administrator mode
  
  
• Type, "DISM /Online /Cleanup-image /Restorehealth" (without the quotes), and wait for it to finish.
  Note: DISM stands for "Deployment Image Servicing and Management tool". It often repairs Microsoft related files, such as issues with Window apps. Some problems with the next file checker can only be fixed after running this one first.
  
  
• Now type, "sfc /scannow" (without the quotes), and wait for it to finish.
  Note: sfc stands for "System File Checker". This one will repair system files, (such as important Windows drivers).
  
  
•  Lastly, restart your PC.

As for the DxDiag log, everything seemed to be in order as I wasn't seeing anything that could possibly be an issue, (besides the GPU's version, as I've mentioned you could try version 561.09).

Outside of that, the issue with the BypassIO largely seems to be a conflict between Windows Defender/Security and the EAC, (and if it is, I would hope that EA/Respawn looks into getting it resolved because I don't know about you, but I wouldn't want to play a game that makes me turn off security settings).

Midnight9746​ Thank you for those suggestions. Both of the scans came back clean for me. I did actually roll back to 566.36 after seeing another video on GPU crashes. The lack of crash logs or error messages just has me trying anything at this point, honestly. I can certainly try downgrading to 561.09 and seeing if that helps too. Ive attached my DXDiag log as well (before downgrading).

For what it's worth, my Core Isolation setting is also already off.

Thank you for looking at all of this! 

So the solution is to turn off security features to appease a kernel level anti-cheat even more? Lol, nah, I uninstalled Apex, not worth all the trouble

Big_Ronnie_C wrote:

So the solution is to turn off security features to appease a kernel level anti-cheat even more? Lol, nah, I uninstalled Apex, not worth all the trouble

I honestly don't blame you for uninstalling the game, (as I would too, if I had to turn off any security setting as well).