Now what? Error or not? AN ABOMINATION?

I think it is a pretty good abomination. I can play, but for 20-30 minutes, then the game gives up. Also if I exit before 25-30 minutes, it freezes, only alt-tabbing and manually killing the game helps.

Graphics drivers: latest (AMD Radeon 22.5.2), and one version older (22.5.1).
Game files: verified.
Mods: yes, and without them too (disabled in FC launcher, deleted modlist.txt file, cut mods from the folder and put on a USB-stick - would have been better to take a screenshot of that).
Antivirus: Windows Defender, added the whole steam folder to the exclusions.

By the way: it is pretty annoying that I can not play, but weirdly funny too at the same time.

2 Likes

So it is crashing without mods?

What does your crash log say?

C:\Program Files (x86)\Steam\steamapps\common\Conan Exiles\ConanSandbox\Saved\Logs.

Find the reason for the crash which is usually the lines leading up to FATAL ERROR.

2 Likes

[2022.06.06-16.11.05:827][693]LogThreadingWindows:Error: Runnable thread TaskGraphThreadBP 14 crashed.
[2022.06.06-16.11.05:827][693]LogWindows:Error: === Critical error: ===
[2022.06.06-16.11.05:827][693]LogWindows:Error:
[2022.06.06-16.11.05:827][693]LogWindows:Error: Fatal error!
[2022.06.06-16.11.05:827][693]LogWindows:Error:
[2022.06.06-16.11.05:827][693]LogWindows:Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000f722
[2022.06.06-16.11.05:827][693]LogWindows:Error:
[2022.06.06-16.11.05:827][693]LogWindows:Error: !0x0000000000000000
[2022.06.06-16.11.05:827][693]LogWindows:Error:
[2022.06.06-16.11.05:827][693]LogWindows:Error: Crash in runnable thread TaskGraphThreadBP 14
[2022.06.06-16.11.05:854][693]LogExit: Executing StaticShutdownAfterError
[2022.06.06-16.11.05:854][693]LogWindows: FPlatformMisc::RequestExit(1)

This is the last section of the log, here is the fatal error.

2 Likes

TaskGraphThreadBP is an unreal thing. Seen it reported in other games. Try a verify game files in steam.

3 Likes

I did that with no positive results… I guess I’ll wait until the update comes out :laughing:
(or a Windows update, that would not be the forst case it borked one or another game(s).)

1 Like

Exactly.
Ryzen 5700X with a Radeon 6700XT.
I experienced a lot of weird stuff that fixed itself seemingly (I did not have to do anything, just wait till some updates came out game/system/driver-wise).

Do you (or any of you kind guys) have any ideas what should I do?
Because if every time an update comes (sytem, drivers), and f…s up one game, and I can’t do anything just wait for a “miracle”, that setup of mine won’t last long.

1 Like

Dunno, it seems related to your CPU at this point. Try messing with the affinity of CE.

2 Likes

One heart because you used the word abomination, catchy :rofl::rofl::rofl:. I hope your problem will be solved m8, I need you around :wink:

2 Likes

I hope so too. I just DDU’d and reinstalled the graphics driver, the chipset drivers, anything, but still.
So I’m more and more closer to the conclusion that this is a windows update issue. Might try deleting the last updates and see if it’s working!

1 Like

Good luck @rolee9309, thanks @drachenfeles for your help, it’s really appreciated really, I want this guy back to fun immediately.

1 Like

This was happening to me about a third to a half of the times I started the game - no exaggeration. I was able to get that down to about one in 20 loads by setting the game’s FPS cap limit to 60. Before I was having to just reload the game repeatedly until it made it past the error. Now when It happens I’m doing like you and playing for about 30min. till it just quits and then on reload I don’t get the error - so far.

So, cap the FPS to 60 and pray! :wink:

3 Likes

I’ll give it a shot too! Thanks.
Capped at 120, but it can be too much.
I know dome games which has problems at uncapped or capped at high FPS (looking at you Claptrap in the elevator :angry: ).

Yeah, I was having that trouble at 140 and 120… It took a reduction down to 60 to make the difference.

This is absolutely a bug that needs to be fixed though!

1 Like

Yeah… whatever it is that isn’t computing, only seems to happen during the initialization and allocation phases though. You know, just the startup procedures. Sounds like they need to add some wait states or something… :stuck_out_tongue:

2 Likes

I can not unistall them, they are 2021. april updates, and my system was reinstalled 3 months ago (game is on a different disk, after the system reinstall, the game worked perfectly).

@TeleTesselator capping the FPS to 60 also did not help.

1 Like

An other option is to see if I have a system restore point to the start of May.

Eadit: won’t happen, the only dates are 06.06.

Oh man…

A few weeks ago in the bug report section a moderator here responded to this same thing (being reported as a bug) and provided a list of about 10 or 15 possible fixes. They were things like remove all overclocks, and so on. I wonder if maybe you can find that thread and try a few of them.

1 Like

Did you mean by this? I tried everything sadly, and STILL, the error persists… :slightly_frowning_face:
I mean everything but once, I keep forgetting: I set the VGA profile to silent, and the undervolted the CPU via PBO2. I disable them if I get back home, and hope for the best. This is the last thing I could do. If it won’t work, I’m gonna wait till 3.0 :grin:

1 Like

Yes.

1 Like

Nope, did not help.

Thank you guys for all the help by the way! Appreciate it.
But now I have to wait for a driver/windows/game update, and hope for the best.

1 Like