Help troubleshooting constant freezes after autoreboot

[Morke]

Hi all
I built a home Proxmox server using my old pc.
Sometimes and only sometimes after I'm AFK, the server autoreboots and freezes.
I have to manually start it again.
The freeze means the server is inaccessible both remotely or locally. Remotely shows up as "Can't reach", and I can't ping it at all.
Locally it shows as a black screen. No output.

Edit: Today the image froze in the login console after 48hs of running

This issue doesn't happen if I manually reboot the server.
I've run CPU and RAM tests and haven't found any issues.
I've also checked the journal but didn't find any consistent error showing up at the log after freezes.
I'm not sure what to do next to troubleshoot the issue.
This smells like a PSU or Motherboard issue, but I'm not sure how to validate or if its possible in Proxmox.


The hardware is:

|| || |Motherboard|Gigabyte GA-AX370-Gaming K5|

|| || |CPU|AMD Ryzen 5 1600|

|| || |RAM|16 GB DDR4 |

|| || |Disks|- 1 SSD for boot - 2× 512GB SSDs for VMs - 4× 4TB HDDs for storage (ZFS pool)|

|| || |GPU|NVIDIA (GF108)|

|| || |Proxmox Version|8.4.x (with kernel 6.8.12-8-pve)|

 

[mariol]

Hello @Morke, and welcome to the proxmox community.

What filesystem you are using?
Could it be that the RAM was running out of space? How much RAM is allocated to the VMs/CTs?

Please attach the journal from the time when the freeze is also included. Please adjust date and time.

journalctl --since "2025-10-01 00:00" --until "2025-10-03 16:00" > "$(hostname)-journal.log"

 

[MarkusKo]

just some ideas for troubleshooting

update your bios and try to disable c-states there, some users had instabilities with amd cpu's and disabling c-states helped
your mainboard has an intel nic, check if you are affected by the e1000e bug - check dmesg for entries with " e1000e Detected Hardware Unit Hang"