MH Wilds: GPU reset with subsequent loss of VRAM, games crash
I have encountered this largely with Monster Hunter Wilds but it did happen to me also with RE4 Remake. Attaching screenshot of behaviors from journalctl. This is followed by Wayland and KDE completely failing and restarting after the game crashes. After this sequence occurs I always have the following results:
- Black screen (probably due to GPU resetting itself)
- Game crashes
- KDE Restarts
- After KDE restarts, no game is able to be launched without restarting the entire machine
Journalctl displays pages of coredumps after this happens. At this stage I am not sure what causes the crash to even happen in the first place, nor am I sure what causes games to not be able to launch without a restart. At the current stage I am unable to play MH Wilds.
Versions:
rpm-ostree version: '2024.9'
branch: bazzite:stable Bazzite 41
Linux: 6.13.5-100.bazzite.fc41.x86_64
Proton: Bleeding Edge, also tried with Hotfix
Mesa: 24.3.4
System Specs:
AMD Ryzen 5 5600X
AMD Radeon RX 6800XT
ASUS ROG B550F gaming wifi motherboard
10 Replies
I'm in a rather similar boat and will try to share if I find any actionable advice. I have issues with MHWilds on a 5950X and 6900XT and Bazzite 41. Yesterday I tripped the Denuvo DRM and wasn't able to keep experimenting with Proton or in-game settings to find something helpful.
The previous open beta weekend I could play pretty reliably so I felt somewhat comfortable picking up the released game
for me crashing begins in the second biome (~1hr in?) but became 100% repeatable
I tried a couple launch command additions, Proton Hotfix/Experimental/Experimental-bleeding-edge and one more I can't remember, and dropping the in-game stuff to potato settings. I could reliably crash the benchmark with any kind of FSR so I disabled that regardless.
ProtonDB thread had folks suggesting undervolting and under clocking and by that point I was feeling 🥴 and then the DRM kicked me out for the day.
I'm reasonably hopeful this will get better for all amd users after the first week or two, but perhaps that's naive of me.
oh and to confirm my symptoms are ~identical except that I can go on to play other less-demanding games without a full reboot, but I was manually killing the session with
loginctl and then restarting display-manager.service with systemctl to bring ssdm back
I was monitoring it with ssh from an adjacent laptop and could watch the symptoms begin in dmesg -wI wonder if this is a rdna2 problem because reading through chats it seems like people play no problem, mostly people with 7000 series cards or even nvidia
I’m on rx6800 and have the same issue.
Someone on protondb posted that switching to mesa 25 more or less fixes crashing, but i don’t know how do to that to test it
I have an rx 7600 and I'm also encountering this problem when in the oilbasin map.
I would definitely like to know an estimate on when the mesa 25 drivers will be available on the bazzite image because yeah, I heard the same thing. As of right now we can only wait
Meanwhile switching to ge-proton-9.25 seems to have solved the crashing (so far at least in a ~1hr long sesh)
I also have RX 6800, what works for me is going into Steam, Monster Hunter Wilds properties, turn on force compatibility tool, and Proton Experimental. Haven't crash since.
experimental (and bleeding edge) crashed for me. So i guess not everything works for everyone
But i’m 10 hrs in with ge-proton9-25, not a single crash so far
My happiness didn’t last long, started crashing again :NotLikeThis:
Lots of people in the proton support thread suggest using the AMDVLK driver. This driver sucks absolute ass and I'm forced to crank down all my graphics settings, but it doesn't crash afaik
Shadows and rendering options don't work right now. I can change them, but it makes no difference and revert back. I'm only 4 hours in, not looking forward to crashing later on =/
I've noticed that changes to in-game settings aren't preserved reliably if you crash out after making the changes. If I make significant changes I quit all of the way out of the game so it doesn't reset on me.
the saving wheel indicator when you confirm the settings seems to be somewhat of a lie