My Proxmox 9 server keep hanging, completely frozen !?

shodan

Active Member
Sep 1, 2022
210
58
33
Hi,

I cobbled together a bunch of parts into a nice new-to-me Proxmox server.

Unfortunately, it keeps hanging after a couple of hours no matter what I do !

This server has

Code:
CPU0: AMD Ryzen 7 1700 Eight-Core Processor (family: 0x17, model: 0x1, stepping: 0x1)

Gigabyte Technology Co., Ltd. B450M DS3H V2/B450M DS3H V2, BIOS F67h 08/12/2025

EFI v2.7 by American Megatrends

ACPI=0xbcf0b000 ACPI 2.0=0xbcf0b014 SMBIOS=0xbd9f2000 SMBIOS 3.0=0xbd9f1000 MEMATTR=0xb777f398 ESRT=0xb98f6b98 MOKvar=0xbda1f000 INITRD=0xb68aee18 RNG=0xbc830018

Memory slots populated: 1/4

These devices

Code:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller (rev 01)
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 16)
06:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
06:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
07:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor (PSP) 3.0 Device
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
08:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
08:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller


So, I tried testing stuff


Memtest ran a whole day, zero errors

Then I installed windows 10, I ran Prime95 all day, next day I ran a GPU stress test in a loop, CPU at
60C, GPU at 80C all day, not a single crash, hang, error or even stutter !!

Then I installed debian 13 standard without a graphical interface, left that running a few days, no issues

Lastly I installed debian 13 with KDE desktop, left that running a few days, still no hang, no crash, nothing wrong !


Now I've reinstalled Proxmox 9 and it's always hanging after a while.

I'm 99% there's nothing exactly wrong with the hardware.



Here is what happens in the logs when it crashes (nothing)

Code:
Sep 21 12:56:45 proutmox pvescheduler[1301]: starting server
Sep 21 12:56:45 proutmox systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
Sep 21 12:56:45 proutmox systemd[1]: Reached target multi-user.target - Multi-User System.
Sep 21 12:56:45 proutmox systemd[1]: Reached target graphical.target - Graphical Interface.
Sep 21 12:56:45 proutmox systemd[1]: Startup finished in 6.573s (firmware) + 8.144s (loader) + 5.579s (kernel) + 10.771s (userspace) = 31.069s.
Sep 21 12:59:06 proutmox chronyd[962]: Can't synchronise: no selectable sources
Sep 21 12:59:58 proutmox systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Sep 21 12:59:59 proutmox systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Sep 21 12:59:59 proutmox systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Sep 21 13:07:27 proutmox systemd[1]: Starting logrotate.service - Rotate log files...
Sep 21 13:07:27 proutmox pvefw-logger[757]: received terminate request (signal)
Sep 21 13:07:27 proutmox pvefw-logger[757]: stopping pvefw logger
Sep 21 13:07:27 proutmox systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Sep 21 13:07:28 proutmox systemd[1]: pvefw-logger.service: Deactivated successfully.
Sep 21 13:07:28 proutmox systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Sep 21 13:07:28 proutmox systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Sep 21 13:07:28 proutmox pvefw-logger[3052]: starting pvefw logger
Sep 21 13:07:28 proutmox systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Sep 21 13:07:28 proutmox systemd[1]: logrotate.service: Deactivated successfully.
Sep 21 13:07:28 proutmox systemd[1]: Finished logrotate.service - Rotate log files.
Sep 21 13:12:17 proutmox systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Sep 21 13:12:17 proutmox systemd-tmpfiles[3822]: /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring.
Sep 21 13:12:17 proutmox systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Sep 21 13:12:17 proutmox systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Sep 21 13:17:01 proutmox CRON[4584]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 21 13:17:01 proutmox CRON[4586]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 21 13:17:01 proutmox CRON[4584]: pam_unix(cron:session): session closed for user root
Sep 21 13:24:20 proutmox chronyd[962]: Source 149.56.19.163 replaced with 207.210.46.249 (2.debian.pool.ntp.org)
Sep 21 13:26:37 proutmox smartd[896]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 70 to 74
Sep 21 14:00:17 proutmox systemd[1]: Starting apt-daily.service - Daily apt download activities...
Sep 21 14:00:17 proutmox systemd[1]: apt-daily.service: Deactivated successfully.
Sep 21 14:00:17 proutmox systemd[1]: Finished apt-daily.service - Daily apt download activities.
-- Boot 0bf3e923f6304fe59ad8b9be83ccadb8 --
Sep 21 21:02:14 proutmox kernel: Linux version 6.14.8-2-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-2 (2025-07-22T10:04Z) ()
Sep 21 21:02:14 proutmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.14.8-2-pve root=/dev/mapper/pve-root ro quiet
Sep 21 21:02:14 proutmox kernel: KERNEL supported cpus:
Sep 21 21:02:14 proutmox kernel:   Intel GenuineIntel
Sep 21 21:02:14 proutmox kernel:   AMD AuthenticAMD
Sep 21 21:02:14 proutmox kernel:   Hygon HygonGenuine
Sep 21 21:02:14 proutmox kernel:   Centaur CentaurHauls
Sep 21 21:02:14 proutmox kernel:   zhaoxin   Shanghai
Sep 21 21:02:14 proutmox kernel: BIOS-provided physical RAM map:


So I'm at a loss of what to try next. I imagine something wrong about ACPI or C-States, power management ?
 
I ran my own above post into chatgpt

Here are the avenues it suggest

That the problem is somehow related to "C-state or SMM (System Management Mode)"
That Proxmox 9 is "known to be unstable with a Ryzen 1 CPU on B450 chipset"
That "Ryzen 1xxx has known C6 state bugs"

And to try the following

Code:
Global C-state Control → Disable
Power Supply Idle Control → Set to Typical Current Idle
Cool’n’Quiet → Disable
CPB (Core Performance Boost) → Disable

To try these kernel parameters

Code:
processor.max_cstate=1 idle=nomwait

To try "irqbalance"

To disable XMP/DOCP

Update microcode or AGESA ??


----

So I'm going to try the kernel parameters and see what happens overnight
 
I tried

Code:
processor.max_cstate=1 idle=nomwait


but it still crashed/ hung

Code:
Sep 22 06:25:01 proutmox CRON[9765]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Sep 22 06:25:01 proutmox CRON[9763]: pam_unix(cron:session): session closed for user root
Sep 22 06:42:29 proutmox chronyd[975]: Source 155.138.155.0 replaced with 149.56.19.163 (2.debian.pool.ntp.org)
Sep 22 06:53:09 proutmox systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Sep 22 06:53:09 proutmox systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Sep 22 06:53:09 proutmox systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Sep 22 07:17:01 proutmox CRON[17988]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 22 07:17:01 proutmox CRON[17990]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 22 07:17:01 proutmox CRON[17988]: pam_unix(cron:session): session closed for user root
Sep 22 07:34:14 proutmox chronyd[975]: Source 206.108.0.132 replaced with 206.108.0.133 (2.debian.pool.ntp.org)
-- Boot b66e9dc50dc64a1aa6dbf59a54f4e0d7 --
Sep 22 18:22:14 proutmox kernel: Linux version 6.14.8-2-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-2 (2025-07-22T10:04Z) ()
Sep 22 18:22:14 proutmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.14.8-2-pve root=/dev/mapper/pve-root ro processor.max_cstate=1 idle=nomwait
Sep 22 18:22:14 proutmox kernel: KERNEL supported cpus:
Sep 22 18:22:14 proutmox kernel:   Intel GenuineIntel
Sep 22 18:22:14 proutmox kernel:   AMD AuthenticAMD
Sep 22 18:22:14 proutmox kernel:   Hygon HygonGenuine
Sep 22 18:22:14 proutmox kernel:   Centaur CentaurHauls
Sep 22 18:22:14 proutmox kernel:   zhaoxin   Shanghai
Sep 22 18:22:14 proutmox kernel: BIOS-provided physical RAM map:


I think I'm going to revert to previous proxmox version see if that fixes it !