EasyAntiCheat Driver | EOSSys.sys loads often; does not support BypassIO → may conflict with DirectStorage

Can someone please help me with Epic Games, Easy Anti Cheat giving me BSOD and crashing my game and whole computer.
I have taken it to Micro Center where all hardware passed their hardware testing.
Windows was reinstalled and all drivers are up-to-date as of July 2025.

My NVMe drive passes SMART and surface tests, but BSODs only occur when EasyAntiCheat runs. System passes initial EAC checks but crashes after 25 minutes.
Logs show DCOM permission denials and BypassIO filter conflicts. The drive supports BypassIO, but EAC’s driver doesn’t. I suspect firmware-level I/O instability.

Only by reseating my RAM, I am able to get in the operating system as if nothing happened. Everything boots normally.
The problem is as follows:
I have started up Fortnite and get this log in my Event Viewer:

File System Filter 'EasyAntiCheat_EOSSys' (Version 10.0, ‎2025‎-‎06‎-‎26T05:00:45.000000000Z) does not support bypass IO.
Supported features: 0x4.

I have:
-Ran fsutil bypassIo state c:\ multiple times
-Verified EasyAntiCheat_EOSSys blocks BypassIO during Fortnite runtime
-Confirmed Microsoft NVMe driver is in use
-Ruled out Sysmon or PowerToys as the source of filtering
-Verified BypassIO works when Fortnite isn’t running
-Disabled Core Isolation (Memory Integrity)
-Disabled Virtual Machine Platform (VMP)
-Uninstalled and reinstalled Epic Launcher via direct website download
-Cleared out all leftover config junk, shader caches, and Epic webcache
-Repaired EasyAntiCheat
-Verified specs: AMD Ryzen 5 5600X, RTX 3050, 32 GB RAM, NVMe storage
-Confirmed OS: Windows 11 24H2 (Build 26100.4652)
-NVIDIA driver: 576.88 WHQL (July 2025)


Please can someone help me?

Read under"improvements"

glasskuter said:

Read under"improvements"

June 11, 2025—KB5063060 (OS Build 26100.4351) Out-of-band - Microsoft Support

support.microsoft.com

Click to expand...

Thank you for the heads up! I believe I have got KB5064489 installed already- it includes what was mentioned in the "improvements" section. I am currently on Windows 11 24H2 (Build 26100.4652).

It's been known online that Easy Anti-Cheat doesn't support BypassIO running.

Until that changes, you have to make a hard choice which is more important to you, playing your games or BypassIO for performance.

Could you please elaborate on how to make this choice?

Im fine with not having BypassIO. But how can I achieve that the game stops crashing?

Follow this YouTube video. Create a reg file which disables BypassIO, and restart Windows.

Thank you.

I have added the entry to the registry but the game still crashes.

Apparently BypassIO was already deactivated due to Avira.

In fact, when checking the state of BypassIO I got before adding the registry entry:

C:\Windows\System32>fsutil bypassio state c:
BypassIo on "C:\Windows\System32" is not currently supported.
Status: 506 (At least one minifilter does not support I/O bypassing)
Driver: rtp2 (avira driver)
Reason: The specified minifilter does not support bypass IO.
Storage Type: NVMe
Storage Driver: Not BypassIo Compatible

After adding the entry to the registry, I get

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

The game still crashes without error while at the same time the system event log like in OP is printed:

The file system filter 'EasyAntiCheat_EOSSys' (version 10.0, 2025-07-18T12:02:50.000000000Z) does not support IO bypass.
Supported features: 0x4.

It is driving me crazy. Do you have any other idea?

Do you have other drives where BypassIO might be enabled (which have their drivers for that device)?

Bearsbon said:

fsutil bypassio state c:

Click to expand...

Try adding the v switch to that and you will see more information.

I get with the v switch:

C:\Windows\System32>fsutil bypassio state /v c:
BypassIo on "C:\Windows\System32" is not currently supported.
Status: 506 (At least one minifilter does not support I/O bypassing)
Driver: EasyAntiCheat_EOSSys
Cause: The specified minifilter does not support bypass IO.
Storage Type: NVMe
Storage Driver: Not BypassIo Compatible
Driver Name: stornvme.sys

I do not have another drive. Would buying a drive that does not support BypassIO maybe help?

Try replacing "Services\EhStorClass" with "Services\stornvme" in the reg file.

Thank you. I did but the game is still chrashing.

garlin said:

Do you have other drives where BypassIO might be enabled (which have their drivers for that device)?

Click to expand...

I do not have any other drives.

I'm having the same issue. Nothing I've done seems to help

Maybe this is something only Epic Games can fix with an update to EAC?

Zixha said:

same issue

Click to expand...

same?

different?

Zixha said:

. Nothing I've done seems to help

Click to expand...

done?

not done?

Zixha said:

Maybe this is something only Epic Games can fix with an update to EAC?

Click to expand...

Please open a new thread with V2 results:

zbook said:

same?

different?




done?

not done?






Please open a new thread with V2 results:

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

Click to expand...

I have also encountered the same issue.
I have tried methods such as checking the hardware, updating drivers, reinstalling the system, and underclocking the CPU and GPU, but none of them resolved the problem.
This is a file obtained using the V2 Log collector. I wonder if the issue can be identified from it. Thank you!

Please open a new thread.

In the new thread please temporarily use English as the default language so that files can be scanned and read.

Even if the system display language is changed, it seems that the exported logs may still appear in other languages or garbled characters.
I wonder if this will help.