Crashes and driver timeouts constantly.
Hello.
Since my tech support ticket has been completely ignored with 0 responses for 43 days, and my steam forum thread also completely got ignored by keen, I reached out to the discord and I was told to make a new bug report here instead.
After playing SE1 for ~1400 hours I wanted to try SE2 in its development stage, however as today I tried it for the first time, I'm running into constant crashes that makes the game completely unplayable.
Upon loading into a world, or a few minutes after it, the game will crash and i'll get a driver timeout from AMD Adrenalin Software, it'll sometimes interfere with other things as well.
Specs:
AMD Ryzen R9 3900x - No overclock, Stock cooler, temps are fine.
AMD RX 5700XT Sapphire Nitro+ version - Also no overclock, and temps are fine.
32 GB DDR4 ram at 3200 Mhz.
Game is installed on my m.2 Nvme SSD.
Windows 11 latest updates installed.
GPU drivers are up to date.
Here are the logs created after a crash:
I have the same bug
Hello Anlistra,
There are a few things we can try:
Let me know if any of these help.
Kind Regards,
Bartosz
Keen Software House
Hello Anlistra,
There are a few things we can try:
Let me know if any of these help.
Kind Regards,
Bartosz
Keen Software House
I have tried both with vsync on and off
I have been playing with windowed mode
I will have to redownload to try no overlays
Does the crash logs give any useful info?
I have tried both with vsync on and off
I have been playing with windowed mode
I will have to redownload to try no overlays
Does the crash logs give any useful info?
Update: Turning Vsync on didn't change anything, still crashes immediately or near-immediately (after less than a minute.)
Update: Turning Vsync on didn't change anything, still crashes immediately or near-immediately (after less than a minute.)
Anything else I can try?
Anything else I can try?
Hello Anlistra,
Please try to run the Game at Low Graphical Preset. Additionally, are you playing on a laptop or PC? Are there any sudden temperature spikes?
Kind Regards,
Bartosz
Keen Software House
Hello Anlistra,
Please try to run the Game at Low Graphical Preset. Additionally, are you playing on a laptop or PC? Are there any sudden temperature spikes?
Kind Regards,
Bartosz
Keen Software House
I have ran the game in lowest and highest graphics and it still crashed, can provide logs of crashes with low graphics if necessary
I am playing on a PC, as my specs are listed above, it is not a laptop.
There are no temperature spikes, I've recently cleaned and repasted my pc, but even without that, my gpu general temp hovers around 65c the hot spot temps usually +10c above general temp.
I have ran the game in lowest and highest graphics and it still crashed, can provide logs of crashes with low graphics if necessary
I am playing on a PC, as my specs are listed above, it is not a laptop.
There are no temperature spikes, I've recently cleaned and repasted my pc, but even without that, my gpu general temp hovers around 65c the hot spot temps usually +10c above general temp.
Well since I had hoped I would get a reply to try something I havent actually tried and fix my issue, I hesitated on refunding the game in hopes to fix it, and now its past the eligibility window, having established that, what else I can try that could fix this?
Well since I had hoped I would get a reply to try something I havent actually tried and fix my issue, I hesitated on refunding the game in hopes to fix it, and now its past the eligibility window, having established that, what else I can try that could fix this?
Hello, I would also like to comment that I have been experiencing a similar issue. Sudden crashes with the screen going black for a moment then back to desktop. Sometimes there would be an AMD "Driver Timeout" message alongside a General system tray message "Default performance tuning settings have been restored due to an unexpected system failure."
These are the various things I have tried to fix the constant "driver timeout" game crashing to desktop error.
Multiplane Overlay (MPO) instability - disabled
Check for GPU VRAM Instability, reducing Graphics card memory frequency, reduced memory clock by 100-200mhz
Reducing RAM frequency clock by 1000mhz - removed 2x sticks of ram (64gb DDR4 down to 32GB)
Increase Windows TDR Delay
Check GFX card power plug isn't daisy-chained (mine was) - corrected with 2nd pcie cable
Clear Corrupted DirectX Shader Cache - no change
Strip Down Third-Party Overlays (discord, steam, epic games etc) - no change
Wipe the Space Engineers 2 appdata Folder - no change
Cap Your Framerate - capped to 60fps
After troubleshooting for about 6 hours I came to the conclusion that my save game was corrupted and there was some funky physics going on or a bugged grid somewhere.
I could play the game for around 10-15 mins but it would eventually crash mainly when travelling through space at 300m/s
It got to the point where I would load my save game and turn my character to face my ship and it would instantly crash.
I have now started a new survival save and got approx. 60 minutes in before it crashed.
This time it was not the AMD driver timeout error, just the regular timeout error.
latest crash report attached as well las one from old save, also pc specs.
Cheers, Shaun.
Hello, I would also like to comment that I have been experiencing a similar issue. Sudden crashes with the screen going black for a moment then back to desktop. Sometimes there would be an AMD "Driver Timeout" message alongside a General system tray message "Default performance tuning settings have been restored due to an unexpected system failure."
These are the various things I have tried to fix the constant "driver timeout" game crashing to desktop error.
Multiplane Overlay (MPO) instability - disabled
Check for GPU VRAM Instability, reducing Graphics card memory frequency, reduced memory clock by 100-200mhz
Reducing RAM frequency clock by 1000mhz - removed 2x sticks of ram (64gb DDR4 down to 32GB)
Increase Windows TDR Delay
Check GFX card power plug isn't daisy-chained (mine was) - corrected with 2nd pcie cable
Clear Corrupted DirectX Shader Cache - no change
Strip Down Third-Party Overlays (discord, steam, epic games etc) - no change
Wipe the Space Engineers 2 appdata Folder - no change
Cap Your Framerate - capped to 60fps
After troubleshooting for about 6 hours I came to the conclusion that my save game was corrupted and there was some funky physics going on or a bugged grid somewhere.
I could play the game for around 10-15 mins but it would eventually crash mainly when travelling through space at 300m/s
It got to the point where I would load my save game and turn my character to face my ship and it would instantly crash.
I have now started a new survival save and got approx. 60 minutes in before it crashed.
This time it was not the AMD driver timeout error, just the regular timeout error.
latest crash report attached as well las one from old save, also pc specs.
Cheers, Shaun.
So, with the information added by the fellow user here, is there anything keen can say about this? It seems to be something at least partly related to AMD graphics cards or AMD drivers.
So, with the information added by the fellow user here, is there anything keen can say about this? It seems to be something at least partly related to AMD graphics cards or AMD drivers.
If Keen will not be providing any further assistance with this issue I will be issuing a refund on steam, but I'd like to ask one more time just to be sure
If Keen will not be providing any further assistance with this issue I will be issuing a refund on steam, but I'd like to ask one more time just to be sure
Hello, I am also having a simular issue as Shaun described. I have played both with vsync on and off. Here is the crash report.
One thing that seemed to help was creating a new world and importing my ship. That however was only temporary for about 1h of gameplay
Hello, I am also having a simular issue as Shaun described. I have played both with vsync on and off. Here is the crash report.
One thing that seemed to help was creating a new world and importing my ship. That however was only temporary for about 1h of gameplay
I'm having the same issue but with Nvidia graphics card, running Ubuntu 26.04 LTS. I ruled out settings, with V-sync on and off, high, medium and low settings, plus various custom settings just to try to find the culprit, but always the same. I ruled out Proton, spending a lot of time checking the logs and tinkering (including using different variants) but everything was working fine there. I ruled out graphics drivers, using both proprietary and open versions, plus backdated drivers, even manually forcing it to compile shaders on launch with no luck. Of course I also did the usual stuff too like verifying game files etc.
From what I can see on my end, the GPU consumes high Vram but with a low power consumption during the crash which I found odd. I can reliably repeat this crash by loading my save which is flying my ship at 1080 m/s and then leave the seat to walk down the corridor of the ship, it will crash about half-way down the corridor (so easy to reproduce using any settings) despite there being very little graphically down the corridor, just a few doors and interior lights, and it's always fine and stable when stationary or if I remain in the seat (at least in all the tests I've done).
I then decided to go a step further and get Claude code (Fable) on the case because I was adamant that it was my setup that was the issue, possibly a driver or how the vulkan shaders are handled, and while I've done a lot of tinkering myself, frankly Claude is better than I am at this. So I set it to monitor the process and logs, and it said "The evidence points to the VRAGE engine, not the driver, Proton or shaders. On every hang the GPU stalls rather than spins: utilisation jumps to 100 percent while power draw halves for about four seconds, then the kernel logs an NVRM Xid 109 context-switch timeout, vkd3d-proton reports device lost, and the game's watchdog writes a RenderThreadFreeze dump and kills the process. A crash dump of the frozen process shows every CPU thread idle and waiting on the GPU, so the CPU side is innocent. The trigger is a burst of streaming work when the player sprints through a ship travelling at high speed, with encounter grids spawning and despawning nearby, and that burst appears to take longer than the driver's per-context time limit, so the driver declares the GPU hung and resets it. It is not VRAM pressure, since the hang is identical at the Low preset with under 5 GB in use, and it is not shader compilation, since rewriting every shader through a Vulkan layer changed nothing. Nor is it driver-specific: it reproduces on the 580 and 595 NVIDIA branches, open and proprietary, and Windows users on AMD report the same timeouts in Keen tickets 54202 and 52794. NVIDIA drivers are known to be more sensitive to this class of long submission (NVIDIA bug 5052028), which likely explains why it hits so quickly on Linux, but the workload that overruns the limit is the engine's."
With that in mind, I've reached the limit of what I can realistically do to solve this myself. I'd be happy to try and help where I can but I feel this is an engine issue as opposed to a driver / platform / GPU brand issue, just from my findings so far. I attached my save file and logs for reference.
I'm having the same issue but with Nvidia graphics card, running Ubuntu 26.04 LTS. I ruled out settings, with V-sync on and off, high, medium and low settings, plus various custom settings just to try to find the culprit, but always the same. I ruled out Proton, spending a lot of time checking the logs and tinkering (including using different variants) but everything was working fine there. I ruled out graphics drivers, using both proprietary and open versions, plus backdated drivers, even manually forcing it to compile shaders on launch with no luck. Of course I also did the usual stuff too like verifying game files etc.
From what I can see on my end, the GPU consumes high Vram but with a low power consumption during the crash which I found odd. I can reliably repeat this crash by loading my save which is flying my ship at 1080 m/s and then leave the seat to walk down the corridor of the ship, it will crash about half-way down the corridor (so easy to reproduce using any settings) despite there being very little graphically down the corridor, just a few doors and interior lights, and it's always fine and stable when stationary or if I remain in the seat (at least in all the tests I've done).
I then decided to go a step further and get Claude code (Fable) on the case because I was adamant that it was my setup that was the issue, possibly a driver or how the vulkan shaders are handled, and while I've done a lot of tinkering myself, frankly Claude is better than I am at this. So I set it to monitor the process and logs, and it said "The evidence points to the VRAGE engine, not the driver, Proton or shaders. On every hang the GPU stalls rather than spins: utilisation jumps to 100 percent while power draw halves for about four seconds, then the kernel logs an NVRM Xid 109 context-switch timeout, vkd3d-proton reports device lost, and the game's watchdog writes a RenderThreadFreeze dump and kills the process. A crash dump of the frozen process shows every CPU thread idle and waiting on the GPU, so the CPU side is innocent. The trigger is a burst of streaming work when the player sprints through a ship travelling at high speed, with encounter grids spawning and despawning nearby, and that burst appears to take longer than the driver's per-context time limit, so the driver declares the GPU hung and resets it. It is not VRAM pressure, since the hang is identical at the Low preset with under 5 GB in use, and it is not shader compilation, since rewriting every shader through a Vulkan layer changed nothing. Nor is it driver-specific: it reproduces on the 580 and 595 NVIDIA branches, open and proprietary, and Windows users on AMD report the same timeouts in Keen tickets 54202 and 52794. NVIDIA drivers are known to be more sensitive to this class of long submission (NVIDIA bug 5052028), which likely explains why it hits so quickly on Linux, but the workload that overruns the limit is the engine's."
With that in mind, I've reached the limit of what I can realistically do to solve this myself. I'd be happy to try and help where I can but I feel this is an engine issue as opposed to a driver / platform / GPU brand issue, just from my findings so far. I attached my save file and logs for reference.
Thank you for the reply, also interesting to see that this isn't specific to AMD graphics cards although it could have to do with Linux too (I am all too unfamiliar with how it works though.)
Ultimately sadly Keen doesn't really seem to care for the people having issues, as after trying to contact them here, through another ticket, their discord 3 times, their steam forums across ~ 3 months , i havent had a single response. And sadly while waiting for them to care about it, the game's past the refund window so I can't refund it either. So I am essentially sitting with a game I can't play.
Hope you eventually find a fix to this though!
Thank you for the reply, also interesting to see that this isn't specific to AMD graphics cards although it could have to do with Linux too (I am all too unfamiliar with how it works though.)
Ultimately sadly Keen doesn't really seem to care for the people having issues, as after trying to contact them here, through another ticket, their discord 3 times, their steam forums across ~ 3 months , i havent had a single response. And sadly while waiting for them to care about it, the game's past the refund window so I can't refund it either. So I am essentially sitting with a game I can't play.
Hope you eventually find a fix to this though!
I am having the same issue.... Just crashes for no apparent reason no matter my graphic card settings....
Mobo: Gigabyte Z590 AORUS Master
CPU: Intel Core i7 11700K
RAM: 2X Corsair CMW32GX4M2E3200C 16 (32GB)
GPU: AMD Radeon RX 9060 XT (16GB)
I attached the DMP file
I am having the same issue.... Just crashes for no apparent reason no matter my graphic card settings....
Mobo: Gigabyte Z590 AORUS Master
CPU: Intel Core i7 11700K
RAM: 2X Corsair CMW32GX4M2E3200C 16 (32GB)
GPU: AMD Radeon RX 9060 XT (16GB)
I attached the DMP file
Replies have been locked on this page!