Fatal error after a while.

[CobbleSansPyro]

IDK why but I just keep getting a fetal error after a while of playing. I haven't noticed a specific action before crashing. However, it has only occurred, like i mentioned before, after a decent amount of time playing, on a single player world, while building. I do have mods but all of them are up to date. Could this be related to a memory issue?

[JJDrakken]

Originally posted by Mario Morbini:

IDK why but I just keep getting a fetal error after a while of playing. I haven't noticed a specific action before crashing. However, it has only occurred, like i mentioned before, after a decent amount of time playing, on a single player world, while building. I do have mods but all of them are up to date. Could this be related to a memory issue?

Until you can post a screen shot or error codes. Ain't no one going be able to help you.

[Shambeh-Bambeh]

Does it happen in other games you play too?

If the answer is yes, you might want to open up your command prompt in admin mode and type: sfc /scannow

If it finds and corrects any faults, you should reboot your pc.

[Bill Nye The Fire Guy]

Originally posted by JJDrakken:

Originally posted by Mario Morbini:

IDK why but I just keep getting a fetal error after a while of playing. I haven't noticed a specific action before crashing. However, it has only occurred, like i mentioned before, after a decent amount of time playing, on a single player world, while building. I do have mods but all of them are up to date. Could this be related to a memory issue?

Until you can post a screen shot or error codes. Ain't no one going be able to help you.

You say this on every post then proceed to not help anyone when they provide the error message. Just don't comment period since you have no intention of actually helping.

[CobbleSansPyro]

The error message is just: Fatal Error!
That's it. Only happens on this game. Tried finding crash logs.
Found absolute nihil. Yesterday's last crash was just a straight up freeze tho. No error. It didn't even do the standard not responding thing. But I suspect that one's an edge case.
Anyhow, I'll time it. See if there are consistencies in the time it takes to crash.

[Raithe]

Oi. Crash logs. Sec.

[Raithe]

Mine are in "C:\Program Files (x86)\Steam\steamapps\common\Conan Exiles\ConanSandbox\Saved\Logs". I found it by right clicking conan in steam and using "Manage>Browse Local Files". Then I picked though logs and found the error listed in "ConanSandbox.log".

[Raithe]

I still have the same error though. I have reinstalled visual c++ stuff, my graphics card drivers, updated windows 10, chose to specifically allow windows 10 to install its new feature, Messed with admin/compatibility settings for the .exe's, cleaned up my registry, dealt with random spyware, added a security exception to the folder conan stuff is in to my windows av stuff...did some other stuff I can't remember now...danced a jig on my desk......

NOTHING.

If you fix it man please post.

[CobbleSansPyro]

I've checked that file already. The log just cuts off. No error. Also, so far had 2 crashes. 1 fatal error(At 1:32:18) and the error-less freeze(At 46:23).
Notable thing before fatal: Double clicked on a modded buildable IIRC.
Notable thing before freeze: Just lookin around quickly while building.

[CobbleSansPyro]

Just another quick thing I wanted to mention. Validated my files... 1059...

[Ankido]

The problem is caused because Conan doesn't like mods. Yes, they support mods and have a workshop. Believe me, this game doesn't play well with mods. I have to validate my game every single time I play about 5 times before my server says, "Ok fine, I'll let you in." I always get Fatal Error with no description.

Validate all the time at least 3 times in a row in order to play a stable game for a while. It's bound to crash again with the error. The nature of the game and it's compatibility with mods.

[Raithe]

Nope. No mods here. Never have used them ever for Conan. Vanilla and official is my thing. I'll try that bit about repeat loading and validating cause....why not?

[Xevyr]

@Raithe There is entirely the chance that you're experiencing completely different things btw. If you're just having general crashes that you can't pinpoint.. on official servers... then that's a tough one... A small percent of people had that even prior to update.. it was conflicts with anti-virus software, driver issues, silly software installed by Asus motherboards like armoury crate.. etc interfering... some cases were only solved by a full windows reinstall.

@Mario, You do have mods so like Ankido said a large amount of the recent game crashes are due to slight incompatibilities with mods, since Funcom simply didn't give modders time to prepare and dumped the update on them earlier than they implied it would happen.

And just because they're updated does not mean that a.) you got the latest version (since steam is having problems pushing out workshop updates, so you might have to unsub from all mods, validate files then resub to them again to get all the current versions FOR REAL :) )
b.) modders didn't have a lot of time like I said above so it's entirely possible some of them have errors and need further patches.

@Ankido if you're getting crashes on loading like that, could it be that your server is using Hosav's UI? There's currently a bit of a hiccup with it, I'm sure he's working on it, in the meantime I found that if you simply start your game in single-player with all mods active and then log back only to the menu and then join your server it won't crash.
If you're getting mod mismatch errors and you get a restart loop, that's a different story :)

[Ankido]

Originally posted by Xevyr:

@Raithe There is entirely the chance that you're experiencing completely different things btw. If you're just having general crashes that you can't pinpoint.. on official servers... then that's a tough one... A small percent of people had that even prior to update.. it was conflicts with anti-virus software, driver issues, silly software installed by Asus motherboards like armoury crate.. etc interfering... some cases were only solved by a full windows reinstall.

@Mario, You do have mods so like Ankido said a large amount of the recent game crashes are due to slight incompatibilities with mods, since Funcom simply didn't give modders time to prepare and dumped the update on them earlier than they implied it would happen.

And just because they're updated does not mean that a.) you got the latest version (since steam is having problems pushing out workshop updates, so you might have to unsub from all mods, validate files then resub to them again to get all the current versions FOR REAL :) )
b.) modders didn't have a lot of time like I said above so it's entirely possible some of them have errors and need further patches.

@Ankido if you're getting crashes on loading like that, could it be that your server is using Hosav's UI? There's currently a bit of a hiccup with it, I'm sure he's working on it, in the meantime I found that if you simply start your game in single-player with all mods active and then log back only to the menu and then join your server it won't crash.
If you're getting mod mismatch errors and you get a restart loop, that's a different story :)

That's exactly what I did last night when I figured it out from Trial and error. I said EFF this and started playing single player. My group said, "Come on, keep trying." First try, I logged in. I put two and two together. BAM!

[Raithe]

I can't even get into single player without the fatal error. It still opens ( the fatal error is a popup that I can minimize). It still connects. It still plays fine. But it crashes the moment the fatal error box is closed AND within 5 minutes it forces closes on you while you are playing. I mean the game looks just fine but it won't stay running. Its wierd. I spent 3 days on this and am now just playing elden ring.

[CobbleSansPyro]

Ok, so basically, once I start getting fatal errors, validate? After I validated yesterday, everything seemed to be bueno. 0 crashes.
I mean, I can definitely wait for validation since I already have to bloody wait 6 feckin minutes to start the bloody thing.