File System Filter EasyAntiCheat_EOSSys` does not support Bypass IO [CRASHING]

Question

Hello,

For about a month now, I would have trouble with a game (Fortnite) crashing a steady amount due to the anti cheat Epic Games uses, EasyAntiCheat. When I look in event viewer after a crash, it presents this:

_______________________________________________________________________________________________________________________

Log Name: System

Source: Microsoft-Windows-FilterManager

Date: 12/14/2024 10:05:04 PM

Event ID: 11

Task Category: None

Level: Warning

Keywords:

User: SYSTEM

Computer: DESKTOP-NLJH1M8

Description:

File System Filter 'EasyAntiCheat_EOSSys' (Version 6.1, ‎2024‎-‎11‎-‎27T06:19:31.000000000Z) does not support bypass IO.

Supported features: 0x4.

Event Xml:

11

0

3

0

0

0x8000000000000000

66328

System

DESKTOP-NLJH1M8

EasyAntiCheat\_EOSSys

6

1

2024-11-27T06:19:31.0000000Z

0x4

_______________________________________________________________________________________________________________________

I tried reinstalling the game which didn't work, along with internet research which didn't present many results and no working solutions. I disabled my AV to see if that was the cause as well, but no difference.

At this point I am at my wits' end.

Any solutions or ideas?

All will be greatly appreciated!

Cheers,

PM

Answer 1

Have you checked Core Isolation is off?

Also ensure that you completely uninstall EasyAntiCheat

https://www.easy.ac/en-US/support/articles/eac-windows-service

Then do reboot, then reinstall after the above actions I stated.

This works on Intel Core Ultra 9 I can’t say if this fix works on Raptor Lake, etc.

Answer 2

been dealing with the same issue on apex and cant figure out how to fix it. i can play for about 1-2 hours before it just crashes on me. has anyone found a way to fix this issue???

Answer 3

It's early days,  but I think I am able to share a potential resolution that may help other users. I am an IT Field Engineer, and also run the Youtube Channel Next Level Sim Gaming

 As stated, the issue is that Easy Anti Cheat shows that File Filter does not support Bypass IO, this is a widespread issue that is affecting a number of Core Ultra 9 owners, largely due to the new architecture of the processor, but also other users in general, the issue is that the NVME driver is not correctly filtering the ByPass IO feature, which is a Windows 11 feature, and detailed here -  

BypassIO for Filter Drivers - Windows drivers

Suggested fixes show that disabling Core Isolation, and Virtualisation, and being on the latest Windows 24H2 should mitigate this issue, this is not however correct for Intel. First of all, I completely uninstalled EasyAntiCheat. On my system for example, I have 4 Nvme drives, all are Bypass IO compatible, so the initial error did not make sense to me, upon investigation of the filter drivers, the Intel RST driver relies on Virtualisation and Hyper V to run correctly 

C:\Windows\System32>fsutil bypassIo state C:\
BypassIo on "C:" is currently supported

Storage Type:   NVMe

Storage Driver: BypassIo compatible
I set the following elevated commands to activate Hyper V, and also Credential Guard, also activated Intel Virtualization, Core Isolation is still disabled (open command prompt as admin, and copy and paste each value)  ****

DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V reg add

HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard /t REG_DWORD /v

EnableVirtualizationBasedSecurity /d 1 /f reg add

HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard /t

REG_DWORD /v Enabled /d 1 /f reg add

HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity /t REG_DWORD /v Enabled /d 1 /f reg add

HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\KeyGuard\Status /t REG_DWORD /v CredGuardEnabled /d 1 /f reg add

HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\KeyGuard\Status /t

REG_DWORD /v KeyGuardEnabled /d 1 /f

I also in BIOS disabled AMI Native NVME Driver Support
I then reinstalled EasyAntiCheat from drive H from the iRacing EAC folder
Previously the game would crash within minutes, however now, I have played successfully for some time now, and have had no Events relating to the issue, sharing here if anyone else has the same issue 😀

Answer 4

This is what I did to resolve the event errors caused by EAC leading to crashes. It’s been a little over a month now and so far, my system is stable, most event errors are gone and no longer experiencing any game crashes.

The only game's I've tested these steps with is Elden Ring and Lords of the Fallen but this should help with most games that specifically require EAC.

ISSUE 1 : Event ID 2 Kernel Event Tracing.

This was reporting every 60 seconds (literally) when I was running games that use EAC.

ISSUE 2 : Event ID 11 FilterManager

File System Filter 'EasyAntiCheat_EOSSys' (Version 6.1, ‎2024‎-‎12‎-‎13T09:34:34.000000000Z) does not support bypass IO.

Supported features: 0x4.

PLEASE NOTE: You may still see a few (Event 11 FilterManager) in the event viewer but in my case, only showing 3x when launching an EAC game. After that, my event viewer is clean for the entirety of my gaming sessions lasting 8-10 hour. Network connectivity is great, Online multiplayer/Coop gameplay has no disconnects and absolutely NO crashing or freezing. Plus, these steps also removed/resolved hundreds of Kernel Event Errors that was previously showing every 60 seconds while playing an EAC game 😀

SOLUTION :

STEP 1 :

Find ALL "EAC Exe" then Right click -> Properties -> Compatibility and Check the box to Run this Program as an Administrator. This needs to be done inside both the EAC Main Folder (likely C:) and inside the Game Folder using EAC. In my case, I install my games on the D: but simply go to wherever the game is installed. I've typed the locations but the exe in BOLD are the EXE’s you're looking for.

Main Folder :

• C:\Program Files (x86)\EasyAntiCheat_EOS\ EasyAntiCheat_EOS.exe

Game Folder :

• D:\steamapps\common\GameTitle\Game*start_protected_game.exe*

- D:\steamapps\common\GameTitle\Game*Game.exe*

• D:\steamapps\common\GameTitle\Game\EasyAntiCheat\ easyanticheat_eos_setup.exe

STEP 2 :

Add the same EAC.Exe to the "Allow an App through firewall" List!

Click on Settings -> Privacy and Security -> Open Windows Security -> Firewall and network protection -> Allow an app through firewall -> Change settings -> Allow another app -> Browse ->

Main Folder :

• C:\Program Files (x86)\EasyAntiCheat_EOS\ EasyAntiCheat_EOS.exe

Game Folder :

• D:\steamapps\common\GameTitle\Game*start_protected_game.exe*

- D:\steamapps\common\GameTitle\Game*Game.exe*

• D:\steamapps\common\GameTitle\Game\EasyAntiCheat\ easyanticheat_eos_setup.exe

Hoping this helps someone. I do not work for Microsoft or have an affiliation with them. Please let me know if you have any questions and would be happy to help.

✌️ Will

P.S. If you're still having crashes and/or still see a lot of event errors in event viewer, you may have other non EAC related issues and for the best and cleanest results : start fresh by wiping/reformating ssd’s, then re-install Windows from a USB media creation tool.

(Don’t use reset my pc, nor reinstall windows from disk or cloud as it tends to keep remnants with corrupted/conflicting issues).

After reinstalling Windows with USB, let it perform all updates and driver installations. After that, pause updates, disconnect internet, boot into safe mode, DDU GPU drivers, boot back into normal mode, re-install the most stable GPU drivers (Not necessarily the most recent...pointing at you Nvidia), then follow the STEP 1 & 2 above for your EAC games to run at their best again!

Good Luck!

Answer 5

I had the same issue on Windows 11 and noticed it started after I received a recent virus definition update in Microsoft Defender. My workaround is this: whenever I experience problems and the game crashes or disconnects me from the session, I close the game, open the Windows virus scanner, update the security definitions, and run a quick scan. Then I restart the game, and it should work again—at least, that’s what worked for me. Good luck!