You are not logged in.

Pages: 1

#1 2025-09-02 17:50:54

bowlin
Member
Registered: 2025-02-27
Posts: 56

Getting seemingly random crashes no matter the WM.

Hey.

Been troubleshooting this issue of mine for the past couple of weeks. Sometimes my PC just locks up (cursor stutters and then stops moving) and crashes right afterwards. Screen goes black (out of signal) but the computer stays on. The only way to get it up and running again is to hold the power button and boot it again. This started happening a couple weeks back.

Here's some general info:
GPU: AMD Radeon RX 570 Pulse 4GB
CPU: AMD Ryzen 5 2600X
MOBO: B450M PRO-VDH MAX
RAM: 16 Gigs of DDR4

DM: None
WM: DWM

Here's a log from the previous boot when it crashed:
http://0x0.st/KHCk.txt
I'm 99% sure the last bit is where the crash has happened.

Thank you for your help.

Offline

#2 2025-09-02 18:02:42

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 8,999
Website

Re: Getting seemingly random crashes no matter the WM.

Have you installed the amd-ucode package and ensured the µcode is loaded? Your revision number looks old to me but I might be wrong. I think those 2nd generation Ryzens do need the fixes.

Otherwise check your memory health.

EDIT: those PCIe bus errors at the end of the journal lead me to https://forums.unraid.net/topic/90337-s … or-in-log/, which was fixed by updating the firmware ("BIOS").

Last edited by Head_on_a_Stick (2025-09-02 18:05:31)

Jin, Jîyan, Azadî

Offline

#3 2025-09-02 19:19:19

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,820

Re: Getting seemingly random crashes no matter the WM.

Sep 02 18:51:40 Archie kernel: DMI: Micro-Star International Co., Ltd. MS-7A38/B450M PRO-VDH MAX (MS-7A38), BIOS B.20 09/18/2019
Sep 02 18:51:40 Archie kernel: amdgpu 0000:29:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 32
Sep 02 18:51:40 Archie kernel: amdgpu 0000:29:00.0: amdgpu: Using BACO for runtime pm
Sep 02 18:51:40 Archie kernel: amdgpu 0000:29:00.0: [drm] Registered 6 planes with drm panic
Sep 02 18:51:40 Archie kernel: [drm] Initialized amdgpu 3.64.0 for 0000:29:00.0 on minor 1
Sep 02 18:51:40 Archie kernel: fbcon: amdgpudrmfb (fb0) is primary device
Sep 02 18:51:40 Archie kernel: amdgpu 0000:29:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Sep 02 18:51:41 Archie kernel: snd_hda_intel 0000:29:00.1: bound 0000:29:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Sep 02 18:58:07 Archie kernel: amdgpu 0000:29:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 02 18:58:07 Archie kernel: amdgpu 0000:29:00.0:   device [1002:67df] error status/mask=00001000/00002000
Sep 02 18:58:07 Archie kernel: amdgpu 0000:29:00.0:    [12] Timeout
amdgpu.aspm=0 amdgpu.bapm=0 amdgpu.runpm=0 pcie_aspm=off

https://wiki.archlinux.org/title/Kernel_parameters

And test the LTS kernel.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#4 2025-09-23 13:32:05

bowlin
Member
Registered: 2025-02-27
Posts: 56

Re: Getting seemingly random crashes no matter the WM.

Sorry for the late response. I have amd-ucode installed, will look into the bios part. I thought the issue magically fixed itself but today I got a proper coredump out of a crash. After stuttering, it brought me back to a tty and typing, navigating in 'less' was VERY stuttery.

coredumpctl info $pid:
https://bpa.st/FREQ

journalctl -b -1:
http://0x0.st/KADZ.txt


Edit:
Checked that the microcode is being loaded early (journalctl -k --grep='microcode:'):
https://bpa.st/KULA

Last edited by bowlin (2025-09-23 13:43:55)

Offline

#5 2025-09-24 12:18:41

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,820

Re: Getting seemingly random crashes no matter the WM.

Sep 23 15:58:29 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:29 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:40 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:40 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:41 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:41 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:41 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:41 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:41 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:41 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:42 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:42 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:42 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:42 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:43 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:43 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:44 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:44 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:45 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:45 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:45 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:45 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:46 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:47 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:47 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:48 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:49 Archie kernel: pcieport 0000:00:03.1: AER: Multiple Correctable error message received from 0000:00:00.0
Sep 23 15:58:49 Archie kernel: amdgpu 0000:29:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:49 Archie kernel: snd_hda_intel 0000:29:00.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:51 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:51 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:51 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:51 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:51 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:51 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Multiple Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: amdgpu 0000:29:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: snd_hda_intel 0000:29:00.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Multiple Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Sep 23 15:58:52 Archie kernel: pcieport 0000:00:03.1: AER: Multiple Correctable error message received from 0000:00:00.0
Sep 23 15:58:52 Archie kernel: amdgpu 0000:29:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Sep 23 15:58:52 Archie kernel: snd_hda_intel 0000:29:00.1: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
Sep 23 15:58:53 Archie kernel: pcieport 0000:00:03.1: AER: Multiple Correctable error message received from 0000:00:00.0
Sep 23 15:58:53 Archie kernel: amdgpu 0000:29:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)

There're ~10.000 line of that in the journal, starting ~13 minutes into the boot out of pretty much nowhere.
Have you tried to disable "pcie_aspm=off", https://wiki.archlinux.org/title/Kernel_parameters ?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#6 2025-10-04 15:46:44

bowlin
Member
Registered: 2025-02-27
Posts: 56

Re: Getting seemingly random crashes no matter the WM.

Booted with that parameter.

journalctl -b: https://bpa.st/LXBQ

Offline

#7 2025-10-04 16:35:17

LuxFerre
Member
Registered: 2010-03-01
Posts: 87

Re: Getting seemingly random crashes no matter the WM.

bowlin wrote:

The only way to get it up and running again is to hold the power button and boot it again

Won't fix your issues but did you try Sysrq REISUB?
Cycling the power should always be last resort...

Offline

#8 2025-10-04 18:59:55

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,820

Re: Getting seemingly random crashes no matter the WM.

The journal are only 3 minutes, are the link layer errors now gone?
What's the situation on the original problem?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#9 2025-10-05 10:32:22

bowlin
Member
Registered: 2025-02-27
Posts: 56

Re: Getting seemingly random crashes no matter the WM.

Will give Sysrq a look, thanks.

Yes the link layer errors are gone. As for the original problem, I'm not sure because it often happens out of the blue, or just when I start my system. There can be days in between of crashes.

Offline

#10 2025-10-05 12:41:30

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,820

Re: Getting seemingly random crashes no matter the WM.

Ok, look out for them - I'd not be overly surprise if this hinges on the bus errors, maybe check "lspci -tvnn" to see what's behind the noisy bus…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#11 Yesterday 15:16:22

bowlin
Member
Registered: 2025-02-27
Posts: 56

Re: Getting seemingly random crashes no matter the WM.

Okay the issue still persists, booted my pc up and the stutters began, again resulting in a crash. (https://bpa.st/6O2Q) All I could gather from the log are the errors in regards to my HDD.

Upon booting it up again, now it just works again.. I sometimes think its connected to booting the PC up after a longer period of it being turned off.

Offline

#12 Yesterday 19:48:44

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 68,820

Re: Getting seemingly random crashes no matter the WM.

You rebooted w/ the power button again? sysrq wasn't enabled or didn't work?

Oct 09 17:58:37 Archie kernel: input: C-Media Electronics Inc. USB Audio Device as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.3/0003:0D8C:0014.0002/input/input4
Oct 09 17:58:37 Archie kernel: hid-generic 0003:0D8C:0014.0002: input,hidraw1: USB HID v1.00 Device [C-Media Electronics Inc. USB Audio Device] on usb-0000:03:00.0-3/input3
Oct 09 17:58:37 Archie kernel: input: C-Media Electronics Inc. USB Audio Device as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.3/0003:0D8C:0014.0002/input/input13
Oct 09 17:58:37 Archie kernel: cmedia_hs100b 0003:0D8C:0014.0002: input,hidraw1: USB HID v1.00 Device [C-Media Electronics Inc. USB Audio Device] on usb-0000:03:00.0-3/input3
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Frame ID 870 (reg 7024, index 1) beyond range (881, 1773)
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Ignore frame ID field, use SIA bit instead
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Frame ID 871 (reg 7024, index 2) beyond range (881, 1773)
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Ignore frame ID field, use SIA bit instead
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Frame ID 872 (reg 7024, index 3) beyond range (881, 1773)
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Ignore frame ID field, use SIA bit instead
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Frame ID 873 (reg 7024, index 4) beyond range (881, 1773)
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Ignore frame ID field, use SIA bit instead
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Frame ID 874 (reg 7024, index 5) beyond range (881, 1773)
Oct 09 18:04:25 Archie kernel: xhci_hcd 0000:03:00.0: Ignore frame ID field, use SIA bit instead

can you replicate the stutter w/o that audio device?
(Though unless the stutter/problems began around that time this might be a complete red herring)

Oct 09 17:58:38 Archie kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oct 09 17:58:39 Archie kernel: EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended
Oct 09 17:58:39 Archie kernel: EXT4-fs (sda1): mounted filesystem 5eea8e1a-d8ad-4c49-a962-2dc9060825a4 r/w with ordered data mode. Quota mode: none.
Oct 09 18:04:02 Archie kernel: EXT4-fs (sda1): error count since last fsck: 1
Oct 09 18:04:02 Archie kernel: EXT4-fs (sda1): initial error at time 1756910319: ext4_validate_block_bitmap:423
Oct 09 18:04:02 Archie kernel: EXT4-fs (sda1): last error at time 1756910319: ext4_validate_block_bitmap:423

this is most likely a consequence of the hard reboots, but you want to fsck them nevertheless.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#13 Today 19:46:40

bowlin
Member
Registered: 2025-02-27
Posts: 56

Re: Getting seemingly random crashes no matter the WM.

Yes I did. And I tried to enable Sysrq, but the thing is that once the system crashes my monitor goes black as if there was no signal.

Offline

Pages: 1

Board footer

Powered by FluxBB