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:
instead of 0011000
after selection press downcore apply changes or discard if made mistake
octool port to linux
7950x not boosting pass 5.5G -> check that CStates is not disabled
Detailed Explanation on CState Boot Limiter
X3D OC Preset for those MB with asynch BCLK Support: (for simple slight perf boost for X3D)
DOCP/EXPO Tweaked: (for simple timings tightening)
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.
Solved! Go to Solution.
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.
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.
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?
Yes, it's not possible to apply as much CO anymore as the curve seem to be more optimized from start so less headroom for tweaking but in the end performance should be ~same