ValveSoftware / SteamOS

SteamOS community tracker
1.57k stars 70 forks source link

Crash Bandicoot N. Sane Trilogy Crashing *ERROR* ring gfx_0.0.0 timeout #1526

Closed jackintoshplus closed 4 months ago

jackintoshplus commented 4 months ago

Your system information

Please describe your issue in as much detail as possible:

First, I played all of Crash Bandicoot (1) with absolutely zero issue then moved onto Crash 2: Cortex Strikes Back. I expected the same smooth experience.

I was in the middle of playing "Sewer or Later" in Crash Bandicoot 2: Cortex Strikes Back and I started experiencing crashes which resulted in the Steam Deck rebooting and showing a screen with 'Verifying Installation' and a loading bar beneath it.

I had FSR on which I assumed might have been the issue, but even after turning it off, the crashes still happened. I also tried the following solutions but had no luck:

I do not have Decky installed, and I have not tinkered with any of the Steam Overlay Performance settings since re-imaging my Deck. No shenanigans in the BIOS either.

I am using a Steam Deck LCD with a 2TB TEAMGROUP M.2 SSD installed. This doesn't appear to be happening with any other games I've tried such as Sonic Adventure 2 and Call of Duty: Black Ops III.

In my systemreport-[date].txt log file, I noted this snippet: May 25 18:54:13 steamdeck kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=252371, emitted seq=252373\ May 25 18:54:13 steamdeck kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process CrashBandicootN pid 9166 thread dxvk-submit pid 9220\ snippet.txt

Steps for reproducing this issue:

  1. Run game, choose any Crash Bandicoot game, either use a new or previous save file.
  2. Enter a level, it can even be the first level if using a new save file. Alternatively, sit inside of the warp room (Crash 2: Cortex Strikes Back)
  3. Play the level for 1-5 minutes, or if idling in the warp room- wait 5-10 minutes.
jackintoshplus commented 4 months ago

So I just found out within the past couple of days this is now happening with multiple games such as Sonic Adventure 2 and Call of Duty: Black Ops III. Did a re-image and APU graphics driver reset but it did not make a difference, even when doing the aforementioned resets on a SteamOS install on the stock eMMC my Deck came with. Guess I'm gonna RMA.