Random crashes on Manjaro Gnome

Support Graphics & Display
,
1

Hi folks,
after installing Manjaro on a new desktop-PC I’ve experienced crashes forcing me to reboot the machine. They present as follows:

The last screen image stays on indefinitely. Sounds and music loop indefinitely, like a broken record. The mouse cursor doesn’t respond to input. Pressing the tty-shortcut also has no effect.

As stated in the title, I’ve been unable to discern a pattern to these crashes as of now, except that they never happen right after login but at least a few minutes after. Moreover, the crashes happen infrequently. I checked gnome-logs but didn’t find anything obviously related to the crash.

Is there anything else I could try?

Inxi:

  Kernel: 6.12.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=e2b06ab7-5745-4a81-ba94-7075d2030a77 rw quiet splash apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 49.2 Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME B650-PLUS WIFI v: Rev 1.xx
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 3057 date: 10/29/2024
CPU:
  Info: model: AMD Ryzen 5 9600X bits: 64 type: MT MCP arch: Zen 5 gen: 5
    level: v4 note: check built: 2024+ process: TSMC n4 (4nm) family: 0x1A (26)
    model-id: 0x44 (68) stepping: 0 microcode: 0xB404023
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 480 KiB desc: d-6x48 KiB; i-6x32 KiB L2: 6 MiB
    desc: 6x1024 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3004 min/max: 600/5484 boost: enabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 3004 2: 3004 3: 3004
    4: 3004 5: 3004 6: 3004 7: 3004 8: 3004 9: 3004 10: 3004 11: 3004 12: 3004
    bogomips: 93461
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
    svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: IBPB on VMEXIT only
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
    STIBP: always-on; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB on VMEXIT
Graphics:
  Device-1: NVIDIA GB206 [GeForce RTX 5060 Ti] vendor: Micro-Star MSI
    driver: nvidia v: 580.119.02 alternate: nouveau,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-11) arch: Lovelace
    code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 1
    speed: 2.5 GT/s lanes: 4 link-max: gen: 5 speed: 32 GT/s lanes: 16 ports:
    active: HDMI-A-2 empty: DP-2,DP-3,DP-4 bus-ID: 04:00.0 chip-ID: 10de:2d04
    class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
    vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DP-1,Writeback-1 bus-ID: 0c:00.0
    chip-ID: 1002:13c0 class-ID: 0300 temp: 34.0 C
  Device-3: WaveRider USB Live camera driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:3
    chip-ID: 0c46:64ab class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: gnome-shell driver:
    gpu: amdgpu,nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: MPI7002 serial: <filter> built: 2007
    res: 1024x600 dpi: 144 size: 255x255mm (10.04x10.04") diag: 222mm (8.7")
    ratio: 4:3, 3:2 modes: max: 1024x600 min: 640x480
  Monitor-2: HDMI-A-2 model: LG (GoldStar) 24MB35 built: 2014 res: 1920x1080
    dpi: 96 gamma: 1.2 size: 510x290mm (20.08x11.42") diag: 587mm (23.1")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
    drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.119.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2
    memory: 15.56 GiB display-ID: :0.0
  Info: Tools: api: eglinfo,glxinfo gpu: nvidia-settings,nvidia-smi
    x11: xprop,xrandr
Audio:
  Device-1: NVIDIA GB206 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 4 link-max: gen: 5 speed: 32 GT/s
    lanes: 16 bus-ID: 04:00.1 chip-ID: 10de:22eb class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0c:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: C-Media Q9-1 driver: hid-generic,snd-usb-audio,usbhid type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 0d8c:0135
    class-ID: 0300
  Device-5: WaveRider USB Live camera driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:3
    chip-ID: 0c46:64ab class-ID: 0102 serial: <filter>
  API: ALSA v: k6.12.63-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: AzureWave driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 08:00.0 chip-ID: 14c3:0616 class-ID: 0280
  IF: wlp8s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:5 chip-ID: 13d3:3614
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 2.85 TiB used: 699.85 GiB (24.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Crucial model: CT1000P3PSSD8
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR40D temp: 29.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: MZVPW128HEGM-00000
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: CXZ7300Q temp: 32.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM003-1SB102
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC43 scheme: MBR
  ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM010-2EP102
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC43 scheme: MBR
Partition:
  ID-1: / raw-size: 256 GiB size: 250.92 GiB (98.02%) used: 90.01 GiB (35.9%)
    fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:7
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 31.3 MiB (32.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 3.99 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 39.0 C mobo: 30.0 C gpu: amdgpu temp: 33.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 14.77 GiB used: 3.43 GiB (23.2%)
  Processes: 407 Power: uptime: 6m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 5.87 GiB services: gsd-power,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Packages: 1700 pm: pacman pkgs: 1668 libs: 404
    tools: gnome-software,pamac,yay pm: flatpak pkgs: 32 Compilers: clang: 21.1.6
    gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: ghostty inxi: 3.3.40```

Journalctl

Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: RDSEED32 is broken. Disabling the corresponding CPUID bit.
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU1: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU2: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU3: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU4: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU5: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU6: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU7: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU8: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU9: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU10: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: microcode: No sha256 digest for patch ID: 0xb404035 found
Dez 21 11:44:03 mydesktoppc kernel: microcode: CPU11: update failed for patch_level=0x0b404035
Dez 21 11:44:03 mydesktoppc kernel: hid-generic 0003:0D8C:0135.0009: No inputs registered, leaving
Dez 21 11:44:04 mydesktoppc kernel: 
Dez 21 11:44:04 mydesktoppc kernel: usb 3-2: Failed to query (GET_INFO) UVC control 5 on unit 1: 0 (exp. 1).
Dez 21 11:44:04 mydesktoppc kernel: usb 3-2: Failed to query (GET_INFO) UVC control 7 on unit 1: 0 (exp. 1).
Dez 21 11:44:04 mydesktoppc kernel: usb 3-2: 3:1: cannot get freq at ep 0x84
Dez 21 11:44:13 mydesktoppc kernel: usb 3-2: 3:1: cannot get freq at ep 0x84
Dez 21 11:44:13 mydesktoppc kernel: usb 3-2: 3:1: cannot get freq at ep 0x84
Dez 21 11:44:30 mydesktoppc gdm-password][2304]: gkr-pam: unable to locate daemon control file

Edit: Spelling fixes, Clarification

2

There are issues with the Nvidia 580xx series drivers and apparently the 590xx series isn’t expected to be much better.

See the recent Stable Update Announcements:

The symptoms you describe may be related. It has been suggested to install the 570xx or 575xx series drivers for the time being.

I hope this helps.

Regards.

3

Thanks for the hint! Ought to have looked more carefully at update announcements. I’ll investigate the driver aspect, though (I reckon) it was updating to the 580 driver that enabled Manjaro to detect my GPU at all. :face_with_diagonal_mouth:

Edit: Clarification

5

Switched to 575xx. Crashes keep happening.

Maybe I should add that I’m also experiencing crashes on windows. However, those happen right after logging in, while the Manjaro-crashes are less predictable: Sometimes I’m watching videos, sometimes the PC has been idling for a few minutes, sometimes a more than 8h session goes by without crashes.

I have a secondary screen connected to the motherboard. The MB has an AMD igpu. I’ve tried turning off the secondary screen because I saw an error mentioning AMD graphics. Nothing changed.

Edit:
The Windows crashes also lead to an automatic system reboot, while the Linux crashes only result in a frozen image and looping audio and require a manual restart. I’ve read that another user was able to fix a similar problem by updating their BIOS. But I’m hesitant to try that, as it might brick my system for good.

6

It was new just a couple months ago, with new installation of Manjaro and Windows? All arrows are pointing to a hardware problem.

Do you have the memtest86+ grub entry? Try that. It can catch some problems related to bad memory or CPU cache. The latter is more common than you think. Often producing results like you mentioned.

metest86+ is pretty basic, good at testing memory, but there’s weird ways CPU cache can fail that this doesn’t catch.

But I would at least start there.

Given the state or your unstable computer I would not do this.

But his is a weird circumstance. Normally, do not be afraid to do this!

All the horror stories of a BIOS flash bricking a PC, are usually outdated or just plain wrong.

The process is much more simple than it used to be. (Often copying a single a file to a USB stick.)

It does a checksum, not to just make it’s not corrupt, but also to make sure you are putting the right one in (model-wise). So it’s near impossible to screw up there.

And it will not brick your system, even if you lose power.

Ignore what you heard, it is pretty darn safe. Nothing like 3+ decades ago. Some of these firmware updates are the only way to patch severe CPU flaws. So I would never not do it!

7

Yes, maybe you should have.

That nugget of knowledge just changed the context of the issue completely – as @Molski has rightly surmised, your problem now seems obviously hardware related – perhaps a faulty RAM module.

Try re-seating the modules, and the GPU (if discrete graphics).

Your UEFI/BIOS seems relatively recent, nonetheless, check the ASUS site in case there is updated (non-beta) firmware available.

1 Like
8

Thanks for the replies!

I’ve run memtest86+ now: 4 passes, no errors found.

Yeah, I realise now that was a stupid omission. Unfortunately, I may have made yet another one while we’re at it:

Very rarely when powering up the PC I wouldn’t even get to the BIOS (“Press F2 or DEL”) screen, let alone GRUB. Fans would keep roaring without an image on screen. That issue would resolve after multiple startup attempts, sometimes keeping the PC disconnected from power for a minute between attempts.

I hope this is useful in diagnosing the issue. Seemed very remote from the topic of Manjaro. Thank you all for being patient with me.

Newest firmware version available, as per the ASUS website, would be 3602.

9

While yours is currently 3057:

Most interesting is: – 2.Improves compatibility with various CPUs and devices – despite the typically generic description, updating to this version may prove beneficial.

10

That sounds like either a damaged motherboard — possibly bad capacitors — or a dying power supply.

1 Like
11

I assembled the PC in August 2025 and made sure all parts were compatible. If your suspicion is true, those parts you mentioned have failed rather quickly.

Regarding possible damage: During assembly I put in a wrong screw. The MB got bent a little in the process of fixing that. Could that lead to bad capacitors?

12

We’ve all been there, done that. The safest approach is to unscrew everything and re-seat the mainboard – needless to say, there are few of us who actually do that if we (think) there’s an easier way.

Bad capacitors, good soldered contacts gone bad – but, to answer your question – yes, absolutely.

It is, however, not something that’s very easily diagnosed from afar – or even up close, for that matter, unless there’s reason to suspect it – and you’ve just provided that reason.

For what it’s worth, at least the mainboard should be well within the warranty period, though, it might be best not to volunteer any mention of the rogue screw.

1 Like
13

It happens. I once had a computer that, within six weeks after having bought it, had a damaged hard disk drive, a dead power supply, a bad memory module, and the BIOS was seriously outdated and flawed.

I had another — and quite expensive! — dual-socket machine that never worked properly. I then got into a long battle with the company that had custom-built it for me, and after over three years, they supplied me with another, new machine. This one was however not the configuration I had ordered, and it also had a bad processor — it was also a dual-socket machine — and a bad memory module.

I’ve also had yet another machine whereby the HDD died within the month, and the speaker jack on the motherboard would sometimes lose the right speaker channel. This was from a different shop, and they replaced both parts under warranty in two days.

Not to bad capacitors, but to broken conductor paths, and then they could intermittently fail to make a connection, depending on the temperature inside the chassis, due to contraction and expansion of the motherboard material.

1 Like