Random crashes during startup and shutdown

I migrated from Mint to Manjaro about two months ago, and, admittedly, this issue was already present in Mint. I tried to get help on its forum, but it was of no use. Eventually I just got used to the issue, but now, after switching OSs, I want to fix it.

For about a third of the times I boot or try to shutdown my computer, it crashes. The boot crashes usually happen between when the cursor appears on screen and right after I log in, and the shutdown crashes happen right after I click shutdown.

In those crashes, the screen freezes and no commands work. I can’t open a TTY, I can’t shutdown my computer through a key combination, literally nothing works. The only solution is to press down the power button.

One of the suggestions that appeared on the Mint post I wrote was to switch kernels. I did back then, and it appeared to have solved the issue. But it didn’t. No matter what kernel I use, if I stick to it long enough, those crashes start happening.

After the two most recent crashes and searching a bit for answers in this forum, I decided to inspect the output of journalctl.

This is the output (the last part of which, at least – I don’t know how much of it I should post here) of journaltcl -b -1 on the boot following a crash during startup:

ago 15 11:43:07 kvothe kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-15
ago 15 11:43:07 kvothe kernel: Linux version 5.19.1-2-MANJARO (builduser@fv-az397-245) (gcc (GCC) 12.1.1 20220730, GNU ld (GNU Binutils) 2.39) #1>
ago 15 11:43:07 kvothe kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19-x86_64 root=UUID=01070a50-d90a-4393-b111-113423c883d8 rw quiet resume=>
ago 15 11:43:07 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
ago 15 11:43:07 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
ago 15 11:43:07 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
ago 15 11:43:07 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
ago 15 11:43:07 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
ago 15 11:43:07 kvothe kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
ago 15 11:43:07 kvothe kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
ago 15 11:43:07 kvothe kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
ago 15 11:43:07 kvothe kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
ago 15 11:43:07 kvothe kernel: signal: max sigframe size: 2032
ago 15 11:43:07 kvothe kernel: BIOS-provided physical RAM map:
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x0000000040400000-0x000000006c5b2fff] usable
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x000000006c5b3000-0x000000006c5b3fff] ACPI NVS
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x000000006c5b4000-0x000000006c5b4fff] reserved
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x000000006c5b5000-0x000000007732dfff] usable
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x000000007732e000-0x0000000077939fff] reserved
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x000000007793a000-0x00000000779b6fff] ACPI data
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x00000000779b7000-0x0000000077abdfff] ACPI NVS
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x0000000077abe000-0x000000007912ffff] reserved
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x0000000079130000-0x00000000791fdfff] type 20
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x00000000791fe000-0x00000000791fefff] usable
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x00000000791ff000-0x000000007f7fffff] reserved
ago 15 11:43:07 kvothe kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
...skipping...
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension BIG-REQUESTS
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension SYNC
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XKEYBOARD
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XC-MISC
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension SECURITY
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XFIXES
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension RENDER
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension RANDR
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension COMPOSITE
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension DAMAGE
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension MIT-SCREEN-SAVER
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension DOUBLE-BUFFER
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension RECORD
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension DPMS
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension Present
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension DRI3
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension X-Resource
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XVideo
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XVideo-MotionCompensation
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension GLX
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension GLX
ago 15 11:43:14 kvothe /usr/lib/gdm-x-session[870]: (II) Indirect GLX disabled.
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) AIGLX: Loaded and initialized iris
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) GLX: Initialized DRI2 GL provider for screen 0
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XFree86-VidModeExtension
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XFree86-DGA
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension XFree86-DRI
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension DRI2
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension NV-GLX
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) Initializing extension NV-CONTROL
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) modeset(0): Damage tracking initialized
ago 15 11:43:15 kvothe /usr/lib/gdm-x-session[870]: (II) modeset(0): Setting screen physical size to 508 x 285

This is the output of journaltcl -b -1 on a boot following a crash during shutdown:

ago 13 18:36:15 kvothe kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-15
ago 13 18:36:15 kvothe kernel: Linux version 5.19.1-2-MANJARO (builduser@fv-az397-245) (gcc (GCC) 12.1.1 20220730, GNU ld (GNU Binutils) 2.39) #1>
ago 13 18:36:15 kvothe kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.19-x86_64 root=UUID=01070a50-d90a-4393-b111-113423c883d8 rw quiet resume=>
ago 13 18:36:15 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
ago 13 18:36:15 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
ago 13 18:36:15 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
ago 13 18:36:15 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
ago 13 18:36:15 kvothe kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
ago 13 18:36:15 kvothe kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
ago 13 18:36:15 kvothe kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
ago 13 18:36:15 kvothe kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
ago 13 18:36:15 kvothe kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
ago 13 18:36:15 kvothe kernel: signal: max sigframe size: 2032
ago 13 18:36:15 kvothe kernel: BIOS-provided physical RAM map:
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x0000000040400000-0x000000006c5b2fff] usable
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x000000006c5b3000-0x000000006c5b3fff] ACPI NVS
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x000000006c5b4000-0x000000006c5b4fff] reserved
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x000000006c5b5000-0x000000007732dfff] usable
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x000000007732e000-0x0000000077939fff] reserved
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x000000007793a000-0x00000000779b6fff] ACPI data
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x00000000779b7000-0x0000000077abdfff] ACPI NVS
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x0000000077abe000-0x000000007912ffff] reserved
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x0000000079130000-0x00000000791fdfff] type 20
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x00000000791fe000-0x00000000791fefff] usable
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x00000000791ff000-0x000000007f7fffff] reserved
ago 13 18:36:15 kvothe kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
...skipping...
ago 13 20:11:34 kvothe kernel: audit: type=1131 audit(1660432294.107:111): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed>
ago 13 20:11:34 kvothe audit: BPF prog-id=0 op=UNLOAD
ago 13 20:11:34 kvothe audit: BPF prog-id=0 op=UNLOAD
ago 13 20:11:34 kvothe audit: BPF prog-id=0 op=UNLOAD
ago 13 20:11:34 kvothe kernel: audit: type=1334 audit(1660432294.201:112): prog-id=0 op=UNLOAD
ago 13 20:11:34 kvothe kernel: audit: type=1334 audit(1660432294.201:113): prog-id=0 op=UNLOAD
ago 13 20:11:34 kvothe kernel: audit: type=1334 audit(1660432294.201:114): prog-id=0 op=UNLOAD
ago 13 20:11:43 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:11:43 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:12:15 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:12:19 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:12:20 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:12:34 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:12:41 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:12:49 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:13:18 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:13:24 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:13:37 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:14:02 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:14:14 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:14:22 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:14:38 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:14:55 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:14:57 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:15:07 kvothe systemd[1382]: app-gnome-chromium-3378.scope: Consumed 1min 8.579s CPU time.
ago 13 20:15:17 kvothe gnome-shell[1480]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 3
ago 13 20:15:17 kvothe wpa_supplicant[974]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
ago 13 20:15:19 kvothe gnome-session-binary[1465]: Entering running state
ago 13 20:15:19 kvothe gnome-shell[1480]: Ignored exception from dbus method: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_>
ago 13 20:15:21 kvothe org.gnome.Nautilus[2007]: warning: ... repeated 20 times...
ago 13 20:15:26 kvothe gnome-shell[1480]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 3
ago 13 20:15:28 kvothe systemd-logind[702]: System is powering down.

Output of

export LANG=C; inxi --admin --verbosity=7 --filter --width

below:

System:
  Kernel: 5.19.1-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.19-x86_64
    root=UUID=01070a50-d90a-4393-b111-113423c883d8 rw quiet
    resume=UUID=fa2e3f4c-90a0-436e-9ce4-8ebd9d6f88e8 udev.log_priority=3
  Desktop: GNOME v: 42.4 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 42.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: Dell product: G3 3590 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0GDFK2 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.11.1 date: 08/19/2020
Battery:
  ID-1: BAT0 charge: 30.7 Wh (79.1%) condition: 38.8/51.0 Wh (76.1%)
    volts: 11.3 min: 11.4 model: LGC-LGC4.474 DELL 415CG99 type: Li-ion
    serial: <filter> status: discharging
Memory:
  RAM: total: 7.6 GiB used: 2.31 GiB (30.4%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
    required.
CPU:
  Info: model: Intel Core i5-9300H bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 9 built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158)
    stepping: 0xA (10) microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 2212 high: 2400 min/max: 800/4100 scaling:
    driver: intel_pstate governor: powersave cores: 1: 2400 2: 2400 3: 900
    4: 2400 5: 2400 6: 2400 7: 2400 8: 2400 bogomips: 38408
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor
    movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp
    rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
    syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi
    vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:3e9b class-ID: 0300
  Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Dell
    driver: nvidia v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-07) arch: Turing code: TUxxx
    process: TSMC 12nm built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f91 class-ID: 0300
  Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-5:2 chip-ID: 0c45:671f class-ID: 0e02
  Display: x11 server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa gpu: i915 display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-size: <missing: xdpyinfo>
  Monitor-1: eDP-1 model: LG Display 0x05c4 built: 2018 res: 1920x1080
    hz: 60 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    ratio: 16:9 modes: 1920x1080
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 22.1.6
    direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell
    driver: sof-audio-pci-intel-cnl
    alternate: snd_hda_intel,snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0401
  Device-2: NVIDIA vendor: Dell driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:10fa class-ID: 0403
  Sound Server-1: ALSA v: k5.19.1-2-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.56 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Dell driver: r8169 v: kernel pcie: speed: Unknown lanes: 63
    link-max: gen: 6 speed: 64 GT/s port: 3000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    vendor: Dell driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 bus-ID: 04:00.0 chip-ID: 168c:0042 class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-14:3
    chip-ID: 0cf3:e009 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.03 TiB used: 121.36 GiB (11.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN520
    NVMe WDC 128GB size: 119.24 GiB block-size: physical: 512 B logical: 512 B
    speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter> rev: 20240012
    temp: 44.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD10SPZX-75Z10T2 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A03 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 114.74 GiB size: 112.38 GiB (97.94%) used: 23.74 GiB
    (21.1%) fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3 label: N/A
    uuid: 01070a50-d90a-4393-b111-113423c883d8
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 312 KiB
    (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: NO_LABEL
    uuid: 571C-DE0F
  ID-3: /home raw-size: 931.51 GiB size: 915.81 GiB (98.31%) used: 97.63 GiB
    (10.7%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: ade67289-8f81-47fd-9baf-d44c05aeacf8
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: fa2e3f4c-90a0-436e-9ce4-8ebd9d6f88e8
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-5:2 info: Microdia Integrated_Webcam_HD type: Video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 0c45:671f class-ID: 0e02
  Device-2: 1-14:3 info: Qualcomm Atheros type: Bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 0cf3:e009
    class-ID: e001
  Hub-2: 2-0:1 info: Super-speed hub ports: 8 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 37.0 C pch: 37.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 242 Uptime: 14m wakeups: 2588 Init: systemd v: 251
  default: graphical tool: systemctl Compilers: gcc: 12.1.1 clang: 14.0.6
  Packages: pacman: 910 lib: 272 Shell: Zsh v: 5.9 running-in: gnome-terminal
  inxi: 3.3.20

Welcome to the forum!

I see nothing in that output that would hint at a software problem, and given that you’ve also had the same problem earlier in Mint, I suspect an intermittent hardware failure.

It doesn’t appear to be heat-related — the temperature reported by inxi looks very healthy — so my first guess would be an intermittent failure in a memory module. This is actually a far more common phenomenon than what one might suspect, courtesy of the increase in mass production without a matching increase in quality control.

What you could do is run memtest86 and let it run non-stop for 24 hours in order to check for things like parity errors, but the problem here is that memtest86 needs to boot the machine in BIOS emulation mode, because it cannot handle a native UEFI boot. And in addition to that, even if memtest86 doesn’t find any errors, that still doesn’t mean there aren’t any. Sometimes it’s just a small random fluctuation that triggers the crash.

Other factors that may contribute to the probability of a crash are the reliability of the power supply — but given that your system is a laptop and that it therefore directly sources its current from the battery instead of from the PSU, I doubt that it would be the case here — and the GPU(s). I’ve had a machine a few years ago — granted, it was a refurbished box — with a failing power supply and an equally failing onboard GPU, and it was extremely unstable. It would crash multiple times in a row and literally every day, for no apparent reason.

Either way, the bottom line is that it’s most likely a hardware failure, and then no kernel switching or whatever other software-based measures will do you any good. :man_shrugging:

Gentle shut down a suddenly hanged PC to minimize a chance of getting a broken filesystem and data loss:

1 Like

@Aragorn Thank you for your thorough reply!

I was so sure it was a software issue that I didn’t even mention it, but prior to Mint I ran Windows for a year and a half and never had any problems of that nature with it.

I could do that, but will take me sometime, for I have to get a USB. And I’m not sure my PC supports BIOS.

Given that I had no problem with Windows for quite a while, do you still think it probably is hardware related? I hope not, because my insurance expired six months ago :cry:

Microsoft Windows does not check the individual hardware components until they are actually being accessed. The Linux kernel on the other hand checks all hardware for proper functionality at boot time and will keep an in-memory index of hardware components that fail, provided that the system itself doesn’t crash, of course.

All x86 UEFI implementations (except on Intel-based Macs) do still support legacy BIOS emulation.

Yes, I’m afraid so.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.