CPU overheating and shutting down while I game

My CPU is overheating and I don’t know why. I’ve replaced thermal paste, I am running a MSI brand cooler and not sure if it’s the cooler dying or not. Can anyone help with this? I’m out of options to be honest.

Is it a liquid cooler or air cooler? If liquid is it a all in one (AIO) or a loop?

We can start with an inxi

inxi -Fazy

Any other logs showing the processes etc?

AIO cooler

Kernel: 6.6.8-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
root=UUID=7fed2da7-3788-487f-9cab-16c56b8aff0a rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Manjaro Linux base: Arch Linux
Type: Desktop System: Gigabyte product: B550 GAMING X v: N/A
Mobo: Gigabyte model: B550 GAMING X v: x.x serial:
UEFI: American Megatrends v: F10 date: 09/18/2020
Device-1: ps-controller-battery-4c:b9:9b:c6:dc:ae model: N/A serial: N/A
charge: N/A status: charging
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA201006
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: 1x32 MiB
Speed (MHz): avg: 2185 high: 2200 min/max: 2200/4650 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 2200
3: 2200 4: 2200 5: 2106 6: 2200 7: 2200 8: 2200 9: 2116 10: 2200 11: 2200
12: 2200 bogomips: 88658
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: XFX 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 bus-ID: 0b:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 21.1.10 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: VG27VQM serial:
built: 2023 res: 1920x1080 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 640x350
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.1.9-manjaro1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (navi22 LLVM
16.0.6 DRM 3.54 6.6.8-2-MANJARO) device-ID: 1002:73df memory: 11.72 GiB
unified: no
API: Vulkan v: 1.3.274 layers: 6 device: 0 type: discrete-gpu
name: AMD Radeon RX 6700 XT driver: amd v: 2023.Q4.2 (LLPC)
device-ID: 1002:73df surfaces: xcb,xlib
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: 0b:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Sony DualSense wireless controller (PS5)
driver: playstation,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 1-1:2 chip-ID: 054c:0ce6 class-ID: 0300
Device-4: Jieli USB Composite Device
driver: hid-generic,snd-usb-audio,usb-storage,usbhid type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4:3 chip-ID: 4c4a:4155
class-ID: 0300 serial:
API: ALSA v: k6.6.8-2-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.0.0 status: off with: pipewire-media-session
status: active tools: pw-cli
Server-4: PulseAudio v: 16.1 status: active with: 1: pulseaudio-alsa
type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 08:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac:
Device-2: Sony DualSense wireless controller (PS5)
driver: playstation,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 1-1:2 chip-ID: 054c:0ce6 class-ID: 0300
Local Storage: total: 4.09 TiB used: 958.39 GiB (22.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: fw-rev: 2B2QEXE7 temp: 26.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000NM0035-1V4107
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: fw-rev: TN05 scheme: GPT
ID-1: / raw-size: 465.46 GiB size: 457.09 GiB (98.20%)
used: 431.63 GiB (94.4%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 296 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Alert: No swap data was found.
System Temperatures: cpu: 89.2 C mobo: 20.0 C gpu: amdgpu temp: 30.0 C
mem: 30.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Processes: 322 Uptime: 1m wakeups: 0 Memory: total: 64 GiB note: est.
available: 62.72 GiB used: 2.42 GiB (3.9%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1709 libs: 455 tools: pamac pm: flatpak pkgs: 0
Shell: Zsh v: 5.9 default: Bash v: 5.2.21 running-in: yakuake inxi: 3.3.31

Please use the </> button to format your post.
I should have included this guide

Yeah that looks not so good.

You have BIOS updates.
Covering everything from security to … support for ryzen 5000 cpus
So … I would do that if I were you.
If my search is correct:

Okay. How would I have that updated?

You must consult the manufacturer.

I think they support something called ‘q-flash’ that will allow you to update from the file on a USB.

Will do.

I have another cooler, Corsair. But I don’t know if it’s the cooler that is failing, or not.

I would try whatever you find easier, but @cscs may also be onto something if your bios doesn’t officially support your CPU.

Upgrading your BIOS should be high on your todo list. Your current BIOS F10 is from 2020; there is a stable F15 BIOS available from Gigabyte, along with several beta versions listed above it.

I’d suggest trying the F15 first, and see if that improves things, otherwise, the latest F16g (beta) might be the better choice.

Some games can (and do) demand a lot from a machine; temperatures can soar; often to the point of causing what seems to be a crash. In fact, this is usually by design as a safety measure, preventing your CPU from being damaged.

If updating your BIOS shows no improvement, then seriously rethink your cooling and ventilation strategy. The cooling fan that comes with an off-the-shelf system, for example, is rarely sufficient for high loads, and simply replacing it with something similar (or with pretty rgb effects) is unlikely to improve things.