Games causing system to reboot after updating to SteamOS 3.5.5 stable

[Hawk4x4]

Has anyone had issues with the system rebooting while in-game after updating to SteamOS 3.5 stable? I updated last night and was testing it out. Some games and emulators will launch and after a few minutes in game, my Deck will suddenly reboot to the “verifying installation” screen like it was forced to restart.

Specific examples:
-I tested out Cyberpunk, which caused this reboot twice once the city loaded, but on the third test, the game started functioning normally.

-I tested a lighter game. Shredder’s Revenge launched and played with no issues.

-Yuzu lets me get to game title screens, but then reboots the Deck as soon as it loads into the actual games, regardless of the game.

-FF7 Remake launches and plays fine, but I did notice that it was recompiling the shaders before launching the game, which I haven’t seen since the game was first installed.

-Sonic Frontiers got to the title screen, but never got past the loading screen before the system rebooted. I did notice that like FF7, the game was compiling the shaders again before launching.

I am not noticing any issues with temps, the max temp reported by the system HUD was 78C. Could this be an issue with shaders having to be recompiled in the background? I’m trying to troubleshoot what could be causing the OS to crash and reboot.

[Jesse025]

Same here since the new update all my gallery...

[FriendlyFire]

I'm experiencing the same issue with Borderlands 2 on my Steam Deck (LCD 256GB model). Latest Steam update, no updates visible in Steam or Linux system settings, no software tweaks from my side. Tested with Proton Experimental and 8.0-4 (selected by Valve). The game freezes, screen goes black for a couple frames, then shows the game again, after which I'm kicked out to the login screen.

[Hawk4x4]

Update: many games had small updates come through in the past few days that made them playable again.

Still having the issue with Yuzu, but it gets progressively better with each daily Yuzu update. Still will randomly freeze up and cause a full system reboot. Strangely enough, Yuzu seems to run better in desktop mode, which makes no sense to me.

[Statesidemonk]

Same. This is ridiculous and needs to be addressed ASAP. I’ve only had my Deck for a couple weeks now and it is essentially unplayable because of this bug. I expected better.

[stephaine.cork16]

Same problem even after new update today. Games are still shutting down and rebooting. Was hoping the new update would fix the issue but nope, still unplayable.

[Chevi]

new recently update does not work either.... need a solution ASAP!!!

[FriendlyFire]

Since 3.5.7 the same issue happens to me with No Man's Sky - a game that basically I bought the Deck for, game that had the Verified status since it launched on the Deck and game that I had 0 issues with prior to 3.5.7. I even played it in couple last days before updating to 3.5.7 for longer time and experienced no issues.

[Statesidemonk]

I just submitted a ticket requesting help or a replacement. Everyone should do the same. My Deck is only a couple weeks old, so it's unacceptable that it's now essentially bricked. Hopefully a quick update is all it takes, but if not Steam needs to replace these defective units we are experiencing.

[FriendlyFire]

Potential fix found on Reddit?
https://www.reddit.com/r/SteamDeck/comments/182o9sl/fix_random_reboot_verifying_installation_355/

Can somebody test it out? I'm currently AFD.

UPDATE:

Tried this trick with my Deck, selected the 4GB option. Sadly no dice, the two games Im interested in still suffer from freeze and reboot.

[Hawk4x4]

引用自 FriendlyFire：

Potential fix found on Reddit?
https://www.reddit.com/r/SteamDeck/comments/182o9sl/fix_random_reboot_verifying_installation_355/

Can somebody test it out? I'm currently AFD

I just did it. I never increased the UMA Buffer previously because I thought it was dynamic, but I set mine to 4GB in the BIOS and so far the crash hasn't happened. I've only tested it on a couple games in the past 20 minutes, but so far so good! I'll update if the issue comes back.

[Statesidemonk]

It definitely has something to do with the 200-1040MHz bug, and Gamescope.

After a crash and reboot, I noticed in the performance settings, the manual GPU rate was set to 1000, which I did not set to that low. Immediately after I changed it back to 1600, it set itself back to 1000. This was still in the settings menu, not in-game via the overlay. It did this multiple times before finally sticking with the 1600 I set.

I then tried to play Skyrim, which was giving me the most crashes, and had no issues.

Until Valve releases an updated firmware that fixes this bug, try manually setting the GPU rate and give it a minute to make sure it adheres. Make sure it doesn’t change with specific game profiles for added measure.

[deaddoof]

引用自 Statesidemonk：

It definitely has something to do with the 200-1040MHz bug, and Gamescope.

After a crash and reboot, I noticed in the performance settings, the manual GPU rate was set to 1000, which I did not set to that low. Immediately after I changed it back to 1600, it set itself back to 1000. This was still in the settings menu, not in-game via the overlay. It did this multiple times before finally sticking with the 1600 I set.

I then tried to play Skyrim, which was giving me the most crashes, and had no issues.

Until Valve releases an updated firmware that fixes this bug, try manually setting the GPU rate and give it a minute to make sure it adheres. Make sure it doesn’t change with specific game profiles for added measure.

Gamescope crashing and 200-1040Mhz bugs should not be the same.

200-1040Mhz is probably issues with cpu time. The 200-1040 Mhz bug can be related to the audio issue.

Gamescope runs pretty much hosts the whole the game itself. The bug above should not cause crashing.

I remember my update from 3.4->3.5 game causing caused by Anti cheat not being updated. I had to delete a few files to tell Steam to reinstall the anti cheat.

[Statesidemonk]

引用自 deaddoof：

引用自 Statesidemonk：

It definitely has something to do with the 200-1040MHz bug, and Gamescope.

After a crash and reboot, I noticed in the performance settings, the manual GPU rate was set to 1000, which I did not set to that low. Immediately after I changed it back to 1600, it set itself back to 1000. This was still in the settings menu, not in-game via the overlay. It did this multiple times before finally sticking with the 1600 I set.

I then tried to play Skyrim, which was giving me the most crashes, and had no issues.

Until Valve releases an updated firmware that fixes this bug, try manually setting the GPU rate and give it a minute to make sure it adheres. Make sure it doesn’t change with specific game profiles for added measure.

Gamescope crashing and 200-1040Mhz bugs should not be the same.

200-1040Mhz is probably issues with cpu time. The 200-1040 Mhz bug can be related to the audio issue.

Gamescope runs pretty much hosts the whole the game itself. The bug above should not cause crashing.

I remember my update from 3.4->3.5 game causing caused by Anti cheat not being updated. I had to delete a few files to tell Steam to reinstall the anti cheat.

My mistake. I thought Gamescope only handled those performance settings, as well as the overlay. Gamescope may still have something to do with the crashing, at least in my case, as when I enter desktop mode and check the crashed process viewer, the only logs are for Gamescope, and they coincide with when I experienced the crashes.

[deaddoof]

引用自 Statesidemonk：

My mistake. I thought Gamescope only handled those performance settings, as well as the overlay. Gamescope may still have something to do with the crashing, at least in my case, as when I enter desktop mode and check the crashed process viewer, the only logs are for Gamescope, and they coincide with when I experienced the crashes.

When the application crashes, it also crashes gamescope. You should publish the bracktrace of it.

coredumpctl list

 coredumpctl debug <pid>
bt

It should dump what calls it was running.

[Viper X8]

I got the problem, that i boot after sleep mode games dont start or if started show black screen. if i use the quick menu (3 dots) i see the game screen (if started)