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

[murphyjohn]

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:

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

[HotRunes]

I'm also experiencing this same issue, mainly with Kingdoms of Amalur: Re-Reckoning, Grim Dawn and Bioshock: Remastered, but it seems to happen with every game and has rendered my Steam Deck unusable. My VRAM is set to 4GB, I have tried the 'disable Updated Fan Control' fix advised to me by Steam Support, and have also tried setting a fixed GPU clock speed (as it seems like I'm also experiencing the 200/1040MHz bug too?). I've also completed a full re-image of the Deck from scratch, so a brand new installation.

None of these fixes have resolved the issue, and it's basically a total crapshoot as to how long I'll actually get to play a game for, it could be 45 mins and then the game will freeze, and my Steam Deck will reboot with the 'Verifying Installation' screen appearing first. Or it could be one minute into loading into the game and the same thing will happen.

It's really very annoying, as I've only had my Steam Deck for about three weeks, maybe four. At this point I'm tempted to return it for a refund, as it just seems very unreliable, what's the point if I'm not actually going to be able to play any games on it for an extended period of time.

[AleSank]

Also me, after update to 3.5.5, and also after 3.5.7, I can't play to anything. I have tested the deck with Spiderman Remastered, Cyberpunk and Forza Horizon 5. With stock settings, at the start menu, the console freeze and reboot with the message 'Verifying Installation'. I have tried with the changes:

• UMA 4gb
• GPU clock limit to 1600

and with this configuration I can play for maybe 10 minutes, but same error and same message.

Ps: before the 3.5.5 update the settings were all default and, with overlay 3 in battery settings, I noticed the 200/1040 mhz from CPU.

PPS: but valve read this comments?

[murphyjohn]

I'm not sure if valve read this. So please also create a support ticket for this problem and reference and link to this open issue.

[LEVIMITSU]

Same happening here, though I've just got my steam deck so I know no life before 3.5.5

I'm on 3.5.7 and play games downloaded from steam for around 10 minutes if I'm lucky and then they crash I've upped my VRAM to 4GB and clock speed at 1600 and still getting crashes in games like divinity, apex & the Witcher 3

I don't want to jump to conclusions and send it back for replacement or repair etc as it sounds like software to me

I just need steam or valve to clarify and I'm happy to wait, anyone else weighing in on this conversation is appreciated, I love the steam deck, as soon as it works as intended I'll be one happy fella!

[murphyjohn]

@LEVIMITSU I think it is very likely that it is a software issue that can be patched but you should make a support ticket via Steam anyway and see if they can resolve it for you or give you an RMA. As with others be sure to mention this github issue as being related.

I opened my ticket 2 days ago and have still not had a response from Steam.

[HotRunes]

@LEVIMITSU I think it is very likely that it is a software issue that can be patched but you should make a support ticket via Steam anyway and see if they can resolve it for you or give you an RMA. As with others be sure to mention this github issue as being related.

I opened my ticket 2 days ago and have still not had a response from Steam.

I opened a ticket back on Monday afternoon, then got a response on Tuesday evening. Though they advised troubleshooting and trying the 'disable Updated Fan Control' fix, which didn't work and I replied to them to advise of this, though I'm still waiting on further support.

[LEVIMITSU]

@murphyjohn @HotRunes I have also opened a ticket with them, what is the disable 'updated fan control' fix? i'm willing to give that a try if they advised that themselves the issue must be known and surrounding that? i'll update you guys here with my response from valve / steam too whenever they respond, thanks guys

[LEVIMITSU]

yep just tried turning off updated fan control and still crashing!

[LEVIMITSU]

Also just to clarify, I installed Emudeck and have been emulating, i'm not sure how invasive some of these files or plugins are that may be included, i'm going to flatten / re-image the steam deck later and see how i get on, for anyone else that may also have emudeck installed it may be that clashing with new OS or something to that effect, i'll keep you updated as this may be useful to some of you!

[murphyjohn]

I have Emudeck also

[LEVIMITSU]

If steam games run fine / as they should without emudeck installed I will try manually installing the emulators after to minimise problems

[HotRunes]

I don't have Emudeck installed now, but I did previously. I re-imaged my Steam Deck and am running a vanilla install (no addons or tools etc) and I'm still experiencing the same crash and reboot issues. Have you guys upgraded the SSD in your SD by any chance? As I have the 64GB LCD version, but I upgraded to a 1TB Sabrent Rocket 2230, the day after I received the device. I'm tempted to switch the SSD back to the original 64GB version and re-image that drive, then see if I experience the same issue. As if I do, then it's obviously a hardware/software issue, if not, then it could be the Sabrent SSD.

[HotRunes]

@lostgoat Hi there, are you aware of the issues described in this thread? Any idea of a fix for these issues, or is it hardware/software related that Valve will need to resolve?

[murphyjohn]

Have you guys upgraded the SSD in your SD by any chance?

No. I have a 256GB model and never opened it. I think it is almost certainly a software issue given the occurrence after the SteamOS upgrade beyond 3.5.5, and the mitigating effect of upping the UMA frame buffer to 4GB.

[HotRunes]

Is there anywhere that hosts old versions of the SteamOS software image? As it could be an idea to try installing an older version of the OS to test for this issue and then run that for the time being (if this issue isn't present in that version), until this gets picked up and fixed by Valve.

[LEVIMITSU]

Is there anywhere that hosts old versions of the SteamOS software image? As it could be an idea to try installing an older version of the OS to test for this issue and then run that for the time being (if this issue isn't present in that version), until this gets picked up and fixed by Valve.

i was also thinking to possibly do this

[LEVIMITSU]

I don't have Emudeck installed now, but I did previously. I re-imaged my Steam Deck and am running a vanilla install (no addons or tools etc) and I'm still experiencing the same crash and reboot issues. Have you guys upgraded the SSD in your SD by any chance? As I have the 64GB LCD version, but I upgraded to a 1TB Sabrent Rocket 2230, the day after I received the device. I'm tempted to switch the SSD back to the original 64GB version and re-image that drive, then see if I experience the same issue. As if I do, then it's obviously a hardware/software issue, if not, then it could be the Sabrent SSD.

I upgraded to an integral 1tb

[Statesidemonk]

I’m also having this issue.

I bought the 64GB LCD Steam Deck, new, directly from Steam (not a third-party seller) just over a month ago.

It’s one of the “newer” ones, with the black board protector with only two screws.

I upgraded to a Corsair MP600 Mini 1TB, but the problem also exists when using the stock 64GB drive.

I’ve tried everything imaginable. I tried setting the buffer to 4GB, and lower. Manually setting the GPU to 1600. Doing a clean reinstallation with the Steam Recovery image, on both the 64GB drive and the 1TB. I tried all three OS builds, and every Proton (including GE). Enabling battery mode in the bios and then powering it back on a couple minutes later with the power cable. Nothing.

I’ve contacted Steam Support, and they suggested I try plugging the stock power supply cable firmly into the Deck. That seemingly worked, but it was just a fluke as the crashing returned on the third gaming session. They also suggested I remove the SD card, disable the updated fan controls, and not use any extensions. Still no dice, and it’s been over a day since I last informed them that I still needed assistance.

This is extremely frustrating. I just want to be able to play my Steam Deck, not have it sitting in its case collecting dust.

[lostgoat]

After running into this issue, could someone submit a system report at the bottom of Settings->System.

Send me your steam username or a link to your steam profile and I'll be able to pull the logs.

A system report includes info for the current and previous boot. So ensure that you submit the system report immediately after the crash happens on the next boot.

[LEVIMITSU]

flattened it and the problem still exists, used an old image and it updated to 3.5.5 there was no way to stop it updating, absoloutely sh*t

[HotRunes]

After running into this issue, could someone submit a system report at the bottom of Settings->System.

Send me your steam username or a link to your steam profile and I'll be able to pull the logs.

A system report includes info for the current and previous boot. So ensure that you submit the system report immediately after the crash happens on the next boot.

@lostgoat I've encountered the issue again just now, so I have submitted a system report to the Steam Support servers. My Steam username is yon123, here is a link to my profile: https://steamcommunity.com/profiles/76561197969609441/

[hafley66]

I've had this issue as well, playing crystal project. i did factory reset and played for hours and it was fine.

Just turned on my steamdeck and caught it restarting by applying some update, and now its back to crashing about a few minutes into playing all the time.

username is hafley66

[Khristophor]

@lostgoat also just reproduced and submitted a system report. Did a factory reset and tried out the preview channel, still happening.

Steam profile https://steamcommunity.com/id/khristophor/

[lostgoat]

Thanks for the system reports. It seems like all three reports point to the same crash signature:

                                                   Stack trace of thread 13998:
                                                   #0  0x00007f04833b226c n/a (libc.so.6 + 0x8926c)
                                                   #1  0x00007f0483362a08 raise (libc.so.6 + 0x39a08)
                                                   #2  0x00007f048334b538 abort (libc.so.6 + 0x22538)
                                                   #3  0x00007f048334b45c n/a (libc.so.6 + 0x2245c)
                                                   #4  0x00007f048335b3d6 __assert_fail (libc.so.6 + 0x323d6)
                                                   #5  0x000056093b5d5647 n/a (gamescope + 0x7d647)
                                                   #6  0x000056093b69a33f n/a (gamescope + 0x14233f)
                                                   #7  0x000056093b5b24fd n/a (gamescope + 0x5a4fd)
                                                   #8  0x000056093b5c6501 n/a (gamescope + 0x6e501)
                                                   #9  0x000056093b5c7b7f n/a (gamescope + 0x6fb7f)
                                                   #10 0x00007f04836e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                                   #11 0x00007f04833b044b n/a (libc.so.6 + 0x8744b)
                                                   #12 0x00007f0483433e40 n/a (libc.so.6 + 0x10ae40)

We'll take a look.

[AleSank]

Guys, a little edit from me: I have updated the client to the latest, restored 'best default' in bios settings (I have changed only UMA), removed the GPU clock at 1600 and set only limit to 40fps. I have been played a Forza horizon 5 for 2 hours without restarts.

[Statesidemonk]

After running into this issue, could someone submit a system report at the bottom of Settings->System.

Send me your steam username or a link to your steam profile and I'll be able to pull the logs.

A system report includes info for the current and previous boot. So ensure that you submit the system report immediately after the crash happens on the next boot.

Here is a link to my Steam profile. I just submitted system report directly after the latest crash. Let me know if you need any more information.

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

For added information, this is off of a clean factory reset. Stock 64GB drive. The game I was playing was Deadrising, installed to the internal drive. No SD card inserted. Everything was on default settings, with the exception of “enable updated fan control” being disabled.

I was able to play earlier, fresh off of the factory reset and using the stock power cable to power on the Deck after it was in Battery Storage Mode, but it crashed a minute or two into the second game play. For the second session, I powered on from off, not sleep mode. The power cable also wasn’t plugged in this time, as the battery was over 80%.

I saw that you have received other reports showing similar crashes, so hopefully this can further assist the debugging.

Thank you.

[kjbracey2]

I've been having regular crashes in Disco Elysium, and checking my system report, I've got the same backtrace as above.

[LEVIMITSU]

@lostgoat I have created a report (i think i was logged in) i logged out and back in to file it so hopefully that doesn't change anything) let me know what you see, i can recreate it if needs be!?

https://steamcommunity.com/profiles/76561199483281078/

[LEVIMITSU]

I may have made a small discovery, I have started booting the games that were crashing via desktop mode and they work perfectly, this tells me there's a bug in the steam deck game mode overlay that's clashing, as a temporary work around you can go into desktop mode and open steam and create a shortcut to it as a non steam game and THEN it will boot from steam deck game mode (or simply boot from desktop mode if you're happy playing the game from there), only annoying thing is that it doesn't have the artwork but for now until they patch it because i'm 90% sure it's software.

What's weird though is there must be different parts for different steam decks as my dad has one too and his runs as it should and we have the same model, same everything when we look at version codes, processor info etc, I even logged into his and downloaded the games that were crashing and they don't crash on his via game deck mode.

3.5.5 & 3.5.7 isn't one size fits all (it seems)

there is clearly something wrong / different with the executable in game mode vs desktop / linux mode

If we're all having the same problem let me know if the above helps ^^^

the two games that i can make crash consistently were divinity, original sin 2 & apex legends,

witcher 3 crashed once via steam deck mode and hasn't crashed since, I can also run sekiro with no crashes

thanks guys

[murphyjohn]

@LEVIMITSU I have also seen users on discord/reddit report the same thing (games don't crash in desktop mode). I tried setting my VRAM buffer back to 1GB and playing games last night to reproduce the issue for sending a system report and in true debugging fashion, I got no crashes in over an hour of playing and cannot reproduce the issue when I want it to happen. lol Thanks to those who have submitted reports though and very big thanks to Andres @lostgoat for looking into the issue.

[LEVIMITSU]

yes, it's still annoying that they crash via the game overlay, but hopefully that gets fixed soon, i also set my vram back, just so everything runs as intended.

just to add i doubt it makes much difference but i added shortcuts to the desktop version to for the games i play, with the problems being executables it might make a difference (just something to bare in mind lol)

we should still look into this, i hope it gets sorted sooner than later because it is still a major bug!

[HotRunes]

I tried running a game that was crashing in game mode via desktop mode (as per the above suggestion), and it still crashed after about five minutes. Though this time it didn't reboot my Steam Deck, or show the 'Verifying Installation' screen, it just crashed to desktop, and it looked as if the game was still open as it was still visible on the taskbar at the bottom, but if I clicked on the game icon, it wouldn't do anything.

To be honest, I think I'm just going to return my Steam Deck for a refund. I'm just a bit fed up and frustrated with the fact that I can't actually use it to play games without it crashing, along with the fact that there's no indication on whether this is a hardware or software issue, and whether Valve will be rolling out a fix, if it is software related.

I'm also very unhappy with the length of time it's taking to get any correspondence back from Steam Support on my ticket, and to reach a resolution for the problem. So the Steam Deck is currently an expensive paperweight.

[Statesidemonk]

It’s not just in games and game mode. It’s also done this in Desktop mode using Firefox.

[Statesidemonk]

Just curious. Given that you have identified that we are facing the same crash signature, does this point more to a software or hardware issue?

[lostgoat]

Most likely a software issue.

I’m curious, does everyone here have HDR Visualization enabled under Settings->Display?

[murphyjohn]

I’m curious, does everyone here have HDR Visualization enabled under Settings->Display?

I do not.

[HotRunes]

Most likely a software issue.

I’m curious, does everyone here have HDR Visualization enabled under Settings->Display?

@lostgoat

No, it's disabled on my Steam Deck as well:

'HDR Visualization - None'

[HotRunes]

Is anyone experiencing this issue on the new OLED Deck, or does everyone have the LCD model? I'm on a 64GB LCD model, with my SSD upgraded to a 1TB Sabrent Rocket 2230.

[lostgoat]

I suspect that doing a SteamOS re-image will get undo whatever combination of variables is causing this crash.

Just wanted to mention that in case anyone wants the most crude solution to the problem.

However, I’m pretty interested in finding out what is actually triggering this crash and we are still investigating the issue to fix it properly.

If you also see the games crash in desktop mode that is also useful information. If that happens I’d love to see a system report after that happens. Having a timestamp for when the game crash happened is also useful.

[HotRunes]

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

@lostgoat

I've re-imaged my Steam Deck four times in total, and it still didn't fix the problem. Twice on the 1TB Sabrent SSD that I installed, then another two times on the original 64GB eMMC SSD that I put back into the Steam Deck to test the issue with. Currently my device is completely unusable, it's sat gathering dust. I've been advised that I should RMA it by Steam Support, and they've sent me all of the RMA details to get that process underway.

[murphyjohn]

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

I'm going to avoid re-imaging, both to avoid the pain of setting things up again and in hopes that if I do encounter the issue again (I still have not had it happen since a few days ago after dozens of instances before then) I will be able to submit logs for helping find the actual cause. It's very curious how it is occurring to a (relatively) small percentage of users, yet we seemingly all have a variety of different hardware models, and games and software. It's a juicy bug for sure.

[Statesidemonk]

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

I’ve tried doing a SteamOS re-image before, and it did not solve the problem. I used a SanDisk 128GB Ultra Dual Drive Go USB Type-C Flash Drive, Black - SDDDC3-128G-G46; the official and latest OS image provided by Steam/Valve; and used the latest version of Rufus (on Win 11) to write the boot drive. It shows up as EFI in the boot drive menu.

If it is related to imaging the boot drive, what can I do differently to ensure a proper installation?

I’ve had the Deck crash the same way when using FireFox in Desktop mode. I’ll repeat it and submit the crash report for that, as well as for a game or two.

Thank you again for bearing with us and trying to help us get our Steam Decks working.

[Menahen]

I was having this same problem, the game would crash every 5 minutes, sometimes instantly when it was a heavier game, I did several things, increased vram, reset the gpu, did the factory reset, nothing worked, even in mode desktop crashed every 5 minutes. However, my problem was resolved by doing a factory reset and then resetting the gpu, after that I did a test and left Just Cause 3 running for another 5 hours and I didn't have any more crashes, and now it's been 3 days and I haven't had any more crashes.

[lostgoat]

Quick update on this. It looks like the problem starts with the game causing a GPU hang, from which the deck fails to recover. This GPU hang is what then causes gamescope to crash with the stack above. E.g.

Dec 01 12:09:36 steamdeck kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=204307, emitted seq=204309
Dec 01 12:09:36 steamdeck kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process DeadRising.exe pid 2480 thread dxvk-submit pid 2500
Dec 01 12:09:36 steamdeck kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset begin!

When gamescope crashes you get a "verifying installation" screen the next time it starts. This looks like a reboot happened since the system compositor crashed, but the deck isn't actually rebooting. It is just restarting all the processes that died.

So, the next question to answer is what is causing these games to hang the GPU. From what I can see in the logs it is related to the GPU receiving bad commands. This can due to a variety of reasons, from bug in gpu drivers, to a bug in the game, or possibly a bug in proton.

It would be good to know if switching proton versions makes a difference for anyone. The bad thing is that due to the nature of the bug (it doesn't reproduce consistently) it becomes hard to check if a change successfully mitigated the problem or not.

If anyone has a suggestion for a specific game+proton combination that causes this to problem to reproduce semi consistently and quickly it would help speed up testing.

[lostgoat]

Something else that can cause these issue is undervolting.

Some people have mentioned that they've reset their BIOS to default and the problem is still happening for them. So I don't think it is the root cause of the problem here. But if anyone here has their deck undervolted I'd strongly recommend removing the undervolt otherwise we can incorrectly get undervolt crashes and crashes from this bug mixed up in the thread.

[lostgoat]

Some other data that would be useful to hear if you are experiencing this issue:

• Do you have an OLED deck or LCD?
• How long have you had your deck?
• When did the problems start happening? (Please answer with a time measurement, e.g. 1 week ago, 3 weeks ago, 6 months ago, etc).

[Khristophor]

@lostgoat

LCD 256GB Steam deck, purchased at launch. I think I received it July 2022?

I've kept it stock the entire time, played it fairly regularly (weekly, if not daily). This is the first time I've had issues with stability.

Noticed issues presenting November 23 after updating from 3.4.x to 3.5.x. Performed a factory reset and the issue persisted.

I've been testing with Demons Tilt, it consistently crashes in under a minute. This time I was pinned at Proton 8.0-4. I submitted another system report.

I can also confirm it happens in desktop mode and is consistent with your findings: the game crashes but remains in the taskbar and I can no longer open it. I also noticed visual issues after the crash in desktop mode where the start menu doesn't render. I submitted a system report after it happened in desktop, it should be my second most recent one.

I'll be away for a few days so I won't be able to help debug until Thursday, but I can probably get more crashes/screen recordings if you're still looking into it then.

[Statesidemonk]

I bought my LCD Deck Oct. 26th of this year, and received it Nov. 2nd. So I’ve only had it for about a month now.

I didn’t really play resource heavy games during the first week or two. I installed a couple and just walked around in the worlds for a minute or two, but no real gameplay. I mainly played Vampire Survivors, which I had zero issues with. It’s only with heavier, 3D world games that seem to cause the crashes.

Skyrim:SE, Prey (2017), and Deadrising caused crashes for me, on every Proton version, including the default setting of not forcing any. They crash when installed on the internal drive, or when installed on an SD. Those would be the top 3 games and settings I can attest create this issue. At least on my Deck.

I’ll continue testing out the new settings I mentioned above, and can try to induce crashes I’ve experienced in Desktop mode with a game and Firefox, if that data would help.

*edit

No undervolting in the bios. Though I did try very modest undervolting settings in an attempt to see if it would help with his problem. It didn’t. I’ve since returned those settings to their default, using both the “return to default” option in the bottom left corner of the bios, and by powering on while using the button combination to reset the CMOS.

[aero64]

Some other data that would be useful to hear if you are experiencing this issue:

• Do you have an OLED deck or LCD?
• How long have you had your deck?
• When did the problems start happening? (Please answer with a time measurement, e.g. 1 week ago, 3 weeks ago, 6 months ago, etc).

I'm having the same issue as stated.

1. LCD 64gb, Upgraded to Sabrent 1TB.
2. September 2023 (3 months)
3. It started happening with the 3.5 update. Before that I would play demanding games on the docked mode and have no issue with crashing whatsoever. Recently (1.5 weeks ago), I started playing BFV and noticed it crashing heavily in docked mode, at 720p and 1080p resolutions. These crashes continued in handheld mode, although at a much lower rate. I upgraded to 3.5.8 Preview and the 200/1040mhz issue is gone, but my Deck is still crashing with the GPU at 200mhz when it crashes, so the problem still persists.

[emcy849]

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

Hi @lostgoat I am also having this same issue, which has rendered my deck unusable for many games. The observed behaviour is that certain games will crash game mode (gamescope), and after some time the deck will display 'verifying installation' and restart game mode.

I have a game where this is a 100% reproducible issue, and it is Halo Infinite campaign mode. The game starts in multiplayer mode and you switch it over to campaign mode from there. Strangely the multiplayer mode works without a problem. I took a video of exactly what happens here, note there is nearly 2 minutes of a black screen before game mode restarts: https://files.catbox.moe/zb9n6l.mp4 (you probably want to download the file in full before playing since Catbox seems to not have enough bandwidth to play videos smoothly in the browser these days). The developer launches Halo Infinite with proton experimental by default, but changing it to proton 8 or even 7 had no effect, game mode still crashes.

To reiterate, with H I campaign mode the issue is 100% reproducible for me, i have been unable to play campaign mode at all since this problem started (tried many times), with one exception: It starts fine in desktop mode! even when using Big Picture via desktop mode! Thats the only way i can launch it now.

As for when this problem started, it started immediately upon updating my deck from OS 3.4.11 to 3.5.5 stable, on the day 3.5.5 stable was released. And by immediately i mean H I campaign mode was the first thing i tried after the update, and it wouldnt work and has never worked since. Before updating to 3.5.5 i had never ever had any problems with game mode crashing before with any game. I purchased my deck around April this year, a LCD 512GB model. I havent changed anything in the BIOS, ive never even entered the BIOS settings. Currently my deck is on OS 3.5.8 beta (because i was also getting the 200mhz/1040mhz thing and that fixes it) and Stable branch for the steam client.

I have submitted a system report immediately after the crash you see in the video i linked, my steam profile is https://steamcommunity.com/profiles/76561197974200199

I believe these factors point very strongly towards this bug being a problem with Gamescope, introduced at least when OS 3.5.5 stable was released. If you need any more help or info just hit me up, im keen to get this bug dealt with because its basically stopping me enjoying me deck at the moment. Thanks.