Random shutdowns

[undo]

So i have been using Proxmox for a couple of months now so im pretty new to it. I have been having this problem where sometimes after a couple of hours the pc running Proxmox just powers off. This happens sometimes after hours sometimes it lasts a couple of days but the max i have been able to run my pc with Proxmox is 4 days. The specs of the pc running Proxmox are,

Mobo: x99 dual CPU (chinese sadly)
CPU: 2x intel xeon E5-2670 v3
Ram: 4x 16GB 2133Mhz ECC (Soon upgraded to 8x)
PSU: 500 watts (i tested how much watt the pc is pulling when running vms and containers and its only using max 300watts, so i think its not a PSU problem)

I have been looking at the syslog to see what the problem could be but like i said im new to the whole Proxmox thing so im not sure what is considered good or bad. I will show you some of the syslog data from before and after the reboot. what is also weird is that it says "reboot" but the pc never really restarts by itself. It just shuts down and never really restarts. I notice that it shut down when my Home assistant is not responding or my plex media is not playing.

Feb 21 15:23:30 Proxmox-Server pvedaemon[108482]: <root@pam> successful auth for user 'root@pam'
Feb 21 15:23:56 Proxmox-Server pvedaemon[311976]: starting vnc proxy UPIDroxmox-Server:0004C2A8:00860447:63F4D3FC:vncproxy:102:root@pam:
Feb 21 15:23:56 Proxmox-Server pvedaemon[108482]: <root@pam> starting task UPIDroxmox-Server:0004C2A8:00860447:63F4D3FC:vncproxy:102:root@pam:
Feb 21 15:23:57 Proxmox-Server pvedaemon[108482]: <root@pam> starting task UPIDroxmox-Server:0004C2AC:0086048E:63F4D3FD:vncproxy:101:root@pam:
Feb 21 15:23:57 Proxmox-Server pvedaemon[311980]: starting vnc proxy UPIDroxmox-Server:0004C2AC:0086048E:63F4D3FD:vncproxy:101:root@pam:
Feb 21 15:23:57 Proxmox-Server pvedaemon[108482]: <root@pam> end task UPIDroxmox-Server:0004C2A8:00860447:63F4D3FC:vncproxy:102:root@pam: OK
Feb 21 15:24:11 Proxmox-Server pvedaemon[108482]: <root@pam> end task UPIDroxmox-Server:0004C2AC:0086048E:63F4D3FD:vncproxy:101:root@pam: OK
Feb 21 15:24:11 Proxmox-Server pvedaemon[312053]: starting vnc proxy UPIDroxmox-Server:0004C2F5:00860A3C:63F4D40B:vncproxy:102:root@pam:
Feb 21 15:24:11 Proxmox-Server pvedaemon[100928]: <root@pam> starting task UPIDroxmox-Server:0004C2F5:00860A3C:63F4D40B:vncproxy:102:root@pam:
Feb 21 15:24:13 Proxmox-Server pvedaemon[100928]: <root@pam> end task UPIDroxmox-Server:0004C2F5:00860A3C:63F4D40B:vncproxy:102:root@pam: OK
Feb 21 15:24:13 Proxmox-Server pvedaemon[312057]: starting vnc proxy UPIDroxmox-Server:0004C2F9:00860ACB:63F4D40D:vncproxy:101:root@pam:
Feb 21 15:24:13 Proxmox-Server pvedaemon[108482]: <root@pam> starting task UPIDroxmox-Server:0004C2F9:00860ACB:63F4D40D:vncproxy:101:root@pam:
Feb 21 15:24:14 Proxmox-Server pvedaemon[108482]: <root@pam> end task UPIDroxmox-Server:0004C2F9:00860ACB:63F4D40D:vncproxy:101:root@pam: OK
Feb 21 15:24:14 Proxmox-Server pvedaemon[101175]: <root@pam> starting task UPIDroxmox-Server:0004C2FC:00860B23:63F4D40E:vncproxy:100:root@pam:
Feb 21 15:24:14 Proxmox-Server pvedaemon[312060]: starting vnc proxy UPIDroxmox-Server:0004C2FC:00860B23:63F4D40E:vncproxy:100:root@pam:
Feb 21 15:24:16 Proxmox-Server pvedaemon[101175]: <root@pam> end task UPIDroxmox-Server:0004C2FC:00860B23:63F4D40E:vncproxy:100:root@pam: OK
Feb 21 15:38:31 Proxmox-Server pvedaemon[101175]: <root@pam> successful auth for user 'root@pam'
Feb 21 16:17:01 Proxmox-Server CRON[325503]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 21 16:17:01 Proxmox-Server CRON[325504]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 21 16:17:01 Proxmox-Server CRON[325503]: pam_unix(cron:session): session closed for user root
Feb 21 17:17:01 Proxmox-Server CRON[338386]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 21 17:17:01 Proxmox-Server CRON[338387]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 21 17:17:01 Proxmox-Server CRON[338386]: pam_unix(cron:session): session closed for user root
Feb 21 18:17:01 Proxmox-Server CRON[351301]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 21 18:17:01 Proxmox-Server CRON[351302]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 21 18:17:01 Proxmox-Server CRON[351301]: pam_unix(cron:session): session closed for user root
-- Reboot --
Feb 21 22:33:35 Proxmox-Server kernel: Linux version 5.15.85-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.15.85-1 (2023-02-01T00:00Z) ()
Feb 21 22:33:35 Proxmox-Server kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.85-1-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on
Feb 21 22:33:35 Proxmox-Server kernel: KERNEL supported cpus:
Feb 21 22:33:35 Proxmox-Server kernel: Intel GenuineIntel
Feb 21 22:33:35 Proxmox-Server kernel: AMD AuthenticAMD
Feb 21 22:33:35 Proxmox-Server kernel: Hygon HygonGenuine
Feb 21 22:33:35 Proxmox-Server kernel: Centaur CentaurHauls
Feb 21 22:33:35 Proxmox-Server kernel: zhaoxin Shanghai
Feb 21 22:33:35 Proxmox-Server kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 21 22:33:35 Proxmox-Server kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 21 22:33:35 Proxmox-Server kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 21 22:33:35 Proxmox-Server kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Feb 21 22:33:35 Proxmox-Server kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Feb 21 22:33:35 Proxmox-Server kernel: signal: max sigframe size: 1776
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-provided physical RAM map:
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007834bfff] usable
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x000000007834c000-0x0000000079322fff] reserved
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x0000000079323000-0x0000000079f58fff] ACPI NVS
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x0000000079f59000-0x000000008fffffff] reserved
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed44fff] reserved
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 21 22:33:35 Proxmox-Server kernel: BIOS-e820: [mem 0x0000000100000000-0x000000107fffffff] usable
Feb 21 22:33:35 Proxmox-Server kernel: NX (Execute Disable) protection: active

I really hope someone could help me finding what the problem could be, cause its very annoying specially since im running my smart home, my gaming servers and my media of of proxmox. also dont ask me how these smilies are in there, i just copy/pasted the text from the syslog.

 

[nunner]

Hi,

there's nothing immediately obvious in your syslog that seems to indicate a software failure. Are you sure that you don't have a PSU (or any other hardware, e.g. disk) fault? Do you maybe have a second PSU that you can swap with the current one? iirc the -- Reboot -- line just separates boot entries in journalctl, and doesn't necessarily indicate an actual reboot.

dont ask me how these smilies are in there, i just copy/pasted the text from the syslog.

You can format the logs as code to prevent that from happening

 

[undo]

Even without running any vm's or containers this happens. it happened today 3 times in a matter of 7 hours. no clue what could be the problem i ordered a new motherboard to see if that would help and also new ram sticks in the hope it would help. i just think its weird how this keeps happening