PC Freezes yet again (goodbye TFD) :: The First Descendant General Discussions

Store Page

The First Descendant

All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

The First Descendant > General Discussions > Topic Details

DudeBro69

6 Aug @ 3:05am

PC Freezes yet again (goodbye TFD)

(I won't be around much but hope this sheds light for those facing this and for others who are about to face it)

3rd time this week and probably 15th time in the past 3 months playing on and off.
PC froze at the usual ''connecting'' screen

Again event viewer shows last data.

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

Fortnite shows the same error but never crashes or freezes my pc so its probably this game code alone.

Ran every typical test you can think of

-memory scan
-windows health repair
-ssd check
-core isolation
-secure boot on and off
-verify file integrity
-reinstall EasyAntiCheat
-dism /online /cleanup-image /restorehealth
-Sfc /scannow
-Repair the c++ redistributables
-moved game from Gen 4 ssd to Gen 3 ssd

Only two things I havent done is force start the game without EAC which i dont want to risk.
Also have not tried to bypass the 2nd anti cheat used by the game which is called Black Cipher. I don't even know if there is even a way to locate where it is

Anyways, no change. Same freeze and only on this game.

I play maybe 20 games including VR games, many intensive, some others with EAC as well and they all work flawlessly.
Have not had a single bsod or crash or any issue imaginable with my setup except for this exact specific type of freeze and only with this game.

I was an avid supporter of this game from first playtest to this day and have spent over 600 bucks in game and played every season but i cannot just cannot destroy my computer in the process when a dev wont even respond or acknowledge this issue that has been repeatedly talked about for months.

Well i did my best.

Goodbye and good luck.

Specs:

Core Ultra 265k
RTX 5080
64gb ddr5 6000mhz cl30
Previously installed on - Samsung 980 pro - gen4 (crashed here)
Was currently installed on/now uninstalled permanently -Samsung 980 - Gen 3 (crashed here too)

Last edited by DudeBro69; 7 Aug @ 11:00am

< >

Showing 1-15 of 36 comments

Oddi

6 Aug @ 3:53am

I ask myself: Is there a way to diable bypassIO in Windows temporarely?

sry can't look after it due to lack of a windows system.

DudeBro69

6 Aug @ 4:19am

Originally posted by Oddi:
I ask myself: Is there a way to diable bypassIO in Windows temporarely?

sry can't look after it due to lack of a windows system.

Event viewer says the same thing in Fortnite but Fortnite has never crashed or frozen my pc ever

This is the only game of the 20 or so games im playing right now that freezes my PC.

With a heavy heart I have to quit this game.

The content on my drives are too valuable. Work and assets etc.

Last edited by DudeBro69; 6 Aug @ 4:37am

MadMat007

6 Aug @ 5:24am

Originally posted by Oddi:
I ask myself: Is there a way to diable bypassIO in Windows temporarely?

sry can't look after it due to lack of a windows system.

https://www.reddit.com/r/FortNiteBR/s/s2m3PJesk2
I did find this

Last edited by MadMat007; 6 Aug @ 5:25am

DudeBro69

6 Aug @ 5:44am

Originally posted by MadMat007:
Originally posted by Oddi:
I ask myself: Is there a way to diable bypassIO in Windows temporarely?

sry can't look after it due to lack of a windows system.

https://www.reddit.com/r/FortNiteBR/s/s2m3PJesk2
I did find this

I get the error on event viewer when launching Fortnite but it has no effect on the game.

It wont crash or harm the pc.

In fact that error should not affect the game or the pc.

In TFD for some reason it causes a crash and pc freezes.

Fortnite only uses EAC

TFD uses 2 anti cheats

EAC + Black cipher

I think EAC goes through and on connecting screen maybe black cipher causes the crash and freeze.

Sad day

Oddi

6 Aug @ 5:49am

Originally posted by MadMat007:
Originally posted by Oddi:
I ask myself: Is there a way to diable bypassIO in Windows temporarely?

sry can't look after it due to lack of a windows system.

https://www.reddit.com/r/FortNiteBR/s/s2m3PJesk2
I did find this

Very interresting - thx for that link

Qetu

6 Aug @ 1:33pm

When I get something like this launching TFD, I reset shader cache and then it launches.

vladeemer

6 Aug @ 2:02pm

I've had this installed on a 990 pro with 0 issues, but I'm running an AMD processor with a 4090. The I/O bypass is a Windows 11 thing, which is apparently problematic with certain hardware configurations

Kestrel

6 Aug @ 3:21pm

i hope core isolation is off

DudeBro69

6 Aug @ 4:22pm

Originally posted by Kestrel:
i hope core isolation is off

Yup

Did pretty much all the typical checks

memory scan
windows health repair
ssd check
core isolation
secure boot on and off
verify file integrity etc

CorZ

6 Aug @ 4:27pm

reinstall EasyAntiCheat

#10

DudeBro69

6 Aug @ 4:28pm

Originally posted by CorZ:
reinstall EasyAntiCheat

Done and done

Like the first thing

Have done pretty much anything reasonably doable you could find online

There wasnt much if anything left to do other than force start game without EAC or deep digging into how to bypas Black Cipher or redo all steps from scratch after reinstalling windows for the 2nd time.

It became pointless and dangerous for me to even play the game so its uninstalled now.

Can't run any other tests but hopefully others facing this problem can find some shelter.

Last edited by DudeBro69; 6 Aug @ 4:30pm

#11

CorZ

6 Aug @ 4:29pm

Originally posted by DudeBro69:
Originally posted by CorZ:
reinstall EasyAntiCheat

Done and done

Like the first thing

Have done pretty much anything reasonably doable you could find online

open command prompt as administrator

run this command

dism /online /cleanup-image /restorehealth

After this is finished

Sfc /scannow

Repair the c++ redistributables (open the files and run a repair each file please this are two different files)

https://aka.ms/vs/17/release/vc_redist.x86.exe

restart windows

https://aka.ms/vs/17/release/vc_redist.x64.exe

restart windows

#12

DudeBro69

6 Aug @ 4:33pm

Originally posted by CorZ:
Originally posted by DudeBro69:

Done and done

Like the first thing

Have done pretty much anything reasonably doable you could find online

open command prompt as administrator

run this command

dism /online /cleanup-image /restorehealth

After this is finished

Sfc /scannow

Repair the c++ redistributables (open the files and run a repair each file please this are two different files)

https://aka.ms/vs/17/release/vc_redist.x86.exe

restart windows

https://aka.ms/vs/17/release/vc_redist.x64.exe

restart windows

Done and done

This is the usual test done every month since the issue

There was no issue found after i ran those tests.
VCredists done, each one. One by one on programs and uninstall./

Just did it 3 days ago.

PC froze twice since.

Same spot, at the ''connecting'' screen

If the text does not change from ''connecting'' to the ''enter'' text then i know the pc freeze is about to happen any moment.

No theres no crash logs on M1 folder, if thats the next ask.
The pc freezes before the crash can even be logged.

This has been posted here and on reddit multiple times and the devs dont care.

There is no clean and easy way to even get to the devs.

Good luck to those facing and about to face it with any newer setups

Last edited by DudeBro69; 6 Aug @ 4:34pm

#13

CorZ

6 Aug @ 4:34pm

Originally posted by DudeBro69:
Originally posted by CorZ:

open command prompt as administrator

run this command

dism /online /cleanup-image /restorehealth

After this is finished

Sfc /scannow

Repair the c++ redistributables (open the files and run a repair each file please this are two different files)

https://aka.ms/vs/17/release/vc_redist.x86.exe

restart windows

https://aka.ms/vs/17/release/vc_redist.x64.exe

restart windows

Done and done

This is the usual test done every month since the issue

There was no issue found after i ran those test.

Just did it 3 days ago.

PC froze twice since.

Same spot, at the ''connecting'' screen

If the text does not change from ''connecting'' to the ''enter'' text then i know the pc freeze is about to happen any moment.

This has been posted her and on reddit multiple times and the devs dont care.

There is no clean and easy way to even get to the devs.

Good luck to those facing and about to face it with any newer setups

had the same problem back in the day, but I'm not 100% sure how I did it in the end.

Last edited by CorZ; 6 Aug @ 4:35pm

#14

vladeemer

6 Aug @ 4:57pm

Originally posted by DudeBro69:

This has been posted here and on reddit multiple times and the devs dont care.

There is no clean and easy way to even get to the devs.

Good luck to those facing and about to face it with any newer setups

My condolences, but this is most likely not something the devs are going to fix. It isn't a matter of them 'not caring' so much as it's a niche problem created recently by Microsoft that only fails with a subset of hardware configurations.

When you've calmed down and have the energy for more research, do some more digging and see if you can identify what about your setup is clashing with the unhelpful Windows 11 contribution and see if there's a workaround on your end. Waiting for devs to fix Microsoft's problems will only lead to frustration and disappointment.

#15

< >

Showing 1-15 of 36 comments

Per page: 1530 50

The First Descendant > General Discussions > Topic Details

Date Posted: 6 Aug @ 3:05am

Posts: 36