I just started running into this issue as well. Easy Anti-cheat prevents the game and steam from shutting down cleanly and eventually leaded to windows crashing! They need to fix this crap!

Originally posted by Xsile:

I just started running into this issue as well. Easy Anti-cheat prevents the game and steam from shutting down cleanly and eventually leaded to windows crashing! They need to fix this crap!

Yup ive tested this multiple times.

It's only this game.

I play fortnite on and off and that uses EAC as well and have never faced this issue there.

Originally posted by DudeBro69:

Reposting from a reply.
This is becoming common for quite a few of us.

I have had these happen in the past 3 months as well some times.

Today the game launched and went to black screen and then you could hear the music.
But game was unresponsive.

Then eventually in under a minute the entire pc froze/

I did some digging and it turns out that it is related to EasyAntiCheat.
The exact event viewer error:

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

This is the only game this happens to.


PC Specs:

Intel Core Ultra 7 265k
64GB ddr5 6000mhz cl30
RTX 5080
980 Pro NVME

the reason for why so many old bugs are still not fixed to this day is because no one in the player base lets the devs know this is still a problem or the devs dont know how to even fix it heck every update makes the game run even worse or its maxing out my cpu wich is all so not a good thing it should be close to 50% on my gpu and 50% on my cpu but its more like 100% on cpu and 5 to 10 % on gpu lol.

Originally posted by HaloSign:

This error is an indicator for an underlying issue in the OS. EAC runs on BypassIO configured storage without problems, so do not take this error message literally.

Reasons could be e.g.:

#1 bugged/corrupted driver such as Intel RST driver
#2 corrupted OS files
#3 Inconsistent EAC installation

For #1 try to reinstall or repair the corresponding driver (most current drivers can be downloaded on the webpages of the manufacturers such as Intel or Samsung)

For #2 run (as Administrator in the PowerShell or Command Window)
sfc /scannow
dism /online /cleanup-image /restorehealth

Additionally: repair all Microsoft Visual C++ redistributables (best when using: “Control Panel\All Control Panel Items\Programs and Features” and then per C++ library press change and repair )

For #3 remove and reinstall EAC

Done all of that in the past

I even reinstalled windows fresh.

Originally posted by HaloSign:

Originally posted by DudeBro69:

Done all of that in the past

I even reinstalled windows fresh.

Which SSD do you have?
Is the Steam Game folder on C: or do you have more than one SSD?

Check if you have the SSD management software installed. E.g. for Samsung it is the "Magician" app. These apps provide some good checks for healthy and integrity of the SSDs. Firmware can be validated as well (there is maybe some updates).

What is the exact TFD error message from the folder:
c:\Users\<your user name>\AppData\Local\M1\Saved\Crashes.

Check the most recent folder there and look for the file CrashContext.runtime-xml.
There is a line "<ErrorMessage>". Post the info here as well

It was on C for some time, i moved it to my 2nd nvme which is a 980 not a 980 pro
Coz somewhere i read it could be a gen4 vs gen3 nvme issue.
So right now i placed it on my gen 3 nvme

It was on the Samsung 980 pro NVME on C. Now i placed it on D, which is on the 980 regular not pro

The firmware is fully updated on the Samsung Magician app as well as the app itself.

Also i dont see a crash folder in that exact location you mentioned.

Another place i read it could be an intel virtualization issue with that particular EAC from 2024 patch i believe. The core ultra series dont use hyperthreading as it already has 20 cores so they did not need hyperhtreading but EAC was patched with hyperthreading.

Again this was another post somewhere.
I don't know exactly whats what, im looking at any possible solution.

After spending 600 bucks in game and then the game to possibly kill my computer, it sucks.

Seems like this issue is popping up in places more commonly now

Originally posted by HaloSign:

Originally posted by DudeBro69:

It was on C for some time, i moved it to my 2nd nvme which is a 980 not a 980 pro
Coz somewhere i read it could be a gen4 vs gen3 nvme issue.
So right now i placed it on my gen 3 nvme

It was on the Samsung 980 pro NVME on C. Now i placed it on D, which is on the 980 regular not pro

The firmware is fully updated on the Samsung Magician app as well as the app itself.

Also i dont see a crash folder in that exact location you mentioned.

Another place i read it could be an intel virtualization issue with that particular EAC from 2024 patch i believe. The core ultra series dont use hyperthreading as it already has 20 cores so they did not need hyperhtreading but EAC was patched with hyperthreading.

Again this was another post somewhere.
I don't know exactly whats what, im looking at any possible solution.

After spending 600 bucks in game and then the game to possibly kill my computer, it sucks.

Seems like this issue is popping up in places more commonly now

OK, just be on the same page regarding the M1 folder. Open the explorer and click step by step thru the path.
c:\
Users
<your user name>
AppData
Local
M1
Saved
Crashes

When you do not use the English GUI then folder "Users" will be displayed translated in your language!

Inside crashes folder: the folders looks like this “UECC-Windows-F6D8934B48F5003372CF44B7D4D85A30_0000”.
In each folder you potentially can see the file “CrashContext.runtime-xml”.

NB: AppData is usually hidden so you have to unhide it first in explorer, options, View: “show hidden files and folders” must be checked.

Go step by step toward the folder crashes. When you do not have it then the whole installation might be corrupted as this folder is created by default.

In this case open Steam and validate the TFD Installation Files for consistency (right click on TFD Installed Files, “check installed files” button (as I do not use the English Steam GUI the wording might differ… check).

Yup i went exactly there.

All the folders lined up correctly expect there is no Crashes folder.

I did a verify in

Originally posted by HaloSign:

Originally posted by DudeBro69:

It was on C for some time, i moved it to my 2nd nvme which is a 980 not a 980 pro
Coz somewhere i read it could be a gen4 vs gen3 nvme issue.
So right now i placed it on my gen 3 nvme

It was on the Samsung 980 pro NVME on C. Now i placed it on D, which is on the 980 regular not pro

The firmware is fully updated on the Samsung Magician app as well as the app itself.

Also i dont see a crash folder in that exact location you mentioned.

Another place i read it could be an intel virtualization issue with that particular EAC from 2024 patch i believe. The core ultra series dont use hyperthreading as it already has 20 cores so they did not need hyperhtreading but EAC was patched with hyperthreading.

Again this was another post somewhere.
I don't know exactly whats what, im looking at any possible solution.

After spending 600 bucks in game and then the game to possibly kill my computer, it sucks.

Seems like this issue is popping up in places more commonly now

OK, just be on the same page regarding the M1 folder. Open the explorer and click step by step thru the path.
c:\
Users
<your user name>
AppData
Local
M1
Saved
Crashes

When you do not use the English GUI then folder "Users" will be displayed translated in your language!

Inside crashes folder: the folders looks like this “UECC-Windows-F6D8934B48F5003372CF44B7D4D85A30_0000”.
In each folder you potentially can see the file “CrashContext.runtime-xml”.

NB: AppData is usually hidden so you have to unhide it first in explorer, options, View: “show hidden files and folders” must be checked.

Go step by step toward the folder crashes. When you do not have it then the whole installation might be corrupted as this folder is created by default.

In this case open Steam and validate the TFD Installation Files for consistency (right click on TFD Installed Files, “check installed files” button (as I do not use the English Steam GUI the wording might differ… check).

Yup did exactly as you asked.

The folders lined up exactly except there is no Crashes folder in the final location at Saved

I ran the Verify Integrity option in steam to maybe fill in any missing or corrupted files and nothing.

It did not create the Crashes folder.

I believe a crash has to happen to create the folder?? maybe?

I know some other games needed a crash to happen and same in windows, crash creates crash data and maybe the folder itself?

My understand is that EAC is stalling the pc even before the game crashes.
Or maybe something else is going on here?


The game screen is black and then I can alt tab for maybe the next 15 seconds and then soon enough the computer itself freezes.

Other times it goes to the first screen but is stuck at connecting and then in a few seconds it freezes at connecting

It wont BSOD just a freeze. Everything unresponsive

This leads me to do a hard shut down holding the power button


I can play the game now, but this crash could happen any time again during game launch. The game has never crashed during play. This happens only during the launch phase of the game.

It comes and goes weekly

Everytime I click play on steam, It's a gamble and has become a high stress situation in my head.
I'm constantly rethinking if i should just abandon the game to save my PC

Haven't read every post in the thread but this usually helps when I start having this problem:

- uninstalling and reinstalling EAC (in the game's installation folder there are .bat files that let you do it)
- try deleting your graphics shader cache, updating your graphics card driver will also delete them.
- verify integrity of game files in steam library, especially after patches
- reinstall the game

You will not find any crashlogs for this issue but it is very real and has been reported by more than enough users.

Originally posted by Ahriman:

Haven't read every post in the thread but this usually helps when I start having this problem:

- uninstalling and reinstalling EAC (in the game's installation folder there are .bat files that let you do it)
- try deleting your graphics shader cache, updating your graphics card driver will also delete them.
- verify integrity of game files in steam library, especially after patches
- reinstall the game

You will not find any crashlogs for this issue but it is very real and has been reported by more than enough users.

Yup there are no crash logs for this because the system freezes before the crash can even be logged

BSOD from windows logs are different, they are built to store the logs
Game crash logs depend on windows basic function to even log it

All of those things are good checks but they have almost no effect as in i did all of that very recently and pretty much the next day system froze.


Again only this game.

Ppl will say oh its your setup etc etc but i use my setup for so many things including vr games, video editing, vfx, colouring and a large variety of other games and mmos including old and new etc and everything works flawlessly except this game

What does running this say? or whatever the drive you installed to...

fsutil bypassIo state /v c:\

Originally posted by Rogue:

What does running this say? or whatever the drive you installed to...

fsutil bypassIo state /v c:\

C:\Windows\System32>fsutil bypassIo state /v c:\

BypassIo on "c:\" is currently supported
Storage Type: NVMe
Storage Driver: BypassIo compatible
Driver Name: stornvme.sys



My drives are

C: Samsung 980 Pro Gen 4
D: Samsung 980 Gen 3

I read somewhere that particular version of EAC has gen4 bypass io issues

so just 3 days ago i moved my TFD install from C to D drive.

Since then no crash yet.

Could be that solved it or maybe it will freeze my system again for some other reason

Also that "error" message is just a warning message from EOS. Nothing to do with crashes or even black screen...

Black screen can be a myriad of things, from faulty monitor to PC not waking up from sleep state properly(restart pc...)

Originally posted by Rogue:

Also that "error" message is just a warning message from EOS. Nothing to do with crashes.

I know.

I shared that as in that is the last thing the event viewer sees.

Then i check online if there is any correlation anywhere.

Ppl say it could be either gen 4 ssd with that EAC version issue.

Or it could be tied to the new intel cpus not using hyperthreading because the new cpus already use physical 20 cores instead of faking 20 cores. While that EAC is outdated as in it seems like 2024 EAC which is built for hyperthreading in mind. Seems like maybe EAC needs an update?
But again even ppl with older cpus seems to be facing this issue but many seem to have this samsung 980 pro

Its hard to say whats what.

Could be anything but thats the last data available on event viewer

I don't know too much, im just collecting all data possible

Originally posted by Rogue:

Also that "error" message is just a warning message from EOS. Nothing to do with crashes or even black screen...

Black screen can be a myriad of things, from faulty monitor to PC not waking up from sleep state properly(restart pc...)

Black screen as in monitor is still on and I can see the cursor.
Its clearly not a monitor issue.

TFD first splash screen or intro screen hasnt shown yet but you can hear the music.
I can alt tab and see the taskbar but i cant click on anything.
Cursor will move around for maybe 15 seconds or so.
Im guessing the system already froze and its only running from residual memory.
And then soon enough even cursor wont move as in a full system freeze.

Other times it will even go to the first intro screen where it says ''connecting'' and it will stay stuck on 'connecting' slowly blinking but never changing.

If it stays stuck on 'connecting' and never changes to the enter button, i know the system is about to freeze at any moment.

Staying stuck on ''connecting'' has been the clearest sign of the freeze about to happen
Which is a closer indicator to the game or eac tied issue