X670 / X870 resource thread

[Shamino]

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:

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


DOCP/EXPO Tweaked: (for simple timings tightening)


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:

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





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.

[Damianos83]

Thats why i dont use memory context. I was having the same occasionally with 1.4v but without context restore the problem was gone. Vdd 1.4 and disabled context wnd power down and you will be fine.

[666CZR]

I did try MCR OFF a few bios versions ago, but not with power down disabled

[magix86]

I have seen 3 power down and 2 context in the menu.

One Power Down is linked with one Context, if you change one power, it change one context. but not the other and not all.

I don't remember which are linked each other, and in which menu. All enabled, on my MB, but with manual voltage unstability  like said by Damiannos83 (more in manual than in auto)

[Damianos83]

You have 2x32GB. Maybe you need more than 1.4v. For 16gb 1.4v is enough,maybe for 32gb more is needed like 1.43v.  

[666CZR]

I was thinking the same but I'm playing blind, not even sure what's the safe limit

@magix86 I'm always making sure I change all iterations by using the search (F9) function.

[Damianos83]

Hello. Sorry, i wrongly write( sorry for bad english). I know you dont have random reboots, my solution is for your  problem with random stuck at memory training.My CPU is 7950x3d. For Soc voltage i use 1.175 to be sure of stability because the minimum stable for 6000mhz is 1.15v if you use 2 stics 16GB.Also have uclk=memclk. Glad i help. I was long strugle with this training issue. I dont use MCR becasue im not fully sure of stability with this option enabled. If you will have in future problems after reboot then disable MCR. I dont use it and like I said before, after changing DRAm to 1.4 i never have problems.Oh and about MCR, if you have enable this you always need to enable Power DOWN too.You have Ryzen 9950x, this CPU from what i Know have the same ININITY FABRIC quality as 7000series so you can try this SOC Voltage at 1.175. Theoreticly 9000 series should need lower voltages. You have 32GB stics and maybe you need 1.25 but i would try 1.175 or 1.2v .I I know for sure that to run on my CPU , ram at 6400mhz i need soc 1.25v minimum. I hope this all helps. Thanks for trying my advice. 

[JRepin]

---

@dinosaur wrote:

"3. Improved system performance and fixed various bugs."

As a software developer myself, seeing such a laconic (and pretty much useless) change log entry bothers me to no end...

ASUS, pretty please, be more accurate about what changes go into your BIOS, especially about the "various bugs". As users, we want to know exactly what to expect from a new BIOS: is the bug we were seeing in a former BIOS fixed, or are the fixes of no concern to us (be it because they do not affect our CPU model, RAM or whatnot) ?...

For example, I experienced total system freezes with 2308 and 2401 on my X670E Hero (and reverted to 2204 as a result), and I also reported an issue about the Power Down setting getting screwed up between ASUS' BIOS settings and AMD's ones, but I cannot know if any of these bugs (the first being a show stopper) have been fixed or not...

---

Couldn't agree more. I hate this modern trend of some useles generic changelogs that tell nothing. Please be more libre/opensource software or for example something like Valve does for SteamOS and Steam client changelogs. Don't treat us as some clueless consumers who don't know much. Especially since we pay so much for the hardware I think we deserve some more respect with proper and full changelogs providing full and complete details of what is changed.

[Celestion]

Any idea where an updated X670E-I bios is at?

[MoKiChU]

---

@Braegnok wrote:

Thanks, EC Version is 0263 on Gene.

---

---

@Goose3080 wrote:

No noticeable changes on ASUS X670e Gene between 2308 and 2403.

---

Hi,

I think this is an mistake from ASUS staff in the changelog, this line in the changelog only concerns the X870(E) motherboards.

---

@Celestion wrote:

Any idea where an updated X670E-I bios is at?

---

Hi,

It should be released in the next few days as per usual, with the second wave for ROG B650(E), unless major issue detected in the first wave. I'm waiting myself for the BIOS 304x Final for my ROG STRIX B650E-F GAMING WIFI (i'm currently using the BIOS 3040 Beta).

[Braegnok]

Correct sir,.. thanks

The EC Version changed to 0119 on X870E Hero with 0501 update. 👍