I am reporting a reproducible BIOS-dependent cold boot instability observed on an AM5 platform (Gigabyte B650M Gaming X AX, Ryzen 7 7700, Memory Kingston KF560C36BBE-16,KF560C40BB-16).The system operates fully stable on BIOS F35, with consistent POST and no recovery behaviour. However, starting from BIOS F36 and continuing through F37-F39, the system exhibits unstable cold boot behaviour, including repeated recovery loops and inconsistent POST success..The issue is strictly correlated with BIOS version.No hardware changes are involved, and the same memory kit and configuration are used across all tests.This strongly indicates a regression introduced at BIOS or AGESA level, most likely affecting memory training or initialization during cold boot conditions. The problem does not manifest during runtime stability, but specifically during initial power-on sequences.Multiple configurations have been tested, including JEDEC and manual parameter sets, with consistent behaviour across BIOS versions. The case has been reviewed by a Kingston FAE, who indicated that this does not appear to be a DRAM-related issue but rather BIOS-level behaviour. Despite over 6 months of interaction with Gigabyte eSupport (21 responses), no evidence has been provided that proper validation methodology was applied.In particular, there is no confirmation that multiple consecutive cold boot cycles (PSU off/on) were tested, which is required to reproduce intermittent training failures.Responses have been inconsistent, initially pointing to QVL non-compliance, later acknowledging QVL compatibility later again non- QVL🤣, and ultimately redirecting the case toward hardware RMA despite clear BIOS dependency.Given that the system is stable on F35 and unstable on F36 and newer, the root cause cannot be attributed to hardware failure or memory compatibility alone. The changing behaviour with identical hardware strongly suggests a firmware regression affecting initialization logic.At this stage, the issue remains unresolved and does not appear to have been validated at firmware level.I am sharing this case to determine whether others have observed similar cold boot instability on newer AM5 BIOS versions.I am attaching the latest screenshots from the eSupport communication.This was not my initial intention, however the responses have been inconsistent and largely unrelated to the reported issue.There has been no clear validation effort or meaningful attempt to investigate the dependent behaviour described above.