Aorus X570 Master

[jesdals]

Playing around with mixed core settings for curve optimizer - core 0, 3, 12 and 15 at negative 5 and rest at negative 10

Does seems like average max is higher - did try to set the same 4 cores to positive values but was not stable and positive 0 gave less of a result than just not enabling the curve setting

 

[Calmmo]

Info:
- Agesa 1.1.9.0 finish validation, BIOS will be compiled shortly
- Agesa 1.2.0.0 under validation,issues with USB's and others

At least we know they're not working exclusively on intel bioses for now

 

[juanyunis]

Info:
- Agesa 1.1.9.0 finish validation, BIOS will be compiled shortly
- Agesa 1.2.0.0 under validation,issues with USB's and others

At least we know they're not working exclusively on intel bioses for now

HI, I wanted to ask you where did you find that info?

 

[Calmmo]

They get posted on TT.
Trying F32a beta atm agesa 1.2.0.0

 

[juanyunis]

They get posted on TT.
Trying F32a beta atm agesa 1.2.0.0

View attachment 184264

I got the beta BIOS. Thanks!

@Calmmo damm, that new BIOS i just installed and made able to boot with 4X8GB at 4000Mhz with FCLK 2000Mhz. Now, I have perfect ratio with high clocks.

 

[SesioN]

Hey guys,

can it be that I have such a bad CPU?? Probably bronze?

I've the following specs:

MB: Gigabyte X570 AORUS MASTER v1.2
CPU: 5950X
RAM: G.SKill TridentZ 32GB Kit DDR4-3200 CL14 (Running in XMP profile currently)
Cooling: AiO ARCTIC Liquid Freezer II 360 (In general very well cooled pc-case with many good fans and proper air-flow concept)
Bios: F32a
(same results on previous official one)

I tested like all possible settings.

Curve optimizer all cores -5 leads to instant blue screen when windows is loading. No matter what settings I try.

Example settings:

Vcore: auto
LLT: auto
PBO: 200/140/140
boost override +50 Mhz
curve optimizer: all core -5

I've tested all combinations. No matter what I blue screen or not stable or totally hot.

 

[jesdals]

You can see PBO/Curve settings in this thread https://www.techpowerup.com/forums/...-guides-experience.275640/page-6#post-4438393 and that memory stability can be an issue try raising CL to 16 if your having problems with the settings

 

[polarox]

hi guys,

does anyone have the bitspower or EK monoblock for this motherboard? Is it worth the money?

 

[jesdals]

F32 up on gigabyte site - will do some test later this week

 

[juanyunis]

F32 up on gigabyte site - will do some test later this week

I have it. It is basically the same thing with F31. It even uses the same AGESA combo 1.1.0.0 patch D. Not sure why they didn't release it with AGESA 1.1.9.0 or 1.2.0.0. Honestly AGESA 1.2.0.0 is looking good, it let met boot with FCLK 2000mhz and up. So I guess FCLK 1900 would be more stable.

I did notice that I have clock stretching with this update, not sure if they tweaked voltage table.

 

[jesdals]

F32 seems stable but no improvement over F31, PBO setting with P200, T125 and E110, +500MHz and -20 negative curve

 

[Calmmo]

Yeah because F32 official is still just same old 1.1.0.0

 

[juanyunis]

Correct. Sucks, but yeah. At least there is a new f33a beta with agesa 1.2.0.0. Testing it.

Quick question, does anyone here has an issue with the mouse move lag. For example sometimes when I move the mouse it feels slow and gets stuck. It only happens when I enable PBO.

 

[jesdals]

Quick question, does anyone here has an issue with the mouse move lag. For example sometimes when I move the mouse it feels slow and gets stuck. It only happens when I enable PBO.

I only use the red 3,1 ports so not here

 

[jesdals]

Get WHEAs with the new F33a beta bios but Infinity 2000MHz did boot in first try - will do some stability test and mem settings test

 

[tabascosauz]

Correct. Sucks, but yeah. At least there is a new f33a beta with agesa 1.2.0.0. Testing it.

Quick question, does anyone here has an issue with the mouse move lag. For example sometimes when I move the mouse it feels slow and gets stuck. It only happens when I enable PBO.

Also, some recent GB BIOSes have "improve USB 2.0 hub stability" in their patch notes, so they've definitely tried to address it.

 

[Zach_01]

View attachment 185422
Get WHEAs with the new F33a beta bios but Infinity 2000MHz did boot in first try - will do some stability test and mem settings test

CPU Bus/Interconnection errors must be IF related.

 

[juanyunis]

Also, some recent GB BIOSes have "improve USB 2.0 hub stability" in their patch notes, so they've definitely tried to address it.

I'm running that latest bios. And nope, still had the bug. In my case what fixed it (mostly, barely happens now, rare) is to disable global c states and change power supply common current to typical current idle.

CPU Bus/Interconnection errors must be IF related.

Correct, I spent good time tweaking the vddp, vddg and SoC voltage but was unable to make it stable.

 

[tabascosauz]

I'm running that latest bios. And nope, still had the bug. In my case what fixed it (mostly, barely happens now, rare) is to disable global c states and change power supply common current to typical current idle.


Correct, I spent good time tweaking the vddp, vddg and SoC voltage but was unable to make it stable.

Global C-states (in theory, at least it works that way on Asus, but GB is pepega sometimes) should do both cores and IF C-states so now that yall 5000 owners are trying for 4000 it's probably best to just disable C-states. Or find the DF one specifically and do that without touching the cores. Don't want the DF downclocking and messing with your already precarious IF stability

Been running with DF C-states off on my 4650G @ 4200. Otherwise I risk random reboots sometimes when pushing 4133/4200.

 

[Zach_01]

From a certain (GB) BIOS version there is a distinct setting in BIOS for DF C-states. So you can have CPU C-states enabled and DF C-states disabled.
If I remember correctly, Its under AMD CBS >> SMU common options or something like that.

 

[juanyunis]

From a certain (GB) BIOS version there is a distinct setting in BIOS for DF C-states. So you can have CPU C-states enabled and DF C-states disabled.
If I remember correctly, Its under AMD CBS >> SMU common options or something like that.

That's correct. So if one wants to push if 2000 should disable df c states or global c states. Also I noticed that with beta bios f33a when you push flck 2000mhz uncore is enabled automatically.

 

[tabascosauz]

I'm running that latest bios. And nope, still had the bug. In my case what fixed it (mostly, barely happens now, rare) is to disable global c states and change power supply common current to typical current idle.


Correct, I spent good time tweaking the vddp, vddg and SoC voltage but was unable to make it stable.

I spent a lot of time trying to solve 3733 and 3800 Bus/interconnect WHEAs by tweaking the secondary voltages. Never succeeded in the end, eventually intermittent POST failures and BIOS crashes forced me back to 3600. The Memtesthelper guide is *somewhat* helpful and accurate when it comes to VDDG and VDDP, but not 100%. And well, DRAM Calc is straight up full of shit so no help there.

Though, lower is better for those two, that's what I can say for sure, as low as you can run them

I strongly suspect the IF on my 3700X is slowly degrading because after about 6 months I'm forced to play the VDDG/VDDP game again, this time even at 3600. Haven't seen any problems for about a week, but if past experience is anything to go by Ill probably see another bus/interconnect when i least expect it. I've never run my 3700X above 1.1V SOC, talk about AMD quality

 

[nguyen]

I spent a lot of time trying to solve 3733 and 3800 Bus/interconnect WHEAs by tweaking the secondary voltages. Never succeeded in the end, eventually intermittent POST failures and BIOS crashes forced me back to 3600. The Memtesthelper guide is *somewhat* helpful and accurate when it comes to VDDG and VDDP, but not 100%. And well, DRAM Calc is straight up full of shit so no help there.

Though, lower is better for those two, that's what I can say for sure, as low as you can run them

I strongly suspect the IF on my 3700X is slowly degrading because after about 6 months I'm forced to play the VDDG/VDDP game again, this time even at 3600. Haven't seen any problems for about a week, but if past experience is anything to go by Ill probably see another bus/interconnect when i least expect it. I've never run my 3700X above 1.1V SOC, talk about AMD quality

My nephew's PC which has X570 Aorus Elite + R5 3600 would sometime fail to boot at 3600mhz DDR4, lower it down to 3466mhz solved the problem but I always thought it was mobo-related. So it could have been the CPU the whole time.

 

[jesdals]

F33a is not stable for me - even with the settings mentioned above - and 1967/1933 also has wheas - im going to test som more at 1933 - but for now F32 seems to be the safe bet.

Gave up on F33a and went back to F32

 

[Zach_01]

Yeah, I would stay away from early betas (a,b,c...)
And to be honest, if the system is solid already I would go only for final versions