Linux crashing on my pc

Issues & Assistance
1

My system crashing randomly. When I boot and try to do something or even don’t do anything, my pc stutter for few milliseconds or for few seconds, then display freezes for some seconds, then pc restart.
I see some error codes on next boot after crash. Those error codes are here within brackets-
{

[ 0.624336 ] [ Hardware Error ] : System Fatal Error,
[ 0.624343 ] [ Hardware Error ] : CPU : 10 (17 : 71 : 0) MC5_STATUS [- I UE I MiscV I AddrV I PCC I TCC I SyndV I - I - I - ] : 0xbea0000000000108
[ 0.624356 ] [ Hardware Error ] : Error Addr : 0x0001ffffc095007c
[ 0.624361 ] [ Hardware Error ] : IPID : 0x000500b000000000, Syndrome : 0x000000004d000000
[ 0.624368 ] [ Hardware Error ] : Execution Unit Ext. Error Code: 0
[ 0.624369 ] [ Hardware Error ] : Cache level : RESV, tx: GEN, mem-tx: GEN

}

sometimes system on next boot after crash shows similar error codes, sometimes even more.

 
System:
Kernel: 6.8.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=46c6a142-17f9-4129-8a6a-611b966027f2 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: X570-A PRO (MS-7C37) v: 3.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: H.M0 date: 10/13/2023
CPU:
Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701030
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2468 high: 4125 min/max: 2200/4208 boost: enabled
scaling: driver: acpi-cpufreq governor: conservative cores: 1: 2200 2: 2200
3: 2200 4: 2050 5: 2050 6: 4125 7: 2200 8: 2200 9: 2200 10: 2050 11: 2050
12: 4100 bogomips: 86404
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Sapphire 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: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1
bus-ID: 2f:00.0 chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1536x864 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
navi22 LLVM 17.0.6 DRM 3.57 6.8.8-zen1-1-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 8 device: 0 type: discrete-gpu name: AMD
Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.0.6-arch1.2
device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.0.6-arch1.2 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2f:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI X570-A PRO
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 31:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.8.8-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8812AE 802.11ac PCIe Wireless Network Adapter
driver: rtl8821ae v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: c000
bus-ID: 29:00.0 chip-ID: 10ec:8812 class-ID: 0280
IF: wlp41s0 state: up mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 4.23 TiB used: 15.31 GiB (0.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M8500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: S5Z42105 temp: 38.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT120BX500SSD1
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: R013 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM004-2CV104
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: LITE-ON IT model: LSS-32L6G-HP
size: 29.82 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 704 scheme: GPT
Partition:
ID-1: / raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 15.31 GiB (51.9%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 15.31 GiB (51.9%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 15.31 GiB (51.9%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 15.31 GiB (51.9%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 55.4 C mobo: N/A gpu: amdgpu temp: 50.0 C
mem: 42.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 3.13 GiB (10.0%)
Processes: 398 Power: uptime: 2m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1410 libs: 392 tools: octopi,pamac,paru
pm: flatpak pkgs: 0 Compilers: gcc: 13.2.1 Shell: garuda-inxi default: fish
v: 3.7.1 running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-05-02
Last full system update: 2024-05-16
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:
2

Since when have you had this problem, from the beginning?
What operating system did you previously install?
Were there similar issues?

Overclocking, undervolting or other gimmicks?
If so, turn it off.

Graphics card recently replaced?

Does your power supply have enough power for the hardware?

Please answer all questions.

Welcome to the community :slight_smile:

3 Likes
3

I have this problem since i tried very first distro, i think it was manjaro or may be mint.
I have two m.2 ssd one nvme with windows 11 installed on it. And other m.2 sata with garuda linux.
Windows don’t have this issue. Only linux have this. I tried many distro same issue.
No overclocking, undervolting, or other gimmicks. Also my system doesn’t overheat.
Previously i was on 1050 ti, i was having same issue. But after changing graphics card i did fresh installation, but same issue.
My power supply is powerfull enough to supply 1.3+ times what my system will consume at full system stress.

4

A hardware error only on Linux :thinking: ?
Shutdown on M$ (do not reboot to Linux), disable fast and secure boot.
Check in BIOS for raid/ahci modus.

3 Likes
5

Uefi enabled, fast boot and secure boot disabled also cleared keys. I have changed to ahci as i heard somewhere that raid on linux is not good experience. Also i am fully on gpt. Master Boot Record was worst.

Sorry, it’s late night :bridge_at_night: here. I will be online tomorrow :sunrise:. :sleeping:

6

Damn.

7

Sorry, it’s late night :bridge_at_night: here. I will be online tomorrow :sunrise:. :sleeping:

8

There is an update for your BIOS/UEFI. Maybe this would help.

6 Likes
9

Then you have automatically tried several kernels. In addition, there are some garuda´s flying here in the forum on the same CPU/GPU w/o issues.

Since Windows is running without problems, I’m guessing power management. Linux and Windows kernels are different, it is possible that Linux doesn’t like the power saving settings in your BIOS. Try deactivating the c-state in your BIOS.

And do a BIOS update as @Apocalypticus already suggested.

2 Likes
10

Im not sure but maybe you check also that you have CMS activated in your Bios and the setting to Uefi and Legancy installation i have to set mine also to other OS enabled =)

11

Aren’t other user already using garuda linux without bios update.
I don’t think bios update is the issue.

12

I did everything - disabled c-state, updated bios, nothing helped.
Here is recent garuda-inxi output, if that can help you find the issue.
And here are the link to my other forums opened with msi and amd for this issue -
msi - How do i install linux os? X570a pro motherboard | MSI Global English Forum
amd - Ryzen 5 3600 with x570 motherboard not letting me ... - AMD Community

garuda-inxi
System:
Kernel: 6.8.9-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=46c6a142-17f9-4129-8a6a-611b966027f2 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.2.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: X570-A PRO (MS-7C37) v: 3.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: H.N0 date: 04/02/2024
CPU:
Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701033
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2300 high: 2800 min/max: 2200/4208 boost: enabled
scaling: driver: acpi-cpufreq governor: conservative cores: 1: 2200 2: 2200
3: 2200 4: 2800 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2800 11: 2200
12: 2200 bogomips: 86404
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Sapphire 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: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1
bus-ID: 2f:00.0 chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.7
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1536x864 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.7-arch1.3
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
navi22 LLVM 17.0.6 DRM 3.57 6.8.9-zen1-2-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 12 device: 0 type: discrete-gpu name: AMD
Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.0.7-arch1.3
device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.0.7-arch1.3 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2f:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI X570-A PRO
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 31:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.8.9-zen1-2-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.6 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp39s0 state: down mac: <filter>
Device-2: Realtek RTL8812AE 802.11ac PCIe Wireless Network Adapter
driver: rtl8821ae v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: c000
bus-ID: 29:00.0 chip-ID: 10ec:8812 class-ID: 0280
IF: wlp41s0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 4.23 TiB used: 16.18 GiB (0.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M8500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: S5Z42105 temp: 41.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT120BX500SSD1
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: R013 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM004-2CV104
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: LITE-ON IT model: LSS-32L6G-HP
size: 29.82 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 704 scheme: GPT
Partition:
ID-1: / raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 16.18 GiB (54.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 16.18 GiB (54.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 16.18 GiB (54.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 29.52 GiB size: 29.52 GiB (100.00%)
used: 16.18 GiB (54.8%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 52.4 C mobo: N/A gpu: amdgpu temp: 51.0 C
mem: 44.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 598
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 2.77 GiB (8.8%)
Processes: 369 Power: uptime: 2m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1385 libs: 393 tools: octopi,pamac,paru
Compilers: gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: yakuake inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-05-02
Last full system update: 2024-05-16
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:            nmb.service
14

BIOS updates are there for several reasons. Mostly compatibility and security issues. Things that work for others don’t necessarily have to do the same for you.

The error you posted actually points to a hardware defect (CPU, RAM, power supply etc.). With the BIOS update possible incompatibilities are now excluded.

What surprises me is that the problems occur with various linux distros, but not with windows, which actually speaks against a defect.

It’s difficult to say what to do now. There were few suggestions that doidn´t help. Maybe @nepti is right with power management. Neverless I would run a memtest, if possible test a different CPU and a different power supply to be able to definitively rule out such things.

EDIT:
I saw your post after I had sent this one. So you can forget almost everything I wrote.
Nevertheless, i am glad that you have at least found a workaround and that the problem is now localized :+1:

15

:+1:A workaround helped, disabling c-state from bois->overclocking fixed issue temporarily.
That’s just a temporary solution suggested by amd on some other post.
Issue was ryzen 3000/5000 series and 500 series motherboard chipset only.
Some users may also have to change power control from auto to typical.

Again that’s just temporary solution amd promised to give bios update to fix that issue but seems like issue still persist for ryzen 3000/5000 cpu with 500 series mobo.
It’s risky, as changing power control can lead your processor to work at higher watt, which may or may not cause damage.:+1:

16

That’s exactly what I mean. I was just about to reply, but you were a few minutes quicker to post. I’ll post my answer here anyway, maybe it will help someone:

Garuda or other Linux distributions are not the cause.
If the error is the same every time (CPU), then it sounds like the AMD CPU has a problem with Linux and the power settings. This AMD-specific problem has been known since last year (keyword c-state/p-state).

Try changing the power governor from ‘conservative’ to ‘performance’ under Linux.

If that doesn’t help, try disabling all power management options in the BIOS.

Same with ACPI, try disabling it as a test.

Find out more about kernel parameters for ACPI and the limitation of c-state in the arch-wiki.

Another point is that hardware ages - including CPUs. In this case it usually helps to increase the vcore a little bit if a CPU is running unstable. That has often helped.

3 Likes
17

Glad to see @nepti gave you your solution.

Now that your issue is resolved I will make a couple of comments about things that were brought up on this thread.

I my experience, it is unlikely a hardware issue if symptoms persist in Linux, but not Windows. However, this does not mean it’s impossible it’s a hardware issue. I run into this regularly with Ethernet troubleshooting, in Linux. Users often balk at the suggestion that it could be the cable because it “works in Windows”. Oftentimes it is the cabling even though the Ethernet works adequately well in Windows. This is just one example that goes to show that Linux and Windows are very different, and they can react differently with different hardware.

I have written a very extensive and detailed guide on troubleshooting crashing issues that is in the forums FAQ & Guide section. One of the primary steps in this guide is to ensure the bios is up to date. Again users, often balk at this suggestion because of a fear of updating the computer’s bios. My reaction to this is, don’t expect help on the forum if you refuse to update your bios. I’ve seen too many threads go on for 50-100 posts, only to be resolved when the user finally agreed to update their bios. Updating the bios should be a primary step for anything that could potentially be a hardware issue, as that is what bios updates are often for.

So in sumarry:

Windows and Linux are very different, so you can’t discount a hardware problem, incompatability, or driver issue just because it works in Windows.

Don’t expect help if you refuse to update your bios, because many forum assistants will bypass your help request if the bios isn’t up to date.

Glad you found a resolution.

3 Likes
18

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