The fix is to increase your vram to 4gb in the bios settings. Takes half a minute to do

Video guide here https://youtube.com/shorts/4pqfH2gYH1k?si=Oe5X8pEgTxttrvar

The fix is to increase your vram to 4gb in the bios settings. Takes half a minute to do

Video guide here https://youtube.com/shorts/4pqfH2gYH1k?si=Oe5X8pEgTxttrvar

Don’t worry, you are very much not alone. This happens to me too. Prey was doing it within twenty minutes, every time, the Yuzu emulator too and pretty much any demanding title. It’s definitely a software issue and a bug that’s appeared since 3.5. There’s another two posts about it (if you keep scrolling for a long whole haha) with multiple people commenting to say they have the same issue. You won’t have to return your Deck. This will be fixable, either through user methods or, eventually and hopefully soon, standard updates.

Changing the vram to 4gb seems to have fixed it for me, I haven’t removed Docky, but I haven’t had time to extensively test it to be certain. However I did sneak two hours of play in Prey yesterday and it didn’t crash.

Given it always happened when the performance monitor was reporting more than 4gb of vram in use, and that Yuzu has recently been suffering from a vram memory leak bug, I really do think the issue is vram related. People have been saying the issue doesn’t happen in Desktop mode but I haven’t tried playing any games in that mode to test (other than one but I don’t know how demanding it was on vram). It could be a bug with Gamescope, the Game mode window manager.

Here is how to change the vram

https://youtube.com/shorts/4pqfH2gYH1k?si=456vc7kUwJRG32ef

I’m curious, did doing this change the boot icon? Would hate to lose the red deck symbol upon boot up… Unless that part of the boot is the bios?

I’m curious, will doing this (or outright swapping the two drives) change the boot icon? Would hate to lose the red deck symbol upon bolt up… Unless that part of the boot is the bios?

How did you change the dedicated vram?

Same here. Ever since the first 3.5 update. It’s genuinely gutting. At first I thought it was a Yuzu bug, then I realised it was happening in all games. The time it takes to happen seems random but never longer than 30 minutes. People in the yuzu forums suggested it was a vram leak causing the problem, which was interesting to me as I noticed the issue always happened when the vram in the performance monitor exceeded 4gb.

Can anyone confirm if their games crash around the same figure? Prey, which doesn’t run for longer than ten minutes before crashing my deck to Verifying Installation, quickly hits more than 4.0 vram in the performance monitor… Could the crashing be a result of gamescope not coping correctly since the update?