cancel
Showing results for 
Search instead for 
Did you mean: 

X670 / X870 resource thread

Shamino
Moderator

ill use this thread to collect some new test bioses for the boards, maybe also to explain some less understood options

to disable cores ccd go here and choose ccd xx bit map down core.
each ones stand for an enabled core
best to disable from the back, ie:
110000
instead of 0011000
after selection press downcore apply changes or discard if made mistake

ocpak/octools

FAQ:
7950x not boosting pass 5.5G -> check that CStates is not disabled
Detailed Explanation on CState Boot Limiter


Test BIOSes:

Spoiler

new:
X3D OC Preset for those MB with asynch BCLK Support: (for simple slight perf boost for X3D)
97792

DOCP/EXPO Tweaked: (for simple timings tightening)
97793

strixe-e 1515 

strixe-f 1515 

strix e a 1515 

crosshair hero 1515 

crosshair gene 1515 

crosshair extreme 1515 

creator 670 1515

creator b650 1515

strix 650E I

strix 670 itx

 

 

for crosshair and strix e-e:

explanation of segment2 Loadline:

dualseg.jpg

customize a heterogenous loadline for a dual segment workload range.

example above shows loadline=L6 when current is in range of 0~40A, and Level4 when current is above 40A.

 

 

 


Adds for x3d

dynamic ccd priority switch with core flex, os / driver agnostic so win10 win11 ok

97403

97404

Algo as follows:
If condition reached and ccd0 specified, then check current mem/cache activity > threshold and hysteresis reached, if fulfilled then switch
If condition reached and ccd1 specified, then check current mem/cache activity <=threshold and hysteresis reached,, if fulfilled then switch
Default hysteresis =4

Can combine multiple algos for ccd priority so combinations are wide

works on non x3d too but of course senseless on it. detailed explanation here.

 

1,761 Views
5,221 REPLIES 5,221

I have a 9800x3d with the x670 e -e and bios 3003 totally wrecked my lian li wireless fans and added several other idiosyncrasies. Ive run bios usb flash after renaming on every bios released going back to my am4 board, have had this board since launch week and this is the first bios that i truly regret installing. you made a wise choice. 

Is that for the crosshair hero x870e also?

Hi,

Yes of course, since your ASUS ROG Crosshair X870E Hero motherboard has an Intel I226-V 2.5Gb Ethernet Controller (in addition to an Realtek 5Gb Ethernet Controller).

Is this for the x870e Crosshair hero? Don't see it on the Asus site

silicongod
Level 8

I don't know about other mobos but ASUS has posted new official BIOS for X670E-F (v3003, dated 06-May-2025):

https://rog.asus.com/au/motherboards/rog-strix/rog-strix-x670e-f-gaming-wifi-model/helpdesk_bios/

Cheers

I guess I got my answer from AI, not sure why everyone is upset or frying their X3D chips. If you left the VSOC on auto it would just be fixed at 1.25V always and safe. Obviously people frying their CPU increased it over AMD's 1.3V recommendation. Per Grok

VSoC for DDR5-6200 with Tight Timings
Typical VSoC Range: Achieving stability at DDR5-6200 with a 1:1 UCLK:MCLK ratio (memory controller and RAM clock synchronized) and a Fabric Clock (FCLK) around 2000–2067 MHz often requires a VSoC between 1.20V and 1.30V.
Users have reported needing 1.25V to 1.28V for stability with 6200 MHz and tight timings on dual-rank (DR) kits, especially with larger capacities like 96GB (2x48GB). For example, one user stabilized 6200 MHz at 1.28V but found errors at lower voltages, while 1.30V was stable but considered high for 24/7 use.

Higher VSoC (e.g., 1.30V) may be needed for marginal IMC samples or dense memory configurations, but stability issues above 6200 MHz often arise due to IMC limitations rather than insufficient voltage.

Tight Timings: Tight timings (e.g., CL30 or lower) increase stress on the IMC, potentially requiring slightly higher VSoC (closer to 1.25–1.30V) compared to looser timings (e.g., CL36). Specific sub-timings like tRP, tRAS, or tRCD also influence stability, and tuning these may reduce the VSoC needed if done carefully.

Safe Fixed VSoC for Everyday Use
Safe VSoC Limit: For 24/7 operation, a fixed VSoC of up to 1.30V is generally considered safe for Ryzen 9000 series CPUs, including the 9950X3D, as AMD has reportedly capped VSoC at this level to prevent damage. However, for longevity and thermal considerations:

Recommended Range: 1.15V to 1.25V is safer and often sufficient for DDR5-6000 to DDR5-6200 with most kits. Many users achieve stability at 1.18–1.25V for 6000 MHz with tuned timings, and 6200 MHz may work at 1.25V with a strong IMC.

Conservative Approach: If possible, aim for 1.20–1.22V to minimize long-term stress on the SoC while maintaining stability. One user reported 1.18V as stable for 6000 MHz with 96GB, suggesting that 6200 MHz might be achievable at 1.22–1.25V with similar configurations.

Risks of High VSoC: Running VSoC at 1.30V continuously is safe per AMD’s limits but may increase heat output and could, in theory, accelerate degradation over many years. Voltages above 1.30V are not recommended and are typically hard-capped by firmware.

Additional Considerations
Memory Kit and Capacity: Dual-rank or high-capacity kits (e.g., 96GB) stress the IMC more, often requiring higher VSoC (1.25–1.30V) compared to single-rank 32GB kits, which may stabilize at 1.20–1.25V. Hynix M-die modules are common in high-speed kits and may need 1.35–1.4V for VDD/VDDQ (memory voltage), but this is separate from VSoC.

FCLK and UCLK: For DDR5-6200, setting FCLK to 2000–2067 MHz and UCLK=MCLK (1:1 ratio) is optimal for performance. FCLK above 2067 MHz often fails to boot reliably without significant voltage increases (e.g., 1.30V+), so 2000 MHz is a safer target.

Motherboard and BIOS: High-end motherboards (e.g., ASUS ROG, ASRock X870E) with robust power delivery and updated BIOS (e.g., AGESA 1.2.0.2a) improve IMC stability, potentially lowering the VSoC needed. Features like ASUS Memory Presets or EXPO profiles can simplify tuning.

Testing Stability: Use stress tests like Prime95, OCCT, or AIDA64 to verify stability. Instability at 6200 MHz may require loosening timings (e.g., CL32 instead of CL30) or increasing VSoC slightly (e.g., from 1.25V to 1.28V) rather than jumping to 1.30V.

Whitebeard47
Level 9

X670 Series Beta Bios 3003 for my Hero Mainboard has a training error, my RAM is not training and I have extreme problems with the BIOS. I rollback to BIOS Version 2904

Yeah I'm staying with 2904. As far as the VSOC issue,  it is NOT an issue. Auto has it pegged at 1.25V, which is far under AMD's 1.3V spec. I tried offsetting it and no post. Then I manually put in values and tested for stability.  I was 100% stable at 1.20V. So just find your lowest stable VSOC and be under 1.3V and you will never burn up your CPU. Only idiots that set VSOC > 1.3V had a problem. I know non-overclockers like a fluctuating VSOC on demand to save a TINY bit of power and heat, but fluctuating between 0.9 - 1.3V based on load is NOT going to make a stable system because your overclocked ram needs a constant VSOC. I am extremely happy with the previous bios and locking VSOC at a low 1.20V which is more than safe.

If you leave VSOC on AUTO does it actually swing between 0.9 - 1.3V depending on the load? I thought VSOC=AUTO still behaved similarly to setting a static value, with 1.25V being a common voltage seen when setting AUTO. I use a manually defined voltage for VSOC so maybe I misunderstood how AUTO functions in this case.

Also, who is complaining that VSOC is being set too high? I only see people complaining that in recent BIOS versions they weren't able to raise VSOC above 1.2V.

Yes on previous bios VSOC on AUTO is pegged at 1.25V, no fluctuations, it is broken (as it should fluctuate). But it is NOT broken because it doesn't NEED to fluctuate. I guess if you are not overclocking memory, using PBO, ect.. running full stock, fluctuating can same a tiny bit of heat and energy. But I always run mine manual and set it to 1.20V, which is beyond safe and lower than the ASUS stuck 1.25V. I think the problem (and need for newer bios) is some idiots set manual to like 1.4V and fried their X3D chips, blaming it on the mobo. VSOC at AUTO pegged to 1.25V would NEVER fry any cpu. But I understand why they put out a new bios since AUTO doesn't do what it is supposed to. I think they just put a safe value in when X3D chips were released. I see ZERO reason to upgrade the bios for crappier memory timings when you can just manually put VSOC at whatever you want. Just don't be an idiot and go over 1.3V for daily use.