3.5.5 broke my games

[OldSchoolScrub]

I've played darktide on my deck for months with absolutely no issues. Ever since I updated to 3.5.5 the game, and multiple others, will crash to a full system reboot/verifying os install almost every time I start it. I'm genuinely upset about this. It was one of my favorite games, and I have no idea what to do. I've tried using various protons. I've verified. I've completely re-installed. I've deleted proton files. It works maybe 1 in 20 launches. The worst part is, one it's up it plays absolutely great. Even better than before. However, the constant launch crashes are unacceptable. Any ideas? It always crashes at the initial shader configuration screen.

[MISO4EVER]

I’ve heard a lot of bad things about the new os and it’s many issues. So far I have had one issue which caused a freeze up where I needed to force reboot and than it verified the os. But it seems a bit shotty hopefully it improves

[Broseph Joseph]

Originally posted by OldSchoolScrub:

I've played darktide on my deck for months with absolutely no issues. Ever since I updated to 3.5.5 the game, and multiple others, will crash to a full system reboot/verifying os install almost every time I start it. I'm genuinely upset about this. It was one of my favorite games, and I have no idea what to do. I've tried using various protons. I've verified. I've completely re-installed. I've deleted proton files. It works maybe 1 in 20 launches. The worst part is, one it's up it plays absolutely great. Even better than before. However, the constant launch crashes are unacceptable. Any ideas? It always crashes at the initial shader configuration screen.

Confirmed, i get this most consistently with halo infinite campaign mode. Multiplayer works fine but if i try to switch to campaign mode, the deck will hard crash to 'verifying installation' every time. Tried it with a bunch of different proton versions too. I am completely unable to play that game at all right now.

[OldSchoolScrub]

Originally posted by Isadoraisacat:

I’ve heard a lot of bad things about the new os and it’s many issues. So far I have had one issue which caused a freeze up where I needed to force reboot and than it verified the os. But it seems a bit shotty hopefully it improves

Mines done this dozens if not hundreds of times now

[OldSchoolScrub]

Originally posted by Broseph Joseph:

Originally posted by OldSchoolScrub:

I've played darktide on my deck for months with absolutely no issues. Ever since I updated to 3.5.5 the game, and multiple others, will crash to a full system reboot/verifying os install almost every time I start it. I'm genuinely upset about this. It was one of my favorite games, and I have no idea what to do. I've tried using various protons. I've verified. I've completely re-installed. I've deleted proton files. It works maybe 1 in 20 launches. The worst part is, one it's up it plays absolutely great. Even better than before. However, the constant launch crashes are unacceptable. Any ideas? It always crashes at the initial shader configuration screen.

Confirmed, i get this most consistently with halo infinite campaign mode. Multiplayer works fine but if i try to switch to campaign mode, the deck will hard crash to 'verifying installation' every time. Tried it with a bunch of different proton versions too. I am completely unable to play that game at all right now.

Yep, since posting I've tried all three update channels, re-imaged, same problems continue. It's borked.

[Qmitsu]

"I'm experiencing the same issue. Have you managed to deal with this problem in any way?"

[TeXnoFile]

So far, I had only one crash in deep rock and once half life froze completely. Im not sure, if it is more or less than it happened before because i havent played on 3.5.5 a lot, only like 4 hours, but you are not the only one complaining about this

[djgpdazl]

I`ve been having this "freeze" "verifying" problem for a few months. It literally happens to all my games... no fix until this moment! Really sucks

[Wyrmhole on a String Theory]

I haven't found a fix for this yet unfortunately but I updated my deck to 3.5.7 yesterday and am having the exact same issue in Warframe; brand new 512 LCD deck too from a recent RMA