Fatal error! Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xfaf70000 !0x0000000000000000 Crash in runnable thread TaskGraphThreadBP 14

Conan Exiles PC Discussion PC Bug Reports
, ,
1

Basic Info:

Platform: Steam
Issue Type: Crash
Game Mode: =GAME MODE=
Server Type: =SERVER TYPE=
Map: =MAP=
Server Name: None
Mods: None

Bug Description:

As soon as I open the game, a fatal crash window appears that states the following:
“Fatal error! Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xfaf70000 !0x0000000000000000 Crash in runnable thread TaskGraphThreadBP 14”
When I close this window the came closes. I tried updating my graphics card’s drivers, I tried verifying the files’ integrity but nothing worked. I am running on a Intel Core i9-9900k, an RTX 2080 and 32Gb RAM

Bug Reproduction:

Press “launch” in Conan Exile on the Funcom Launcher

3

Update: If I ignore the fatal error window I can play the game for about 5 minutes before it closes

4

Check to see if you are missing any windows updates.

5

Am guessing you have also checked your connection speed, etc? That can also be a ‘thing’ sometimes - but everything darth says.

6

My Windows OS is perfectly up to date

7

The error occurs as soon as I open the game, so even if it was a connection problem, I could still play single-player. Furthermore, when I ignore the crash window I am still able to join an online server and play around for some 5 minutes, so the problem is definitely not connection.

8

That error is a resource error which means the game is trying to use an already used memory location; no mods pretty much rules out the game and leaves a driver or windows feature or other program getting in the way. So its either conflicting video from onboard vs your 2080, a windows update, or some other system software, unless you tinkered with your game files. So the solution is probably very system specific for you. Check your windows processes in task manager at the same time it occurs to see whats running. It may or may not help but you’ll probably have to start killing other processes and seeing which one is the problem.

9

Update: I reset my PC now the fatal error is no more.

10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.