• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Ryzen 64GB oc check-in thread

Soulkeeper

Soulkeeper

Diamond Member
I figured i'd start a thread to see what others are able to do with this unfavorable config on ryzen.

I'm maxing out at 2667 14-16-14-16-34 with my 4x16 ecc

Are any of you able to get higher speeds ?
Anything anyone would like to see me test with this setup ?
 
You're one of the few I've noticed with 64 GB, much less over-clocking with that much 🙂

Those clocks and timings, especially with ECC looks quite healthy.
 
Is there a reason you are using ECC memory? You don't see many people overclocking ECC memory when stability is of the utmost importance.
 
I've never used ecc before, I just wanted to try it out I guess. Besides I figured it could come in handy.
The computer is both for work and fun.

I just spent several hours testing memory settings out and discovered something interesting
This was being shown in the regular bios and the beta bios.

My gigabyte bios lists the following:
tRFC 312
tRFC2 192
tRFC4 132

but in reality it appears to be setting:
tRFC 420
tRFC2 312
tRFC4 192
 
here are my settings for now at 2666MHz

IMG_0792.JPG

IMG_0795.JPG
 
Is DVID (Dynamid VID) part of the Ryzen platform, or specific to that motherboard?

The reason I ask is, I was using both Ryzen Master (now un-installed), AND the UEFI to overclock, and the UEFI in my ASRock AB350M Pro4 doesn't allow setting LLC, SoC voltage, or offset / DVID.

But I thought that I had read somewhere that Ryzen Master implemented its VCORE setting, by using an offset.

And if DVID is how they do that, but it's implemented as a platform feature, then maybe Ryzen Master set an offset VCORE / DVID, when I used it, and then when I tweaked the UEFI's VCORE, then they added together...?

The reason that I bring this up, is HWMonitor shows my VCORE as 2.64V.

The other possibility is that HWMonitor is simply reading my currently-set VCORE (in UEFI),. doubled.

In the UEFI, it displays my VCORE as normal, as does CPU-Z (ok, a tad bit higher in CPU-Z, but that could be my LLC kicking in, even though I can't set it manually).
 
VirtualLarry said:
Is DVID (Dynamid VID) part of the Ryzen platform, or specific to that motherboard?

The reason I ask is, I was using both Ryzen Master (now un-installed), AND the UEFI to overclock, and the UEFI in my ASRock AB350M Pro4 doesn't allow setting LLC, SoC voltage, or offset / DVID.

But I thought that I had read somewhere that Ryzen Master implemented its VCORE setting, by using an offset.

And if DVID is how they do that, but it's implemented as a platform feature, then maybe Ryzen Master set an offset VCORE / DVID, when I used it, and then when I tweaked the UEFI's VCORE, then they added together...?

The reason that I bring this up, is HWMonitor shows my VCORE as 2.64V.

The other possibility is that HWMonitor is simply reading my currently-set VCORE (in UEFI),. doubled.

In the UEFI, it displays my VCORE as normal, as does CPU-Z (ok, a tad bit higher in CPU-Z, but that could be my LLC kicking in, even though I can't set it manually).
Click to expand...

I'd think most any board would allow it, I dunno.
 
VirtualLarry said:
Is DVID (Dynamid VID) part of the Ryzen platform, or specific to that motherboard?

The reason I ask is, I was using both Ryzen Master (now un-installed), AND the UEFI to overclock, and the UEFI in my ASRock AB350M Pro4 doesn't allow setting LLC, SoC voltage, or offset / DVID.

But I thought that I had read somewhere that Ryzen Master implemented its VCORE setting, by using an offset.

And if DVID is how they do that, but it's implemented as a platform feature, then maybe Ryzen Master set an offset VCORE / DVID, when I used it, and then when I tweaked the UEFI's VCORE, then they added together...?

The reason that I bring this up, is HWMonitor shows my VCORE as 2.64V.

The other possibility is that HWMonitor is simply reading my currently-set VCORE (in UEFI),. doubled.

In the UEFI, it displays my VCORE as normal, as does CPU-Z (ok, a tad bit higher in CPU-Z, but that could be my LLC kicking in, even though I can't set it manually).
Click to expand...
HWMonitor voltage is useless. Try HWinfo.
 
what im curious is does the ECC actually work?

i remember read that it wasnt fully supported, and hence why manufacturers did not state full support.

Have you done a couple of memtests on it to see if it has issues?
Did you have any problems with it?
Does the RAM detect as ECC?

I am genuinely interested in that ram now since it is ECC, and i have been wanting ECC for my 1800X more so then 3200mhz.
 
formulav8 said:
People on Reddit has recently tested and a couple with specific mobo's has verified it seems. TR will most likely contain more boards providing ECC options.
Click to expand...

This seems to be the concensus with ECC and Ryzen tho, even in that thread...

reddit said:
ECC support with Ryzen is practically non-existent. You may get some portion of ECC working, or you may not, as no vendor that I know of supports it officially. So you can't rely on it at all.
Click to expand...

which is a big bummer.... i value ECC on this machine as i use it to encode remux's and do large file transfers where i need full confidence data will not get corrupted. :T

Again sorry for slightly derailing the thread, as i really wanted to know if the OP had any issues with his ECC running, as he is the first person i have seen with ECC ram on his Ryzen setup that's not a front page forum writer.
 
I only have 32GB (2x16GB DDR4-2400). Similarly to yours it will run at 2667MHz, though with slightly worse timings of 16-17-17-39 at the default 1.2V. I haven't tried increasing the voltage because I prefer to maintain power efficiency, nor have I spent any time adjusting the timings other than reducing CAS, because it doesn't really make much difference.

Interestingly, when letting the BIOS set everything automatically, it runs at 2T command rate, whereas when it is overclocked it gets set to 1T, even though that is not a user-adjustable setting.

At some point I'll upgrade the BIOS on my Taichi with the one with the new AGESA and see if that lets it run any faster.

AdamK47 said:
Is there a reason you are using ECC memory? You don't see many people overclocking ECC memory when stability is of the utmost importance.
Click to expand...
ECC works great with overclocking because you can see it start to correct errors when you have overclocked too far.
 
aigomorla said:
which is a big bummer.... i value ECC on this machine as i use it to encode remux's and do large file transfers where i need full confidence data will not get corrupted. :T

Again sorry for slightly derailing the thread, as i really wanted to know if the OP had any issues with his ECC running, as he is the first person i have seen with ECC ram on his Ryzen setup that's not a front page forum writer.
Click to expand...
If you are on windows, then you must manually enable ECC support via the WHEA Policy Settings.

See here https://docs.microsoft.com/en-us/windows-hardware/drivers/whea/whea-pfa-registry-settings and https://docs.microsoft.com/en-us/windows-hardware/drivers/whea/how-whea-performs-pfa-on-ecc-memory

Using windows power shell, just enter "Get-WHEAMemoryPolicy", to see what it currently it is set to, and if you want to set things, use "Set-WheaMemoryPolicy" with the parameters mentioned here https://technet.microsoft.com/en-us/library/mt575534(v=wps.620).aspx

Oh, and if you do enable it, and have bit errors while o/c'ing, on the next restart, windows will map out those areas that it detected bit errors with, so it is a bit harder to remember to clear the memory mapping before changing timings or whatever else!
 
Wow, I just managed to get 2933 stable 15-17-15-17-35 1.25v
3200 will boot, but it seems to want more than 1.38v which i'm not willing to do.

The trick was LOWERING procODT to 40ohms and loosening rfc
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top