This UCLK just dont look right can someone maybe help me

[brandon7171]

This UCLK just dont look right could anyone tell me if any of this looks right please.. Using Ryzen 3700x with Asus Rog Crosshair Formula X570.. Ram Im using B-Die sorry for the bold print when i copy and paste it does this

G.SKILL Trident Z Neo Series 32GB (4 x 8GB) DDR4 3600 (PC4 28800) Desktop Memory Model F4-3600C14Q-32GTZNB

​

 

[A Computer Guy]

Do you have an ASRock board? A UEFI/BIOS update should fix the VDDG CCD, VDIMM, and MEM VTT readouts on ZenTimings. Not sure if that's related to the UCLK problem.
Your voltages don't look right either: I think it supposed to be VSOC > IOD > VDDP, CCD
for example VSOC=1.1, CLDO VDDP=0.95v, VDDG CCD=0.95v, VDDG IOD=1.05v

 

[ir_cow]

Looks like your in Gear 2 (2:1 Ratio).

 

[tabascosauz]

This UCLK just dont look right could anyone tell me if any of this looks right please.. Using Ryzen 3700x with Asus Rog Crosshair Formula X570.. Ram Im using B-Die sorry for the bold print when i copy and paste it does this

G.SKILL Trident Z Neo Series 32GB (4 x 8GB) DDR4 3600 (PC4 28800) Desktop Memory Model F4-3600C14Q-32GTZNBView attachment 260278​

Did you already run 3800 previously and your settings just got messed up? Or is this your first try and you don't know if your CPU can do it?

Think it's safe to say there is not a single Ryzen 3000 CPU in the world that can sustain 1900MHz 1:1 Fabric on only 1.0V, VSOC. Little too optimistic.

VDDP doesn't help you run 3800, drop it to 0.9V. Bring VSOC up until FCLK can do 1900 without crashing. Leave both VDDGs until you figure out VSOC first (I don't think VDDG_CCD is software visible on Ryzen 3000, but it should still exist).

 

[ir_cow]

The op is also running 4x single rank @ 3800. That might be a challenge to get going on a Ryzen 3000. I remember having to play around with the voltages and PRocODT, RttNom,RttWr, RttPark to be stable since the memory training refused to boot in Gear 1 without doing so.

 

[brandon7171]

Do you have an ASRock board? A UEFI/BIOS update should fix the VDDG CCD, VDIMM, and MEM VTT readouts on ZenTimings. Not sure if that's related to the UCLK problem.
Your voltages don't look right either: I think it supposed to be VSOC > IOD > VDDP, CCD
for example VSOC=1.1, CLDO VDDP=0.95v, VDDG CCD=0.95v, VDDG IOD=1.05v

Running Asus Rog Crosshair Formula 8 X570, Im pretty sure im in UEFI..

 

[A Computer Guy]

Running Asus Rog Crosshair Formula 8 X570, Im pretty sure im in UEFI..

Yea I always type UEFI/BIOS for the old timers like myself that are like UEFI what?

You might take a look if you have any unapplied UEFI updates and try that to see if those fix ZenTimings however that might be a bit off the beaten path to your original question and I don't want to confuse the original topic if there is just something in your UEFI you likely need to fix. I don't have an Asus UEFI so I won't be much help in that regard finding that setting.

 

[ir_cow]

The op is on the newest BIOS. I don't think this is a BIOS issue really. This has happened to me since day 1 of X570 on multiple motherboards. Basically when the FLCK=AUTO this can happen. Its now in 2:1 mode for the memory controller but the Infinity fabric is still at 1800MHz.. Manually set this to 1900. The Uclock should follow. - It probably won't boot though without changing SoC voltage. I would do DDR4-3600 first and see

 

[brandon7171]

The op is on the newest BIOS. I don't think this is a BIOS issue really. This has happened to me since day 1 of X570 on multiple motherboards. Basically when the FLCK=AUTO this can happen. Its now in 2:1 mode for the memory controller but the Infinity fabric is still at 1800MHz.. Manually set this to 1900. The Uclock should follow. - It probably won't boot though without changing SoC voltage. I would do DDR4-3600 first and see

View attachment 260289

I know this may be alittle hard to see but here is mine it’s on auto

 

[Zach_01]

FCLK on auto never set it self above 1800MHz
And the other are at MCLK=UCLK/2

Simple as that...

 

[brandon7171]

FCLK on auto never set it self above 1800MHz
And the other are at MCLK=UCLK/2

Simple as that...

My fclk is at 1800 my mclk is at 1900 and uclk is at 950 and I’m not sure why that is I was is other OS But just changed it to windows uefi and it still didn’t change it.

 

[A Computer Guy]

My fclk is at 1800 my mclk is at 1900 and uclk is at 950 and I’m not sure why that is I was is other OS But just changed it to windows uefi and it still didn’t change it.

In your UEFI set FLCK from AUTO to 1900. Does that fix the problem?

 

[brandon7171]

In your UEFI set FLCK from AUTO to 1900. Does that fix the problem?

You talking about this correct. I’m not sure if their is another location with FCLK?

 

[Zach_01]

In your UEFI set FLCK from AUTO to 1900. Does that fix the problem?

Also he must find the:

"UCLK DIV1 MODE" setting and set to "UCLK==MEMCLK"

 

[ir_cow]

You need to set your FLCK to 1900MHz and not auto. But it still might have not boot. 4x DIMM can be a challenge.

Also he must find the:

"UCLK DIV1 MODE" setting and set to "UCLK==MEMCLK"

Thats on MSI you get a choice. I believe ASUS just puts auto does it once you type in a FLCK value.

 

[Zach_01]

You need to set your FLCK to 1900MHz and not auto. But it still might have not boot. 4x DIMM can be a challenge.


Thats on MSI you get a choice. I believe ASUS just puts auto does it once you type in a FLCK value.

My Gigabyte AorusPro has it...

An old screenshot:

 

[tabascosauz]

My Gigabyte AorusPro has it...

An old screenshot:
View attachment 260301

That's not an Asus thing. Every board vendor adds different stuff to their Tweaker page, doesn't mean that's where you'll always find it.

On Asus I've never had a problem with setting FCLK manually on Tweaker page. Unless the conditions aren't right for CPU to do it, of course.

There was one bug with earlier AGESA where 1:1 Fabric on APUs showed as desync in Zentimings, but that doesn't look like what's going on here.

 

[brandon7171]

You need to set your FLCK to 1900MHz and not auto. But it still might have not boot. 4x DIMM can be a challenge.


Thats on MSI you get a choice. I believe ASUS just puts auto does it once you type in a FLCK value.

I just set fclk to 1900 and everything is at 1900 is that ok/safe?

 

[Zach_01]

That's not an Asus thing. Every board vendor adds different stuff to their Tweaker page, doesn't mean that's where you'll always find it.

On Asus I've never had a problem with setting FCLK manually on Tweaker page. Unless the conditions aren't right for CPU to do it, of course.

Yeah, I think our matter is not where its placed...

I just set fclk to 1900 and everything is at 1900 is that ok/safe?

You will tell us...
If its stable or if you're getting any WHEA errors/warnings

 

[A Computer Guy]

I just set fclk to 1900 and everything is at 1900 is that ok/safe?

Well it might not POST so there is that.

 

[brandon7171]

I just set fclk to 1900 and everything is at 1900 is that ok/safe?

 

[tabascosauz]

View attachment 260302

Great. Now drop VDDP down and work on the rest of your timings, and see if Fabric is stable.

 

[A Computer Guy]

... image trimmed ...

Nice!

 

[Zach_01]

As I remember he has a really good/expensive B-die kit

Oh yes, you can see it on first ZenTimings screenshot

 

[ir_cow]

My Gigabyte AorusPro has it...

An old screenshot:
View attachment 260301

I like how every MB adds and removes things with BIOS updates. Its annoying to keep track of. A one point you can set the UCLK and FLCK separately on the MSI X570 Carbon. A update removed that and you can't even set the UCLK anymore or see it. I don't remember ever seeing UCLK Control as a option on ASUS though. Probably just named something different. ASUS likes to do that.