Space Engineers: Main Menu Crash & System Freeze - Troubleshooting Report

Space Engineers Support ●

Hello!

Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.

Kind Regards,

Keen Software House

Reply URL

1

Keen SWH QA Agent 2 ●

Hello Engineer,

Thank you for providing your log files. They have been very helpful in our investigation.

After reviewing both logs, we can confirm that the crash appears to be occurring at the GPU driver level rather than within the game itself. The game reaches the main menu and then the process stops abruptly without recording any exception, which is consistent with a GPU driver timeout causing a full system freeze.

To help us investigate this further, we would like to gather a bit more information.

Firstly, we noticed the following entry in your game log:

Service.OwnsGame: False

This indicates that, at the time of the crash, Steam was not recognizing the game as owned by the account that was running it. Could you please let us know how you are launching the game? For example, are you using Steam Family Sharing from another account, or is the game registered directly to your Steam account? This will help us better understand the environment in which the crash is occurring.

Secondly, could you please provide the relevant entry from Windows Event Viewer from around the time of the crash? This will allow us to check whether Windows recorded any GPU driver timeout or related events.

To get the Windows Event Viewer log, please open the Event Viewer (from the start menu, type Event Viewer). In the Event Viewer, go to Windows Logs, Application, and send the top “.NET Runtime” error from Application: SpaceEngineers.exe. (please see attached image).

To do this right, please follow these steps:

1) Select the correct file on the left side (Application)

2) Select first the .NET runtime error from the top (using default ordering)

3) Copy the large bottom text and send it to us.

Please Note: make sure that the info is from the Application: SpaceEngineers.exe

Kind Regards,

Keen Software House: QA Department

Files:

Reply URL

1

AnovriaL ●

Hello, dear Keen Software House team,

Thank you very much for your reply. I am the person who submitted this bug report. Since I am in China, I need to use some special methods to access foreign websites, so my replies might be delayed (I almost couldn't even register on this forum). From now on, I will use this forum account to reply to you regarding the issues submitted for this bug.

(1) Regarding the Service.OwnsGame: False issue you mentioned: This might have been triggered because I used the [Start Game Offline] feature on the Steam platform to conduct more comprehensive game runtime tests. In other words, this issue is only triggered when the game is launched in offline mode. My usual way to start the game is by logging into my own Steam account, finding the game in my library, and clicking the "Play" button to launch it directly. As you can see in the screenshot [P1] I provided, I am logged into my account, and the game is in my library. Therefore, this might not be the key cause of the game crash.

(2) Regarding the Windows Event Viewer logs you asked for: I only found records with [Level: Information, Source: Windows Error Reporting] in my system's Event Viewer. I could not find any reports of the same category as the ones in the picture [Windows Event Viewer log].jpg you sent, specifically those with Level: Error and Source: .NET.

Here are the standard contents from my Event Viewer log:

Fault bucket 2256219206946218545, type 5

Event Name: RADAR_PRE_LEAK_64

Response: Not available

Cab Id: 0

Problem signature:

P1: SpaceEngineers.exe

P2: 1.0.0.0

P3: 10.0.26200.2.0.0

P4:

P5:

P6:

P7:

P8:

P9:

P10:

Attached files:

?\C:\Users\username\AppData\Local\Temp\RDR3A7B.tmp\empty.txt

?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ff8de467-b9c7-4364-90c6-26e2abb636ce.tmp.WERInternalMetadata.xml

?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f334cf62-f261-4bde-bb62-18d8a4239613.tmp.csv

?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.66ba3de0-9f5e-4d53-8e43-dc8ae077c320.tmp.txt

?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6f9d6311-c737-438a-a5de-2a3a4b44559a.tmp.xml

These files can be obtained here:

NULL

Analysis symbol:

Recheck for solution: 0

Report Id: 21ede3a8-a4a2-424a-8cd8-d4f959772b53

Report status: 268435456

Hashed bucket: 69611a859f4f6d757f4fb36a2d716231

Cab Guid: 0

Here is the detailed content from the Event Viewer :

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" /> <EventID>1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2026-07-05T05:14:37.7550249Z" /> <EventRecordID>112560</EventRecordID> <Correlation ActivityID="{20840f12-ad6a-4f36-9b71-afdff8ca76c5}" /> <Execution ProcessID="16800" ThreadID="24940" /> <Channel>Application</Channel> <Computer>mycomputer</Computer> <Security UserID="S-1-5-21-1839024233-2694251189-1458707920-1001" /> </System> - <EventData> <Data Name="Bucket">2256219206946218545</Data> <Data Name="BucketType">5</Data> <Data Name="EventName">RADAR_PRE_LEAK_64</Data> <Data Name="Response">不可用</Data> <Data Name="CabId">0</Data> <Data Name="P1">SpaceEngineers.exe</Data> <Data Name="P2">1.0.0.0</Data> <Data Name="P3">10.0.26200.2.0.0</Data> <Data Name="P4" /> <Data Name="P5" /> <Data Name="P6" /> <Data Name="P7" /> <Data Name="P8" /> <Data Name="P9" /> <Data Name="P10" /> <Data Name="AttachedFiles">\\?\C:\Users\username\AppData\Local\Temp\RDR3A7B.tmp\empty.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ff8de467-b9c7-4364-90c6-26e2abb636ce.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f334cf62-f261-4bde-bb62-18d8a4239613.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.66ba3de0-9f5e-4d53-8e43-dc8ae077c320.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6f9d6311-c737-438a-a5de-2a3a4b44559a.tmp.xml</Data> <Data Name="StorePath">NULL</Data> <Data Name="AnalysisSymbol" /> <Data Name="Rechecking">0</Data> <Data Name="ReportId">21ede3a8-a4a2-424a-8cd8-d4f959772b53</Data> <Data Name="ReportStatus">268435456</Data> <Data Name="HashedBucket">69611a859f4f6d757f4fb36a2d716231</Data> <Data Name="CabGuid">0</Data> </EventData> </Event>

The above is all the content related to SpaceEngineers.exe that I could find in the Event Viewer. I will provide you with an overview in picture [P2]. Unfortunately, my viewer does not have the type of error you demonstrated.

(3) Regarding the issue I mentioned in my initial bug report about the game crashing when staying on the main menu for too long:

The issue of crashing after staying on the main menu for a long time has now been resolved. Here is my troubleshooting process: [1. I updated my NVIDIA graphics driver to the latest version (610.74), but the game continued to crash after testing. 2. I used the DDU tool to completely uninstall the driver, and then installed an older driver version (572.83) as well as the subsequent 580 series. All of them ended with the game crashing after staying on the main menu for a long time. 3. I finally realized a key point: all of this happened after I updated my motherboard BIOS. I didn't have this issue when using BIOS version F39, but the problem occurred after I updated to F41. The purpose of the update was to use the new memory XMP profile. I then thought that maybe updating again would solve it, so I updated my BIOS to version F42a, which was recently released on July 1st. After completing the update, I launched the game and stayed on the main menu for a very, very long time. This time, the crash issue never occurred again! (Of course, during this period, I also upgraded my graphics driver back to the latest version, 610.74.)]

(4) After I managed to fix the main menu crash issue myself (even though it might have been a problem with my own computer), I tried to play Space Engineers with my Steam friends, and a new problem emerged...

① Connecting to his save file triggers a game crash. This time, there was a crash prompt, meaning the automatic feedback window popped up normally. I did submit the report, but I am very sorry because I didn't write any comments as I was too fast. [This crash can be consistently reproduced.]

② When he connects to my save file, he successfully joins, but he gets stuck in the center of a planet (this planet only renders a rough atmosphere, but no surface terrain; he is located in the center of the planet, at least it looks that way). The HUD displays "Game Paused" at the top, and he cannot load anything or select a spawn point, but he can freely rotate his camera, which is very strange... Ridiculously, I am completely normal in the save file, with no crashes or any issues, and can play normally. When he joined, I did see the "Friend has come online" prompt (the standard player join notification), but I cannot see my friend or find his entity, you know.

Currently, the testing environment for [Issue (4)] includes Workshop mods. Due to some real-life time constraints, we didn't have the opportunity to test it extensively, and I also failed to find relevant error logs. I am very sorry about this. I will conduct a detailed test when my friend is available next time and upload the error report. Regarding the crash issue in this environment, there is a small side note: before the core DLC update, I was playing multiplayer normally with Workshop mods and another friend (not the one I tested the crash with). At that time, we played normally with Workshop mods without any crashes. The crash issue only appeared after the ECONOMY DLC update, which is why I started testing.

(5) Following up on Issue (4): Since July 7th, 2026, and now today (July 9th), I just received your reply and started writing this. I also tested with another Steam friend (note: this is a different friend, completely unrelated to the two friends in Issue (4)). He has not subscribed to any mods. In total, 3 friends helped me test and try multiplayer for this bug. They did not encounter my issues, and two of them even played multiplayer normally with Workshop mods. So, is it more likely a compatibility issue between my computer and the game framework? For example, a compatibility issue at the CPU or GPU level? This time, I disabled all Workshop mods, completely deleted the game folder, and redownloaded the game to test. Surprisingly, it worked! No crash was triggered, and we could indeed play multiplayer normally... I am not sure yet whether it was a BIOS/graphics driver issue or a game mod/patch issue. I suspect it might be the latter? However, after the BIOS update, the automatic crash after staying on the main menu for a long time has indeed never happened again.

(6) Summary of specific details: I had 3 friends as references while troubleshooting this bug. Let's call them A, B, and C.

Friend A: I played with him for a long time before the CORE SYSTEMS DLC update. We played multiplayer normally with Workshop mods, and no issues ever occurred.

Friend B: This friend was the key trigger point for the crash. I discovered this bug while playing with him, and it was already after the ECONOMY DLC update. Friend A had stopped playing, and Friend B was someone I played with later. His Workshop mods were identical to mine with no differences, but the crashes indeed started from this point.

Friend C: This is the friend I just tested with. With a completely vanilla game, after I updated my BIOS, we played multiplayer and found the game was working normally. But there are too many variables during this period, so I cannot confirm exactly where the problem lies...

(7) That is all for this report. Thank you very much for reading until the end, and thank you for your hard work for the game and the players! This post was also translated and polished with AI assistance. I sincerely apologize if this causes any misunderstandings or translation errors! I still very much look forward to your reply!