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.

2,170 Views
2,457 REPLIES 2,457

It was pretty bad for me too, but after changing a lot of voltages and memory settings it is stable and with lower voltages and tighter memory than before.

It's not that bad, it's even very good imo just different and one needs to compensate. Sadly so does Auto looks to be tuned for older AGESA, this bios is no good for a one click setup you need to know your way around

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

So you have a problem, 1000 others don't have problems using 1410 and expo profiles... The linked article is pure click bait.

1410 is rock stable for me. EXPO II @6000CL30 no problem at all. 1410 - never had a BSOD. 


@frytom wrote:

1410 is rock stable for me. EXPO II @6000CL30 no problem at all. 1410 - never had a BSOD. 


There are different definitions of "stable" for sure.

I also never had a BSOD on those, but still y-cruncher VST or memtest86+ (or both) showing errors. So occasionally you might have browser tabs crashing or similar issues - but it does not necessarily mean it's "stable" as per definition of others.

I am not saying that everyone is requiring a 100% stable system in the sense that you can run y-cruncher for days without any single error as it is unlikely to face a sustained load on the same level in day-by-day operations. So if your system crashes under artificial load it does not mean it is necessarily crashing during gameplay or office work. But it might well get unstable in some specific situations.

And yes, my personal definition of stable is that I can throw any workload at it any time and it is supposed to handle it without any error sustained for days, weeks and months of operation. So I'd rather disable EXPO than accepting occasional memory errors which might or might not crash my workload at random intervals. But YMMV and it's perfectly fine to set the bar to "runs Fortnite stable" and therefore run a bit more towards the edge of stability but eventually gaining a few more percent of performance.

After installing 1410 beta bios I got a bsod soon as I logged into windows. First my pc screen went black when i logged into windows, and then my pc restarted. I had this happen to me twice after installing 1410. The first BSOD was around 4.49am when I installed 1410 and right afterwards I logged into windows, then around 10pm on the same day when I turned on my pc and logged in , exactly the same BSOD code and exactly the same means it happened. Before this beta bios I was on stable release of 1202 and then 1303 since these have been launched which is a few months and never had this issue. I wanted to install 1410 because of the so called cpu and motheboard melting. I have a x670e hero and a 7900x

theteamcaptain
Level 8

I can't believe how broken this whole thing is. More than 6 months after I bought my Hero and we still don't have an acceptable BIOS revision we can run, that is safe, performant and configurable as described. It's absolutely mental that this isn't a bigger story than it should be - we are being used as a proving ground for BIOS stability at our own expense, sometimes with serious and dangerous consequences. ASUS and AMD must increase the resourcing and priority of these problems to accelerate a fix. I don't think I can stomach another Asus product now because this is just a shambles from start to finish.

This is because AMD change platform.

im on 1410 now. when i run core cycler with prime for some time hwinfo shows me, vcore reaching 1.385v. is this a normal behaviour? 

 

7950x3d, x670e-f

it's a bug of HWinfo!!!!

ok, so what tool shows the proper vcore?