I’m running Dragon’s Dogma 2 on Fedora 40 with AMD CPU/GPU setup, and it keeps crashing my PC, though the music still plays and USB devices remain connected. The emergency commands don’t help and I have to power cycle. Looks like my AMD GPU driver is causing the issue based on journalctl logs. Nothing I tried from Google searches has helped. Has anyone dealt with a similar situation, or got any fixes or troubleshooting steps that could help me out?
4 Answers
For the ‘GPU ring gfx timeout’, you can try searching the web for more specific fixes; this type of error pops up with AMD GPUs sometimes. Here’s a plan you might want to consider: Stress-test your system on Windows to rule out hardware issues. Try underclocking your GPU when on Linux. Alternatively, rolling back to a stable older kernel might fix it as some kernels work better with certain drivers. As a side note, on Windows, recoveries from such crashes are typically smoother.
If you’re facing this kind of crashing issue, you might want to explore the SysRq key feature—specifically, alt + SysRq + e, which should end all processes and can be a gentler way to shut down instead of simply cutting power, helping avoid data probs. But if even that isn’t working, it could indicate a deeper issue with drivers or hardware, so you’ll need to look further into potential solutions.
If you’re using the MESA driver, you could try switching to the latest AMDVLK driver. Grab the latest from their GitHub, move the necessary files (amd_icd64.json and amdvlk64.so) to a location you can access. Modify the paths in the json file to point to the new location, then set up the Steam launch options with: VK_ICD_FILENAMES=[path to]/amd_icd64.json WINEDLLOVERRIDES=dinput8=n,b %command%. This workaround might help stabilize Dragon’s Dogma 2, and could be useful for similar games too.
It might be RAM related, as these kinds of driver crashes often are. Load up your BIOS and restore the default settings to see if the game still messes up. Sometimes the simplest BIOS settings can have a sneaky impact on stability, especially if there have been tweaks.
Thanks for the hint, but even the SysRq combo isn’t responsive. My keyboard seems a bit confusing on that front, but I’ll double-check.