PC shuts down

Hey, I have the system up do date with Gnome and a couple of weeks after install it shuts down on its own, I noticed it while gaming but I sometimes come back home to an off PC as well.

Shows some CPU related errors when rebooting.

I didn’t make any hardware changes and temps are on the cool side (according to Windows monitoring), any help in diagnosing this would be appreciated!

When you say “shuts down on its own”, do you mean a normal shutdown procedure is initiated, or it simply ceases to have power mid-session?

Reboots itself without input.

Are you able to share your hardware spec:
inxi -Fxxc0z

And if it’s a desktop system, make and model (or at least wattage) of your power supply?

> System:
  Kernel: 6.9.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
  Desktop: GNOME v: 46.1 tk: GTK v: 3.24.42 wm: gnome-shell dm: GDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX B550-F GAMING v: Rev X.0x
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 2803
    date: 04/27/2022
CPU:
  Info: 6-core model: AMD Ryzen 5 5600 bits: 64 type: MT MCP arch: Zen 3+
    rev: 2 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2462 high: 4750 min/max: 2200/6063 boost: disabled
    cores: 1: 4750 2: 2200 3: 2200 4: 2200 5: 2800 6: 2200 7: 2200 8: 2200
    9: 2200 10: 2200 11: 2200 12: 2200 bogomips: 114042
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: ASUSTeK driver: nvidia
    v: 550.78 arch: Pascal pcie: speed: 8 GT/s lanes: 16 bus-ID: 0b:00.0
    chip-ID: 10de:1b80
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
    compositor: gnome-shell driver: X: loaded: N/A unloaded: modesetting
    failed: nvidia alternate: fbdev,nouveau,nv,vesa gpu: nvidia note: X
    driver n/a, try sudo/root display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 96
  Monitor-1: DP-2 pos: primary,left res: 2560x1440 dpi: 90
    diag: 842mm (33.15")
  Monitor-2: HDMI-0 pos: right res: 1920x1080 dpi: 102 diag: 547mm (21.54")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 0b:00.1 chip-ID: 10de:10f0
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 0d:00.4 chip-ID: 1022:1487
  Device-3: Universal Audio Volt 1 driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 2b5a:0020
  API: ALSA v: k6.9.1-arch1-1 status: kernel-api
  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
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s
    lanes: 1 bus-ID: 07:00.0 chip-ID: 8086:2723
  IF: wlan0 state: up mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3
  IF: enp10s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-7.2:9 chip-ID: 8087:0029
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 4.54 TiB used: 1.53 TiB (33.6%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN770 1TB
    size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 44.9 C
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS500G2B0C-00PXH0
    size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 53.9 C
  ID-3: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-4: /dev/sdb vendor: Western Digital model: WD10JPVT-00A1YT0
    size: 931.51 GiB type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 serial: <filter>
  ID-5: /dev/sdc vendor: Seagate model: WDC WDS256G1X0C-00ENX0
    size: 238.47 GiB type: USB rev: 3.2 spd: 10 Gb/s lanes: 1 serial: <filter>
  ID-6: /dev/sdd vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
    type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 914.83 GiB used: 232.63 GiB (25.4%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 1022 MiB used: 300 KiB (0.0%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 49.9 C mobo: N/A gpu: nvidia temp: 52 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
  Memory: total: 32 GiB available: 31.25 GiB used: 2.62 GiB (8.4%)
  Processes: 321 Power: uptime: 1h 18m wakeups: 0 Init: systemd v: 255
    default: graphical
  Packages: 1048 pm: pacman pkgs: 1042 pm: flatpak pkgs: 6 Compilers:
    gcc: 14.1.1 Shell: Bash v: 5.2.26 running-in: kgx inxi: 3.3.34

Power Supply: EVGA 450W
1 Like

A 450W PSU for that system is rather low. Brand new, that might have been borderline, but as a PSU ages, it’s power output starts to drop. Some calculators put it well below the recommended wattage for that system.

The main symptoms of insufficient power, are RAM related issues, which might present themselves as crashes and resets (hence why I asked about the PSU).

Now, I’m not going to say I’m totally convinced that’s the cause, just that I’d flag it as a possibility.

If you don’t have a stronger PSU you can drop in there and test with, you might try removing any non-essential components, to reduce power draw. I see you have a few hard drives, for example. If you have a lesser GPU of that generation handy, perhaps try that instead.

2 Likes

Thanks for looking into this.

I know the PSU is cutting it close but only started having issues a few weeks ago when I was trying out Fedora, and coming back to Endeavour the issue started a couple of weeks after install, could it be some new Nvidia driver or something that uses more power than normal? Seems to me like it’s random spikes as it happens once per evening at non specific events.

I can’t try another PSU but I can compare with Windows which doesn’t have such issue even though I run the GPU overclocked in there.

Edit: I just noticed from the readings above that the CPU runs at 4750Mhz which seems incorrect as it is set to 4700Mhz in the bios which is the maximum stable overclock, that might be the issue even though again, I’ve seen it spike to 4800 in Windows with no issuue.

Certainly, stop all overclocking. If the issue persists in a non-overclocked state, then troubleshoot.

You might also check your RAM frequency and timings, ensuring that these are set in accordance with both RAM and CPU spec.

Reading this thread got me curious as to the power supply in my hardware. Interestingly enough, none of my linux setups report anything I can find about a PSU/power supply when executing: inxi -Fxxc0z

This is the case with my 2019 iMac, 2011 MacBookPro laptop, and Dell Optiplex all running current/recent EOS … Is there another way to discern one’s PSU wattage without cracking open the tin? :thinking:

Not really, that information isn’t usually reported to any operating system. You could buy one of those outlets that has a meter on it, so that you could look at it directly.

Interesting - that’s what I thought. It was the data dump from the OP above that got me wondering…

@Gendo

I would suggest updating the UEFI firmware (Bios). There are seven newer updates than your current version 2803 dated 04/27/2022. The latest version includes a new AMD AGESA ComboV2PI 1.2.0.Ca. as well as new security fixes. I would also agree the power supply is on the light side but the Bios update is where i would start. Having said that I would also use the default settings for ram.

You could look at the temperatures in the system with e.g. glances.
Inxi already showed something, looks ok. Glances should show more details.

Thank you all for the feedback! and sorry for the late reply!

It was indeed the overclock, I didn’t even look into it at the beginning as i forgot it was there. Indeed it was the culprit and backed down a tad with no issues to report.

I will update my bios for sure, I’m sure i did not long ago but maybe the update didn’t stick.

1 Like