Hi, I’ve the same problem with my pc running 7900x and ddr5 from gskill at 6000mhz cl36 (trident z neo rgb) officially supported in the memory list.
Sometimes don’t even post, I have to shutdown and reboot, but when I simple reboot it doesn’t do anything with two leds on the mb flashing . I enabled memory context, but this have not changed the issue. This is the third memory kit I change with no luck.
The mb is a x670 gigabyte gaming ax with latest bios. Also, to update the bios was a pain in the ass, as the bios ask to reboot and the reboot failed every time
SoC voltage?
@AusWolf i also tried to
Set the vcore Soc from auto to 1.115 but nothing change
That's really low, which is why it didnt help. These companies were setting 1.30v to get 6000 working
(No, we don't recommend that high. 1.20 to 1.25v is needed sometimes however)
Memory context is bad news. It just causes problems. What is does is saves the training part of the memory boot and applies it next time. However AMD didn't design it to work that way so those same settings might be unstable the next boot.
From what i've read those changes are voltage related, the memory training is a resistance test and each boot pushes voltages up til it posts - manual settings tend to alleviate that.
Throw in the auto settings also messing with Uclk/Fclk like how MSI were lowering it to 850 or whatever (This was patched, but it did happen early on with AM5 on at least one board), and the longer boots get explained.
As a made up example of what i've understood to be happening:
Warm boots could work just because voltages, timings etc are still in use from the prior boot - like when the bios safe modes kick in and force you to jedec ram speeds, the incorrect settings are still chosen in the BIOS, but ignored.
1. The system tries to boot with internally saved 'cold boot' settings, fails.
2. It then tries to boot with higher voltages (Some boards just kept going infinitely here, and thats what killed CPUs)
3. Then it tries to downclock the related dividers - 6000MT/s could be 6000/2000/2000, and then it'll try a safer setting (varies by brand and bios) and try 6000/1800/850, or whatever they feel like.
Then if all else fails, it should kick in to the 'failed boot' mode and run safe settings - even if they're just JEDEC defaults.
Usually the fails were at 3 boots in the past, so I can imagine 2-3 attempts at each setting is why things take so long.
My AX370 Gaming 5 was like this with 3200 on the DRAM, it would work fine in everythiing but then have cold boot issues.
It'd fail from every single shutdown, so it wasn't power or temperature related - just that the settings the BIOS used for 3200 were not stable.
You could then load the saved 3200 profile on that first boot, and it'd work problem free until the next shutdown, much like the old 'memory hole' issues on 1156 where you could use various FSB settings and memory dividers to get the exact same clocks working one way, but not another
That system could only be fixed by lowering the RAM speed/IF clock, 3133 works perfectly with zero issues and boots were almost instant - by the time the screen powered on, i was seeing the windows desktop.
TL;DR: If you get these long boots, manually set your DRAM voltage, SoC voltage, MCLK UCLK and FCLK. Keep them in sync and slowly lower them til the issue is gone, and leave it there until new BIOSes come along.
