X570D4U-2L2T — VCCM BMC thresholds still broken in BMC 1.35
The VCCM sensor thresholds on the X570D4U-2L2T (and likely all X570D4U variants) are still hardcoded at Upper Critical 1.32V / Non-Recoverable 1.38V in BMC firmware 1.35.
The Ryzen 3900X (and other Zen2/Zen3 CPUs) pulls ~1.73V on VCCM under normal operation. This triggers a false positive Non-Recoverable event, causing protective shutdowns on perfectly healthy hardware.
The only workaround is running ipmitool sensor thresh VCCM upper 1.72 1.75 1.80 at every single boot — because BMC thresholds reset on every BMC reboot.
This bug has been reported for years on Level1Techs and other forums. It affects every X570D4U user running Ryzen CPUs at stock settings.
Questions for ASRockRack
- Is a BMC firmware update planned to correct the VCCM thresholds?
- If not, can you at minimum make the thresholds persistent across BMC reboots?
- Is there a way to set persistent sensor thresholds via Redfish that I'm missing?
Running a server board that triggers false emergency shutdowns out of the box is not acceptable. This should have been a day-one firmware fix.
BIOS: P1.70 | BMC: 1.35.0 | CPU: Ryzen 9 3900X | Board: X570D4U-2L2T