AM5 FCLK Overclocking Guide: Tuning, Stress Testing, and Stability Validation
In this AM5 FCLK overclocking guide, we will cover how to tune Fabric Clock, stress-test it with Linpack and y-cruncher, and validate stability on an AM5 Ryzen system.
FCLK Overclocking Basics for AM5
FCLK, or Fabric Clock, is the clock frequency of AMD’s Infinity Fabric interconnect.
On AM5 DDR5 systems, FCLK is usually tuned independently.
FCLK frequency depends on both silicon quality and BIOS/AGESA version. During the early Ryzen 7 9850X3D release window, our chip would instantly crash at 2100 MHz FCLK. With later BIOS/AGESA versions, 2200 MHz became stable on the same chip.
An unstable Curve Optimizer configuration or excessive boost-clock offset can mimic FCLK instability — creating high variation during Linpack and even number variation during y-cruncher VT3.
Before tuning FCLK, make sure your system is running from a known-stable baseline. Your RAM timings, PBO, boost-offset, and Curve Optimizer settings should already be stable. If they aren’t, fix them first, otherwise, Linpack or y-cruncher variation can be caused by something other than FCLK.
Important: Disable your iGPU before proceeding.

Reminder: If your PBO settings or RAM timings are not fully stable, your FCLK tuning results will not be reliable.
If your motherboard allows it, set CPU and VDDCR_SOC/VSOC power and duty control to Extreme for additional stability under load. A higher load-line calibration setting may also help, but this should be determined during your PBO tuning phase.

Voltage Terminology
Before tuning, it’s important to understand the voltage rails involved. BIOS names vary by motherboard vendor, but the terms below match the common AM5/Ryzen terminology used for memory and fabric tuning.
VDDCR_SOC / VSOC
Powers SoC logic, including the DDR5 memory controller and other IOD/SoC IP blocks. Important for RAM and UCLK stability. Do not treat VSOC as the dedicated fabric voltage.
CLDO VDDP / VDDP
The DDR5 bus-signaling / DRAM PHY supply. Affects memory training, boot behavior, and RAM stability.
CLDO VDDG IOD & CCD
Fabric/data-path signaling voltages for the IOD↔CCD Infinity Fabric/GMI links. The primary tools for stabilizing higher FCLK frequencies. These are separate rails and may prefer different values depending on the CPU.
VDDCR_MISC / VDD Misc
A supply rail and the source rail for the internally regulated VDDG fabric voltages. Changing VDD Misc does not automatically change CLDO VDDG CCD/IOD — set and verify VDDG separately.
For FCLK overclocking specifically, the key rails are usually CLDO VDDG IOD and CLDO VDDG CCD, while VSOC should be treated mainly as the voltage needed for your RAM and UCLK target.
FCLK Overclocking and VSOC Behavior
High FCLK can be sensitive to VSOC, but higher VSOC does not universally improve FCLK headroom.
Treat VSOC primarily as the voltage needed for your RAM and UCLK target, and use the lowest stable value — excessive VSOC can hurt FCLK stability. For fabric-specific tuning, focus on CLDO VDDG CCD/IOD.
VSOC requirements are silicon-dependent. On our Ryzen 7 9850X3D, we needed 1.25 V VSOC to run UCLK 3200 MHz.
Before continuing: Find the baseline VSOC voltage that works with your RAM and UCLK target first.
BCLK and Spread Spectrum
Head into the BIOS and find BCLK or CPU Clock Control, then set it to 100.000 MHz. This is a picture from a Gigabyte board:

And here’s the same setting on an ASUS board:

Then look for Spread Spectrum and disable it.

Starting Voltages for FCLK Overclocking
Set VSOC according to your own silicon and memory-controller requirements. Around 1.20 V is a reasonable starting target for many AM5 CPUs, but our sample uses 1.25 V.
Suggested starting values:
- VSOC: Your known-good RAM/UCLK value
- VDDP: 1.00 V
- VDD Misc: 1.10 V
- VDDG CCD: 0.95 V
- VDDG IOD: 0.95 V

The key voltages here are VDDG CCD and VDDG IOD.
On some boards and AGESA versions, Auto rules may make Ryzen Master or HWiNFO report CLDO VDDG CCD/IOD around 1.050 V (1050 mV). Treat this as board/BIOS-dependent behavior, not a universal AMD default.
Some chips may prefer lower IOD voltage. In our FPSHEAVEN consultations, several Ryzen 7 9800X3D systems showed lower Linpack deviation at 970 mV than at 1050 mV, while both settings still passed within accepted deviation. If your system can run lower voltages while remaining stable, that is ideal.
FCLK Overclocking Target
Your goal is to reach 2100 MHz FCLK or higher. 2100 MHz as the first meaningful manual test point.
Recommendation: If you can’t stabilize 2100 MHz after proper testing, do not settle for 2033 MHz or 2067 MHz. Return to 2000 MHz, stop FCLK tuning, and move on to PBO and memory-timing optimization.
For this workflow, use the same test settings after every BIOS change so the results remain comparable.
Required Tools
Download the following tools and place them in a single folder on your desktop.
Required dependency: Install the latest Visual C++ Redistributable Runtime package before running y-cruncher.
Initial BIOS Setup
Enter the BIOS, set FCLK to 2100 MHz, save, exit, and boot into Windows.
Linpack and y-cruncher results can be affected by Windows background processes and other applications, so we’ll run our testing in Safe Mode.
Booting Into Safe Mode
- Open msconfig.

- Go to the Boot tab.
- Select Safe boot.
- Click Apply, then OK.

Your PC will now restart into Safe Mode.
Important: When testing is finished, return to msconfig and uncheck Safe boot. Otherwise, Windows will keep booting into Safe Mode.
Linpack Xtreme Configuration
Once you’re in Safe Mode, open Linpack Xtreme and configure it as shown below.
Step 1 — Enter 2:

Step 2 — Enter 5:

Step 3 — Enter 40:

Step 4 — Answer the remaining prompts:
- Y
- Y
- N
- N — press N when you see the warning

Linpack is now configured to run 40 loops using 10 GB of RAM. You can select 30 loops if you wish to wait less time.
Reading Linpack Results
Each Linpack result has one important value: GFLOPs.
The image below shows a 40-loop, 10 GB result from our Ryzen 7 9850X3D using 950 mV for both VDDG CCD and VDDG IOD.

During FCLK overclocking, Linpack consistency is useful because large GFLOPs swings expose instability quickly. Focus on the difference between the GFLOPs values from each run.
Our standard is strict: we allow a maximum difference of roughly 1.0 to 1.2 GFLOPs at best. Some users may accept variation around 2 GFLOPs, but we prefer tighter consistency.
At the bottom of the result you’ll also see the average and maximum values. These should be as close together as possible but the most important thing is the per-run variation.
This an image from our customer using a 7800X3D. The consistency of the results are excellent.

Example of Unstable Behavior
The altered image below shows what unstable or FCLK-related behavior may look like during Linpack testing.

In this example, some runs show values such as 363, 377, and 375 GFLOPs while others are around 482 GFLOPs. This result is not stable.
At this point, go back into the BIOS and raise VDDG IOD from 950 mV to 1000 mV. We recommend starting with a 50 mV bump to save time during initial testing — once stability is found, you can lower the voltage in 10 mV steps to find the minimum stable value.
Guide limit: In this tuning procedure, keep CLDO VDDG CCD/IOD at or below 1050 mV.
FCLK Tuning Loop
After changing voltage, return to Safe Mode and run the same Linpack test again. When the test is complete, check the GFLOPs variation:
- Is the variation above 2 GFLOPs?
- Is the spread larger than your acceptable limit?
- Are some runs clearly much lower than the rest?
If the variation is still too high, continue tuning:
- Raise VDDG IOD until you reach 1050 mV.
- If variation is still too high, begin raising VDDG CCD by 10–20 mV.
- Retest after every change.
- Do not exceed 1050 mV on either VDDG CCD or VDDG IOD.
If you still can’t achieve consistent Linpack results, set FCLK back to 2000 MHz, stop FCLK tuning, and continue with PBO and memory timing optimization.
Further Validation
After Linpack testing, ou can further validate your AM5 FCLK overclocking stability with y-cruncher and FurMark. We’ll start with y-cruncher and observe the variance between each run.
y-cruncher VT3 Setup in Safe Mode
- Open the folder you created on your desktop.
- Right-click y-cruncher and create a shortcut.
- Right-click the shortcut and open Properties.
- Find the Target field.

At the end of the Target field, append the following command:
stress -TL:3600 VST VT3 -M:28g
The final target should look similar to this:
"C:\Path\To\y-cruncher.exe" stress -TL:3600 VST VT3 -M:28g
This starts y-cruncher for 3600 seconds (one hour) using the VT3 test and 28 GB of RAM. You can adjust the memory amount if needed. Double-click the shortcut to start y-cruncher.

The image above shows our Ryzen 7 9850X3D running VT3.
Reading y-cruncher VT3 Results
During VT3, focus on the first speed value shown in each result line.

We consider a variation of roughly 0.03 to 0.06 acceptable. In our example, the test started around 1.04 and later stabilized around 1.07 — a difference of about 0.03, which is very acceptable.
In Safe Mode, we don’t focus too heavily on y-cruncher speed variation. The main goal is to check whether the test crashes, shows abnormal number variation, or produces WHEA hardware-error events.
A crash may look like this:

You can stress-test with y-cruncher for longer if needed, but one hour is enough for an early stability check. We suggest a minimum of 70 iterations.
Final Confirmation: y-cruncher + FurMark
After passing the Safe Mode checks, leave Safe Mode and boot back into normal Windows. This final AM5 FCLK overclocking test combines CPU, memory fabric, and GPU load to expose instability that may not appear during isolated testing.
- Boot back into normal Windows.
- Download and install HWiNFO.
- Open HWiNFO and press Start.
- Open FurMark and copy the settings shown below.
We use a 1080p monitor, so we keep the FurMark resolution set to 1080p. Start the FurMark test, then minimize it.

Now find your y-cruncher shortcut and run it again. Arrange HWiNFO, FurMark, and y-cruncher on screen so you can monitor all three at the same time.
In HWiNFO, scroll all the way down and look for WHEA Errors. Monitor the WHEA hardware-error counters during the test.

The final FCLK overclocking check should include normal Windows testing, GPU load, and WHEA monitoring. The duration is up to you — FCLK instability often shows up quickly, so even one hour of stress testing can provide useful clues.
Important: Passing every synthetic test does not guarantee perfect real-world stability. FCLK can still be unstable during gameplay.
Use this guide as a repeatable validation process — not a guarantee that every AM5 CPU will reach the same frequency.
Alternative: OCCT Instead of FurMark
You can also use OCCT instead of Furmark to put load into your GPU and FCLK.
- Download OCCT from here and open the application.
- Go to settings and then enable Stop on error and Stop on WHEA error.

- Click on Stability Test and select Combined with 3D Adaptive and VRAM.
- Copy the settings below and start the test.

Wait 10 seconds and then as soon as the test starts, launch y-cruncher.
TL;DR
The short version of this AM5 FCLK overclocking guide:
- Make sure your PBO and RAM tune are rock stable. If unsure, revert to defaults and tune them later.
- Disable the iGPU.
- Set VDDP to 1.00 V, MISC to 1.1 V and VDDG CCD & IOD to 950 mV.
- Boot into Safe Mode and observe Linpack variation. We aim for 1.0–1.5 GFLOPs max.
- If unstable or variation is too high, raise VDDG IOD by 10 mV and retest. If you hit 1050 mV and it’s still unstable, start raising VDDG CCD.
- Stable in Linpack? Run y-cruncher VT3 for further validation — or, if you’re lazy, boot back into Windows and run y-cruncher + FurMark (or OCCT GPU+VRAM) while watching WHEA errors in HWiNFO.
- Rinse and repeat until you’ve found your stable FCLK ceiling.

