Hi, fairly new to Linux, i’ve installed Fedora 44 workstation - KDE on my desktop system, but on a fairly regular basis the system keeps crashing requiring a power down reboot. I’m not sure on how to find out what’s causing the system crashes, had it also when booting my computer earlier. I think there’s a log that stores such information, but i’m not sure where to find it, and likely then what to do to rectify. Any help would be much appreciated as i’d really like to stick with Linux.
System - Intel z890, 270K CPU, AMD 9700XT, 48GB CUDIMMs, On board WiFi (7)
Please post the output from running inxi -ezxx in a terminal as pre-formetted text. You may need to install inxi so we have a more complete understanding of your hardware.
Crashes requiring power cycles are often hardware issues. For newer systems, RAM is the prime suspect, so you should run the standalone memtest86+ (careful to avoid imposters!) overnight for a couple nights. For older systems, power supply issues become more frequent. Make sure cooling is not compromised by dust or fans that don’t work. In some environments, corrosion or fungus can cause problems.
System:
Kernel: 7.1.8-200.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A wm: kwin_wayland dm: N/A
Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG MAXIMUS Z890 APEX v: Rev 1.xx
serial: <superuser required> part-nu: SKU Firmware: UEFI
vendor: American Megatrends v: 3103 date: 03/27/2026
CPU:
Info: 24-core model: Intel Core Ultra 7 270K Plus bits: 64 type: MCP
arch: Arrow Lake rev: 2 cache: L1: 2.4 MiB L2: 40 MiB L3: 36 MiB
Speed (MHz): avg: 800 min/max: 800/5500:5400:4700 cores: 1: 800 2: 800
3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 21: 800
22: 800 23: 800 24: 800 bogomips: 176947
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Arrow Lake-S [Intel Graphics] vendor: ASUSTeK driver: i915
v: kernel arch: Xe2-LPG ports: active: none empty: DP-1,DP-2 bus-ID: 00:02.0
chip-ID: 8086:7d67
Device-2: Advanced Micro Devices [AMD/ATI] Navi 48 [Radeon RX 9070/9070
XT/9070 GRE] vendor: Tul / PowerColor driver: amdgpu v: kernel
arch: RDNA-4 pcie: speed: 32 GT/s lanes: 16 ports: active: DP-5
empty: DP-3, DP-4, HDMI-A-1, Writeback-1 bus-ID: 04:00.0
chip-ID: 1002:7550
Display: wayland server: Xwayland v: 24.1.13 compositor: kwin_wayland
driver: gpu: amdgpu display-ID: 0
Monitor-1: DP-5 model: Dell U3421WE res: 3440x1440 hz: 60 dpi: 109
diag: 867mm (34.1")
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: iris
device: 2 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi wayland:
drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.6 glx-v: 1.4
direct-render: yes renderer: AMD Radeon RX 9070 XT (radeonsi gfx1201 ACO
DRM 3.64 7.1.8-200.fc44.x86_64) device-ID: 1002:7550 display-ID: :0.0
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
driver: mesa radv device-ID: 1002:7550 device: 1 type: integrated-gpu
driver: mesa intel device-ID: 8086:7d67 device: 2 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: speed: 32 GT/s lanes: 16
bus-ID: 04:00.1 chip-ID: 1002:ab40
Device-2: Intel 800 Series Family Audio Context Engine vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 80:1f.3 chip-ID: 8086:7f50
Device-3: HP HyperX QuadCast S driver: snd-usb-audio,usbhid type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-12.3.3:14 chip-ID: 03f0:0294
Device-4: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-4:3 chip-ID: 0b05:1b9b
API: ALSA v: k7.1.8-200.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.8 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 RTL8126 5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie:
speed: 8 GT/s lanes: 1 port: 3000 bus-ID: 84:00.0 chip-ID: 10ec:8126
IF: eno1 state: down mac: <filter>
Device-2: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
driver: iwlwifi v: kernel pcie: speed: 8 GT/s lanes: 1 bus-ID: 86:00.0
chip-ID: 8086:272b
IF: wlp134s0f0 state: up mac: <filter>
Bluetooth:
Device-1: Intel BE200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-14:10 chip-ID: 8087:0036
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.4
lmp-v: 13
RAID:
Hardware-1: Intel Core Ultra 200 Series Processors VMD driver: N/A v: N/A
bus-ID: 00:0e.0 chip-ID: 8086:ad0b
Drives:
Local Storage: total: 20.01 TiB used: 554.94 GiB (2.7%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X 2000GB
size: 1.82 TiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 38.9 C
ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN850X 2000GB
size: 1.82 TiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 33.9 C
ID-3: /dev/sda vendor: Western Digital model: WD20EARX-00ZUDB0
size: 1.82 TiB speed: 6.0 Gb/s serial: <filter>
ID-4: /dev/sdb vendor: Seagate model: ST16000DM001-3Y4103 size: 14.55 TiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 1.82 TiB used: 235.93 GiB (12.7%) fs: btrfs
dev: /dev/nvme1n1p3
ID-2: /boot size: 1.9 GiB used: 665 MiB (34.2%) fs: ext4
dev: /dev/nvme1n1p2
ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
dev: /dev/nvme1n1p1
ID-4: /home size: 1.82 TiB used: 235.93 GiB (12.7%) fs: btrfs
dev: /dev/nvme1n1p3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A gpu: amdgpu temp: 34.0 C
mem: 36.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 48 GiB note: est. available: 46.3 GiB used: 5.88 GiB (12.7%)
Processes: 579 Power: uptime: 1h 52m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 16.1.1
Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.41
I’ll look at running Memtest86+. The system, PSU, coolers etc are all new - my last was all rattling due to age and worn bearings, so replaced all fans and PSU for my sanity from the noise.
New sometimes means “Never Ever Worked”. Be suspicious of any components that were priced under the current market. At work IT made bulk purchase of PC’s that were build with cables with very loose connectors. Some cables came off in shipping. Systems were generally OK until someone moved office or took one on an ocean-going research vessel. Did you reuse any existing cables?
@spartan47 Is the console unresponsive or is the host just off the network?
If you are connecting to a Wi-fi 7 router, you may be encountering a problem with MLO. For my testing, there would be wi-fi connectivity for 5 minutes, then something times out on one of the multiple links and all traffic stops. For this issue, you need to grab the wpa_supplicant v2.12 source from the upstream source (Linux WPA Supplicant (IEEE 802.1X, WPA, WPA2, WPA3, RSN, IEEE 802.11i)) and build it. After you’ve built it, you must boot single user in order to install it. Fedora hasn’t updated to v2.12 yet.
I’ve recently battled both types of problem, tho I use GNOME desktop for my GUI.
The computer crashes completely - gow’s to a screen showing something like a QR code ( which isn’t a QR code) then I have to power down and reboot. Just running Memtest now. All cables are new.
It indicates kernel panic
Does any of these line up with your system?
It may also help to have the logs from the previous boot after the crash.
journalctl -b -1 -p err --no-pager --no-hostname
if you are suspicious of the hardware at all, It might or might be worth the time to run memtest86. I have had several bad sticks in the last set of DDR4 no parity sticks on my current machine.
The test can take some time to run. I usually run my machine overnight.
If you get a large number of errors, it would also be worth it to check bios settings and other related issues.