cancel
Showing results for 
Search instead for 
Did you mean: 

X670 / X870 resource thread

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,502,293 Views
3,183 REPLIES 3,183

The Sleep mode is broken for everyone (for a lot of people) and has nothing to do with your 7800X3D.

Its something with the BIOS that ASUS cant fix for a long time. Its deeper in the AGESA, thats why its so complicated to fix. AMD need to fix it.

I'll see about that when I get my 7800X3D replacement. I can mention that I did a clean install with a MSI X670E motherboard and the exact same thing happened, it doesn't matter if you have EXPO enabled or disabled, it still failed. At the moment the sleep mode works fine with the 9700X, I'm still testing.

jockerfreak
Level 9

No sleep issues here, woke up after 4 hours.

7950X3D with X670E GENE, latest BIOS as of now.

RAM is Corsair Dominator Titanium 6400 CL40

nomoreload
Level 9

Upgraded from 7950X to 9950X.

Same problems as @NerusMorte has.

Mobo: X670E Hero.

Also find that ProcOdt on those sticks with 9950X on this board is around 160-240ohms depending on training. And when I change its value in Extreme Tweaker - DRAM timing control, the changes don't applied.

Values saved in BIOS, but from ZenTimigs I read another values.

Are the values saved in BIOS, though? I can't see why they wouldn't apply if so.

Also what memory kit? 

@NerusMorte AX5U6400C3216G-DCLARBK?

13900KS / 8000 CAS36 / ROG APEX Z790 / ROG TUF RTX 4090

Value saved in BIOS, but in ZenTimings I still see ProcODT 240Ohm for default 4800Mhz or 160Ohm for 6000Mhz or 6400Mhz (when EXPO enabled).

If I change them (for example) to 80, they still 240/160 in ZenTimigs depending on frequency. But when I open the BIOS, I see the saved 80Ohm there.

Looks like values are saved in BIOS, but ignored. BIOS 2304, X670E Hero, 9950X, Win11 24H2, ZenTimigs 1.32.

AX5U6400C3232G-DCLABK

Yes, that is the memory kit I use, but I'm currently running it at 6200 MT/s and I manually set the UCLK = MCLK and the Ryzen 7 9700X is supposed to have better IMC.

I have Ryzen 7800x3D and 6400 UCLK=MCLK 1:1

fractal-zombie
Level 10

@Shamino I found cool thing in asrock and other mobo, they have CO for per core, for all cores, and per ccd, it will be really cool, if you bring this feature for us, i mean per ccd CO.

nomoreload
Level 9

@Silent_Scone I also found that precision boost Fmax override didn't works for 9950X on X670E Hero from ASUS Extreme Tweaker menu. No matter what I put there, HWiNFO64 show the same Fmax value. On 7950X when I change Fmax override, HWiNFO64 shows me that changes. The only thing that was changed is the CPU. The remain parts of my rig are the same.

I also re-flash my BIOS (2403) via flashback. No luck. As I previously reported - extremely high ProcODT, the ProcODT value change didin't affect values that ZenTimings shows to me and that new Fmax override bug.