CPU [20/08/2024]ASRock DeskMini X600 BIOS "4.03.MEM01" (with RAM voltage settings!!!) - AGESA ComboAM5Pi "1.2.0.0a"

[woofaki]

No matter which one you take, all three are the same (they also cover the PMIC cooling in addition to the DDR5 RAM chips), the only difference between these 3 models being (if you look at the product pictures) that there is one with an engraving/inscription "8G" (for 8GB), another with "16G" (for 16GB) and one without engraving/inscription, that's all.

Thank you i ordered the non engraved ones. I just got the copper heatsinks too but i read in a post here that they need to be trimmed,thus why i got those that are easy to be used without trimming...

 

[nirvana]

Just an update, I ended up running this configuration

I tried 6400 in 1:1 but I didn't manage to stabilise it with the amount of vSOC I was willing to use daily.

I then set extremely loose timings and 2000 FCLK, then tried 2:1 mode and things started getting pretty weird. I found a specific combination of vsoc/vdd/vddq/vddio/vddp that would make it POST at 7800 but impossible to boot windows (I left VPP untouched at 1.8v):

VDD 1.45v
VDDQ 1.35v
VDDIO 1.25v
VDDP 1.15v
VSOC 1.15v

With 4.03.MEM01 BIOS, setting VDD above 1.435v results in VDDQ being ignored and set to 1.44v, so VDDQ was actually 1.44v with those voltages. It was very weird because changing any of the voltages up or down more than 20mv would result in no POST at all. Even setting VDDQ to 1.38v would result in no POST despite it being set to 1.44v by the BIOS.

With these voltages I was able to boot windows @7600 but as soon as I ran any test it immediately failed

VDD 1.40v
VDDQ 1.30v
VDDIO 1.20v
VDDP 1.15v
VSOC 1.20v

It was actually impressive that it managed to boot windows consistently with those voltages but it was unable to run anything (p95, y-cruncher, etc).
I was aware that this configuration was violating the rule of VDDP +100mv < VDDIO, but it was the only configuration that would POST and boot windows. Lowering VDDP to 1.1v would result in no POST, same as increasing VDDIO to 1.25v (to comply with the rule).

I was aware that some boards or memory configurations have specific voltage restrictions at high frequencies, like requiring some delta between some voltages, i.e. 100mv delta between VDD and VDDQ but what I was experiencing was too weird, like not being able to POST if VDDIO is increased by 50mv to 1.25v, but it POSTs again if you also lower VSOC by 50mv to 1.15v, which didn't make sense to me since the only restriction is VSOC having to be lower than VDDIO + 100mv.

Keeping the same voltages and lowering frequency to 7400 made it stable enough to run some p95 tests without errors. At this point I started trying different voltages but things still didn't make sense. Adjusting any voltage up or down would result in not being able to run p95, not being able to boot windows or not being able to even POST. It seemed that I would have to try every possible voltage combination to find the right one, which is too much if all 5 voltages need to be adjusted.

At 7000 with almost the same voltages it was stable enough that I could adjust timings knowing whether they were stable. I was able to push them almost all the way down to the same timings I use at 6200, but still not fully stable probably due to voltages. The timings I ended up with seem to even work at 7200.

I know dual rank is a different beast, but does anyone have any idea of what could be happening? I have the feeling that if I mange to fix whatever is wrong with the voltages and make it stable at 7000 I could also make 7200 or even 7400 work.

I have Nitro Mode enabled with 8x/8x just in case it helps with memory training. I also tried data-eye training (which takes 10 minutes to boot each time) but I didn't notice any difference.

Thank you very much in advance.

It looks like VDDQ at 1.2v helps with stability. I didn't try with such low voltages because everything I tried was pointing to requiring more voltage for signal integrity.

Back to testing I guess..