cancel
Showing results for 
Search instead for 
Did you mean: 

X670 resource

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:

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,096 Views
2,297 REPLIES 2,297

theteamcaptain
Level 8

Bit the bullet and upgraded to 1415 this morning, after skipping the last few BIOS updates due to the huge number of problems reported. I am quite uncomfortable with anything but the most basic changes right now, but I figure that getting onto the 1415 BIOS revision that is less likely to fry my motherboard or CPU is preferable, especially now that Asus seem to have come to their senses about liability for using it in the first place.

Very simple config:

  • AI Overclock Tuner - DOCP 1
  • CPB - Enabled
  • MCR - Enabled (in both locations)
  • Power Down Enable - Enabled
  • Armoury Crate - Disabled
  • Integrated GPU - Disabled

I was blue screening without Power Down Enable being switched to Enabled. This didn't used to happen in older BIOS revisions (I think 0905 ?) but seems to be absolutely necessary for MCR to work at the moment.

Right now I can boot to desktop in 25 secs and I can run Cinebench, OCCT and AIDA64 stability tests without failing. I am sure there is a lot of safe changes I can make to improve overall performance, but I think I would like to just wait for a few weeks and see if games, software and productivity tools run without issue.

ASUS ROG Crosshair X670E Hero // AMD Ryzen 9 7950X // 32GB Corsair Dominator Platinum RGB (DDR5-6000 - CMT32GX5M2X6000C36) // ASUS ROG Strix RTX 2080 Ti Gaming OC 11G // Windows 10 Pro

Olli2k
Level 8

X670E Extreme, Bios 1415.
All Settings to default. Not possible to boot in EXPO or EXPO II.

Ram Kit: Corsair CMT32GX5M2D6000Z36 32 GB

Not on QVL I presume? 
And even if it is on a list, it’s an exact same issue I had aside from having 3x32G dominators. Zero reliability with Expo. 

it’s a shame because visually RAM is striking and customizability is amazing (aside from iCue). 
For piece of mind I have with 2x32G G.Skill (only approved kit) and been working fantastically. 

Just checked it. This Domionator was removed from QVL. My original Kit was a Vengenance one and I bought the actual one because of Asus Support and QVL List. Talked to them afterward, and they confirmed my actual Kit is (now was) on the list. I'm pissed!!!!!

Indeed, I am currently trying 1416 on Strix E-E and I can't get those 6400Mhz anymore, back to 6200 using DOCP 6400 but limiting the speed to 6200. I might try a few other things on that point... Or end up buying some other ram ^^

I have yet to find the right settings to get it as stable as 1202, and I am already under what I was able to achieve back then... I'll keep experimenting, but not specially happy so far.

Basically, 6400MT requires silly high VDD/VDDQ which is against the current "cooking the CPU" damage control. Many(most?) product pages for X670/E/B650/E boards have had memory OC changed from 6400-6600 to 6000. Possibly because of, something.

But, yeah even though, you should be able to get it stable again but possibly have to set higher numbers in bios than before, as the new bios looks to have less voltage overshoot.

On the flip side so does the new bios also tend to need less CO to maintain a good voltage curve, and it is working well with tight memory timings at low voltages, rendering high frequency less important.

R9 7950X - ASUS X670E Crosshair Extreme (bios 0803) - 32GB HyperX Fury Beast @6200c32 - Corsair H150i Pro - ASUS RTX3080 TUF OC V2 - Phanteks P400A - Corsair RM850 - WD SN850

That does make a lot of sense, thanks for the info.

I finally settled on ditching DOCP for Manual and using the Hynix 6200Mhz 1.4V SR 2*16 profile and activating Power down, MCR etc, so far so good, but it only has been a few minutes ^^

CO is the current setting I'm trying to define indeed, I'm getting close, it's stable everywhere but the most unstable apps, I'll start checking values (temps, voltage under load, etc ) and performance tests once it's settled.

 

EDIT: I should also add that this Bios does allow me to tweak its settings without BSODing all day (unless I input crazy values of course) , which is already better than most of my tries above 1202 😉

I bought the same G.Skill Kit now. Beside it is ugly as ****** compared to the dominator it was working fine with EXPO II @ 6Ghz. For 2 days. Now I'm in BSOD heaven. IRQ_NOT.. and MEMORY_MANAGEMENT maximum 1 minute after logging into windows.

DNABrooker
Level 8

Did you guys test the Curve Optimizer with the new Bios, did you get the same Results or even better Negative Curves?

Well, that is what I was testing right now, but no luck... Before, I was at -13 on the Curve Optimizer, today I tried as low as -4 to no avail (Windows runs, most apps works, but "crashy" ones crash after 5 minutes each time ) . Therefore I am currently testing without CO ^^

I'll report in a few.

How is it going on your side?