Game keeps on crashing, but especially on start up
I'm trying to load up the game with 8 mods (Refined power, infinite nudge, industrial evolution, vanilla green house, big stroage tank and megapump, faster manual crafting redux, small storage container, and linear overclock) but it keeps on crashing especially on start up, sometimes i get into the main menu and it crashes right after, I try to join my friend with the same mods but it either crashes the second i try to join or the second i actually am in the world.
this is the error code i just got for it crashing the second i saw the main menu(gonna have to split it into parts since i don't have nitro:
Version: 385279, IsEditor: No, IsPerforceBuild: No, BuildConfiguration: Shipping, Launcher: Steam, NetMode: Standalone, IsUsingMods: Yes, IsSaveGameEdited: No
Fatal error: [File:C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 378] DecompressShaderWithOodleAndExtraLogging(): Could not decompress shader group with Oodle. Group Index: 1773 Group IoStoreHash:b9a6126406af9ccc80ee8f09 Group NumShaders: 5 Shader Index: 22738 Shader In-group Index: 1773 Shader Hash: F80C9D4700EE0CF8F376C4E6683CD1B0E1BCBE70
FactoryGameSteam_RenderCore_Win64_Shipping!FIoStoreShaderCodeArchive::CreateShader() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp:2188]
FactoryGameSteam_RenderCore_Win64_Shipping!FShaderLibraryInstance::GetOrCreateShader() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeLibrary.cpp:1037]
FactoryGameSteam_RenderCore_Win64_Shipping!FShaderCodeLibrary::CreatePixelShader() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeLibrary.cpp:3533]
FactoryGameSteam_RenderCore_Win64_Shipping!FShaderPipelineCacheTask::Precompile() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderPipelineCache.cpp:1049]
24 Replies
FactoryGameSteam_RenderCore_Win64_Shipping!FShaderPipelineCacheTask::Tick() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderPipelineCache.cpp:1880]
FactoryGameSteam_RenderCore_Win64_Shipping!FShaderPipelineCache::Tick() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderPipelineCache.cpp:1848]
FactoryGameSteam_RenderCore_Win64_Shipping!TickRenderingTickables() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp:272]
FactoryGameSteam_RenderCore_Win64_Shipping!TGraphTask<TEnqueueUniqueRenderCommandType<
FRenderingThreadTickHeartbeat::Run'::7'::HeartbeatTickTickablesName,FRenderingThreadTickHeartbeat::Run'::7'::<lambda_1> > >::ExecuteTask() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:1270]
FactoryGameSteam_Core_Win64_Shipping!FNamedTaskThread::ProcessTasksUntilQuit() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:648]
FactoryGameSteam_RenderCore_Win64_Shipping!RenderingThreadMain() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp:412]
FactoryGameSteam_RenderCore_Win64_Shipping!FRenderingThread::Run() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp:537]
FactoryGameSteam_Core_Win64_Shipping!FRunnableThreadWin::Run() [C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:149]
if anyone knows how to fix this please tell me i want to play the game but i don't want to deal with thisPlease do not copy-paste it, but upload the full debug info
>debug
We need more information to help you. Before launching the game again, open the Mod Manager and use the "Generate debug info" option, then send the zip file produced in #help-using-mods. This ensures that your help request won't get buried and forgotten in other, non-help channels!
If you need to access older log files, see https://docs.ficsit.app/satisfactory-modding/latest/faq.html#Files_Logs
-# Responding to
Key Details for SMMDebug-2025-01-25-18-35-22.zip triggered by @SillyMonkiManthis log file ends in the game closing normally and not a crash
based on the bits of crash you posted earlier, try this:
>verifysteam
(I forgot to ping)
i got it to crash this time
-# Responding to
Key Details for SMMDebug-2025-01-25-19-21-43.zip triggered by @SillyMonkiMan
-# Responding to
Key Details for SMMDebug-2025-01-25-19-22-44.zip triggered by @SillyMonkiManwhy is it the same when it crashed this itme
-# Responding to
Key Details for SMMDebug-2025-01-25-19-24-44.zip triggered by @SillyMonkiMani don't know why it won't show something different when it just crashed
the bot only extracts certain details + crashes that is knows about
@SillyMonkiMan this crash doesn't point to any mods in particular, did following these steps help? https://discord.com/channels/555424930502541343/1332761292158533684/1332788905795125248
i've verified the files twice today and everytime i did it still crashed
it lets me play sometimes like i was able to eventually play but most of the time it crashes and i just wanna know if there is a way to stop that
does it still crash without mods?
try full reinstall?
Comedy suggestion that's actually not comedy at all: shut down your PC, then start it back up again (do not choose "restart"). Not normally a suggestion I'd make in earnest, but you've got a Raptor Lake CPU and they like to shit the bed in ways that result in IO instability like this.
Regardless of anything else, given that you have one of the affected Raptor Lake CPUs, even if you find things start working again for now, I would highly suggest looking for BIOS updates from your mainboard vendor, which can help prevent this issue from progressing. Unfortunately, I have a feeling that this could very well already be terminal for your CPU ― once symptoms start manifesting (and this particular error seems to be a hallmark of those issues), it is usually too late. Intel (or whoever you bought it from) should have a process for replacing it under warranty if this is the case.
it does if i've recently tried to play with mods and that crashed
processor info from McCovican
Tech details: https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633239
Breakdown: https://www.theverge.com/2024/7/26/24206529/intel-13th-14th-gen-crashing-instability-cpu-voltage-q-a
Intel Core 13th and 14th Gen Desktop Instability Root Cause Update
Following extensive investigation of the Intel® Core™ 13th and 14th Gen desktop processor Vmin Shift Instability issue, Intel can now confirm the root cause diagnosis for the issue. This post will cover Intel’s understanding of the root cause, as well as additional mitigations and next steps for Int...
The Verge
There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any d...
We got some answers from Intel, and more are on the way.