Windowing Crash While Gaming
Hi friends,
I've had a thing happen a couple of times while playing Star Wars Jedi: Survivor. Did some Googling but didn't land on anything definitive, so coming here to see if anyone can point me in the right direction.
Thanks so much in advance!!!
Typically, I have the game running, Discord and maybe Slack, OBS (for Twitch streaming), and Firefox.
I've had a crash happen twice, once during a boss fight and once while I was focused in my browser instead of the game (so the game was just sitting on pause).
Everything will freeze for a few seconds, then both monitors will go black. The monitors come back after a few seconds. Stream in OBS is terminated. With the most recent occurrence, Firefox (which is what I was focusing at the time of the crash) was visible on the side monitor, everything else appears as if they were minimized to the taskbar, which is visible on the main monitor. Some icons in the system tray were missing. Fans spin up and then the game exits. Trying to open the Bazzite menu or attempting to search or do anything in that menu is hit or miss. I end up just restarting to get things back in order.
Operating System: Bazzite 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.4-116.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor 1: AMD Radeon RX 7800 XT
Graphics Processor 2: AMD Radeon Graphics
Manufacturer: ASUS
19 Replies
I've had some crashes recently, you would need to check the log to find the segfault(s) and identify which processes they were in
I think
ujust logs-this-boot should give it, or you can dig through journalctl outputIf I restarted, are those logs still available?
try
ujust logs-last-boot then
You'll want to find something that mentions "dumped core" and a stack traceI tried running with a
-r flag (based on something I found searching Google), but that didn't work to see the most recent logs first. Last boot started 15 days ago, so there are a lot of logs. Is this reading from a file somewhere that I can reference instead of paging through them all? 🙂Ideally you would run it right after a crash
next time you get one, you can run
journalctl -S "2025-10-29 12:34:00" or whatever to see logs since a specified timestamp
Near the end you should find some red text with a stack traceI have the approximate time, so will that command show me everything after a timestamp?
precisely
So you could put it like 2 minutes before the crash, and use
> /tmp/crash.txt to dump it to a file, and then open it in an editor
assuming the logs still existWas getting a parsing error, so I changed to
journalctl --since "2025-10-29 18:11:00" . Just pasting for reference
Here is what I think is the beginning of the crash?
and here is the start of the core dump?
sorry yes, something like
journalctl -S "2025-10-29 03:00:00"
that's one, if you search the text file are there other instance(s) of "dumped core" nearby?yes, there are a number of them
I'm not familiar with the details, but that first dump does indeed appear to be a AMD driver issue. I'm seeing various patch(es) correcting that sort of illegal opcode error in the past.
However, I have no idea if your specific issue has been fixed, and if so, if it will be coming to Bazzite at some point, so I'm no further help here 😛
Just gut feeling, I doubt KDE crashing (the second log) would cause an illegal opcode error, so my current guess is that the first crash somehow led to the second
the order of core dumps is xwayland > maliit-keyboard > plasmashell > obs > xdg-desktop-por
good data, I hope someone with more knowledge can see this at some point
I appreciate the time you've spent, and I come out of this knowing a bit more on how to debug ... or at least get more info
I'm guessing the fix to this is much higher than anything I do on my local machine, so I'll mark as resolved. Thanks again!
I mean it's not really resolved, it's good to know such crashes are happening on specific games
I was hoping someone else could confirm it's likely a driver bug
I can certainly mark as unresolved. Sorry about that.
Just happened again with a different game, this time Signalis. So it's not necessarily the game. Might be OBS causing the crashes.
Most recent logs are failing to load
libnvidia-encode.so.1 and libnvidia-ml.so.1, which makes sense since I'm on AMD?