I tried playing on public servers where I had crashed before, the game didn’t crash.
I tried to play the modded server I usually play on, there I crashed almost immediately when I got in to game.
It seems from the log that my GPU is trying to catch up and is unable to do so.
ConanSandbox.log (1.4 MB)
That’s because the type of error you’re getting can be caused by almost anything and it’s extremely difficult to pinpoint over the internet.
Your graphics card simply stops responding to the game and at that point it’s outside of its hands, so it comes down to a generic system problem… be it software… hardware or just configuration.
It’s why I didn’t ask for a log as I knew it wouldn’t contain anything informative about the crash in this case 
However… what it does contain is a large list of mods, which you neglected to mention in your OP (which is why they have a template where you could list mods for bug reports)
While the crash itself is not related to mods, certain mods CAN trigger it on unstable systems, simply by requiring graphics features that would work your card in a way that exposes this instability.
For example one of the mods you’re using, Beyond Stations has a Volcanic Frost Forge placeable, which due to its reflections etc. CAN cause this type of crash when looking at it.
It’s not the mod’s fault, it’s the computer having a slight instability under certain circumstances.
People who had that could prevent it happening by reducing Effects quality to Medium or below in the graphics settings.
There can be other similar items and features in various other mods.
At the end of the day though the best solution would be to make the system stable… however that’s not always possible as it could have hardware reasons… but in your OP you mentioned this:
Did you also underclock? Very often slightly reducing the clock speed of GPUs can help with these as most cards nowdays come factory-overclocked and not every game always likes that, while most won’t have issues.
I understand, but I have had this crash a dozen times before on public servers also even before I downloaded mods and started playing on a modded server for the first time. The modded server seems to work fine with my old PC, no crashing at all.
Even with the lowest settings the game has crashed both on public and private modded servers, doesn’t seem to be the culprit.
Undervolting/Underclocking aren’t they basically the same thing?
No, quite the opposite.
Chips working at a certain frequency get more stable as the voltage increases, but also produce more heat, which is why these things need to be balanced.
Undervolting without actually reducing the clock speed would just introduce even more instability, since it would try to reach the same clock speed, but with less voltage to drive it.
So typically you’d either want to slightly increase the voltage (not recommended as that direction is more for advanced users as you’d need to monitor the temperatures and stress test it to make sure the chip doesn’t get damaged) OR by bumping the clock speed down a notch, something like a ~25 Mhz should do for starters and see if that makes a difference.
Core Clock down -25Mhz?
What about the Memory Clock?
Yea the core clock for starters, take it down in 25 mhz decrements and test between to see if it helps. If you did that like 4 times and it didn’t help then you can try the memory clock too, just don’t do them at the same time so you can see which one helped in case it does.
I tried all types of variations, still happening. It seems to crash when loading other peoples bases and items. When I am roaming around the map, the game runs fine.
Ok it seems like my GPU is causing the problem. I tried putting the GPU in my other PC and the game crashes exactly the same. The GPU goes up to 100%, temp around 50°C but doesn’t start to throttle, fans are staying at the same speed, therefore causing the game to crash. Is the GPU failing?
Out of curiosity, did you have your framerate locked ingame?
That could be a very simple cause too, that it simply can’t handle close to maximal loads over an extended period of time.
So in case you don’t have your FPS locked in the game settings, try locking them to 60 fps or so.
50°C is not a lot for a GPU so there’s no reason for the fans to spin up at that temperature yet (though you can change that in afterburner or other similar software)
And yes, these types of errors CAN occur if the GPU is faulty, I just didn’t want to go there ofc, since there were a lot of other things to try beforehand.
Typically the thing you would try after exhausting most of the setting changes / driver / clock speed settings would be to try a windows reinstall in case some other software is interfering without you realizing, but you already done that before even coming here.
There’s a certain spot where I always crash (which is someone’s base), I put my settings up to Ultra and managed to not crash there for a longer period of time than usual. Seems that when my GPU reaches 100% usage the game crashes.
I have been playing with locked 60 FPS. I have also tried Uncapped, makes no difference.
I wonder if they have one of those volcanic forge stations inside that I mentioned earlier 
since the mod in question is on your modlist.
In any case the tweaks in afterburner should’ve helped with that, maybe you can experiment a bit more with those.
Lock your FPS back to 60, set the clock speeds back to their default too if you haven’t already, and try limiting the actual power draw to like 90%… It’s a longshot just like the others, but in case there something isn’t entirely right with the power delivery of your system, or the card itself internally, maybe that instability only presents itself after a certain power draw threshold.
Something definitely doesn’t seem right with the card, but maybe with some of these workaround you’ll be able to play.
I tried, still crashes as soon as GPU hits 100%
This is what I get in my Event Viewer,-
''The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.‘’
‘‘Display driver nvlddmkm stopped responding and has successfully recovered.’’
‘’\Device\Video3
Error occurred on GPUID: 100
The message resource is present but the message was not found in the message table’’
‘‘The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout.’’
‘‘The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-7QT1FIJ\illme SID (S-1-5-21-475761616-537545679-848788420-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.’’
‘‘The device driver for the Trusted Platform Module (TPM) encountered an error in the TPM hardware, which might prevent some applications using TPM services from operating correctly. Please restart your computer to reset the TPM hardware. For further assistance on this hardware issue, please contact the computer manufacturer for more information.’’
Yea, I know… it’s a generic TDR error…
I guess as a last resort you could try manually increasing the timeout delay 
I hate resorting to this, cuz it’s not really a fix… but maybe it helps… it might just delay the crash a bit depending on how frequent it gets triggered.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDriversTdrDelay then double-click on it to edit and set it to 10 and hit OkUnfortunately it did not work either, was among one of the first things I tried. Im starting to think I should wipe absolutely everything and install Windows on a different SSD at this point, a complete reset.
Won’t do much since you already confirmed that the GPU has the same result in a completely different computer.
Unfortunately it seems like a hardware issue and if that’s the case there’s really not much you can do about it… with lots of experimenting you might find some workarounds that let you play, but it’s always just going to be workarounds.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.