Bazzite Randomly Crashes

Description:
The crash occurs randomly during the usage of my laptop. No specific software launched that could trigger the crash (cf. attached image).
My guess would be a "safety switch" in case of "overheating"...

Laptop Spec:

MSI Steel Series GL 65 95D

CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 12
On-line CPU(s) list: 0-11
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
CPU family: 6
Model: 158

GPU
NVidia GForce GTX 1660 TI

I've already ran ostree status command:
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:cce2eaa398efc42e0ff3c14c0d54a024a987cde0feeb3b72d7970d0bf54883b8
Version: 43.20251210.1 (2025-12-10T21:44:16Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:15fe467cf18209019339997ed7d5fd4546d5e59d9834fcdb609264ee97f973d2
Version: 43.20251210 (2025-12-10T08:33:46Z)

Regarding boot logs, nothing seems wrong.

Have someone here already experienced this kind of issue ?
If needed I can provide more information.

Thank you in advance for your help !

biebel•12/21/25, 5:02 PM

Since you have a 1660, you should be on the nvidia-open branch. See if it happens when you're on that branch too. You can rebase to it using the brhbrh command. No user data is lost in rebasing.

MitchelloOP•12/21/25, 5:07 PM

Hello biebel, thank you for the quick answer !
I'll try to run the following command and let you know it the issue occurs again.

'rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia-open:stable'

biebel•12/21/25, 5:07 PM

don't pick the unverified one

MitchelloOP•12/21/25, 5:07 PM

Noted, will change that

MitchelloOP•12/21/25, 5:08 PM

Will use the rebase helper ^^'

biebel•12/21/25, 5:09 PM

fyi: brhbrhwill open a text interface that lets you select what you want to rebase to btw, so you don't have to give those lengthy commands

brh rebase bazzite-nvidia-open:stablebrh rebase bazzite-nvidia-open:stable would work too.

MitchelloOP•12/21/25, 5:09 PM

Thanks again !

biebel•12/21/25, 5:10 PM

Also don't worry about crashing during rebasing as the booted image is untouched, so if the update won't complete you can try again without issues.

Bbiebel don't pick the unverified one

dnkmmr•12/21/25, 5:43 PM

Hiw do i switch to the verified one?

biebel•12/21/25, 5:47 PM

Rebase to the verified one. See what you have in rpm-ostree status and replace unverified with signed in the rpm-ostree rebase commandrpm-ostree rebase command, I think.

MitchelloOP•12/21/25, 7:38 PM

Worked a little bit longer but occurred once again, might be residual stuff, will see later

AgentElrond•12/21/25, 8:03 PM

@Mitchello I have a similar graphics card. Can you run this command in a terminal to check the count?

AgentElrond•12/21/25, 8:03 PM

lsof -p $(pidof plasmashell) | grep sync_file | wc -l
1

lsof -p $(pidof plasmashell) | grep sync_file | wc -l
1

MitchelloOP•12/21/25, 8:06 PM

Hello @AgentElrond, the count is 0

MMitchello Hello <@197550393935396865>, the count is 0

AgentElrond•12/21/25, 8:08 PM

OK good, that's not your issue then. On some systems the count keeps increasing

AgentElrond•12/21/25, 8:09 PM

If the crash didn't make you fully reboot, then ujust logs-this-bootujust logs-this-boot may produce useful logs near the bottom to paste here

MitchelloOP•12/21/25, 8:12 PM

That's the problem I think. I can't really get some valuable logs from the boot logs as I must hardstop the computer and wait for it to stop crash loop

AgentElrond•12/21/25, 8:19 PM

ah so ujust logs-last-bootujust logs-last-boot has no interesting info after the reboot, I'm guessing

AgentElrond•12/21/25, 8:20 PM

I've rarely seen that, and don't have any leads on how to debug it when it does.

AgentElrond•12/21/25, 8:21 PM

I don't see how much RAM you have. Have run System Monitor to see if you're running at all close to 100% used in normal usage, e.g. the usage that you're doing when it crashes?

AgentElrond•12/21/25, 8:21 PM

Even a web browser can eat a lot of memory sometimes.

MitchelloOP•12/21/25, 8:54 PM

For the RAM, I have 16Go.
In normal usage, it's around 6Go (Firefox running, some software running in background, etc.)
Randomness is driving everyone crazy when it comes to bugs ^^'

AgentElrond•12/21/25, 8:59 PM

yeah, sounds normal

AgentElrond•12/21/25, 8:59 PM

I wish I had better advice, but I'm in the same situation where I don't know how to debug super hard crashes

AgentElrond•12/21/25, 8:59 PM

I have a GTX 1650 but haven't seen a hard crash in a while

MitchelloOP•12/21/25, 9:18 PM

Just had another crash, and here are the boot logs
déc 21 20:55:05 kernel: Linux version 6.17.7-ba20.fc43.x86_64 (builder@3993c864882b) (gcc (GCC) 15.2.1 2025111>
déc 21 20:55:05 kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/ostree/default-02541ee26c3192da6049cbee4e422e305c9>
déc 21 20:55:05 kernel: BIOS-provided physical RAM map:
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000078533fff] usable
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x0000000078534000-0x000000007962efff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x000000007962f000-0x00000000796abfff] ACPI data
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x00000000796ac000-0x000000007983dfff] ACPI NVS
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x000000007983e000-0x000000007ad0dfff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x000000007ad0e000-0x000000007ad0efff] usable
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x000000007ad0f000-0x000000007fffffff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
déc 21 20:55:05 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000047dffffff] usable
déc 21 20:55:05 kernel: NX (Execute Disable) protection: active
déc 21 20:55:05 kernel: APIC: Static calls initialized
déc 21 20:55:05 kernel: efi: EFI v2.7 by American Megatrends

MitchelloOP•12/21/25, 9:18 PM

déc 21 20:55:05 kernel: efi: ACPI 2.0=0x79648000 ACPI=0x79648000 TPMFinalLog=0x797a8000 SMBIOS=0x7aabc000 SMBI>
déc 21 20:55:05 kernel: random: crng init done

AgentElrond•12/21/25, 9:25 PM

yeah doesn't look like anything related, just normal startup messages

AgentElrond•12/21/25, 9:26 PM

Sadly I have no ideas

AgentElrond•12/21/25, 9:26 PM

actually, maybe one idea

AgentElrond•12/21/25, 9:26 PM

Did you intend to use bazzite-nvidia instead of bazzite-nvidia-open? I would think your graphics card can work with the open version

MitchelloOP•12/21/25, 9:36 PM

Well, I rebased to the open one based on previous advices, but I'll try the "classic one", thanks for the help !

AgentElrond•12/21/25, 9:37 PM

I mean I recommend the open one

AgentElrond•12/21/25, 9:37 PM

ohhhh I'm way too slow, sorry

AgentElrond•12/21/25, 9:37 PM

I missed that someone already suggested you switch above

AgentElrond•12/21/25, 9:37 PM

I thought you were still running the old version

AgentElrond•12/21/25, 9:38 PM

I have no more ideas than. GTX 1650 works fine for me on nvidia-open

MitchelloOP•12/21/25, 9:45 PM

No worry ! Then, it must be something else that a GPU issue, will investigate further more

Bazzite Randomly Crashes

Similar Threads

Similar Threads

Similar Threads