06-07-2025 03:05 PM - edited 06-07-2025 03:06 PM
Hey,
So I've tried the new beta bios, noticed a new DIMM fit functionality, but somehow can't get it to work properly.
1. Simple dimm fit somehow passed in like 30 minutes or so, but it shows 30-38-0-0-80 in the DIMM Fit Store, I don't understand the "0" values and I don't see any values that were adjusted, neither in BIOS nor in zen timings.
2. I tried DIMM Fit Pro several times and failed miserably. I tried different selection rules, I gave it much more time than estimated worst times. Computer at first seemed like it was trying to do something, there were few restarts, diag LEDS were changing, blinking, but finally it stayed on yellow LED and seemed to stop doing anything. For example with below settings, I'm sure the Trtp can be lower than 24, but just for science and what I assumed will be a quick test I did it with the following parameters:
And same thing happened. Few restarts at the beginnig, and then yellow LED. I gave it like 40 minutes even though estimate was 11 minutes, but nothing changed. All tests that I did seem that my current settings are stable enough. OCCT, MemTest5, some light loads and gaming work fine for me without any signs of instability or bluescreens, even though I'm pushing my luck with 6400MT on 7950x3d.
Has anybody got it working successfully?
06-07-2025 11:51 PM
Hi @Garreth1
Depending on the memory configuration, running DIMM Fit can take several hours or more. Pro can take longer, depending on what parameters are selected. Q-Code 15 is a training code. DIMM Fit may adjust ODT settings and run a series of tests multiple times while running, which will result in periods where it appears not to be doing anything.
It's important to know;
1. Condition of the system's memory overclock before entering DIMM Fit
2. Use your most stable settings
3. If the system is already stable, there may be no benefit.
To have the best chance of improving stability, the system should ideally be able to pass stability tests such as Karhu RAM Test or HCI Memtest Pro and will only throw errors into coverage.
Here's a basic example of where running Deterministic Based on Worst Margins helped.