Ryzen - Return of the Jedi

[I.nfraR.ed]

Prime (29.1 x64) works at above settings, also 100% memtest done. Seems pretty fine at these clocks.
Can't test at 3400 with 4x8, because it does not POST above 3300 and trying to clock in windows leads to instant reboot. Tried on different dividers. Maybe I'm hitting the memory hole or it is just what my IMC can handle with 4 single-sided modules.

Memtest 100%


Blend custom, just 30min, don't want to torture this cpu a lot, since I have only one and plan to bench it on LN2


Aida

[chew*]

cool thx.

Had to put my Rottweiler down today out of the blue.....was not expecting it, happened that quick so I'm going to step away from pc's for a couple days get my together as this was a crushing blow for me.

She has lived at my side literally glued to me for the past 7 years so.....yah anyway. to be continued.

[Formula350]

cool thx.

Had to put my Rottweiler down today out of the blue.....was not expecting it, happened that quick so I'm going to step away from pc's for a couple days get my together as this was a crushing blow for me.

She has lived at my side literally glued to me for the past 7 years so.....yah anyway. to be continued.

As a dog owner and dog lover, my condolences. Been in that situation and it effing sucks. Take care man!

[techtrancer]

@chew

Did you know if Ryzen need less SOC with less V-DIMM ?
Also if Ryzen need less SOC with high tRC?

[MusicIsMyLife]

Well done chew* on dual rank modules! This is the first I see someone clocking them above 3000MHz! Magic

In the german HardwareLUXX-Forum a user primed 4x 16gb dual ranked G.Skill TridentZ F4-3400C16Q-64GTZ with ddr4-3050.

I own the same memory kit and currently it runs at ddr4-3000, 14-14-14-39 1t, 1.325 volts. This is my first prime-run (29.10 build 14) with this setup. I've done 30 min 800k with ~48 gb allocated memory but the screenshot is currently out of reach.

For those who are wondering why there is no cpuz in my screenshot: Currently there seems to be a bug with an active raid array.

Four dual ranked dimms can run 3000+ on ryzen. Unfortunately it seems that you have to have the right combination of hardware, skill and pure luck.

[aGeoM]

cool thx.

Had to put my Rottweiler down today out of the blue.....was not expecting it, happened that quick so I'm going to step away from pc's for a couple days get my together as this was a crushing blow for me.

She has lived at my side literally glued to me for the past 7 years so.....yah anyway. to be continued.

I know what you are feeling, been there. "The show must go on" is the best way to overcome, but takes time.
Thank you for all your support.

Be well...

[chew*]

Ive run a bit over 3000.

3400..in prime 90%+ ram allocated was what comment was on.

You need to pay attention to details. 7.3g ram in use out of 68g....is not stressing imc/memory.

15g out of 50g...same..

I can set default blend and pass where i know i cannot pass with 90% allocated just some fyi.

This is why people seem to think blend does not work...improper settings.

Tick blend then tick custom then change amount to 90% of total.

[MusicIsMyLife]

Ive run a bit over 3000.

3400..in prime 90%+ ram allocated was what comment was on.

You need to pay attention to details. 7.3g ram in use out of 68g....is not stressing imc/memory.

15g out of 50g...same..

As I said before: I've done 30 min 800k with 48 gb out of 64 gb, can't show screenshot for now because I'm not at home. 800k is supposed to stress imc/timings most.

I didn't allocate more than 48 gb because I am running a 12 gb ramdisk and I didn't want to get into trouble. So I choosed 48 gb. I will disable ramdisk and play with higher allocation next.

[chew*]

I let it all run. Usually by 12 hours it hits every k possible and has already repeated them. 20 min is good for showing quick problems.

[MusicIsMyLife]

I let it all run. Usually by 12 hours it hits every k possible and has already repeated them. 20 min is good for showing quick problems.

Do you like this screen better than previous one?

I know that it's only a ~40 min-run but thats enough to prove that there are no major problems. Vsoc at 0.98v by the way (1.00 in bios).

This time with cpuz. Got a mail from Franck with newer beta, resolved the issue with SATA-raid.

[Formula350]

Just to confirm what aGeoM has stated regarding modded BIOSes... I went ahead and flashed one of my modded ones to my MSI Titanium yesterday (used the original v1.10 BIOS that my board shipped with, which is the only BIOS I've been using since it worked fine, even with my RAM @ 3200).

Thankfully everything went just fine!

Points of interest:
- SubTimings indeed are currently non-Adjustable on that BIOS version, at least with how I went about making them visible (ticking them all as USER for Access), but I have one last idea... doubt it'll work though. They DO show up, and tell you what they're set to, which (probably unsurprisingly) are different than the Tertiary Timings shown in Mem TweakIt.
- CPU VDDP allows for entering values, even has a Help that indicates the Default (says 1.050V), Low and Max, but since I don't know how to verify that I have no idea if the 1.070V I set is has actually applied. (I think that HWiNFO's VIN6 under the motherboard might be the VDDP, but I have no evidence and it's a shaky theory at best. After fresh boot it hovers around only 1.000V, but after waking from Sleep it is sticking at 1.048V. Lots of odd stuff happens post-sleep so it's hard to determine things then just due to that.) If anyone knows of a way to figure out what CPU VDDP is running at, let me know.
- The thing that bummed me out the most was that due to these BIOSes full on GUI (at least MSI's specifically), the menu structure inside AMIBCP is very oddly laid out. Additionally, there is no way in the actual BIOS to navigate to these other 'un-hidden' menus (though, now after I've had sleep it just dawned on me that the "Search" feature may turn them up). There are plenty of additional menus listed as you can see, but only the highlighted menus are directly accessible (MFlash is as well of course, but that's not really a 'menu' seeing as it's an option that reboots the system):


In the old Award BIOS editor (the cmd prompt one), it allowed you to easily select a menu category and then literally cut-and-paste it elsewhere. The newer AMIBCP versions do not provide that ability at all, which is not only kinda sad given it's a full GUI, but also because v5.xx EXE size is 11MB >_> What's all that code for if it can't even provide drag-and-drop? v4.55 was only 500KB and it offers the exact same functionality *shrug* ANYways... the unfortunate nature of this means I'm unable to do the other primary thing I had wanted to accomplish through modding, which was to enable the PState overclocking options that are tucked inside the OTHER "Advanced" menu (the one with the [+] not the one above '[+]Overclocking'). Sadly, with my skillset (no hex editing know-how) I'm unable to shuffle options around like I had hoped. There are empty spaces, but they're all tied together, and I an't edit the "Handle". So when I changed one space, every empty space on that page mirrored it Oh well...

Thinking bout flashing the 1.41beta (that was pulled). I don't now if the BCLK was visible by default since I never flashed their version, but I did mod it to ensure it's visible ^_^ We shall see how daring I feel. They pulled all their Betas due to a "flaw in the microcode", but what exactly that means I haven't a clue...

[chew*]

Yah soc is a myth....i run 1.05 at 3400

[Formula350]

EVERYthing is a bit of a mystery to me right now.
I've got a...
Core VID @ 0.400V
the VCore @ 0.488V
Core Voltage @ 1.481V
VRM Output @ 1.477V

Mobo sensor of CPU-NB reads 0.960V
1700X calls it SoC Voltage & is 0.950V
VRM sensor VR VOUT reads 0.947V



But wait, there's more!

Toss in the inconsistent terms used across all flavors of motherboards and Ryzen Master, like MEM VDDIO @ 1.080 and MEM VTT 0.590 (neither of which display anything till their option is clicked) that don't seem to coincide with any BIOS setting, but closest to VTT is that DRAM Vref, despite being 0.600V.
A Core Voltage @ 1.35V which I never see anything actually reporting it run near that. The new voltage setting terms of "VDDCR" for CPU and SoC.
Then the CPU's readings of Package Power wattage @ 18.78W, yet the Power (CPU+SoC) reading of 41.53W... Which I've been using that one since math actually results in that number, based on the Core Power when added to the SoC Power wattages.
Oh, and no one quite being sure if the SoC is it's own thing, or if it's the CPU-NB, or if it's the CPU1P8, or...

It's like... YAY, SETTINGS! And yet... YAY, RAMPANT INCONSISTENCIES!
Leaves me to simply pound brick
*sigh*

The only thing I can say with certainty is that the DRAM Voltage is what it is, since that at default is 1.2V or when running at its rated speed is 1.35V. And the PROM Core Voltage, which is what the Chipset is running at since that's codenamed Promontory (thus also referenced as PT in backwater areas of the BIOSes). As for PROM PHY Voltage, I'm pretty certain that's to do with its PCIe, but am not too concerned about anything PROM related currently. heh

[chew*]

Soc is needed only to push (nb) in cpu-z aka fabric.

So only then will you need soc...1.00 is commonly more than adequate for 3200. Small bump for 3400 little more for 3600.

Of course the other limiting factor is can the imc and memory handle 3600...

[ZenEffect]

just some c10 32m testing on some new 3600c15 tridentz. these kits seem to play nice on this platform

[techtrancer]

just some c10 32m testing on some new 3600c15 tridentz. these kits seem to play nice on this platform

Awesom
How much v-dimm?
And wich Chips are on this RAM?
Please can you Look with Thaiphoon Burner?

[chew*]

PC 3400 testing at cl 16 pc 3200 2x16g 32g Prime 95 blend 12+ hours

moving onto cl 14 testing now.......

[ZenEffect]

Awesom
How much v-dimm?
And wich Chips are on this RAM?
Please can you Look with Thaiphoon Burner?

no need to look, they are Samsung b die. vdim was 1.575, they don't like much over 1.6 and you gotta get vdimm dialed to get the times running right.

[techtrancer]

A lot

What does the RAM in Prime Custom Blend and 24/7 Voltage?

[I.nfraR.ed]

3600C12 is now super easy with the new beta bios for CH6. I guess the updated AGESA really helped here.
Basically set bclk to 135, set VDIMM, VCore and timings, it just boots with my sticks.

[chew*]

Nice did you compare effeciency between the two?

[chew*]

A lot

What does the RAM in Prime Custom Blend and 24/7 Voltage?

For all my testing in prime 95 since im trying to cater to 24/7 users vddr is 1.35 and untouched...

Whatever it can do at that voltage i am posting.

When im benching with single rank....it is what it is and not default...not at least on my sticks which are not very spectacular...

[I.nfraR.ed]

Nice did you compare effeciency between the two?

Only Cinebench for now. It is a little faster.

[aGeoM]

... the unfortunate nature of this means I'm unable to do the other primary thing I had wanted to accomplish through modding, which was to enable the PState overclocking options that are tucked inside the OTHER "Advanced" menu (the one with the [+] not the one above '[+]Overclocking'). Sadly, with my skillset (no hex editing know-how) I'm unable to shuffle options around like I had hoped. There are empty spaces, but they're all tied together, and I an't edit the "Handle". So when I changed one space, every empty space on that page mirrored it Oh well...

You can set PStates on that [+]Advanced menu, and then flash it again, it is not the way you wanted, but it works. I have set PSate to 1, and now Core Boost goes to 3750MHz. Further analyses needed.

[I.nfraR.ed]

VDIMM 1.60V
VSOC 1.11V
VDDP 1.20V
VPLL 1.70V



Should spend some time this weekend to optimize windows for Pi.



PS: You can see some key voltages used. Nothing else helps in my testing.
Obviously VDIMM is needed, depending on quality of sticks, timings, frequency, etc.
VDDP helps stabilize memory (IMC maybe?)
VSOC only needed for Infinity Fabric, so when pushing really high clocks it needs to be raised a little, since it is running in sync
VPLL is lower than default, helps boot at high mem and bclk.