When troubleshooting an HPE ProLiant DL385 Gen10 server that freezes during the “Memory Initialization” phase of the Power-On Self-Test (POST), one of the most commonly overlooked causes is an outdated BIOS. This issue is particularly relevant when the server has been upgraded with newer AMD EPYC processors, such as the EPYC 7502 from AMD’s second-generation “Rome” family.
Understanding Memory Initialization
Before a server can boot an operating system, the system firmware must perform a series of hardware checks and configuration tasks. One of the most critical stages is memory initialization, often referred to as memory training. During this process, the BIOS configures the processor’s integrated memory controllers, detects installed DIMMs, establishes timing parameters, and verifies that all memory channels can communicate correctly.
If any part of this process fails, the system may stop responding before completing POST.
The Relationship Between BIOS and Processor Support
The BIOS is responsible for initializing the processor and providing the microcode necessary for proper operation. When a server model is introduced, its firmware is designed to support the processors available at that time.
The HPE DL385 Gen10 was originally released when first-generation AMD EPYC processors were current. Later, AMD introduced second-generation EPYC 7002-series processors, including the EPYC 7502. Supporting these newer processors required significant firmware updates from HPE.
A BIOS version released before support for the EPYC 7002 series may not contain the required microcode, memory initialization routines, or processor-specific configuration tables. As a result, the server may be unable to complete memory training and can appear to freeze during the memory initialization stage.
Why the System Freezes at Memory Initialization
Modern AMD EPYC processors contain integrated memory controllers that manage communication with installed DIMMs. During POST, the BIOS must correctly configure these controllers according to the processor model and memory configuration.
If the BIOS does not recognize the installed processor correctly, several issues can occur:
- Memory channels may not initialize properly.
- Timing parameters may be programmed incorrectly.
- Processor-specific memory training algorithms may be unavailable.
- Communication between the CPU and DIMMs may fail.
Because memory training occurs early in the boot process, the server often freezes at the memory initialization screen rather than displaying a more descriptive error message.
Symptoms of an Outdated BIOS
Servers affected by this issue commonly exhibit one or more of the following symptoms:
- POST stops during memory initialization.
- No operating system boot occurs.
- Fans remain running while the screen remains unchanged.
- The Integrated Management Log may contain processor or memory training errors.
- The problem appears immediately after a CPU upgrade.
- The server works with older processors but not with newer EPYC models.
Why This Is Common After Processor Upgrades
Many organizations extend the life of their servers by upgrading processors rather than replacing entire systems. A DL385 Gen10 originally configured with first-generation EPYC processors may operate flawlessly for years.
However, when second-generation processors such as the EPYC 7502 are installed, the system suddenly requires firmware that understands the newer architecture. If the BIOS was never updated during the server’s life cycle, compatibility problems can appear immediately.
In some cases, the server may not even boot far enough to allow a normal firmware update, requiring the use of supported processors or alternative update methods.
How to Verify BIOS Compatibility
Administrators should compare the installed BIOS version against HPE’s processor support documentation for the specific server model. The server’s iLO interface can often display the current System ROM version even when the server fails to complete POST.
If the installed firmware predates support for AMD EPYC 7002-series processors, updating the System ROM should be considered a high-priority troubleshooting step.
Conclusion
After the system BIOS is updated the server boots all the way through:
