Hi, after updating my kernel to 6.11 (fedora 40) my pc seeming after a random period of time freezes: it does not display any error, it only freezes until i shut it down holding the power button. It happens more frequently when i have an external display plugged in but it also happens when using the laptop normally, like watching youtube. When watching youtube, the audio loops the last 2 seconds of audio. Booting with 6.10 makes it work flawlessly, and i tried both 6.11.5 and 6.11.6. I’m a novice so please ask if you want more context or logs
This will most likely be caused by a kernel / driver bug, most of the time they will be resolved within a few kernel updates so the best course of action would then be to wait.
If kernel 6.10 works well for you and you still have that installed, an option could be to freeze the kernel packages for a while. You can do this by editing /etc/dnf/dnf.conf and adding the line:
excludepkgs=kernel*
Meanwhile you could periodically check the forums and possibly the bugzilla bugtracker if other people are reporting similar issues.
To make your topic more easily findable it would be helpful to add your hardware specifications to the opening post, and to add a few tags that reflect the type of hardware that you are working with.
We need more information to understand the problem. Linux troubleshooting usually needs command-line tools.
When the system “freezes”, does the CapsLock light respond? New kernels often require firmware updates, particularly for laptop power management, so it is important to apply firmware updates from your laptop vendor. Many vendors support linux fwupd. You can list available updates by running sudo fwupdtool get-updates iin a terminal.
We need to see the output from running inxi -Fzxx in a terminal and as post as pre-formatted text (using the </> button from the top line of the text entry panel). This helps us understand your hardware configuration, and because it is searchable text, others with similar hardware and issues can find this topic (“given enough eyes, all (linux) problems are transparent”).
Fedora has journalctl, which captures enormous detail. It can take some effort to find a “filter” that selects entries relevant to your issue. Start by running journalctl --no-hostname -b -1 in a terminal and scroll down to the end to see if there are error messages.
i have not checked my caps lock, but the whole keyboard backlights work (after some afk, they turn off and turn back on when detect input from both keyboard or trackpad). EDIT: the caps lock light DOES NOT work.
The fwupd commands returns this,
fwupd:
uPluginUefiCapsule SMBIOS BIOS Characteristics Extension Byte 2 is invalid -- UEFI Specification is unsupported, but /sys/firmware/efi exists: System does not support UEFI mode
Loading… [****** ]11:59:30.644 FuUsbDevice failed to parse platform BOS descriptor: failed to parse: no supported platform version: did not find magic
Loading… [************************************** ]
Devices with no available firmware updates:
• MSFT0001:00 04F3:3140
• CT1000P3SSD8
• System Firmware
• UEFI Device Firmware
• UEFI Device Firmware
Devices with the latest available firmware version:
• UEFI dbx
No updates available for remaining devices
and the inxi command outputs:
inxi -Fzxx
System:
Kernel: 6.10.12-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.41-37.fc40
Desktop: GNOME v: 46.6 tk: GTK v: 3.24.43 wm: gnome-shell dm: 1: GDM
2: LightDM note: stopped Distro: Fedora Linux 40 (Workstation Edition)
Machine:
Type: Convertible System: LENOVO product: 82HU v: IdeaPad Flex 5 14ALC05
serial: <superuser required> Chassis: type: 31 v: IdeaPad Flex 5 14ALC05
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0R32866 WIN
serial: <superuser required> part-nu: LENOVO_MT_82HU_BU_idea_FM_IdeaPad
Flex 5 14ALC05 UEFI: LENOVO v: GJCN22WW date: 04/28/2021
Battery:
ID-1: BAT0 charge: 32.9 Wh (68.7%) condition: 47.9/52.5 Wh (91.2%)
volts: 11.6 min: 11.5 model: SMP L19M3PD6 serial: <filter>
status: not charging
CPU:
Info: quad core model: AMD Ryzen 3 5300U with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 rev: 1 cache: L1: 256 KiB L2: 2 MiB L3: 4 MiB
Speed (MHz): avg: 400 min/max: 400/3900 cores: 1: 400 2: 400 3: 400 4: 400
5: 400 6: 400 7: 400 8: 400 bogomips: 41521
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Lucienne vendor: Lenovo
driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports:
active: eDP-1 empty: HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:164c
temp: 47.0 C
Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 1-4:2 chip-ID: 5986:212a
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.4
compositor: gnome-shell driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: eDP-1 model: BOE Display 0x08d6 res: 1920x1080 dpi: 158
diag: 355mm (14")
API: OpenGL v: 4.6 vendor: amd mesa v: 24.1.7 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir LLVM
18.1.6 DRM 3.57 6.10.12-200.fc40.x86_64) device-ID: 1002:164c
display-ID: :0.0
API: Vulkan v: 1.3.296 surfaces: xcb,xlib,wayland device: 0
type: integrated-gpu driver: N/A device-ID: 1002:164c device: 1 type: cpu
driver: N/A device-ID: 10005:0000
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
Audio driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 04:00.1 chip-ID: 1002:1637
Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
vendor: Lenovo driver: N/A pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.5
chip-ID: 1022:15e2
Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
vendor: Lenovo driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 04:00.6 chip-ID: 1022:15e3
API: ALSA v: k6.10.12-200.fc40.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.9 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8852AE 802.11ax PCIe Wireless Network Adapter
vendor: Lenovo driver: rtw89_8852ae v: kernel pcie: speed: 2.5 GT/s lanes: 1
port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8852
IF: wlp2s0 state: up mac: <filter>
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-4:3 chip-ID: 0bda:4852
Report: btmgmt ID: hci0 rfk-id: 3 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
Drives:
Local Storage: total: 931.51 GiB used: 174.04 GiB (18.7%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P3SSD8 size: 931.51 GiB
speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 40.9 C
Partition:
ID-1: / size: 464.62 GiB used: 173.65 GiB (37.4%) fs: btrfs
dev: /dev/nvme0n1p5
ID-2: /boot size: 973.4 MiB used: 353.2 MiB (36.3%) fs: ext4
dev: /dev/nvme0n1p4
ID-3: /boot/efi size: 256 MiB used: 51.7 MiB (20.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 464.62 GiB used: 173.65 GiB (37.4%) fs: btrfs
dev: /dev/nvme0n1p5
Swap:
ID-1: swap-1 type: zram size: 7.12 GiB used: 1.15 GiB (16.2%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 53.5 C mobo: N/A gpu: amdgpu temp: 48.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB note: est. available: 7.12 GiB used: 4.22 GiB (59.3%)
Processes: 366 Power: uptime: 52m wakeups: 0 Init: systemd v: 255
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 68
Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.26 running-in: gnome-terminal
inxi: 3.3.36
as for journalctl, i did not see big red bad lines
nov 09 12:48:38 kernel: Linux version 6.11.6-200.fc40.x86_64 (mockbuild@0c05f21b74f045b382c0d64265f3a13b) (gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3), GNU ld version 2.41-37.fc>
nov 09 12:48:38 kernel: Command line: BOOT_IMAGE=(hd0,gpt4)/vmlinuz-6.11.6-200.fc40.x86_64 root=UUID=52c830a8-2b98-4662-ab31-c4bfea4df227 ro rootflags=subvol=root rhgb quiet
nov 09 12:48:38 kernel: BIOS-provided physical RAM map:
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009bfffff] usable
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x0000000009c00000-0x0000000009d90fff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x0000000009d91000-0x0000000009efffff] usable
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x0000000009f00000-0x0000000009f0efff] ACPI NVS
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x0000000009f0f000-0x00000000c72fafff] usable
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000c72fb000-0x00000000cb4fafff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000cb4fb000-0x00000000cd57dfff] ACPI NVS
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000cd57e000-0x00000000cd5fdfff] ACPI data
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000cd5fe000-0x00000000ce7fffff] usable
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000ce800000-0x00000000cfffffff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000fde00000-0x00000000fdefffff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe0fffff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000020f37ffff] usable
nov 09 12:48:38 kernel: BIOS-e820: [mem 0x000000020f380000-0x000000022fffffff] reserved
nov 09 12:48:38 kernel: NX (Execute Disable) protection: active
Looks like you showed us the first screen (of potentially 100’s). Press the $ key to jump to the bottom and look back a few screens.
UEFI: LENOVO v: GJCN22WW date: 04/28/2021
Your UEFI firmware is quite old. My Dell systems get several UEFI firmware update a year. Lenovo does participate in the the fwupd project, so your model may not be officially supported on Linux. It has only 2 entries the LHDB, both using older kernels, so there may not be very many people using this model with Linux.
There have been issues with AMD’s amdgpu and power management for things like resume from sleep, but I did find a 2021 report of Random crashes on Ryzen and AMD GPU under Linux and
AMD GPU crashes. Both have examples using journalctl to idebntify the issue.You may want to try running journalctl --no-hostname -b -1 -g amdgpu to see messages from amdgpu. If those don’t pinpoint your issue, look for “priority” messages using journalctl --no-hostname -b -1 -g amdgpu -p <priority>. See man journalctl for an explanation of the priority levels.
Problems like this are usually not limited to Fedora, but do appear first on Fedora simply because Fedora is often one of the first distros to use recent kernels. You may want to stick with the 6.10 kernels and periodically search for reports of similar issues with 6.11 or newer kernels.
I’m not sure on what command output you’re seeing only the first screen, as both sudo fwupdtool get-updates and inxi -Fzxx finish (i dont have to press q to write other commands) and dont have other outputs other than what i wrote.
Journalctl does return some errors, but i suspect they also appear on 6.10 kernel. This output is using -1 and thats a boot using 6.10
journalctl --no-hostname -b -1 -g amdgpu
nov 09 14:25:16 kernel: [drm] amdgpu kernel modesetting enabled.
nov 09 14:25:16 kernel: amdgpu: Virtual CRAT table created for CPU
nov 09 14:25:16 kernel: amdgpu: Topology: Add CPU node
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: enabling device (0006 -> 0007)
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: amdgpu: Fetched VBIOS from VFCT
nov 09 14:25:16 kernel: amdgpu: ATOM BIOS: 113-LUCIENNE-015
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: vgaarb: deactivate vga console
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: amdgpu: MODE2 reset
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
nov 09 14:25:16 kernel: [drm] amdgpu: 512M of VRAM memory ready
nov 09 14:25:16 kernel: [drm] amdgpu: 3645M of GTT memory ready.
nov 09 14:25:16 kernel: amdgpu 0000:04:00.0: amdgpu: Will use PSP to load VCN firmware
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: reserve 0x400000 from 0xf41f800000 for PSP TMR
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
nov 09 14:25:17 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is initialized successfully!
nov 09 14:25:17 kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
and this is the output from a 6.11 boot that freezed
journalctl --no-hostname -b -2 -g amdgpu
nov 09 14:05:14 kernel: [drm] amdgpu kernel modesetting enabled.
nov 09 14:05:14 kernel: amdgpu: Virtual CRAT table created for CPU
nov 09 14:05:14 kernel: amdgpu: Topology: Add CPU node
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: enabling device (0006 -> 0007)
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: Fetched VBIOS from VFCT
nov 09 14:05:14 kernel: amdgpu: ATOM BIOS: 113-LUCIENNE-015
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: vgaarb: deactivate vga console
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: MODE2 reset
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
nov 09 14:05:14 kernel: [drm] amdgpu: 512M of VRAM memory ready
nov 09 14:05:14 kernel: [drm] amdgpu: 3644M of GTT memory ready.
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: reserve 0x400000 from 0xf41f800000 for PSP TMR
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
nov 09 14:05:14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is initialized successfully!
nov 09 14:05:15 kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
nov 09 14:05:15 kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Is the problem the error, or just that 6.11 handles this error in a somehow worse way than 6.10? Also, thank you, and i will wait for other kernel versions, I made this post just to make it known because it appeared for 2 versions straight.
There is no error/crash visible in the posted logs. What you can do if you roughly know the time at which a freeze happened, is to show all the logs from the day e.g.:
$ journalctl --time-since=today
and then scroll to the time around which the freeze occurred. You may see some more clear messages about the cause this way than with the earlier log.
You need to adjust the boot number if you have rebooted multiple times. See man journalctl for details. You can get a list of previous boots if you aren’t sure about the number of intervening boots with older kernels.
ok, i did that (although the command syntax is wrong i asked chatgpt for the right one) and i fund two things:
amdgpu 0000:04:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
nov 10 12:28:03 cappello-di-feltro kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
nov 10 12:28:03 cappello-di-feltro kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
nov 10 12:28:03 cappello-di-feltro kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
this error is both on 6.10 and 6.11, so thats not what makes it crush, but its red and may be correlated in some way (?)
nov 10 11:46:52 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
nov 10 11:46:57 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
nov 10 11:46:57 cappello-di-feltro tailscaled[1671]: control: NetInfo: NetInfo{varies=false hairpin= ipv6=false ipv6os=true udp=true icmpv4=false derp=#4 portmap=active- link="" firewallmod>
nov 10 11:47:02 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
nov 10 11:47:08 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
nov 10 11:47:13 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
nov 10 11:47:18 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
nov 10 11:47:23 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
nov 10 11:47:28 cappello-di-feltro tailscaled[1671]: [unexpected] magicsock: derp-18 does not know about peer [iLOBD], removing route
theres about 50 lines with the tailscaled error, from 11.42 to 11.46.57, the system crashed at 11.47 immediately after the NetInfo thing and then theres other 6 lines of the tailscaled error.
it should also be noted that 6.10 kernel’s logs times are one hour more than what the real time was: after the crash at 11.47 i rebooted with 6.10 to write this post (now its 12.09) and the journal logs say 12.47 at the boot of 6.10. After a while 6.10 recognizes that the time is wrong and fixes it.
There are other red strings in both 6.10 and 6.11, i didnt report on them because they’re not on the specific time it crashed.
Thats what i did, i checked with “normal” journalctl which was the 6.11 boot and which was the 6.10. I specified since in the command output i included the command itself, so you could be deceived by that.
I wonder if the tailscale messages are related to the freeze. Does tailscale issue13863 seem relevant?
Another possibility is some resource constraint. You could use one of the many GUI tools that track resource usage to see if the tailscale problem is preceeded by some resource limitation (heavy CPU usage or low free memory).
Unfortunately, it just crashed right before my eyes, and i had boh a System monitor window open (from which i did not see anything strange)
(EDIT: i just retried with the “resources” panel open, and cpu was around 20%, while ram was at 60)
and a terminal window with watch -n 5 tailscale status . It didnt report anything strange. I’m sorry this looks like a more difficult issue, thank you so much for the replies
Update: 6.11.7 does NOT solve the issue
Update: 6.11.8 does NOT solve the issue either, im starting to lose hope
The LHDB has many probes for IdeaPad 5 14ALC05 82LM. Crashes that don’t leave evidence that appears in journalctl are likely hardware issues, which can bad RAM, bad solder joints, bad connectors/sockets, or device firmware (GPU, SSD’s). Device firmware often needs updates for newer kernels.
Next steps:
- rule out recent changes in linux by running an older kernel. You can try a LTS kernel
- run memtest86+ overnight for a couple nights
- look for LHDB probes using recent kernels. You can drill down to see details like BIOS and firmware versions
- open up the system to reseat all connectors (after checking for signs of green corrosion)
Thank you for your reply,
You mentioned device firmware, how would i go to update that? Also, the connector reseating is not possible since my ram and gpu are soldered, only the ssd could be reseated. As for the kernel, it surely is a recent change as my 6.10.12 boot works as intended (although it crashes sometimes, it has different symptoms and doesnt happen as frequently)
Edit: memtest returns a PASS score
Lenovo participate in the Linux Vendor Firmware Service (LVFS). In a terminal you use fwupdtool and fwupdmgr. Run with --help to see a list of available options. New firmware is often available directly from the vendor, but sometime as Windows .exe files.
I tried with both gnome-software updates and the terminal with $ fwupdmgr get-devices, and now it doesnt crash! Ill wait a couple days of testing before marking this as solved, but thank you so much!!
It could help others to mention which firmware updates were installed.