Hard random freezes (deadlocks) on 13700KF + RX 9070 XT, SysRq unresponsive

Issues & Assistance
1

System Information:

  • CPU: Intel Core i7-13700KF (No degradation symptoms, latest microcode applied)

  • GPU: AMD Radeon RX 9070 XT

  • DE/WM: KDE Plasma (Wayland)

The Issue: I am experiencing random hard system freezes. The system locks up completely — I cannot switch to a TTY, and Magic SysRq (REISUB) is completely unresponsive, forcing me to do a hard reset via the power button.

This happens randomly during regular desktop usage (not just during heavy gaming).

Logs: 660f158

What I’ve tried so far: A full system update (pacman -Syu) didn’t resolve the issue.

Any help on how to debug a freeze that doesn’t leave logs would be appreciated.

2

One you reboot after a crash, journalctl -b -1 will show you the logs from the previous boot, which might have some more info.

3 
steam[8796]: assert_20260428083319_49.dmp[21947]: Finished uploading minidump (out-of-process): success = no
steam[8796]: assert_20260428083319_49.dmp[21947]: error: Failure when receiving data from the peer
steam[8796]: assert_20260428083319_49.dmp[21947]: file ‘’/tmp/dumps/assert_20260428083319_49.dmp’‘, upload no: ‘‘Failure when receiving data from the peer’’
assert_20260428083800_52.dmp[22006]: Finished uploading minidump (out-of-process): success = no
at-spi2-registryd[1981]: Re-enabling app with pid 3320
assert_20260428083800_52.dmp[22006]: error: Failure when receiving data from the peer
assert_20260428083800_52.dmp[22006]: file ‘’/tmp/dumps/assert_20260428083800_52.dmp’‘, upload no: ‘‘Failure when receiving data from the peer’’
assert_20260428083319_49.dmp[21947]: Finished uploading minidump (out-of-process): success = no
assert_20260428083319_49.dmp[21947]: error: Failure when receiving data from the peer
assert_20260428083319_49.dmp[21947]: file ‘’/tmp/dumps/assert_20260428083319_49.dmp’', upload no: ‘‘Failure when receiving data from the peer’’
pipewire[1773]: spa.alsa: front:3p: (4 suppressed) snd_pcm_avail after recover: Обрыв канала
pipewire[1773]: spa.alsa: front:3p: (0 suppressed) snd_pcm_avail after recover: Обрыв канала
at-spi2-registryd[1981]: Re-enabling app with pid 2031
at-spi2-registryd[1981]: Re-enabling app with pid 2034
at-spi2-registryd[1981]: Re-enabling app with pid 1917
pipewire[1773]: spa.alsa: front:3p: (2 suppressed) snd_pcm_avail after recover: Обрыв канала
at-spi2-registryd[1981]: Re-enabling app with pid 2030
at-spi2-registryd[1981]: Disabling unresponsive app with pid 1917
at-spi2-registryd[1981]: Disabling unresponsive app with pid 2034
at-spi2-registryd[1981]: Disabling unresponsive app with pid 2030
at-spi2-registryd[1981]: Disabling unresponsive app with pid 2031
pipewire[1773]: spa.alsa: front:3p: (11 suppressed) snd_pcm_avail after recover: Обрыв канала
pipewire[1773]: spa.alsa: front:3p: (0 suppressed) snd_pcm_avail after recover: Обрыв канала
at-spi2-registryd[1981]: Re-enabling app with pid 2034
at-spi2-registryd[1981]: Re-enabling app with pid 2031
at-spi2-registryd[1981]: Re-enabling app with pid 1917
at-spi2-registryd[1981]: Re-enabling app with pid 2030

Here, if it helps

4

I changed the kernel to TLS 6.18, and everything is working fine