Frequent kernel panics while gaming on fresh install

I am having a kernel panic every few hours while playing ARC Raiders via Steam. I am on a desktop PC with the attached specs. The panics happen from every hour to every four hours or so. When they happen, I get the attached kernel panic screen stating:

KERNEL PANIC!
Please reboot your computer.
Attempted to kill init! exitcode=0x0000000b

KERNEL PANIC!
Please reboot your computer.
Attempted to kill init! exitcode=0x0000000b

KERNEL PANIC!
Please reboot your computer.
Attempted to kill init! exitcode=0x0000000b

KERNEL PANIC!
Please reboot your computer.
Attempted to kill init! exitcode=0x0000000b

I've tried searching information on this, but I'm pretty inexperienced with Linux and can't figure out what could be causing this. This is a fresh install of Bazzite with very few new apps installed. I have not made any changes to any configuration files, or installed anything using a method other than Bazaar.

This is not a dual boot setup; I wiped the entire drive to install Bazzite. I also had no crashes or other hardware issues when previously running Windows for several years, so I doubt it's a hardware issue (unless it's Linux-specific).

I also tried using

sudo ujust get-logs

sudo ujust get-logs

sudo ujust get-logs

sudo ujust get-logs and have included the information below. The logs seem to end rather abruptly without any obvious error that I can see.

System Information:
 
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:72dc7dd0d4640305b8e07e2e463f19cf8b81491e611c68254d0ab831f16698a0
                  Version: 42.20251018 (2025-10-18T21:29:23Z)
 
Logs This Boot: https://paste.centos.org/view/b58a1b93
 
Logs Last Boot: https://paste.centos.org/view/3e9c9109
 
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/0
Please check whether /run/user/0/wayland-0 socket exists and is accessible.

System Information:
 
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:72dc7dd0d4640305b8e07e2e463f19cf8b81491e611c68254d0ab831f16698a0
                  Version: 42.20251018 (2025-10-18T21:29:23Z)
 
Logs This Boot: https://paste.centos.org/view/b58a1b93
 
Logs Last Boot: https://paste.centos.org/view/3e9c9109
 
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/0
Please check whether /run/user/0/wayland-0 socket exists and is accessible.

System Information:
 
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:72dc7dd0d4640305b8e07e2e463f19cf8b81491e611c68254d0ab831f16698a0
                  Version: 42.20251018 (2025-10-18T21:29:23Z)
 
Logs This Boot: https://paste.centos.org/view/b58a1b93
 
Logs Last Boot: https://paste.centos.org/view/3e9c9109
 
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/0
Please check whether /run/user/0/wayland-0 socket exists and is accessible.

System Information:
 
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:72dc7dd0d4640305b8e07e2e463f19cf8b81491e611c68254d0ab831f16698a0
                  Version: 42.20251018 (2025-10-18T21:29:23Z)
 
Logs This Boot: https://paste.centos.org/view/b58a1b93
 
Logs Last Boot: https://paste.centos.org/view/3e9c9109
 
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/0
Please check whether /run/user/0/wayland-0 socket exists and is accessible.

I would appreciate any help you can provide. Thanks!

Solution

After 4 hours of gaming with no problems on Bazzite, safe to say that my SSD was going bad. The new NVMe SSD seems to have solved the issues. Thanks to everyone for your suggestions as I worked to figure this out.

Jump to solution

皇

皇家海星•11/28/25, 1:37 AM

all the

ujust

ujust

scripts don't require

sudo

sudo

, they will ask for permission if they need it

皇

皇家海星•11/28/25, 1:37 AM

for now can you post the output of

rpm-ostree kargs

rpm-ostree kargs

AnderswoOP•11/28/25, 1:38 AM

rhgb quiet root=UUID=8712a236-a155-4ebe-bf9c-5ee30637bdbe rootflags=subvol=root rw ostree=/ostree/boot.0/default/cc0e5062c182b7c679634cb44e1e63bf8df0b54e86862067a48407fb9490322c/0 bluetooth.disable_ertm=1

rhgb quiet root=UUID=8712a236-a155-4ebe-bf9c-5ee30637bdbe rootflags=subvol=root rw ostree=/ostree/boot.0/default/cc0e5062c182b7c679634cb44e1e63bf8df0b54e86862067a48407fb9490322c/0 bluetooth.disable_ertm=1

皇

皇家海星•11/28/25, 1:41 AM

ok you can try adding a karg by rpm-ostree kargs --append-if-missing=clearcpuid=514rpm-ostree kargs --append-if-missing=clearcpuid=514
This disables umip instructions, which seem to fail a lot in your logs

AnderswoOP•11/28/25, 1:42 AM

Okay, I have done that.

皇

皇家海星•11/28/25, 1:44 AM

once it completes it will tell you to reboot

皇

皇家海星•11/28/25, 1:44 AM

after the reboot you can test if the issue persists

AnderswoOP•11/28/25, 1:45 AM

Okay, I'll do that. Thanks! I will follow up in this thread if it panics again.

皇

皇家海星•11/28/25, 1:46 AM

if it does, then the karg is useless and you can remove it either by bruh momentbruh moment to roll back to the last deployment, or rpm-ostree kargs --remove-if-present=clearcpuid=514rpm-ostree kargs --remove-if-present=clearcpuid=514 to make a new deployment without the karg

AnderswoOP•11/28/25, 4:01 AM

So: I have had three more crashes in the last hour, none of them kernel panics. Each time, the game/OS freezes, audio continues for a few moments, and then the screen goes black and is unrecoverable.

System Information:
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

Logs This Boot: https://paste.centos.org/view/7b69bcea

Logs Last Boot: https://paste.centos.org/view/2a1b85f3

System Information:
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:6195955014538362b2eea306a7dc304a0c78ab714d1d0f777b73821fae5988e1
                  Version: 43.20251126 (2025-11-26T06:01:06Z)

Logs This Boot: https://paste.centos.org/view/7b69bcea

Logs Last Boot: https://paste.centos.org/view/2a1b85f3

AnderswoOP•11/28/25, 4:02 AM

The first crash was after 3 hours of gameplay.
The second crash was after 5 minutes in the game after rebooting.
The third crash was on the login screen after rebooting -- after I hit enter after typing my password to log in, it froze.

皇

皇家海星•11/28/25, 5:46 AM

pretty safe to say you can remove the clearcpuid karg

皇

皇家海星•11/28/25, 5:47 AM

still, not good - there's still nothing that points directly to what caused the kernel panic

AnderswoOP•11/28/25, 6:18 AM

Yeah, this might just be a bust. I switched to CachyOS out of curiosity and sure enough, also a kernel panic after an hour or so.

AnderswoOP•11/28/25, 6:19 AM

For whatever reason, my hardware is not working with Linux.

AnderswoOP•11/28/25, 6:19 AM

It's a real bummer to lose my progress/work at random every few hours so I'm afraid it's back to Windows for now. Maybe my next PC or the Steam Machine will be more stable. Thanks for your help.

AAnderswo Yeah, this might just be a bust. I switched to CachyOS out of curiosity and sure...

nagito || Knight of Emilia•11/28/25, 7:34 AM

is your BIOS up to date?

AnderswoOP•11/28/25, 7:35 AM

I have some friends helping me separately and that's exactly what they suggested, I'm working on updating BIOS now

AAnderswo I have some friends helping me separately and that's exactly what they suggested...

nagito || Knight of Emilia•11/28/25, 7:36 AM

the BIOS does a lot of initialization of stuff so it's possible it's doing something funky currently & may stop when updated

AnderswoOP•11/28/25, 8:00 AM

I've updated BIOS -- no idea if/when it will crash again, but if it does I will follow up.

AnderswoOP•11/28/25, 8:24 AM

No dice, still crashes to black

皇

皇家海星•11/28/25, 8:27 AM

a shot in the dark but maybe power related issues if your area is susceptible to brown outs?

AnderswoOP•11/28/25, 8:28 AM

No, no brownouts here. I never had any issue like this when running Windows. The OS crashes after stuttering for a few moments in-game, and power doesn't shut off -- screen just goes black/nonresponsive.

AnderswoOP•11/28/25, 9:27 AM

Is there a standard protocol for trying to diagnose a problem in Linux when the crash logs don’t reveal any relevant information in the moments before the crash? I’m grasping for any clues I can find and provide.

皇

皇家海星•11/28/25, 10:08 AM

no not really, or at least none that I know of

皇皇家海星 no not really, or at least none that I know of

nagito || Knight of Emilia•11/28/25, 10:13 AM

i mean there are such things as kernel crash dumps

皇

皇家海星•11/28/25, 10:40 AM

true

AAnderswo The first crash was after 3 hours of gameplay. The second crash was after 5 minu...

dnkmmr•11/28/25, 1:34 PM

Hey, I have experienced something like that too but just much rarer

AAnderswo It's a real bummer to lose my progress/work at random every few hours so I'm afr...

dnkmmr•11/28/25, 1:34 PM

You should get a framework

Ddnkmmr You should get a framework

AnderswoOP•11/28/25, 7:56 PM

I don't need a laptop at this time

AnderswoOP•11/28/25, 7:56 PM

Okay so I have also:

Reset BIOS to factory default
Run memtest (https://memtest.org/), it passed

AnderswoOP•11/28/25, 7:57 PM

No crashes yet but I didn't make any big changes so I expect it to happen again.

AnderswoOP•11/28/25, 9:00 PM

Just got a crash on CachyOS that actually gave me some information. I understand this is not Bazzite but it crashed in the same way and Bazzite never gave any error info on kernel panic. There might be a clue in this?