PC does not boot, "hardware error" message

My system does not start anymore. It will start into grub (I have a dualboot system with windows) and then will fail. If Windows was chosen it will just crash, but if I boot Manjaro there appears an error message. The exact same behaviour occurs when I try to boot Manjaro from my usb-stick.

Error message:

[    2.813234] mce: [Hardware Error]: CPU 11: Machine Check: 0 Bank 5: bea000000
0000108
[    2.813240] mce: [Hardware Error]: TSC 0 ADDR 1ffffc0e17554 MISC d01200010000
0000 SYND 4d000000 IPID 500b000000000
[    2.813244] mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1677087635 SOCKET
0 APIC d microcode 8701021
/dev/nvme0n1p5: recovering journal
/dev/nvme0n1pm: clean, 624394/19202048 files, 19788836/76800000 blocks

(One time the microcode was 8701030, otherwise the error message was the same)

What kind of hardware issue can this be? Fedora Linux (live-usb in basic graphics mode) works. In the normal mode Fedora does not work either, but if it works in the basic-graphic mode, how can this be a hardware issue?

System Specs (via fedora live-usb)
 inxi -F
System:
  Host: localhost-live Kernel: 6.5.6-300.fc39.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 5.27.8 Distro: Fedora Linux 39 (KDE Plasma)
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2
    serial: <superuser required> UEFI: American Megatrends LLC. v: F16b
    date: 02/08/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 2197 min/max: 2200/4208 cores: 1: 2200 2: 2200 3: 2194
    4: 2200 5: 2200 6: 2195 7: 2200 8: 2200 9: 2195 10: 2196 11: 2193 12: 2200
Graphics:
  Device-1: AMD Hawaii PRO [Radeon R9 290/390] driver: N/A
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.1
    compositor: kwin_wayland driver: N/A resolution: 1024x768
  API: EGL v: 1.5 drivers: kms_swrast,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.5 vendor: mesa v: 23.2.1 renderer: llvmpipe (LLVM 16.0.6
    256 bits)
  API: Vulkan v: 1.3.250 drivers: llvmpipe surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X]
    driver: snd_hda_intel
  Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel
  API: ALSA v: k6.5.6-300.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 0.3.80 status: active
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 18:c0:4d:94:96:b8
Drives:
  Local Storage: total: 4.58 TiB used: 9.04 GiB (0.2%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SKC3000S1024G size: 953.87 GiB
  ID-2: /dev/sda vendor: Seagate model: ST4000VN006-3CW104 size: 3.64 TiB
  ID-3: /dev/sdb model: General UDisk size: 7.62 GiB type: USB
Partition:
  ID-1: / size: 8.56 GiB used: 6.74 GiB (78.8%) fs: ext4 dev: /dev/dm-0
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 35.9 C mobo: 20.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.5 GiB used: 2.39 GiB (15.4%)
  Processes: 334 Uptime: 2m Shell: Bash inxi: 3.3.33

Hi @questionasker, and welcome!

This

and

…makes me think it’s the CPU, While this:

…makes me think it’s the RAM. And what do they have in common? The motherboard.

So that’s what I think.

Because, as the name says, it’s basic and not every part of the hardware is in use. Luckily:

…your storage seems to be fine.

Hope this means something to you!

1 Like

I tested the RAM with Memtest and it worked without any problems

Thank you for the answer, I will try and test the system with a different motherboard.

1 Like

Or… (random thoughts) you might consider triple-checking all of your BIOS settings; and possibly re-seating your CPU and/or RAM.

As we have no other useful information about your machine, additional assistance might come very slowly. Good luck.

What settings could be relevant for this kind of error?

I have already unplugged and replugged the CPU and RAM once

What information is necessary or could be useful to further analyze the problem?

Thanks :slight_smile: