New System is very unstable (faulty memory discovered)

Joarne · 5 January 2026 22:45

Good evening folks,

I recently build a new system, I have used Manjaro on my old one for years with only a few minor problems now and then, so I really didn’t expect the new one could be that unstable with lot of problems.

Hybernation isn’t working at all, after the first hibernation period the system is basically nuts. It reacts to input by waking up, but sometimes it immediately goes back so sleep. Sometimes I can log in, than it logs me out again, sometimes several times. I basically have to restart, to be able to use it again.
I could live without hibernation. But nearly everytime I use the system some applications just don’t start at all. Sometimes from the beginning, sometimes they work for 20 Min or 1 hour, than crash. Sometimes I can just restart them, sometimes they won’t restart. Be it Browser, Steam or even the protocol viewer that comes with the OS. After a restart they mostly do work again, but usually they crash again later on.

Every component is brand new, so hardware issues seems rather unlikely. The system is freshly installed. I could only install it with open graphic drivers, every attempt to use the proprietary ones results in a freeze while the live-system trys to boot. Installing the propietary drivers later on works, but the whole UI often freezes while using the proprietary drivers. Since the sound continues working in that cases, I assume it’s a problem with the graphic drivers.

I’m basically a little bit lost, because there are so many problems. The only thing I found so far are a few btrfs errors in the log:

22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 525, gen 0
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 525, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 524, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 523, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 522, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 521, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 520, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 519, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 518, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 517, gen 0
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 516, gen 0
22:43:19 kernel: btrfs_dev_stat_inc_and_print: 172 callbacks suppressed
22:43:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 32444416 csum 0x1031a2ee expected csum 0xe2542cd0 mirror 1
22:43:19 kernel: btrfs_print_data_csum_error: 172 callbacks suppressed
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 343, gen 0
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 343, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 28442624 csum 0x3a839dfc expected csum 0x4f4099c6 mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 342, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 28377088 csum 0x8df0e1aa expected csum 0x246c9961 mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 341, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 28311552 csum 0x058268ba expected csum 0xf048d3dc mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 340, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 28246016 csum 0xeb994f8f expected csum 0xf45bd499 mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 339, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 28131328 csum 0x4cfac7b1 expected csum 0xa8341472 mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 338, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 28000256 csum 0x753737ff expected csum 0xb6a94553 mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 337, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 27934720 csum 0xc7d9480f expected csum 0x834ab2ed mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 336, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 27869184 csum 0xb3531cc7 expected csum 0x40f21c77 mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 335, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 27803648 csum 0x32460767 expected csum 0xcc0c9d78 mirror 1
22:42:19 kernel: BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 334, gen 0
22:42:19 kernel: BTRFS warning (device nvme0n1p2): csum failed root 256 ino 289124 off 27738112 csum 0x313b108b expected csum 0xb386547e mirror 1
22:34:22 kernel: BTRFS info (device nvme0n1p2 state M): use zstd compression, level 1
22:34:22 kernel: BTRFS info (device nvme0n1p2): enabling free space tree
22:34:22 kernel: BTRFS info (device nvme0n1p2): turning on async discard
22:34:22 kernel: BTRFS info (device nvme0n1p2): enabling ssd optimizations
22:34:22 kernel: BTRFS info (device nvme0n1p2): checking UUID tree
22:34:22 kernel: BTRFS info (device nvme0n1p2): start tree-log replay
22:34:22 kernel: BTRFS info (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 333, gen 0
22:34:22 kernel: BTRFS info (device nvme0n1p2): using crc32c (crc32c-lib) checksum algorithm
22:34:22 kernel: BTRFS info (device nvme0n1p2): first mount of filesystem 68dd2443-d32a-431c-80ee-193884bc1a3f
22:34:22 kernel: BTRFS: device fsid 68dd2443-d32a-431c-80ee-193884bc1a3f devid 1 transid 545 /dev/nvme0n1p2 (259:2) scanned by mount (313)
22:34:22 kernel: Btrfs loaded, zoned=yes, fsverity=yes

I already tried using the LTS-Kernel 6.12.63-1 instead of 6.18.3-2, the problems remained.
At first I used the 25.1 Manjaro Release and switched to the 26 Release, the problems remained.

I’m thinking about reinstalling the system again with ext4 to see, if that improves the stability. But with btrfs as the recommended filesystem I wonder why using it would cause that much trouble.

I happily provide more info, right now I’m just a bit clueless where to start

System specs:

System:
  Kernel: 6.18.3-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
    root=UUID=68dd2443-d32a-431c-80ee-193884bc1a3f rw rootflags=subvol=@
    quiet splash resume=UUID=8a31998a-cc31-4d57-b1f4-457959766495
    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 Mobo: Gigabyte model: B850 AORUS ELITE WIFI7 v: x.x
    serial: <superuser required> uuid: <superuser required> Firmware: UEFI
    vendor: American Megatrends LLC. v: F6 date: 07/16/2025
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 30.46 GiB used: 3.13 GiB (10.3%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: no module installed
  Device-2: Channel-A DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 6400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: TeamGroup
    part-no: UD5-6400 serial: <filter>
  Device-3: Channel-B DIMM 0 type: no module installed
  Device-4: Channel-B DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 6400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: TeamGroup
    part-no: UD5-6400 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 9800X3D bits: 64 type: 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: 0xB404035
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 smt: <unsupported> cache:
    L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
    L3: 96 MiB desc: 1x96 MiB
  Speed (MHz): avg: 603 min/max: 603/5272 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 603 2: 603 3: 603
    4: 603 5: 603 6: 603 7: 603 8: 603 bogomips: 75054
  Flags: 3dnowprefetch abm adx aes amd_lbr_pmc_freeze amd_lbr_v2 aperfmperf
    apic arat avic avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2
    avx512_vnni avx512_vp2intersect avx512_vpopcntdq avx512bw avx512cd
    avx512dq avx512f avx512ifma avx512vbmi avx512vl avx_vnni bmi1 bmi2 bpext
    bus_lock_detect cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov
    cmp_legacy constant_tsc cpb cppc cpuid cpuid_fault cqm cqm_llc
    cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de
    decodeassists erms extapic extd_apicid f16c flush_l1d flushbyasid fma fpu
    fsgsbase fsrm fxsr fxsr_opt gfni ht hw_pstate ibpb ibrs ibrs_enhanced ibs
    invpcid irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor
    movbe movdir64b movdiri msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx
    ospke osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb
    perfctr_core perfctr_llc perfctr_nb perfmon_v2 pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm svm_lock syscall tce topoext tsc tsc_adjust tsc_scale
    umip user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme
    vmmcall vnmi vpclmulqdq wbnoinvd wdt x2avic xgetbv1 xsave xsavec
    xsaveerptr xsaveopt xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite 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: old_microcode 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: disabled; 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 GB203 [GeForce RTX 5080] vendor: ASUSTeK driver: nouveau
    v: kernel alternate: nova_core non-free: 550-580.xx+
    status: current (as of 2025-11) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 5 speed: 32 GT/s lanes: 16
    ports: active: DP-6,HDMI-A-2 empty: DP-4,DP-5 bus-ID: 01:00.0
    chip-ID: 10de:2c02 class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
    vendor: Gigabyte 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: none empty: DP-1, DP-2, DP-3, HDMI-A-1,
    Writeback-1 bus-ID: 10:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 35.0 C
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: gnome-shell driver: gpu: nouveau display-ID: 0
  Monitor-1: DP-6 model: LG (GoldStar) ULTRAGEAR serial: <filter>
    built: 2023 res: 2560x1440 dpi: 109 gamma: 1.2 chroma: red: x: 0.686
    y: 0.310 green: x: 0.263 y: 0.671 blue: x: 0.149 y: 0.055 white: x: 0.314
    y: 0.329 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 2560x1440, 1920x1080, 1280x720, 1024x768, 800x600, 720x480,
    640x480
  Monitor-2: HDMI-A-2 model: LG (GoldStar) ULTRAGEAR serial: <filter>
    built: 2023 res: 2560x1440 dpi: 109 gamma: 1.2 chroma: red: x: 0.686
    y: 0.310 green: x: 0.263 y: 0.671 blue: x: 0.149 y: 0.055 white: x: 0.314
    y: 0.329 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 2560x1440, 3840x2160, 1920x1080, 1280x720, 1024x768, 800x600,
    720x576, 720x480, 640x480
  EDID-Warnings: 1: parse_edid: unhandled CEA mode 93 2: parse_edid:
    unhandled CEA mode 94 3: parse_edid: unhandled CEA mode 95 4: parse_edid:
    unhandled CEA mode 96 5: parse_edid: unhandled CEA mode 97
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: zink
    device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: zink surfaceless:
    drv: zink wayland: drv: zink x11: drv: zink
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.3.2-arch1.1 glx-v: 1.4
    direct-render: yes renderer: zink Vulkan 1.4(NVIDIA GeForce RTX 5080 (NVK
    GB203) (MESA_NVK)) device-ID: 10de:2c02 memory: 15.55 GiB unified: no
    display-ID: :0.0
  Info: Tools: api: eglinfo,glxinfo x11: xprop,xrandr
Audio:
  Device-1: NVIDIA GB203 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: gen: 5 speed: 32 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22e9
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 10:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 10:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: Shokz Loop120 by driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-1.2.2.1:8
    chip-ID: 3511:2ef2 class-ID: 0102 serial: <filter>
  API: ALSA v: k6.18.3-2-MANJARO status: kernel-api tools: N/A
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8922AE 802.11be PCIe Wireless Network Adapter
    driver: rtw89_8922ae v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    port: d000 bus-ID: 07:00.0 chip-ID: 10ec:8922 class-ID: 0280
  IF: wlp7s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: c000 bus-ID: 08:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:6 chip-ID: 0bda:8922
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 955.74 GiB used: 132.18 GiB (13.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lexar model: SSD NM790 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 18950 temp: 42.9 C scheme: GPT
  ID-2: /dev/sdc maj-min: 8:32 vendor: Transcend model: JetFlash 2G
    size: 1.88 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
    spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 8.07
    scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 920.07 GiB size: 920.07 GiB (100.00%)
    used: 132.18 GiB (14.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 68dd2443-d32a-431c-80ee-193884bc1a3f
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 664 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 57D7-5569
  ID-3: /home raw-size: 920.07 GiB size: 920.07 GiB (100.00%)
    used: 132.18 GiB (14.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 68dd2443-d32a-431c-80ee-193884bc1a3f
  ID-4: /run/media/thorsten/STICK 2 GB raw-size: 1.87 GiB
    size: 1.87 GiB (99.79%) used: 44 KiB (0.0%) fs: vfat dev: /dev/sdc1
    maj-min: 8:33 label: STICK 2 GB uuid: 8C03-66C5
  ID-5: /var/cache raw-size: 920.07 GiB size: 920.07 GiB (100.00%)
    used: 132.18 GiB (14.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 68dd2443-d32a-431c-80ee-193884bc1a3f
  ID-6: /var/log raw-size: 920.07 GiB size: 920.07 GiB (100.00%)
    used: 132.18 GiB (14.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 68dd2443-d32a-431c-80ee-193884bc1a3f
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 33.51 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3 label: swap
    uuid: 8a31998a-cc31-4d57-b1f4-457959766495
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-3:2 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 1-3.1:4 info: Transcend Information JetFlash type: mass storage
    driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 200mA chip-ID: 8564:1000 class-ID: 0806
    serial: <filter>
  Device-2: 1-5:3 info: Yubicom Yubikey 4/5 OTP+U2F+CCID
    type: keyboard,HID,smart card driver: hid-generic,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 30mA
    chip-ID: 1050:0407 class-ID: 0b00
  Device-3: 1-6:5 info: Integrated Express GIGABYTE Device type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 048d:5711 class-ID: 0300
  Device-4: 1-9:6 info: Realtek Bluetooth Radio type: bluetooth
    driver: btusb interfaces: 2 rev: 1.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 500mA chip-ID: 0bda:8922 class-ID: e001 serial: <filter>
  Hub-3: 2-0:1 info: super-speed hub ports: 5 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 2-3:2 info: Realtek Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-6: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-8: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 7-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-10: 7-1:2 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 7-1.1:3 info: HP Officejet 6500 E710n-z
    type: printer,mass storage driver: usb-storage,usblp interfaces: 5 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 2mA
    chip-ID: 03f0:5412 class-ID: 0701 serial: <filter>
  Hub-11: 7-1.2:4 info: Terminus Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 1a40:0101 class-ID: 0900
  Device-1: 7-1.2.1:5 info: Evoluent VerticalMouse 4 type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 1a7c:0191 class-ID: 0301
  Hub-12: 7-1.2.2:6 info: Cambridge Silicon Radio Mpow HC5 Headset in
    charging mode - USB Hub ports: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 0a12:4010 class-ID: 0900
  Device-1: 7-1.2.2.1:8 info: Shokz Loop120 by type: HID,audio
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 5 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 3511:2ef2
    class-ID: 0102 serial: <filter>
  Hub-13: 7-1.2.3:7 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Hub-14: 7-1.2.3.2:9 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 7-1.2.3.2.3:11 info: Philips Speech Processing USB Keyboard
    type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 0911:2188 class-ID: 0301 serial: <filter>
  Device-2: 7-1.2.3.3:10 info: Philips Speech Processing
    type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 0911:2188 class-ID: 0301
Sensors:
  System Temperatures: cpu: 41.9 C mobo: 25.0 C gpu: amdgpu temp: 36.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1134 libs: 339 tools: gnome-software,pamac
    pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.23m.com/manjaro/stable/$repo/$arch
    2: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    3: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    4: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    5: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    6: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    7: https://manjaro.kurdy.org/stable/$repo/$arch
    8: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    9: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 333
  1: cpu: 7.5% command: kgx pid: 7170 mem: 228.6 MiB (0.7%)
  2: cpu: 4.0% command: firefox pid: 4598 mem: 395.7 MiB (1.2%)
  3: cpu: 3.4% command: firefox pid: 4103 mem: 555.9 MiB (1.7%)
  4: cpu: 3.0% command: gnome-shell pid: 2236 mem: 316.3 MiB (1.0%)
  5: cpu: 2.8% command: ./firefox.real pid: 6559 mem: 449.9 MiB (1.4%)
  Memory top: 5 of 333
  1: mem: 555.9 MiB (1.7%) command: firefox pid: 4103 cpu: 3.4%
  2: mem: 449.9 MiB (1.4%) command: ./firefox.real pid: 6559 cpu: 2.8%
  3: mem: 395.7 MiB (1.2%) command: firefox pid: 4598 cpu: 4.0%
  4: mem: 340.3 MiB (1.0%) command: nautilus pid: 5899 cpu: 1.2%
  5: mem: 325.6 MiB (1.0%) command: firefox pid: 4496 cpu: 0.2%
Info:
  Processes: 333 Power: uptime: 41m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.12 GiB services: gsd-power,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: kgx inxi: 3.3.40

tracyanne · 5 January 2026 22:51

Please use a the </> button to encapsulate the the CLI output text.

Joarne · 5 January 2026 22:53

Damn you’re fast ^^
Was already working on it, just took me a few trys to understand how it works, sry for that.

tracyanne · 5 January 2026 22:56

Just doing my morning Moderation duties.

Welcome to the Forum.

Joarne · 5 January 2026 22:59

Thank you for helping this forum to help people like me then

Teo · 6 January 2026 01:32

“a few filesystem errors” can lead to serious issues. Check the filesystem, repair. Reinstall if needed. Check the disk with smartctl for it’s status and internal logs and wear.

Molski · 6 January 2026 03:01

btrfs can catch hardware errors. Sometimes checksum errors can be bad CPU cache (or memory if you’re lucky), which falls on line with this instability too.

Where you see errors in the logs, it is saying something went wrong. It’s a great feature of the file system. ext4 may hum along, then catastrophically fail without any notice. And with btrfs, If you had another device in there, it would repair itself automatically.

But you are on the right track by narrowing things down. And probably easiest to troubleshoot, figuring out if this is a software or hardware issue first. It is a little harder, as it was never setup properly first.

So I’m not sure where to start. Probably with memory tests (which tests cache as well). But you may need a better one than the one that comes with grub.

linux-aarhus · 6 January 2026 05:36

I am sorry to hear that - I am sure you will get it solved.

Comparing issues with a new system to the old faithful is kind’a moot - like apples and bananas - the only thing in common is eatable if you understand what I mean

The new hardware you bought - especially the nvme

may be causing your issue. The btrfs errors in the log point to possible issues with your disk. Try replacing the nvme.

Your old installation is likely running ext4, while the new installation - the filesystem default to btrfs.

Your system is a desktop system and the Linux 6.18 kernel or even Linux 6.19 may have improved support for

And Nvidia GPU

I suggest you use the latest ISO and the the open 590xx driver.

Run below script to see which driver is suggested for your system

nvidia-driver-assistant

Joarne · 6 January 2026 07:02

Alright, I checked with smartctl:

smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.18.3-2-MANJARO] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Lexar SSD NM790 1TB
Serial Number:                      QHU172R000773P220J
Firmware Version:                   18950
PCI Vendor/Subsystem ID:            0x1d97
IEEE OUI Identifier:                0xcaf25b
Total NVM Capacity:                 1.024.209.543.168 [1,02 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1.024.209.543.168 [1,02 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            caf25b 0320000129
Local Time is:                      Tue Jan  6 07:50:03 2026 CET
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     90 Celsius
Critical Comp. Temp. Threshold:     95 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.50W       -        -    0  0  0  0        0       0
 1 +     5.80W       -        -    1  1  1  1        0       0
 2 +     3.60W       -        -    2  2  2  2        0       0
 3 -   0.0500W       -        -    3  3  3  3     5000   10000
 4 -   0.0025W       -        -    4  4  4  4     8000   45000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        34 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    118.800 [60,8 GB]
Data Units Written:                 795.870 [407 GB]
Host Read Commands:                 975.370
Host Write Commands:                4.674.074
Controller Busy Time:               1
Power Cycles:                       33
Power On Hours:                     22
Unsafe Shutdowns:                   15
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               34 Celsius
Temperature Sensor 2:               27 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
Num  Test_Description  Status                       Power_on_Hours  Failing_LBA  NSID Seg SCT Code
 0   Short             Completed without error                  22            -     -   -   -    -
 1   Short             Completed without error                  22            -

Looks fine by me.

Question for the btrfs check. It looks like I need to do that via Live-USB Stick, since the filesystem should be unmounted. Tried to use the –force option, but it didn’t work:

sudo btrfs check --force /dev/nvme0                     1 ✘  7s  
Opening filesystem to check...
ERROR: not a regular file or block device: /dev/nvme0
ERROR: cannot open file system

Am I right or is there another way to check the filesystem?

I checked for the suggested gpu-driver:

sudo pacman -S linux618-nvidia-open                          INT ✘ 
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …

Pakete (5) egl-gbm-1.1.2.1-1  egl-wayland2-1.0.0.rc.r53.gf4a2d32-1
           egl-x11-1.0.4-1  nvidia-utils-590.48.01-2
           linux618-nvidia-open-590.48.01-4

Gesamtgröße des Downloads:             356,86 MiB
Gesamtgröße der installierten Pakete:  866,26 MiB

:: Installation fortsetzen? [J/n] j
:: Pakete werden empfangen …
 egl-wayland2-1.0...    37,7 KiB   414 KiB/s 00:00 [######################] 100%
 linux618-nvidia-...    12,1 MiB  5,65 MiB/s 00:02 [######################] 100%
 nvidia-utils-590...   344,7 MiB  10,5 MiB/s 00:33 [######################] 100%
 Gesamt (3/3)          356,9 MiB  10,8 MiB/s 00:33 [######################] 100%
(5/5) Schlüssel im Schlüsselbund werden geprüft    [######################] 100%
(5/5) Paket-Integrität wird überprüft              [######################] 100%
(5/5) Paket-Dateien werden geladen                 [######################] 100%
(5/5) Auf Dateikonflikte wird geprüft              [######################] 100%
(5/5) Verfügbarer Festplattenspeicher wird erm...  [######################] 100%
:: Paketänderungen werden verarbeitet …
(1/5) Installiert wird egl-wayland2                [######################] 100%
(2/5) Installiert wird egl-gbm                     [######################] 100%
(3/5) Installiert wird egl-x11                     [######################] 100%
(4/5) Installiert wird nvidia-utils                [######################] 100%
Created symlink '/etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'.
Created symlink '/etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'.
Created symlink '/etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'.
Created symlink '/etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service' → '/usr/lib/systemd/system/nvidia-hibernate.service'.
Created symlink '/etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service' → '/usr/lib/systemd/system/nvidia-suspend.service'.
Created symlink '/etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-suspend-then-hibernate.service' → '/usr/lib/systemd/system/nvidia-suspend-then-hibernate.service'.
Optionale Abhängigkeiten für nvidia-utils
    nvidia-settings: configuration tool
    xorg-server: Xorg support [Installiert]
    xorg-server-devel: nvidia-xconfig
    opencl-nvidia=590.48.01: OpenCL support
(5/5) Installiert wird linux618-nvidia-open        [######################] 100%
:: Post-transaction-Hooks werden gestartet …
(1/8) Creating system user accounts...
(2/8) Reloading system manager configuration...
(3/8) Reloading device manager configuration...
(4/8) Arming ConditionNeedsUpdate...
(5/8) Updating module dependencies...
(6/8) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
==> Starting build: '6.12.63-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [kms]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Running post hooks
  -> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
==> Post processing done
==> Building image from preset: /etc/mkinitcpio.d/linux618.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.18-x86_64 -g /boot/initramfs-6.18-x86_64.img
==> Starting build: '6.18.3-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [kms]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.18-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Running post hooks
  -> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
==> Post processing done
(7/8) Reloading system bus configuration...
(8/8) Signing EFI binaries...
Generating EFI bundles....

Is there a reason why the open version is suggested? I was under the impression that nvidia gpus works better with the proprietary drivers.

Teo · 6 January 2026 07:29

Proprietary nvidia works better, when it works. With the free at least a boot is guaranteed, so for troubleshooting is good.
The disk looks new as expected.
You are doing the fsck wrong however. First, i hope this is on live usb and unmounted. Not sure about the force flag, try with and without. But the device name is wrong. Check it with lsblk. It is probably nvme0n1. I forget the n1 all the time too.

Aragorn · 6 January 2026 07:45

Joarne:

sudo btrfs check --force /dev/nvme0                     1 ✘  7s  
Opening filesystem to check...
ERROR: not a regular file or block device: /dev/nvme0
ERROR: cannot open file system

Am I right or is there another way to check the filesystem?

/dev/nvme0 is not a filesystem — it’s your SSD itself.

andreas85 · 6 January 2026 08:54

There is scrub (which tests checksums on all data-blocks)

linux-aarhus · 6 January 2026 10:45

The script is a modified version of the original Nvidia script (original didn’t have support for Manjaro) and the only changes are Manjaro specific - such as kernel and module naming.

So the suggestion of the nvidia-open is because it is the driver recommended by Nvidia for your card.

Joarne · 6 January 2026 12:33

Oh, of course. Thanks ^

Joarne · 6 January 2026 12:34

Ok, that’s cool. I thought Nvidia doesn’t really like the idea of open drivers.
Thanks for the explanation.

Joarne · 6 January 2026 12:45

In the last view hours I did some RAM testing and I would say one of my two new RAM-Sticks seems to be garbage:
For some reason the screenshot isn’t uploaded correctly. In short, the test showed over 4 Mio errors for the faulty stick.

We’ll see, if the system runs stable now with only one of the sticks, which hadn’t any errors while testing.

Thanks everyone so far for helping me troubleshoot. I really didn’t expect it would turn out to be a problem with the newly bought hardware.

soundofthunder · 6 January 2026 12:50

In some cases, simply re-seating the module can prove beneficial.

Joarne · 6 January 2026 12:51

Hm….still problems with crashing applications and still btrfs-errors in the log.
Maybe I should reinstall the system without the faulty RAM-stick involved.

Nachlese · 6 January 2026 12:54

It’ll probably work or be repairable without that faulty RAM present.
But to be sure, that is a good idea - then you can be sure that no data is compromised.

If you know some RAM is faulty - get rid of it.

Joarne · 6 January 2026 12:56

I tested every stick separately and the faulty one was tested in another slot than the one it was installed when I did the first test with both sticks installed.
And judging by the manual of the MB there is no other combination with one or two sticks, than the ones I tested.

So I assume the stick really is the problem.