Share your AIDA 64 cache and memory benchmark here

[mrcardio33x]

I just got this pc back together and threw this memory in to see if it would even boot. I'll fiddle with it soon.

Gotcha.

 

[67Elco]

It made a difference. It does have a lot of errors in OCCT stability test though. Nothing in Linpack so far.

 

[mrcardio33x]

It made a difference. It does have a lot of errors in OCCT stability test though. Nothing in Linpack so far.

View attachment 336545

VPP: 1.85v? 1.8v is what this is normally at.
VDD: 1.4v - May need a bit more ~ 1.43 - 1.45 perhaps.
VDDQ/IO - May need adjusting, probably lower, I would try something like 1.30 - 1.35v
VSOC - Needs to be 1.3v? 1.2v doesn’t work? If 1.20 works you may could run something like 2133 - 2200 FCLK. Or something like 2067- 2167 if 1.25v is needed.
If nothing works tCRD 35 may need to be 36.
Doubt tRAS 30 is an issue but if so bump it up by 2 to 32, etc.
tRC 32 may be a bit low, 34 is lowest mine post.

 

[Zyll Goliat]

Ok just switched to CR1 and "earn" some significant bandwidth.......here is comparison from 2666Mhz/CR2 to 2800Mhz/CR2 to 2800Mhz/CR1

 

[67Elco]

No errors with these settings -

 

[mrcardio33x]

No errors with these settings -

View attachment 336615

View attachment 336616

Nice improvement!

If you'd like it a bit quicker, I'd suggest trying the following:

tRRDS: 4
tRRDL: 8
tFAW: 20
tWTRS: 4
TWR: 48
tWRWRSCL: 8
tRP: 12
tRDWR: 14-16
tWRRD: 2-4
tRDRDSD: 8
tWRWRSD: 8

Do you need 1.3v VSOC for stability? You could be a fair bit quicker / better bandwidth if you could manually lower that to run higher FCLK.

I have little doubt you could be in the ~ 55-58ns range, perhaps a bit better.

Regardless as of now you're better than EXPO and stable so it's up to you

 

[67Elco]

Nice improvement!

If you'd like it a bit quicker, I'd suggest trying the following:

tRRDS: 4
tRRDL: 8
tFAW: 20
tWTRS: 4
TWR: 48
tWRWRSCL: 8
tRP: 12
tRDWR: 14-16
tWRRD: 2-4
tRDRDSD: 8
tWRWRSD: 8

Do you need 1.3v VSOC for stability? You could be a fair bit quicker / better bandwidth if you could manually lower that to run higher FCLK.

I have little doubt you could be in the ~ 55-58ns range, perhaps a bit better.

Regardless as of now you're better than EXPO and stable so it's up to you

I've applied all those figures and it's been about fifteen minutes so far with no boot. I'll give it just a bit longer to be sure.

 

[mrcardio33x]

I've applied all those figures and it's been about fifteen minutes so far with no boot. I'll give it just a bit longer to be sure.

View attachment 336647

Interesting.
The settings I suggested aren't all that aggressive (especially for 6000 MT/s), they generally work for Hynix Adie.

Maybe its voltage related.

Or perhaps disable MCR (Memory Context Restore) / Power Down if you haven't already. Should improve your latency a bit as well.

If it doesn't boot you might have to Clear CMOS.

 

[67Elco]

Interesting.
The settings I suggested aren't all that aggressive (especially for 6000 MT/s), they generally work for Hynix Adie.

Maybe its voltage related.

Or perhaps disabled MCR / Power Down if you haven't already. Should improve your latency a bit as well.

I'll go back into bios and check. The only voltage figure I changed this last go was VSOC to 1.2v...maybe put that back and retry first?

I did have to clear CMOS. Re-applied all figures (forgot TWR and tRP ), put the SOC voltage back to 1.3 and it booted. Perhaps I need to slow down and concentrate on one value at a time and test.

 

[mrcardio33x]

I'll go back into bios and check. The only voltage figure I changed this last go was VSOC to 1.2v...maybe put that back and retry first?

I did have to clear CMOS. Re-applied all figures (forgot TWR and tRP ), put the SOC voltage back to 1.3 and it booted.

View attachment 336654

Perhaps 1.20v VSOC is too low but 1.25v VSOC may work and FCLK to 2066-2100.

This is just what I'd try personally.

I've done a TON of clear CMOS trying to get stuff optimized lol. This stuff can be a headache for sure but there's really no other way that I'm aware of, just trial and error.

 

[67Elco]

Perhaps 1.20v VSOC is too low but 1.25v VSOC may work and FCLK to 2066-2100.

This is just what I'd try personally.

I've done a TON of clear CMOS trying to get stuff optimized lol. This stuff can be a headache for sure but there's really no other way that I'm aware of, just trial and error.

I just now went back into bios and didn't follow my own advice...made two changes at once (TWR and tRP) and it won't boot. Let me figure out the offender and I will lower that voltage again.

Edit: Took tRP out of the mix and it booted. I'll try lowering that SOC voltage now.

Edit: It took the SOC voltage to 1.2v and booted. No errors reported.

FCLK 2100

 

[Paramount]

DDR5 6400 overclocked to 7600MT/s with time tuning

 

[67Elco]

Working on the 8700G this morning. Any reason why Zen timings 1.31 won't report all/correct values?

 

[dgianstefani]

Working on the 8700G this morning. Any reason why Zen timings 1.31 won't report all/correct values?

View attachment 336850

Conflicting sensor software or you have a setting on your motherboard preventing it.

 

[67Elco]

Conflicting sensor software or you have a setting on your motherboard preventing it.

I have three of these mb's, each with a different cpu and the 8700G has never reported correctly in Zen. All pc's are using the exact same software and all three bios's are the same version. Different memory has no effect.

 

[3x0]

ZenTimings doesn't support 8700G most likely. Either that, or one of your Windows 11 installs has enabled additional "security features" that MS likes.

 

[67Elco]

ZenTimings doesn't support 8700G most likely. Either that, or one of your Windows 11 installs has enabled additional "security features" that MS likes.

I'm leaning towards the cpu...all my pc's have the same OS. Pm'd another member with a 8700G to see if he experiences the same.

 

[dgianstefani]

Interesting data from Aeryn.

Similar to my own findings ~6200 MT tuned to the edge is peak performance. Hopefully puts to rest some of the commentary about how RAM doesn't really matter with X3D chips, and XMP/EXPO is fine.

 

[InVasMani]

6200MT/s CL28 in that scenario mostly is just better true latency, but 6400MT/s CL30 and 7800MT/s CL36 that are worse true latency end up better in some of those situations where bandwidth performance comes into play more readily.

True latency from lower to higher would be as follows
6200 CL 28
7800 CL36
6400 CL30

7800MT/s oddly performed better at 1950 rather than 2200. The GB/s dropped significantly though real world usage actually seemed better. It seems like benchmark deviance to me, but maybe it's more than that and something interconnected to CPU itself and/or overall stress to do with CPU itself. It highlights the importance of doing some comparison testing though to get a idea on what's happening.

7600 CL 34 would be a nice one to see higher true latency marginally than 6200 CL 28, but with higher MT/s. If you can run 7800 CL 36 odds are reasonable that you might be able to run 7600 CL34.

 

[Simkin]

Main PC: i9-13900K stock - 48GB G.Skill 8200Mhz CL38
HTPC: Ryzen 9 7900 stock - 32GB G.Skill 6000Mhz CL30

 

[67Elco]

First test of this new kit...untouched.

 

[mrcardio33x]

First test of this new kit...untouched.

View attachment 337341

You can improve on this easy.

Main PC: i9-13900K stock - 48GB G.Skill 8200Mhz CL38
HTPC: Ryzen 9 7900 stock - 32GB G.Skill 6000Mhz CL30


View attachment 337126View attachment 337127

Got pretty much the same latency (63.5ns) running the same Ram kit you are running on EXPO w/ the R9 7900

You could probably get that R9 7900 down to ~ 53-55ns.

I was able to improve it with the following:

CPU: BCLK 105 - LLC7 - Scaler X6 - Boost Clock (-) 150 MHz or 5150MHz

6200 MT/s CL28
VDD: 1.45v VDDQ/IO: 1.30v VSOC: 1.235v

 

[arbiter]

pretty much stock xmp profile corsair vengence RGB memory.

 

[67Elco]

This is kicking my ass...

2100 FCLK

 

[dgianstefani]

This is kicking my ass...

View attachment 337351

Yeah, well running out of sync won't give you performance.

See above post re ideal settings (6200).