amd virtualization
amd virtualization
Alright, everyone here will at least understand that 3.9 is actually acceptable now. Next, let's try a 2666 memory at 100MHz to eliminate it from consideration. That leaves only the motherboard and power supply units, which unfortunately are often the most challenging to identify.
i think it's mobo's bios issue or bios battery, even when psu is related to voltages, i don't think it would touch only core voltages (always) while leaving the rest of the system rock stable, if you have spare time then feel free to RMA the mobo,
there is a tool called ZenStates (
https://zenstates.protonrom.com/
< latest 0.8 beta ver), it have the function to do OC on startup though some users report it as unstable, while some others as "had no problems with it" , which would be just workaround but at least it would be able to cold boot without problems with that
// feel free to set back the ram's mhz to 3000 and cpu core to 3.9 if didn't done yet
I just tried the latest 0.8 version and it seems to work with all mobile brands. The v0.8 beta 3 isn't the one I tested—it was the 0.7 something. I shared the link in my earlier post. I managed to open it on my AsRock AB350M motherboard using R5 1400, so you're welcome to give it a shot after saving your CPU to stock voltage and clock speed in BIOS.
I ran a test run, but since I'm not close to my R5 1400 CPU, I used TeamViewer to access it. It already has an OC set to 3.6 at 1.35 MHz in BIOS. From afar, I can't fully disable that setting. I entered 3.5 MHz in ZenStates 0.8 beta 3 at 1.4V and clicked "autostart" and "apply on boot." After applying and saving, I rebooted. The clocks and voltages checked out—3.5V and 1.4V—so it boots correctly.
Don't forget to set your BIOS clocks and voltages before saving your desired settings in ZenStates to prevent any boot issues from the BIOS side. Hope this helps with your problem for now.