Steam Deck crashes and reboots to "verifying installation" screen in games after update to v 3.5.5 or higher.

murphyjohn commented 9 months ago

Your system information

Steam client version: 1700676668
SteamOS version: 3.5.7
Opted into Steam client beta?: No
Opted into SteamOS beta?: No
Have you checked for updates in Settings > System?: Yes

Since updating to SteamOS versions 3.5.5 and higher on Steam Deck, games crash after a few minutes of gameplay and the console reboots with a "verifying installation" screen upon restart. This occurs throughout all games (both steam and non-steam) and there are also noticeable graphical glitches in games while running.

It appears that this issue is somehow related to VRAM usage as when the UMA Frame Buffer Size is changed from 1GB (default) to 4GB the issue seems to be mitigated somewhat. (EDIT: This is no longer the case. Even with the UMA at 4GB, games now crash and the deck reboots, rendering the deck as an expensive brick).

However this means that there is less VRAM available for CPU usage and it means that games are unplayable on SteamOS on the steam deck without changing this setting in the BIOS for those who are effected.

This is a widespread issue that is reported among numerous other users on Steam deck forums and discussions.

Steps for reproducing this issue:

Update to version 3.5.5 or 3.5.7
Play a 3D game, e.g. Spider-Man: Miles Morales
Game has graphical glitches and console crashes within 2 minutes of play.
Steam Deck reboots itself and verifies installation each time.

HH-Unix commented 9 months ago

After I had the same experience with game crashes on the release of 3.5.5 (Tomb Raider, Death Stranding, Metro 2033 Redux, ...), I went back to 3.4.11. I left the BIOS at 119 for the time being. But I noticed pretty quickly that my Steam Deck crashed (Gamescope error) as soon as I started a game (e.g. Tomb Raider) immediately after booting it up. But if I waited a little and then started a game, I had no problems. I had read here on GITHUB that there might be problems with the sleep/wake state in BIOS 115/116 and that this error might still be present in BIOS 119.

So I also reset the BIOS to 110. What can I say, I have absolutely no problem with any games on the Steam Deck. Everything runs smoothly at 60 FPS.

What I also noticed with the BIOS 115/116 and 119 was, in addition to the sleep/wake state, the battery indicator (the LED did not go off when the battery charge level was 100%).

This may not really help, but the interaction between BIOS 119 and SteamOS 3.5.x may not be perfect.

Best regards

Igor-devc commented 9 months ago

I'm offering you a solution to the problem, not whining and moaning on the forums.

Igor-devc commented 9 months ago

murphyjohn why do you keep throwing your fingers, I made it clear where they belong

murphyjohn commented 9 months ago

murphyjohn why do you keep throwing your fingers, I made it clear where they belong

Hi. I don't think installing a new OS is a very helpful "solution". This issue is about trying to fix a problem with SteamOS.

"Just install a different OS" is pretty much always going to get rid of whatever software problem someone might have. It goes without saying, and is just not useful. As someone else said, it is very much a "nuclear option". I'd be more inclined to return the device than solely run windows on it, since there are other handheld computers more suited to windows use (which I also don't want).

aero64 commented 9 months ago

Just downgraded to 3.4.11 from 3.5.10. No crashes in the games I was crashing in. Looks like I'll be playing like this until Valve comes up with a fix.

Anyone gotten VibrantDeck to work on 3.4 though? It's removed from the Decky Loader store.

AlexNes-SDUser commented 9 months ago

Hi and good morning! I have played Diablo 4 (battle.net, non steam game) for about 3 hours yesterday without any problems. The game runs only for ~4 days without crashing after Patch 1.2 came out... Then I couldn't play longer than 5 minutes,

So I don't know why, but maybe for me its ok now.. and I'm on 3.5.7 stable release, (downgraded from 3.5.8 preview) and BIOS 119

Now I don't know what to do.. I have received RMA documents.. At the moment my Deck runs great.. but for how long?.. and I still don't know what caused the problems ..

Igor-devc commented 9 months ago

murphyjohn why do you keep throwing your fingers, I made it clear where they belong

Hi. I don't think installing a new OS is a very helpful "solution". This issue is about trying to fix a problem with SteamOS.

"Just install a different OS" is pretty much always going to get rid of whatever software problem someone might have. It goes without saying, and is just not useful. As someone else said, it is very much a "nuclear option". I'd be more inclined to return the device than solely run windows on it, since there are other handheld computers more suited to windows use (which I also don't want).

MurphyJohn stop whining, install windows 11 and don't make brains for yourself and people!

Igor-devc commented 9 months ago

Author

Do you want to play and enjoy your device or fix it every day?

AleSank commented 9 months ago

Author

Do you want to play and enjoy your device or fix it every day?

But seriously? So, I bought a device with a specific software ( not windows ) for avoid all drivers, update and various related to windows AND your solution is INSTALL WINDOWS... yes... Or if u prefer is possible use the steam deck like a 'door stop', it can work also for this, right? This thread is for try to understand why many users has a bug with releases after 3.5.5, not for understanding how use steam deck in different mode. So, please, stop with your 'fix", because it isn't that.

aero64 commented 9 months ago

This whole argument is derailing the scope of this conversation. No need to continue further about Windows 11.

Igor-devc commented 9 months ago

Author

Do you want to play and enjoy your device or fix it every day?

But seriously? So, I bought a device with a specific software ( not windows ) for avoid all drivers, update and various related to windows AND your solution is INSTALL WINDOWS... yes... Or if u prefer is possible use the steam deck like a 'door stop', it can work also for this, right? This thread is for try to understand why many users has a bug with releases after 3.5.5, not for understanding how use steam deck in different mode. So, please, stop with your 'fix", because it isn't that.

How is steam os better than windows 11? Steam os does not support half of the games, and a large number of users do not have a console running on steam os. On Windows, everything works fine for almost all games, there is no drop in performance. There are no problems with the fact that it is not possible to use the console as on steam os. Obviously, there is not a single advantage in favor of the raw steam os.

AleSank commented 9 months ago

Author

Do you want to play and enjoy your device or fix it every day?

But seriously? So, I bought a device with a specific software ( not windows ) for avoid all drivers, update and various related to windows AND your solution is INSTALL WINDOWS... yes... Or if u prefer is possible use the steam deck like a 'door stop', it can work also for this, right? This thread is for try to understand why many users has a bug with releases after 3.5.5, not for understanding how use steam deck in different mode. So, please, stop with your 'fix", because it isn't that.

How is steam os better than windows 11? Steam os does not support half of the games, and a large number of users do not have a console running on steam os. On Windows, everything works fine for almost all games, there is no drop in performance. There are no problems with the fact that it is not possible to use the console as on steam os. Obviously, there is not a single advantage in favor of the raw steam os.

Yes, this is clear, but is a choice. If I bought a MacBook, but for example with Linux it work better, change the SO isn't the solution. Apple must fix any problems, because by purchasing a Mac, and having proprietary software, Apple MUST fix its product. Then, if I change the OS to solve the problem, it remains solely my choice.

Igor-devc commented 9 months ago

Author

Do you want to play and enjoy your device or fix it every day?

But seriously? So, I bought a device with a specific software ( not windows ) for avoid all drivers, update and various related to windows AND your solution is INSTALL WINDOWS... yes... Or if u prefer is possible use the steam deck like a 'door stop', it can work also for this, right? This thread is for try to understand why many users has a bug with releases after 3.5.5, not for understanding how use steam deck in different mode. So, please, stop with your 'fix", because it isn't that.

How is steam os better than windows 11? Steam os does not support half of the games, and a large number of users do not have a console running on steam os. On Windows, everything works fine for almost all games, there is no drop in performance. There are no problems with the fact that it is not possible to use the console as on steam os. Obviously, there is not a single advantage in favor of the raw steam os.

Yes, this is clear, but is a choice. If I bought a MacBook, but for example with Linux it work better, change the SO isn't the solution. Apple must fix any problems, because by purchasing a Mac, and having proprietary software, Apple MUST fix its product. Then, if I change the OS to solve the problem, it remains solely my choice.

So let gaben fix your steam deck. It is not clear when this will happen, I would install windows 11. if I need steam os, I must. the console is under warranty, I will go to change to another working console, this is not my problem and I do not need to disassemble and solve it, let gaben solve this problem.

rvreqTheSheepo commented 9 months ago

I'm offering you a solution to the problem, not whining and moaning on the forums.

Sir, this is a thread of SteamOS issues, fuck ups always happen somewhere. People are just providing feedback and expect changes, but it's Valve, they always need some time. And you do moan.

ScottCarammell commented 9 months ago

@ScottCarammell can you submit a system report after the crash happens and link me your steam account profile?

Sorry for the late reply, I saw when this was posted but for some reason my deck didn't crash until just now. Like I said, the issue has gotten much better recently (though it's not gone, and may or may not get worse over time, I'd have to test)

Anyway, you asked for a system report, you've got a system report. https://steamcommunity.com/id/scottcarammell/

LEVIMITSU commented 9 months ago

@lostgoat may I ask, do you work for steam? I'm so close to returning my deck for another and it would put my mind at ease to know it has been acknowledged by the company lol, they aren't helping at all via emails

aero64 commented 9 months ago

@lostgoat may I ask, do you work for steam? I'm so close to returning my deck for another and it would put my mind at ease to know it has been acknowledged by the company lol, they aren't helping at all via emails

If it started happening when you got the 3.5 update, then it is most likely just a software problem which will get resolved one day. Even if it is software, you deserved a device that simply just worked, so if you want to RMA, it's not the end of the world. But you might face the same issue again if Valve doesn't fix the root cause.

I would try doing the 3.4.11 downgrade that user lostgoat mentioned (ONLY DO IF YOU HAVE THE LCD DECK). I did it on my LCD deck and haven't had crashes in the past 8 hours, will update if I experience any later.

ScottCarammell commented 9 months ago

@lostgoat may I ask, do you work for steam? I'm so close to returning my deck for another and it would put my mind at ease to know it has been acknowledged by the company lol, they aren't helping at all via emails

To answer your question, yes, he works for Valve as a software engineer (for Linux primarily, I believe).

Tomspencer42 commented 9 months ago

I've put my system update channel onto preview with 1GB UMA frame buffer size - 3 hours gameplay so far with no issues. Will keep updated

murphyjohn commented 9 months ago

I changed my UMA frame buffer back to 1GB (in attempt to trigger a crash to send a system report).

I have played about 3 hours over 3 play sessions this week without any crash. I am still on 3.5.7. I don't know what has changed. Crashes were frequent, almost ever-present when this issue was created.

emcy849 commented 9 months ago

People are still regularly popping up with this exactly problem https://old.reddit.com/r/SteamDeck/comments/18e1pwy/help/

Its not ubiquitous, but i think ive seen enough to say that its fairly widespread.

Khristophor commented 9 months ago

@lostgoat I downgraded to 3.4.11 this morning from 3.5.10 and a GPU reset (vol - and ...) and it seemed better at first but I'm seeing crashes again. Maybe I'm looking at a coincidental hardware issue caused or exacerbated by BIOS/SteamOS/Mesa updates.

I submitted a number of system reports today, and I've attached some diagnostic dumps based on suggestions from this thread

Any insight would be great, if it's a hardware issue I'd like to start an RMA process.

The big red flag for me today is Dave the Diver. I purchased the game September 15, and I was able to play long sessions without issue throughout September and October. Today, it's crashing almost immediately after gaining control. Right now my Steamdeck screen is black but I can still ssh in to the console.

Here's some text files, taken after crashes in Desktop and gamescope:

dmesg-1.txt.zip journal-1.txt.zip dmesg-2.txt.zip journal-2.txt.zip

(deck@steamdeck ~)$ pacman -Q|grep kdump
kdump-steamos 0.9-2
(deck@steamdeck ~)$ uname -a
Linux steamdeck 5.13.0-valve37-1-neptune #1 SMP PREEMPT Thu, 17 Aug 2023 23:47:04 +0000 x86_64 GNU/Linux
(deck@steamdeck ~)$ flatpak --version
Flatpak 1.12.4
(deck@steamdeck ~)$ flatpak list
Name                           Application ID                               Version           Branch               Installation
Freedesktop Platform           org.freedesktop.Platform                     22.08.19          22.08                system
Mesa                           org.freedesktop.Platform.GL.default          23.1.9            22.08                system
Mesa (Extra)                   org.freedesktop.Platform.GL.default          23.1.9            22.08-extra          system
openh264                       org.freedesktop.Platform.openh264            2.1.0             2.2.0                system
Breeze GTK theme               org.gtk.Gtk3theme.Breeze                     5.27.8            3.22                 system
Firefox                        org.mozilla.firefox                          120.0.1           stable               system
(deck@steamdeck ~)$ uptime
 14:49:31 up 16 min,  2 users,  load average: 1.46, 1.69, 1.27
(deck@steamdeck ~)$ journalctl -b | grep -i kdump
Dec 09 14:32:36 steamdeck systemd[1]: Starting SteamOS kdump loader boot-time service...
Dec 09 14:32:37 steamdeck root[923]: kdump-steamos: pstore-RAM was loaded successfully
Dec 09 14:32:37 steamdeck kdump-load.sh[932]: find: ‘/home//.steamos/offload/var/kdump/*’: No such file or directory
Dec 09 14:32:37 steamdeck systemd[1]: Finished SteamOS kdump loader boot-time service.

If there's any other useful info I can provide let me know.

Statesidemonk commented 9 months ago

The crashing returned for me. I’ll try the 3.4.11 downgrade and see if that helps.

I’ll also add this. I tried playing a game in desktop mode, and it crashed just the same. What was strange, though, was that it broke the desktop. I’ll explain.

The crashing was similar to game mode, only instead of the “verifying installation” message, it just returned to the desktop. The desktop, however, was extremely buggy. The mouse cursor was functional, and the mouse buttons (L2/R2), however, nothing would load properly. Clicking the logo at the bottom left of the screen would open the menu options, but it was completely whited out.

Statesidemonk commented 9 months ago

Ok. I successfully rolled back to 3.4.11. Games still crash, but like @lostgoat said, instead of exiting the game, giving the “verifying” message, and taking you to your library, the game just freezes. I was able to push the Steam button and exit the game that way. I did not need to use the power button.

I submitted another system report immediately after the crash.

https://steamcommunity.com/profiles/76561198076474768/

Details about my system

LCD Steam Deck OS Variant: steam deck-Rx OS Version: 3.4.11 OS Build: 20231005.1 Kernel Version: 5.13.0-valve37-1-neptune BIOS Version: F7A0119

Tomspencer42 commented 9 months ago

Any news on any fixes or anything yet?

bnnblbblgm commented 9 months ago

One thing to add @lostgoat and any other devs, I have found that JUSANT does not crash at all. It's the only game I've played and had absolutely 0 crashes. Not sure if that's useful, but maybe there's something about Jusant that could give a clue?

I'm on the beta channel and just had the latest update, can confirm the crash still happens. Doesn't seem to be much point trying the downgrade from what others have said.

Khristophor commented 9 months ago

Another update. Today I decided to roll back my BIOS to 110 based on this comment further up. Games that I had been testing with for crashes (Dave the Diver, A Hat in Time, Octopath Traveller, and Demon's Tilt) all ran fine, and made it further than any point on 3.5.x or 3.4.11.

Just out of curiosity, I kept the BIOS pinned at 110, and updated to current stable (3.5.7) and lo and behold, I've been playing all evening without a crash.

If anyone else wants to give it a shot, I used https://github.com/ryanrudolfoba/SteamDeck-BIOS-Manager to prevent the OS from updating the BIOS and downloading all the available BIOS versions. For the record, I tried 113 but none of my games would start.

Statesidemonk commented 9 months ago

Replying to https://github.com/ValveSoftware/SteamOS/issues/1257#issuecomment-1849165196

Interesting. I also wondered if the BIOS might be bugged or corrupted. I’ll give it a try on my SD and will post the results.

*UPDATE

Disregard. The crashing returned. BIOS 110 also experiences the crashing, so the issue is not with the BIOS.

AlexNes-SDUser commented 9 months ago

Short Update here: No Crash on the Weekend. But I have "only" played ~5h. Mostly Diablo 4

I'm happy to hear that some of you could play, too but I'm wondering that everyone has another solution.. I'm still on BIOS 119 and 3.5.7 without problems and D4 is running like never before..

emcy849 commented 9 months ago

This thread is getting pretty confusing with what people say works and what doesnt now.

If youve changed something and think it made it better or worse, just give it a little more time to make sure that something actually changed, and in what way, before rushing back here to report. The easier valve can pick actual causative and modifying factors out of the noise, the faster this bug will get addressed. For EG, ive only reported my experiences that are 100% reproducible, as in a certain game that runs every time under 3.4, and not at all under 3.5.

Im particularly confused about people reporting that rolling back to an 18 month old bios helps, as i was able to eliminate bios as a causative factor at least on my deck.

HevyMonkey commented 9 months ago

I do not know if I have the same issue as the other people here but I will comment it anyway. It seems like people have different issues that leads to the same end result here anyway.

For me I got a replacement unit around a week ago and instantly tried out two games that were problematic on my old Deck after the Stable 3.5.5 update, those being Blue Protocol JP and DJMax Respect V. They would either freeze or close down to library. Sometimes they would close down after a few minutes but they could also play for upwards of an hours at random times.

Blue Protocol used to crash to the verifying installation screen on 3.4.11 but I fixed that by increasing the SWAP file which I believe means that the memory manager probably closed down both the game and Steam to clear the RAM.

Rolling back the clocks to August and September I remember that it was 3.5.1 or 3.5.2 that started to be problematic with those games for me. Reverting to 3.4.11 would fix this. But I also want to remember that the original Main 3.5 did not exhibit this behaviour for me and that it was specifically 3.5.x that caused it.

Khristophor commented 9 months ago

Replying to https://github.com/ValveSoftware/SteamOS/issues/1257#issuecomment-1849905055

Respectfully, people posting their experiences around testing isn't the noise in this thread, and the maintainers are capable of determining what is and is not useful information. It's likely there's a multitude of issues ending up here because the presenting issue is gamescope being unable to recover after a game has crashed. What's causing these crashes could be a number of different things for different users.

In my case, a number of games that never crashed before the 3.5.x and F119 BIOS update started crashing. I was able to narrow it down to the BIOS because my feedback loop is very short (on the scale of minutes, and almost always under a minute):

3.5.7 and F119

A Hat in Time: Crashes after attempting to load a new game
Demon's Tilt: Crashes after 30-60 seconds of gameplay
Dave the Diver: Crashes after 30-60 seconds of gameplay
Octopath Traveller: Crashes after attempting to load a new game

3.4.11 and F119

A Hat in Time: Crashes after 30-60 seconds of gameplay
Demon's Tilt: Crashes in under 30 minutes of gameplay
Dave the Diver: Crashes in under 30 minutes of gamplay
Octopath Traveller: Crashes after 30-60 seconds of gameplay

3.4.11 and 3.5.7 and F110

I can play anything for more than 30 minutes, and games no longer immediately crash

It's likely this thread has outlived it's usefulness and people should be opening separate threads based on what they can chase down is the underlying cause behind an increased frequency of game crashes. But just like what is/is not on topic, it's not up to us to make that call.

Tomspencer42 commented 9 months ago

New update on the stable channel- can anyone confirm if this has helped with the issue?

LEVIMITSU commented 9 months ago

New update on the stable channel- can anyone confirm if this has helped with the issue?

not had an update come through yet, keeping an eye out is there a post about it on steam?

Tomspencer42 commented 9 months ago

New update on the stable channel- can anyone confirm if this has helped with the issue?

not had an update come through yet, keeping an eye out is there a post about it on steam?

Yes I'm just applying it now will update how it gets on

Statesidemonk commented 9 months ago

New update on the stable channel- can anyone confirm if this has helped with the issue?

Unfortunately, it still crashes with the new update to the stable channel

Skyrim: Special Edition. It crashed within five minutes of playtime.

Tested with Proton 7.0-6, but I’m assuming that like before it will crash on others, including GE editions.

Everything on default settings. Nothing changed in quick setting’s performance. Medium graphics settings in game.

lostgoat commented 9 months ago

@Khristophor if you re-update to 119 does the issue re-appear?

Every time a bios "update" happens it will trigger memory re-training. It would be good to update and re-test to rule out the possibility that this automatic re-training was the issue.

HH-Unix commented 9 months ago

@Khristophor if you re-update to 119 does the issue re-appear?

Every time a bios "update" happens it will trigger memory re-training. It would be good to update and re-test to rule out the possibility that this automatic re-training was the issue.

My SD is back on 3.5.7 and 119! And it seems OK so far. So far no crashes immediately after starting a game. Apart from the display error in MangoHud, I can't find anything else.

I will continue testing and report here.

What have I done: I upgraded the BIOS to 119 under 3.4.11 and then updated 3.5.7 (stable) - nothing else!

I can't explain this now.

Supplement: I can't set the SSD as default! Every reboot it switches to the MicroSD - I thought this was fixed?

BIOS 119: The battery indicator (LED) does not turn off when the battery level is 100%.

LSCOLMAN commented 9 months ago

I'm on the latest SteamDeck OS 3.5.9 with 119 BIOS.

I've Windows 10 on an SD card with games loaded
I've Windows 11 on an SD card with games loaded
I've Batocera emulation on an SD card with Switch games loaded
I've EmuDeck loaded in Steam Deck Desktop mode with Switch games loaded

In all these environments, I experience games crashing out, with the deck completely restarting in some instances. This makes me think this is underlying firmware/drivers released with 3.5.5, which Windows/Batocera require to operate correctly. Before this update, all these environments were trouble free for me.

I'm considering rolling back the firmware, and see if the crashing stops in Windows 10/11 and Batocera, but concerned that I may end up with a bricked SteamDeck.

Tyreiko commented 9 months ago

Downgrade to 3.4.11 with a bios reset resolve all crash steamdeck work perfectly , device is just hotter than in 3.5.7

emcy849 commented 9 months ago

Am i understanding correctly, the steam deck only trains memory once, per bios update? Not every time the system boots like all other x86 systems?

In that case, theoretically a marginal memory train done once and thereafter used every time the system boots could affect the device the same way every time? I guess i will try the bios reset and report back. Its certainly plausible too that consistently marginal memory could affect 3.5 in a way that it doesnt affect 3.4.

Khristophor commented 9 months ago

@lostgoat I updated my bios directly from 110 to 119 while on 3.5.7 and I haven't seen a recurrence of crashes.

In an attempt to have a repeatable process to reintroduce crashing I spent a few hours last night switching to various bios and OS combinations, but I haven't been able to nail down a particular flow to reproduce. It seemed like the "first" time flashing a bios was the most likely to cause crashes for me. Flashing 116 while on 3.4.11 for example would cause immediate game crashes, but repeating the process rolling to 3.4.11 and 116 from 3.5.7 and 119 did not present immediate crashing. It's possible I didn't let games run long enough to confirm, though. I was trying a bunch of combinations out.

I ended up on 3.5.7 and 110 again but in a bad state, although crashes took longer (closer to 30 minutes). I was able to revert to a good state by rolling back to 3.4.11 and 110 -> 3.5.7 and 110 -> 3.5.7 and 119. I've had games running for a couple hours this morning just to confirm the deck isn't crashing anymore on 3.5.7 and 119

I can try again over the next few days to see if I can get a consistent flow, but is there anything I can provide or try out that'll help you nail down the issue further?

LSCOLMAN commented 9 months ago

Kristopher,

On the current version (3.5.7 for you I understand), are you able to try downgrading to BIOS 110 and then go straight back to 119?

I feel this would probably be the most helpful scenario for the majority of us (including me) to try in that most users are likely on 3.5.5 upwards. This would be only a few steps for us to replicate and offer the memory train that has been mentioned as a potential solution?

Khristophor commented 9 months ago

@LSCOLMAN my deck is currently in a working state on 3.5.7 and 119, so I'll have to play around a bit to see if I can get it back into a crashing state on that combo, and try flashing down to 110 on 3.5.7 and back up to 119.

I can give it a shot later tonight but it might take me a bit to give an answer with 100% certainty.

Statesidemonk commented 9 months ago

I tried @Khristophor ‘s order of operations, but it sadly didn’t fix anything for me.

Preview build now has FW 120, so I’m trying that right now. I’ll post the results, as well as submit a crash report if it does crash.

Tomspencer42 commented 9 months ago

I tried @Khristophor ‘s order of operations, but it sadly didn’t fix anything for me.

Preview build now has FW 120, so I’m trying that right now. I’ll post the results, as well as submit a crash report if it does crash.

I've been playing Arkham: origins for the past 3 hours without a single crash. Before this update the game would work for about 5 minutes before crashing. So all signs looking good so far

bnnblbblgm commented 9 months ago

Returned for RMA today, seeing as the devs seem to have abandoned this thread. Hopefully (for me) it's at least partially a hardware issue, I'll update with whether the replacement unit has the same issue.

LSCOLMAN commented 9 months ago

I tried @Khristophor ‘s order of operations, but it sadly didn’t fix anything for me. Preview build now has FW 120, so I’m trying that right now. I’ll post the results, as well as submit a crash report if it does crash.

I've been playing Arkham: origins for the past 3 hours without a single crash. Before this update the game would work for about 5 minutes before crashing. So all signs looking good so far

What update did you try? Was it Kristophers sequence or the 120 firmware ?

Statesidemonk commented 9 months ago

Returned for RMA today, seeing as the devs seem to have abandoned this thread. Hopefully (for me) it's at least partially a hardware issue, I'll update with whether the replacement unit has the same issue.

I’ve given up and am trying to do that now as well. If it’s not effecting everyone and the devs are unable to reply the crashing, then it’s got to be a defective device. Steam support takes days to respond, and have been giving me more of the same unsuccessful suggestions that I have already told them don’t work, so hopefully they will finally initiate an RMA.

My Deck is relatively new, so they should honor the replacement. My only worry is how long it will take with the holiday seasons, as well as the claims that they are running low on the now discontinued 64GB LCD models.

emcy849 commented 9 months ago

More 'in the wild' sightings of this issue https://old.reddit.com/r/SteamDeck/comments/18isgbm/why_does_it_say_this_after_game_crashes/ https://old.reddit.com/r/SteamDeck/comments/18ijn3i/the_games_closed_and_after_that_appears_this/

Whats the word on BIOS 120? It only comes if you select preview channel right?

ValveSoftware / SteamOS