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:

Spoiler

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.

[Exostenza]

I find it really strange that both myself and my buddy who have the TUF X670E Plus Wifi have both used many different USB sticks and followed the Asus instructions to the letter and it never worked - not once. I literally have my first USB stick ever which is a 4GB Kingston traveller and it most definitely was before USB 3 and that's the stick I used to always update my BIOS with until a few years ago a buddy's partner gave me a ton of 2GBB USB 2.0 2GB sticks as she had a whole box of them from her work. Since then I have been using those for BIOS updates on new PCs without an OS. I have every single generation and size of USB anyone could need, literally a whole box to keep all my USB sticks in, ranging from 2GB 2.0 to 500GB 3.2 and everything in between (4 x 2GB 2.0, 1x 4GB 2.0, 2 x 8GB 2.0, 2 x 16GB 2.0, 1 x 64GB 3.0, 1 x 128GB 3.0, 1 x 256GB 3.1, 1 x 500GB 3.2) that I have collected over the years ranging from complete trash to the best you could get at the time. I have tried all formats and every which way described in youtube vids and forum posts yet neither of us have been able to get either of our boards to use the flashback feature while my buddy with the same board is in another city so he tried a bunch of his own USBs separately which never worked. Then, I just made this PC for a buddy in my city with the TUF X870E Plus Wifi and had the exact same experience. Following Asus' instructions to the letter didn't get it to work trying to update thhe BIOS before loading Windows on and using all sorts of formats, sizes, and generations got me nowhere just like my board so I just used EZ Flash 3 in the BIOS and that works every time. I haven't had a need to use the feature yet but I'd like to know that it is capable of working if I ever need it to. My other buddy with the TUF X670E Plus Wifi literally went to the PC shop to buy the exact USB size and generation that Asus and other guides on the internet say work for flash back as none of his multiple USB sticks would work when he had an issue one time that he thought he needed to use the flashback featuree and he was never able to get it working. Finally he called me and I showed him how to clear his CMOS and thankfully that got him back into the BIOS so he could use EZ Flash 3 - that's what I've had to do when I couldn't POST as flash back just doesn't ever work. I even took extra time building this latest TUF X870E Plus Wifi for a buddy just trying to get the latest BIOS flashed through flashback to see it actually work for once but I couldn't no matter what I did so I just booted into the BIOS and updated it with one of those 2GB 2.0 sticks that I always use for the BIOS on a new machine now - otherwise I just put a new BIOS file in the root of C:/ and flash it from there if Windows is installed on the PC. 

So, I don't know what we're doing wrong but I have tried following the instructions to the letter on two Asus AM5 PCs with many different sticks and a buddy in another city has done the same and we just can't get it to do anything - ever. It always flashes the led three times and goes solid forever which means it isn't doing anything. My buddy actually just left it for like 40 mins once just to see if it would finally do something but it didn't.

I have absolutely no idea why it won't work on three separate boards across 10-20 USB sticks between the three of us but it just won't work. I know my blanket statement that it doesn't work across the board is too much as clearly it has to work for someone or else it wouldn't be an advertised feature but I, and my friends, have wasted so much time trying to get that feature to work on our boards we're all just so frustrated that we've completely given up on it and treat is as a feature that never worked and never will - that frustration led me to make that umbrella statement.

I hope I never actually need to use it as its a non-feature in my eyes due to my, and my friend's, experience trying to get the bloody thing to do something with a plethora of USB sticks across sizes, generations, and formats - I'd love to know what we're doing wrong if it is a feature which works for most people. 

[Silent_Scone]

A long list of USB sticks and “I tried every format” unfortunately, isn’t diagnostic, because FlashBack typically fails on one specific requirement (file naming, partitioning, port, power state, etc.). If you want this to be actionable (and not just anecdotal comments), we need evidence of the exact process as previously requested. Again, I suggest you start a support thread for this, as the vast majority can use this feature absolutely fine.

[gupsterg]

My experience on ASUS with Ryzen is quite high, boards I've had since 2017.

Flashback has been my go to to flash a BIOS. I wanted the Crosshair VI Hero WIFI for that feature, besides other features it had. So I have used it a lot. I use every BIOS that Elmor/Shamino/Safedisk have posted in threads over the years.

As Silent Scone said, it has always been the newer boards get FW before older, but that does not mean to say older boards get left behind. I only recently sold of my Crosshair VII Hero WiFI, which I owned from launch. I've gone AM5, so my Crosshair VIII Dark Hero went to my son.

I remember when the Crosshair VI Extreme, came out. All the owners on OCN in the C6H OC thread were like OMG, the C6H is dead, it's not gonna get updates, yada yada. In fact the C6H got releases first, as the was a "development" board.

If you think ASUS is bad on FW, try ASRock, Gigabyte, MSI.

ASRock, not saying anything.

Plenty of people moan Gigabyte are slow to release FW, then some don't use a beta and beta to "stable" is slow on Gigabyte, trust me I've read the moans on various forums.

Your on OCN, drop a PM to Tatili, or go check his posts. ODT Group A / B has been accessible in ASUS FW since I started using AM5 in 2024, and that was available on a 600 series TUF board. MSI users are still waiting for access. 

I know of posters on OCN who were after screen shots of ASUS BIOS, showing max voltage without LN2 mode, as other vendors don't even allow as much voltage control as ASUS.

Many a time I have considered going ASRock / Gigabyte / MSI, I never make it over to them for various reasons.

[CL26_Master]

@SAFEDISK @gupsterg Hi again! On AGESA 1.2.8.0, I managed to stabilize 90 ns tRFC2 and 55 ns tRFCsb on my H16M kit. However, since it was a beta release, I ran into stability issues. Games were crashing even though long stress tests appeared stable. Additionally, my 6600 CL28 profile was never truly stable on that AGESA.

Because of this, I reverted back to AGESA 1.2.7.0. I really hope ASUS can address these instability problems soon. MSI has already pulled their BIOS version containing AGESA 1.2.8.0 due to multiple user complaints, and I experienced similar instability myself. While long-run tests passed, games would still crash.

@gupsterg On AGESA 1.2.7.0, I was able to tune my 6600 CL28 profile with the timings shown below. Do you think there are any other timings I could still optimize or adjust? You previously mentioned that SCL 5 and tRDWR 14 are quite rare at 6600, and so far they seem stable on my system. I also found that tRAS = tRC = 80 delivered the best bandwidth results in Karhu and with tRAS = tRC = 60, Karhu bandwidth was noticeably reduced.

Thanks again for your help. I’m looking forward to your reply!

[gupsterg]

Honestly there is nothing I could share to help you, there are no recommendations I would make.

There is no "low hanging fruit" left. In my opinion, anything you may get a 1 nCK or more, drop on isn't gonna give you anything to know you got a gain.

When reading your posts before I could see you knew how to tune up/gain stability, you have been helping yourself 🙂 .

Enjoy your system 🙂 .

[Night_Fly]

AGESA 1.2.8.0 with 9921 Beta runs better for me than any previous version.

[Rudi1]

I installed version 1901 on my x870e-e, and everything works correctly with the adjusted timings and configurations from 1.2.7.0, so I'm happy with the results. However, I do see a slight drop in performance in synthetic benchmarks like Cinebench R23 and Cinebench 2024. Another thing that caught my attention is that in the latest updates, CPU Duty Control is set to Extreme; it was previously set to T-Probe. What's the difference, or should I leave it on T-Probe?

[gupsterg]

It's in the helpstring.

CPU VRM either thermal balance (T.Probe) or current balance (Extreme).

[Rudi1]

Thanks for your reply. Yes, I saw it in the help thread, but it's not easy for me to interpret. The question is, why is it set to "extreme" by default? It was previously set to "tprobe," and which would be more suitable?