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,411 Views
2,370 REPLIES 2,370

Does it help if you let the machine sit in the bios for few minutes (without changing anything) and then proceeding to boot the OS (without restart by discarding changes)? (I have some issue with memory stability, where I get plenty of memory errors on first boot in the morning for few minutes). Its not exactly "cold boot" as it doesn't happen again unless machine sits powered off over night or so.

I will try this tomorrow and i will comeback!


@Tsikos wrote:

With version 1004 still have BSOD when cold boot the system!


You might be very close to an unstable system so it might stabilize after VRM did heat up slightly or similar issues. I would recommend to increment MC voltage by 0.025 increments and perhaps try to increase the memory timings (slower timings) slightly until you reach a stable situation. I would recommend to boot into memtest86+ and validate stable memory as booting Windows without BSOD is not a sufficient indicator for a stable system Even if it does not bluescreen you might have memory errors.

Also slightly increasing memory VDD and VDDQ in 0.05V increments might help (usually you should not exceedd 1.4V for safety reasons). If nothing helps try lowering frequency.

Why asus can't fix all that i have this system 7 months and still unstable, i paid 1500 euro to upgrade from x570 to x670e and i think i made a big mistake!


@Tsikos wrote:

Why asus can't fix all that i have this system 7 months and still unstable, i paid 1500 euro to upgrade from x570 to x670e and i think i made a big mistake!


Can you post your complete specs? I guess then your memory and CPU is on the QVL list of your mainboard and you're running default settings, right?

If you are running an untested memory configuration there is no warranty provided that it will be stable - at least not when running overclocking settings (EXPO/DOCP). If your system is unstable in automatic setting with JEDEC DDR5-3600 or max. DDR5-4800 settings then you are within spec and of course right if you complain (given the memory is compliant with the standards and no component is defective). The problem is usually that people EXPECT some overclocking settings to work stable even if this configuration is not tested and approved and might not work for various reasons.

If you want to avoid issues either run JEDEC timings or get a configuration which is on the QVL.

Asus x670e-e 

Ryzen 7900x

G.Skill Trident Z5 RGB 32GB F5-6400J3239G16GX2-TZ5RS

DOCP tweaked and custom memory profile from asus list 32-38-38-36 


@Tsikos wrote:

Asus x670e-e 

Ryzen 7900x

G.Skill Trident Z5 RGB 32GB F5-6400J3239G16GX2-TZ5RS

DOCP tweaked and custom memory profile from asus list 32-38-38-36 


Looks like the F5-6400J3239G16GX2-TZ5RS are on the QVOL list so 2 modules (not 4!) should work at DDR5-6400. However the timings are 32-39-39-102 as on the QVL list and as of module specification. Running them with tighter timings like 32-38-38-36 is very likely going to cause instabilities. Try not to load a custom memory profile and assure your DRAM VDD and VDDQ is set to 1.4000V (try incrementing in 0.010V steps to 1.450V). Also I recommend increasing the MC voltage. Try 1.4V on MC voltage. Set all timings to default DOCP (32-39-39-102).

At least from what you write you are operating the modules outside specifications currently.

This profile i used is made from asus so must work without problems!


@Tsikos wrote:

This profile i used is made from asus so must work without problems!


Which profile exactly are you talking about? The DRAM tuning menu offers a couple of profiles for specific memory chips. However the profile might be for slightly different specs as whitnessed by the timings which do not match your profile. So if you load a profile which is not precisely for your chips and module it might or might not work.

In general it's not the mainboard having to provide memory modules. It's the memory module which provides the profile to the mainboard (EXPO/XMP). Moreover you are using a module which was optimized for Intel (XMP). ASUS is offering to use XMP profiles and adapting them to their best knowledge to AMD specifications - this is what they call DOCP.

Using AMD optimized modules (with EXPO profile) is more advisable on AMD platforms. I guess also for DOCP you  can select something like on EXPO profile I or II. Profile 1 is optimized settings (the mainboard taking the SPD-EEPROM data from the module and adjusting some of those). While Profile 2 is keeping exactly the timings specifyed by the memory module (usually the most stable option).

If you go to the DRAM menu and load a chip-specific setting you are going to overwrite those settings by parameters completely ignoring your memory module SPD-EEPROM data and trying to optimize for the memory chips on the module. However this is very risky also as people do not understand that not only the chips but also the layout and even trace routing on the module has an impact on timings. So essentially only the module manufacturer knows what is tested and validated.

Also you might have noticed that there are multiple profiles for the same DDR5 speed. And this applies to your module too - you cannot just load any Samsung or Hynix DDR5-6400 profile just because you got Samsung/Hynix chips and your module is supposed to be DDR5-6400 approved. That's not how it works.

So again I do recommend first to test "Auto" settings and validate if your system is all-time stable using JEDEC DDR5-4800 timings. Btw. this is also the highest speed AMD actually offering full support for. The Ryzen 7000 specs do not include any higher specification. Everything above DDR5-4800 is overclocking territory.

If your system is proven to be stable at DDR5-4800 speeds then enable EXPO/XMP/DOCP-I profile and try again - do not customize any timings or load further profiles. If it is not stable then try increasing MC voltage and for your modules assure DRAM VDD and VDDQ is set to 1.4V as of the module specification.

If this is all stable, then you might go into the DRAM timings menu and start optimizing some of the timings. But do not expect any significant performance boosts anyway. In most applications you might only see a single-digit uplift in performance on memory-intense applications comparing DDR5-5800 default and DDR5-6400 with optimized and hand-tuned (perhaps unstable) settings. So it's usually not worth the hassle.

@SkyBeam thanks for your explanation. But is it possible to know which modules ASUS validated those timings in the bios for? For example, they list SK hynix 2x16 at various speeds. Obviously they tested specific modules. If I have the same modules, could I then not just use that setting?

Also, what do you use for memory testing? Karhu?

Intel 3770K 4.4ghz, 1.24v. . . . . . . . . . . . . .Intel 4930k 4.7ghz 1.37v........AMD 7800x3D async 104
32 gGSkill DR3Trident 2400mhz 1.65v. . . .32 g 1866 Vengeance Pro.......64 g Hynix 6200
ASUS M5G. Noctua D14. . . . . . . . . . . . . . . H110. Noctua A14x4.............Arctic 420
prime95 stable 78degrees. . . . . . . . . . . . . IBT 75 degrees
OCZ V4 OS. . . . . . . . . . . . . . . . . . . . . . . . . EVO 1TB...............................WDSN850x 2TB
Seasonic 700w. . . . . . . . . . . . . . . . . . . . . .1200AX.................................HX1200i
All tucked into Lian Li A05. . . . . . . . . . . . . .Fractal Midiv2......................BeQuiet802