Game rendering appears to break down.
screenshot was taken after attempting to exit game, hence white overlay
Unsure of cause - could be being thrown as pAI, time played or device not allocating enough memory for the game. Hasn’t happened up until the 24/04/25 update though.
If this is constant, try toggling Compatibility mode in the launcher.
Otherwise you would really need to make a github issue as this is not enough info to tell what is going on.
This is something that has been happening to me but it’s far more severe than the game simply crashing. My entire windows can halt and it then cascades into chaos. Windows wallpaper goes black and you get that old school windows trail effect. I’m sure this has something to do with my system, but SS14 is the only game that causes it to happen almost constantly.
With the compatibility mode on it happens less, but still happens. The game is installed on a NVME SSD and I have an RTX 2080 and i9 CPU.
The problem is the server I play on cannot be played on with compatibility on. It instantly crashes the client if I try to join the server. I don’t know why.
It’s strange that I can play some really demanding games for hours with no issues, except a minor pause now and then but with SS14 I would say that every 1 and a half an hour the game completely will crash if I don’t restart the client.
When it does crash I have to reboot my entire PC. Few weeks ago this would also cause a BSOD but I managed to fix that using typical windows tools to repair it, but this also only happened during SS14 which probably caused a few windows files to go corrupt.
I’ll try to get more information if it happens again. If it helps at all, i was running the game on a laptop i use at work that has been consistently decent at running ss14. Others would frequently freeze trying to run it so it getting hit with that business was a shock.
If it is Goob station, they fixed the wizard shader that crashed on Compatibility
Could be Library interaction issue. I would suggest updating C++ runtime and dotnet runtime.
If that does not help i would recommend running windows system files repair and check in CMD(command prompt)
One after another
Remove junk left after updates and component installs:
Dism /online /cleanup-image /startcomponentcleanup
Scan your system image and compare to Microsoft:
Dism /Online /Cleanup-Image /ScanHealth
Repair everything that is deviant from Microsoft:
Dism /Online /Cleanup-Image /RestoreHealth
Run the system file checker last:
sfc /scannow
WARNING! ADVANCED USER ONLY THING. IF YOU ARE NOT POWER USER PLEASE IGNORE THIS
More advanced stuff is components\windowsApps themselves and can be done in PowerShell. Will require you to go in by link PowerShell provides and updating to new version of Power shell manually. After you installed new version of power shell, open it and use this command
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “(_.InstallLocation)\AppXManifest.xml”}
The game uses its own dotnet runtime, so updating it won’t do anything. (Unless you replace game files, which will result in you losing support from us)
We don’t use anything c++, no point.
Reading this thread, this really looks like an issue with your system. Probably with Windows, I suggest following the above guide to try to repair your system, but honestly I would recommend a full windows reinstall if it does not help.
Also make sure you have the latest graphics drivers for your GPU and Windows updates, they are indeed important.
If you still have issues, I may start looking at your graphics card. Run a stress test on your GPU or see if you can borrow another card by someone to test with.
If you have a 13-14th gen intel CPU, I would make sure you have your bios updated due to these cpu’s having the tendency to try to go into an early grave early.
It`s not for game. But for interaction between windows components. Since he bsod with corrupt files, issue is with system. Game just revealed that by calling something in a system and that calling to another thing, that thing calling to other etc(cannot tell what without running SysinternalsSuite process logging tools), C++ and DotNet are in case its related to how windows handles interaction between processes.
GPU and CPU check are also valid. Especially CPU(since it can bork system files due to CPU error)
