Game scope crashing 2-4 minutes into the game no matter the setting.
So I have bazzite on my Rog Ally Z1E, ROG Ally X and a custom build desktop (all is well with those 3) but I recently picked up a "minis fourm" PC (Ryzen 5700G 32gb 3600mhz ram, and a amd rx 7600 GPU) I have the igpu disabled because at first I thought that was the issue. But playing Spider-Man MM in gamescope 2 or 4 minutes into the game loading any save. Gamescope reboots and kicks me out of the game. When I try it in desktop mode game runs great for 2-4 minutes then bogs from 170+ fps to 8-13 fps no crash but unplayable. (CPU and GPU temps are in the 50s so it's not thermal or power limited) Scratching my head
22 Replies
I should mention I thought it might be hardware related but then the issue doesn't happen in windows at all.
Are all your other system fully updated?
Same version bazzite?
Yes all systems are on deck "stable" channel, and bazzite 41
Bazzite 41 is just that's its based on F41. Doesn't mean it's the same version.
The 1700x system and the 5700G system were flashed off the same iso/drive
Have you tried just running
ujust update
?
In terminalI'll try that again. I did a fresh install before dinner a few hours ago to make sure I didn't mess anything up in the process
There's new versions about twice a week and maybe a version introduces or fixes an issue.
Gamescope is often updated too
Gamescope crashing is very often some regression made by valve
That's why I stopped using "beta"
Gamescope itself is in the bazzite image
It's not in steam
Updates says everything is good
I'll do a reboot and re test
Can you post
rpm-ostree status
? The output.I have 1 more theory
So it's a weird thing but the bios supports PBO and so windows seems to know not to use it on this board (this mini PC only supports up to 65watt CPUs) and with p95 or Aida 64 or cinabench it basically stops it at 65watts all the time no spikes. But I noticed while loading shaders in gamescope it's pushing near 130watts. (I know that's because of the good temps+PBO) but I would think that would crash the whole system not just restart gamescope 🤔
Nah. I don't think so.
Can you post output of
rpm-ostree status
?
You'd get kernel panics
And possibly segfaults
If it was cpu instability
I just want to know what version you're on now and what version you were on before
Because of gamescope version differences.
You can test it now see if it still crashes or not. I can't help you further today since I'm going to bed.This?
Bump. Still looking for a solution. Not sure how to help and give more info. If someone can teach me how to pull logs I will supply them
Let gamescope crash and then type
ujust post-gamescope-logs
in a terminal.
Post the link hereThis ujust seems broken
Never mind that
Unfortunately
One thing you could try is rebasing to an old version
see if its a gamescope regression
bazzite-rollback-helper rebase 41.20241216
This build fixed the crash issue on another user I helped.
I mean I think it's worth a try if you're already thinking its some kind of hardware issue.
could clear that up for youI think I figured it out. It had to do with proton and the hdmi being the cause. After changing the default audio device and swapping to proton 8 it seems that it works fine now. (Testing as we speak)