Laptop crashes completely, can't figure out why

EuroNutellaMan · 2025-02-03 22:08:56

Hi everyone,

I'm having issues with my laptop but I can't pinpoint if it's the hardware or the software that's causing issues.
Basically it crashes randomly, and by that I mean everything completely freezes, computer becomes unresponsive (I have to push the power button for a few seconds to shut it off and then turn it on again), if audio is playing it start lagging and cutting off before total silence. It also has a tendency to get pretty hot, with CPU temps reaching upwards of 80°C sometimes according to btop, other times it crashes on idle while RAM, CPU and disk usage are practically at 0 and temps are average (40~50 °C).
It's been going on for months, following multiple updates (I usually update twice a week).

The laptop is a Lenovo A285, here's a quick fastfetch:

OS: Arch Linux x86_64
Host: 20MXS0HG0Y (ThinkPad A285)
Kernel: Linux 6.12.10-arch1-1
Packages: 1383 (pacman)
Shell: zsh 5.9
Resolution: 1920x1080
DE: KDE Plasma 6.2.5
WM: KWin (Wayland)
WM Theme: CatppuccinMocha-Modern
Theme: Breeze (CatppuccinMochaYellow) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
Icons: Papirus-Dark [Qt], Papirus-Dark [GTK2/3/4]
Terminal: WezTerm 20240203-110809-5046fc22
CPU: AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx (8) @ 2.00 GHz
GPU: AMD Radeon Vega 8 Graphics [Integrated]
Memory: 3024 MiB / 7311 MiB

and here's the output of journalctl with the last two crashes, I cleaned it up from things I already know aren't the cause (some irq_handler stuff that can be ignored):

Feb 03 21:11:02 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #409543 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:11:02 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #409544 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:11:02 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #409546 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:15:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #584675 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:15:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #584676 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:15:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #584677 ] -- see the man page entry for --no-replay and --rep%lay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:15:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #584678 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:15:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #584679 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:15:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #584680 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:15:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #584681 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:34:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #805086 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Feb 03 21:34:04 hostname nm-openvpn[2822]: AEAD Decrypt error: bad packet ID (may be a replay): [ #805087 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
-- Boot dd3633625a604ec6b0dacec9e2ebe639 --
Feb 03 22:00:16 hostname kernel: platform USBC000:00: failed to claim resource 0: [mem 0x8ce7d8c6-0x8ce7e8c5]
Feb 03 22:10:26 hostname systemd-coredump[3754]: Process 3749 (gldriverquery) of user 1000 dumped core.

                                                      Stack trace of thread 3749:
                                                      #0  0x00000000ebc58579 n/a (n/a + 0x0)
                                                      ELF object binary architecture: Intel 80386
Feb 03 22:10:55 hostname kwin_wayland[1413]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Feb 03 22:11:10 hostname kwin_wayland[1413]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Feb 03 22:11:10 hostname kwin_wayland[1413]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Feb 03 22:11:14 hostname kwin_wayland[1413]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Feb 03 22:11:57 hostname kwin_wayland[1413]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
-- Boot c4e02bddbac24b578daab535b3029a71 --
Feb 03 22:13:05 hostname kernel: platform USBC000:00: failed to claim resource 0: [mem 0x8ce7d8c6-0x8ce7e8c5]

Now to be clear I am pretty sure the AEAD stuff is completely irrelevant I'm only leaving it here just in case it may be.
In this case Crash 1 happened at ~22:00 while I was watching youtube while Crash 2 happened at ~22:30 while I had just started Hearts of Iron 4, barely loading the launcher. In both scenarios I had ProtonVPN and qBittorrent also running.

Now this has been going on for a few months, and it happens at random times and during random activities (including sometimes doing nothing for some minutes), sometimes I would think there's a pattern with certain activities like opening Vesktop would usually crash it but once I try doing more of that it doesn't, every time I look at journalctl or dmesg it's either nothing or something different each time and I can't reliably reproduce the issue.
It only happens on my laptop, not my desktop which runs CachyOS (I had similar issues with Cachy on the laptop too, don't remember if also with mint)
I even tried running a live Fedora image with KDE to try and reproduce it to no avail, I couldn't exactly reproduce everything I do on my laptop so I can't conclusively say if nothing happened because it doesn't happen or simply because I was lucky or didn't do whatever triggered the event.
I'm currently not able to install other distros to see if it's an issue with the latest kernel or Arch (even then I wouldn't be able to exactly reproduce what I use and do but still) as I'm in the middle of my university's exam session and don't have much time to set everything up and mess with stuff.

Another oddity is that during installation arch install left about 40GBs of my drive encrypted but unallocated idk if it's normal with BTRFS and LVM.
It also tends to get very hot even when doing tasks like watching a video file using VLC, having steam open or watching Youtube, I also noticed some pretty serious performance drops for a while and while using different distros. this makes me believe it's probably a hardware issue but when I went back home and brought it up to my father (who is pretty good at computers usually) but he believes it's probably a software issue and didn't want to help me open it to check if anything was visibly wrong. I can't open it right now either as I don't have a suitable screwdriver but I guess I'll go pick one up as soon as I can, in the meantime I'd like to know if anyone else had this issue and/or if anyone can help me try and find out more about why this could be happening.

Last edited by EuroNutellaMan (2025-02-03 22:12:58)

Head_on_a_Stick · 2025-02-03 22:13:01

I'm very tired so I didn't read your wall of text but I did search for "microcode" or "ucode" and it wasn't found so look that up in the ArchWiki, the Ryzen 2500 needs it to stop falling over.

EuroNutellaMan · 2025-02-03 22:19:13

Head_on_a_Stick wrote:

I'm very tired so I didn't read your wall of text but I did search for "microcode" or "ucode" and it wasn't found so look that up in the ArchWiki, the Ryzen 2500 needs it to stop falling over.

amd-ucode is already installed. I will try what the wiki suggests with system halts I guess.

PatoPatoPato · 2025-02-04 04:42:48

I don't know about the temps, but the freezes may be related to an issue with amd APUs and mesa packages:
https://bbs.archlinux.org/viewtopic.php?id=301798
https://www.reddit.com/r/archlinux/comm … ng_inputs/

I 've been experiencing this on a ryzen 3200g, the computer would randomly freeze and for some reason starting GIMP would trigger this crash almost immediately, forcing me to reboot.
I was able to get it working again by downgrading the following packages to these versions:

mesa: 1:24.2.7-1 — Core OpenGL library.
lib32-mesa: 1:24.2.7-1 — 32-bit version of Mesa for compatibility.
lib32-vulkan-radeon: 1:24.2.7-1 — Vulkan driver for AMD GPUs (32-bit).
vulkan-radeon: 1:24.2.7-1 — Vulkan driver for AMD GPUs (64-bit).
llvm-libs: 18.1.8-1 — Provides the backend for shader compilation and GPU optimizations.
lib32-llvm-libs: 1:18.1.8-1 — 32-bit version of LLVM libraries.
libglvnd: 1.7.0-1 — OpenGL vendor-neutral dispatch library for managing multiple drivers.

Arch Linux

#1 2025-02-03 22:08:56

Laptop crashes completely, can't figure out why

#2 2025-02-03 22:13:01

Re: Laptop crashes completely, can't figure out why

#3 2025-02-03 22:19:13

Re: Laptop crashes completely, can't figure out why

#4 2025-02-04 04:42:48

Re: Laptop crashes completely, can't figure out why

Board footer