Recently traveled away from my home network. I’ve avoided updating because everything was working perfectly. Unfortunately, and I honestly don’t know how, after connecting to a new network my deck updated to 3.5.5 and then again to 3.5.7. The update to 3.5.7 was my choice. I figured it already updated to 3.5.5 so 3.5.7 must fix whatever bugs I was avoiding in 3.5.5.

Now, every single game ends in an OS crash and “verifying update” appears. Emulation still works perfectly. I can get anywhere from 30 second to several minutes before a crash.

Things I’ve tried:

  • make hotspot ssid and pw match my home network
  • hold … and power. Unfortunately 3.4 had already been overwritten by 3.5.7 and 3.5.5
  • restarted
  • hard shutdown and restart

Any ideas what I could try next? TIA

  • davidraidBEnglish
    1·
    10 months ago

    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?