Can someone clarify this crash report?
Can someone clarify this crash report?
It comes from a game titled satisfactory. After saving and switching to the desktop, I check my Steam list and see the satisfactory name showing a cloud save icon, the game image, the name satisfactory, and 100% at its side. Eventually, that 100% vanishes and it displays satisfactory experimental as expected. When I close the game, I realize if it’s going to crash. In my Steam list it says satisfactory running, and the text is green—not blue?????
One point that confuses me is the second sentence… it mentions UE4 Engine, but the game actually uses UE5. Several players have reported this kind of crash for months, yet it only started happening recently and I haven’t made any changes.
FOOTNOTE… When I posted this, those smiley faces appeared, but I didn’t add them.
Version: 406341
IsEditor: No
IsPerforceBuild: No
BuildConfiguration: Shipping
Launcher: Steam
NetMode: Standalone
IsUsingMods: No
IsSaveGameEdited: No
Assertion failed: PreloadEntry->NumRefs == 0
[File
😀
:\BuildAgent\work\1\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 1837] Group 5383 still has 3 references on deletion. Group extended debug info: Not compiled in (set UE_SCA_DEBUG_PRELOADING to 1 in ShaderCodeArchive.h and recompile the game binary)
FactoryGameSteam_RenderCore_Win64_Shipping!FShaderLibraryInstance::~FShaderLibraryInstance()
[D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeLibrary.cpp:921]
FactoryGameSteam_RenderCore_Win64_Shipping!TArray<TUniquePtr<FShaderLibraryInstance,TDefaultDelete<FShaderLibraryInstance>>,TSizedDefaultAllocator<32>> >::~TArray<TUniquePtr<FShaderLibraryInstance,TDefaultDelete<FShaderLibraryInstance>>,TSizedDefaultAllocator<32>>
FactoryGameSteam_RenderCore_Win64_Shipping!UE::ShaderLibrary:
😛
rivate::FNamedShaderLibrary::`scalar deleting destructor'()
FactoryGameSteam_RenderCore_Win64_Shipping!TSparseArray<TSetElement<TTuple<FString,TUniquePtr<UE::ShaderLibrary>>
😛
rivate::FNamedShaderLibrary,TDefaultDelete<UE::ShaderLibrary>
😛
rivate::FNamedShaderLibrary> > >,TSparseArrayAllocator<TSizedDefaultAllocator<3() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\Core\Public\Containers\SparseArray.h:384]>
FactoryGameSteam_RenderCore_Win64_Shipping!FShaderCodeLibrary::Shutdown() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeLibrary.cpp:3459]
FactoryGameSteam_RenderCore_Win64_Shipping!UE::ShaderLibrary:
😛
rivate::FNamedShaderLibrary::~FNamedShaderLibrary() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\RenderCore\Private\ShaderCodeLibrary.cpp:920]
FactoryGameSteam_RenderCore_Win64_Shipping!TSparseArray<TSetElement<TTuple<FString, TUniquePtr<UE::ShaderLibrary>>
😛
rivate::FNamedShaderLibrary> > >,TSparseArrayAllocator<TSizedDefaultAllocator<3() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\Core\Public\Containers\SparseArray.h:384]]
FactoryGameSteam_RenderCore_Win64_Shipping!FEngineLoop::Exit() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\Launch\Private\LaunchEngineLoop.cpp:5145]
FactoryGameSteam_Win64_Shipping!GuardedMain() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\Launch\Private\Launch.cpp:202]
FactoryGameSteam_Win64_Shipping!GuardedMainWrapper() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp:118]
FactoryGameSteam_Win64_Shipping!LaunchWindowsStartup() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp:258]
FactoryGameSteam_Win64_Shipping!WinMain() [D:\BuildAgent\work\1\UE4\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp:298]
FactoryGameSteam_Win64_Shipping!__scrt_common_main_seh() [D:\a_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288]
kernel32
There was update to the beta experimental branch few weeks ago.
Patch notes:
https://store.steampowered.com/news/app/...2930712785
Since you're playing beta and rather full/stable build, bugs/issues/crashes are given. If you do not want those issues, do not play the beta (experimental) version of Satisfactory.
In Steam:
Green game name = game is running
Blue game name = game is closed and is syncing to Steam or is waiting for update ("Update Queued") or downloading update
White game name = game is installed and ready to play
Gray game name = game is in your library but not installed
Hi there... I've been using this experimental version for a long time and know all the updates. I believe you might have overlooked something confusing. The green status indicator changes to blue almost instantly when switching back to the desktop, but it has remained green for several days until I received a crash report.
Depending on the developers, they might or might not respond.
Generally, developers receive your bug report, but when the game has a large player base with tens of thousands of users, they might receive thousands of reports and struggle to reply to all of them. In smaller games (like indie titles), developers may be more likely to reply.
Over the years, I've submitted numerous bugs for many games I've played. It's been quite uncommon to receive a reply.
However, if you really need a response (even just confirmation that your bug was noticed), you could share it on the Satisfactory community, such as their Discord or Reddit channels.
For contacts: https://www.satisfactorygame.com/#community
Please note, the team here isn't connected to the Satisfactory game and can't assist with your problem.
If the issue involves software (OS) or hardware, there are troubleshooting steps you can try. But since your problem is tied to a specific game and its beta version, it's best to ask the game's community directly.
ESET Nod32 was once reliable, about ten years ago. Now it seems less effective.
Presently, MalwareBytes stands out as a strong choice. It offers both free/trial and premium versions, which require annual payments. I've been using MWB Premium for the last 3 to 4 years across our computers, laptops, and even smartphones.
For additional recommendations:
https://www.pcmag.com/picks/the-best-ant...protection
Sophos is a solid alternative. It’s relatively light, lacks ads, works fast and well. There are no notable positive or negative reviews. After ten years of use on Windows (both free and paid versions), I haven’t encountered any issues.
i use malwarebytes free and run windows defender once a week. many years ago i had a pc that had tons of problems it ran very slow but i could not find out why. a local shop sold me webroot spysweeper which found some keyloggers and a few other issues, but now it can only be bought as part of an anti virus package.