Hi everyone,

Very new to RAM OC'ing but very interested in learning everything by testing.
I'm running an AMD Ryzen 7 9850X3D on an Asus STRIX X870-F board, combined with a G.Skill F5-6000J3038F16GX2-TZ5NR DDR5 kit. Overall I'm very happy with the performance even tho it was a pre-build system.

In HWInfo64 I noticed the memory running at 3000MHz as well as the UCLK running at 3000MHz. I assume the UCLK is adjusting to run in a 1:1 ratio with the memory.
the FCLK is 'only' running at 2000MHz and ChatGPT is telling me I could reduce the latency between the CPU and RAM if I bump this higher. While it's actually not really OC'ing the RAM but actually the CPU I want to play with this.

How plausible is it that I could make the FCLK run at 3000MHz? So they run at a 1:1:1 ratio? If I try to bump this speed, at what intervals would you all recommend I do this? And how big are the chances that I'm putting too much of a burden on the infinity fabric?

Thanks for reading my stuff :) appreciated!

This will be trial and error and will depend on many variables of the quality of your hardware silicon and motherboard and it's Bios
Try bumping it slowly step by step and test stability and performance... on my Asrock X870 I could only do 2133 Fclock, any higher it would no longer boot... but that was early AM5 days, so Biosses have matured big time overtime...

On 4/11/2026 at 4:02 PM, Leeghoofd said:

This will be trial and error and will depend on many variables of the quality of your hardware silicon and motherboard and it's Bios
Try bumping it slowly step by step and test stability and performance... on my Asrock X870 I could only do 2166 Fclock, any higher it would no longer boot... but that was early AM5 days, so Biosses have matured big time overtime...

What increments do you recommend testing? Are there 'logical' increases, ratio-wise?

The system I bought from them is this one so I assume cooling should be sufficiënt for CPU overclokcing, right? I'm sure the guys from FENN would be happy to test this for me but I want to enjoy / learn this myself so I'm not going to bother asking them.

PS: Are you Dutch Leeghoofd?

Jups uit Belgie, Fenn Systems ja mooie builds

But is the system designed to run "asynchronously"? (RAM at 3000 MHz and FCLK at 2000 MHz).?
But isn't the 1:1:1 ratio on DDR5 suicidal?
I think that, even under nitrogen, the FCLK doesn't go much beyond 2400-2500 MHz on Ryzen. Reaching 3000 MHz would require such high voltage that the chip could degrade from "electrical death" even if it's frozen.

Edited April 14Apr 14 by TheFyxxxer

4 hours ago, Leeghoofd said:

Jups uit Belgie, Fenn Systems ja mooie builds

Leuk!

Ja ik ben best tevreden van het systeem, zeer proper in mekaar gestoken!

2 hours ago, TheFyxxxer said:

But is the system designed to run "asynchronously"? (RAM at 3000 MHz and FCLK at 2000 MHz).?
But isn't the 1:1:1 ratio on DDR5 suicidal?
I think that, even under nitrogen, the FCLK doesn't go much beyond 2400-2500 MHz on Ryzen. Reaching 3000 MHz would require such high voltage that the chip could degrade from "electrical death" even if it's frozen.

Hey, thanks for your feedback. So I shouldn't expect to get it going to 3000 haha..

Unfortunately, I only have a quick overview of that beautiful processor. I'm currently playing with older stuff. I still think FCLK at 2166 is a good compromise for Zen 5. Technically, you should focus on tightening the secondary timings instead of chasing the FCLK frequency... you should get huge performance gains with AM5.
It's a structural limitation of AMD's Chiplet architecture that we've been carrying around since the first Ryzens. The 1:1:1 ratio that worked well with DDR4 3600-3800 MHz has become impossible. U are forced to "unhook" the FCLK and let it run at its maximum stable rate, then focus on synchronizing only the memory controller (UCLK) with the RAM (MCLK).
If AMD were to design an infinity fabric that scales linearly with RAM...Ryzen processors would become power monsters, almost a whole other category of CPU!!!

If you can keep the temperatures in check and tighten the secondary timings, that 96 MB of cache becomes a nuclear weapon in benchmarks...illegal stuff lol! 🚨