Monday, May 8th 2023

Latest AMD AGESA that Nerfs Ryzen 7000X3D Voltage Control Also Limits Memory Overclocking

The latest AMD AGESA 1.0.0.7 AM5 platform microcode that the company recently released to improve stability of machines powered by Ryzen 7000X3D processors, more importantly, prevent them from physical damage due to increased voltage in voltage-assisted overclocking scenarios; reportedly impacts memory overclocking capabilities, too, reports g01d3nm4ng0. The "PROCHOT Control" and "PROCHOT Deassertation Ramp" toggles that were available in the oldest versions of AGESA for AM5, are not available in the latest production AGESA.

The memory compatibility is also affected. AMD recently added support for odd-density DDR5 memory modules, such as 24 GB and 48 GB, which make up 48 GB and 96 GB 2-module (dual-channel, four sub-channel) kits. It is possible to max out 192 GB, but while the older AGESA 1.0.0.6 allowed memory frequencies of up to DDR5-6000 with SoC voltage of 1.3 V, the newer AGESA is only stable up to DDR5-4400 at this density. To be fair, most motherboards advertise maximum memory frequencies of under DDR5-4800 for memory configurations where there are two DIMMs per channel, and both DIMMs are dual-rank (so four dual-rank DIMMs in all, which is the least optimal memory configuration from a memory frequency and latency perspective).
Source: g01d3nm4ng0 (Twitter)
Add your own comment

73 Comments on Latest AMD AGESA that Nerfs Ryzen 7000X3D Voltage Control Also Limits Memory Overclocking

#26
Metroid
I said this would happen and some people here said I was wrong. Now you trolls who said I was wrong can see it clear as a bright sky.
Posted on Reply
#27
rv8000
somebodys_kidOh good call. I'll try the 1410 later today. 1401 just capped the voltage without the AGESA update.
The spec listed by GSKILL wants 1.35 volts for the EXPO settings.
G.skill lists VDD, not VSOC. 1.35v VDD (essentially vdimm/vmem). The naming scheme for voltage rails has gotten out of hand with newer platforms.

1.35 VDD for your memory is absolutely fine and 100% safe.
Posted on Reply
#28
unwind-protect
DavenYou predicted 24 GB and 48 GB memory configs would be clock limited after this update? Wow that’s a pretty specific prediction. Kudos to you! I would have never predicted that this specific memory configuration would be only effected.
You misunderstood. I predicted that when the overvoltage issue gets fixed that they throw out the baby with the bathwater and disable a random bunch of legitimate overclocking options.
Posted on Reply
#29
phanbuey
To be fair it didn't scale past 6400 anyways, so it's not like you're losing a whole lot here?

Not sure what SOC needs to hit 6000 cl30 but that seems to be the sweet spot.
Posted on Reply
#30
Slizzo
phanbueyTo be fair it didn't scale past 6400 anyways, so it's not like you're losing a whole lot here?

Not sure what SOC needs to hit 6000 cl30 but that seems to be the sweet spot.
I'm running 1.2v SoC currently at 6000MT/s
Posted on Reply
#31
phanbuey
SlizzoI'm running 1.2v SoC currently at 6000MT/s
In my case on the Intel platform the difference between 6000 cl30 to 6200 cl32 to 6400 cl34 was basically nothing... doesn't seem like nerfing that last 400mhz will do anything -- especially since x3d chips already have that cache cushion.
Posted on Reply
#32
rv8000
phanbueyTo be fair it didn't scale past 6400 anyways, so it's not like you're losing a whole lot here?

Not sure what SOC needs to hit 6000 cl30 but that seems to be the sweet spot.
There’s plenty of “scaling” to be had, it’s just very rare for a chip to be able to do 6600, or maintain mclk/uclk/fclk ratios to not tank performance.

I’ve seen a few posts with 7000-7200 if I recall, but then you can’t maintain mclk:uclk @ 1:1, so performance takes a nose dive.

With 6600 c28-c30 you can shave another 2-3ns off latency and get some additional bandwidth over 6400. Requires a lot of VDD(vdimm) and good 7000 chip.
Posted on Reply
#33
phanbuey
rv8000There’s plenty of “scaling” to be had, it’s just very rare for a chip to be able to do 6600, or maintain mclk/uclk/fclk ratios to not tank performance.

I’ve seen a few posts with 7000-7200 if I recall, but then you can’t maintain mclk:uclk @ 1:1, so performance takes a nose dive.

With 6600 c28-c30 you can shave another 2-3ns off latency and get some additional bandwidth over 6400. Requires a lot of VDD(vdimm) and good 7000 chip.


This is the max difference I could find without tuned subs between 6200CL34 and higher ram speeds (13900K with 4090) -- the jump of 1000mhz on the ram netted 3fps at the lows and 7.6% at the averages - so with less headroom than this... scaling is what - 5% max? I wouldn't say that's plenty -- that's basically you couldn't tell the difference unless you were staring at a framerate graph.

If you're saying "Im nerfing memory from 8000 to 6000" then yes- that's a huge nerf... outliers that can do 6600 aside (and even then) at most this is a 5% difference given the same timings? Probably less once you tighten timings on the faster kits as low as they will go.
Posted on Reply
#34
b1k3rdude
"It is possible to max out 192 GB, but while the older AGESA 1.0.0.6 allowed memory frequencies of up to DDR5-6000 with SoC voltage of 1.3 V, the newer AGESA is only stable up to DDR5-4400 at this densit"

As Long as I can install 32GB of DDR5-6000 CL30 or faster, then like a lot of users, I would never run into the issue above. But its seems the memory compatibility pages for mobo makers still need updating -

www.msi.com/Motherboard/MAG-X670E-TOMAHAWK-WIFI/support#mem
Posted on Reply
#35
rv8000
phanbuey

This is the max difference I could find without tuned subs between 6200CL34 and higher ram speeds (13900K with 4090) -- the jump of 1000mhz on the ram netted 3fps at the lows and 7.6% at the averages - so with less headroom than this... scaling is what - 5% max? I wouldn't say that's plenty -- that's basically you couldn't tell the difference unless you were staring at a framerate graph.

If you're saying "Im nerfing memory from 8000 to 6000" then yes- that's a huge nerf... outliers that can do 6600 aside (and even then) at most this is a 5% difference given the same timings? Probably less once you tighten timings on the faster kits as low as they will go.
Like I mentioned earlier, reviews that show memory scaling are pretty pointless. They don’t spend with secondary and tertiary timings, so auto rules start loosening those timings and simply upping the ddr5 frequency and controlling primaries isn’t really “tuning”.

It will vary from game to game, but from personal testing going from c36 6000 expo to 6200 c30 tightening primary/secondary/tertiary was about a 6% gain in CP2077 at 1080p low preset. I can probably test 6400 now that I have a good kit of A-die.
Posted on Reply
#36
phanbuey
rv8000Like I mentioned earlier, reviews that show memory scaling are pretty pointless. They don’t spend with secondary and tertiary timings, so auto rules start loosening those timings and simply upping the ddr5 frequency and controlling primaries isn’t really “tuning”.

It will vary from game to game, but from personal testing going from c36 6000 expo to 6200 c30 tightening primary/secondary/tertiary was about a 6% gain in CP2077 at 1080p low preset. I can probably test 6400 now that I have a good kit of A-die.
That's right -- I think my argument was more that the SOC limit is really at the frequency, not as much for the timings -- you're absolutely spot on about the subs loosening at the higher speeds which makes those comparisons pretty misleading.

That being said -- most people don't really tune subs, and to them 6000 to 6600 or 6400 EXPO is going to be very little difference for the reason above. For the people that DO tune subs the focus on OCing will fall to the timings -- and a C26/C28 6200 with aggressive primary/secondary/tertiary will still net a huge performance boost, -- maybe you will lose 5% not being able to go to 6400/6600 if that's the sweet spot of the kit... but the difference isn't going to massive in either case.
Posted on Reply
#37
rv8000
phanbueyThat's right -- I think my argument was more that the SOC limit is really at the frequency, not as much for the timings -- you're absolutely spot on about the subs loosening at the higher speeds which makes those comparisons pretty misleading.

That being said -- most people don't really tune subs, and to them 6000 to 6600 or 6400 EXPO is going to be very little difference for the reason above. For the people that DO tune subs the focus on OCing will fall to the timings -- and a C26/C28 6200 with aggressive primary/secondary/tertiary will still net a huge performance boost, -- maybe you will lose 5% not being able to go to 6400/6600 if that's the sweet spot of the kit... but the difference isn't going to massive in either case.
This is the other half of the story, and sadly reviewers only show this.

They could have a c32 6000 kit and a c32 6400 kit with a 1% difference or less when set to expo. The 6000 kit could have very tight sub timings like trfc, terfi, for some hefty gains. The 6400 kit could have the most abysmal trfc and trefi at almost double/half the other kit. This will vary from kit to kit, brand to brand, and even worse mobo vendor to mobo vendor as most of them will define their own timing rules for secondary/tertiary as dram vendors don’t always seem to define those values in xmp/expo profiles (or autocorrection takes over).

So technically to say there’s no scaling just is not true; ticking expo and dialing up the frequency while having no idea what the motherboard is setting sure.

Id say overclocking has changed, and requires a lot more finesse and understanding than previous brute forcing methods in the past. And again, sadly, reviewers don’t have the time or luxury to spend actually testing or showing this.
Posted on Reply
#38
Airisom
I haven't updated, but I'm running 1.25v SOC with 2x32GB 6000CL30 with tweaked timings on PBO 7800X3D with 104mhz eclk. Stable as a rock on X670E Hero
Posted on Reply
#39
evernessince
unwind-protectYou misunderstood. I predicted that when the overvoltage issue gets fixed that they throw out the baby with the bathwater and disable a random bunch of legitimate overclocking options.
It's a little early to say which changes will stick. The recent BIOS updates were put together in a day or two and were not intended to be the long term fix. They are only to prevent any further burnt CPUs / motherboards while AMD fully investigates the issue.
Posted on Reply
#40
somebodys_kid
rv8000G.skill lists VDD, not VSOC. 1.35v VDD (essentially vdimm/vmem). The naming scheme for voltage rails has gotten out of hand with newer platforms.

1.35 VDD for your memory is absolutely fine and 100% safe.
Tried again with the 1410 BIOS and still crashes after 20 minutes with RE4 remake. Will try again with the next BIOS until they get it right I suppose.
Posted on Reply
#41
ir_cow
Looks like the DDR5-4400 is just for 4x Dual-rank (128/196). I am able still able to run 2x single-rank 6200.

Every IMC will be different but this is what I'm needing for stability. Basically at least on this GB Elite AX motherboard you need to manually set the VDDIO_Mem because it just stays at 1.1V otherwise. I assume the DDR5-6000 is still a thing, but some for some that may be 5600 now. Dependent on the IMC.

Yes, Gigabyte still allows over 1.3V, you just get a warning now is all...


















Memory Support BIOS F8d
SpeedRanks / DIMMsBootsStable(?)Auto VoltagesMCLK GearFCLKSoCVDDIO_Mem
DDR5-6000Single-Rank / 2xYesYesYes1:12000 MHz1.25 V1.10 V
DDR5-6200Single-Rank / 2xYesYesNo1:12000 MHz1.30 V1.20 V
DDR5-6400Single-Rank / 2xYesNoNo1:12000 MHz1.40 V1.25 V
DDR5-6600Single-Rank / 2xNoN/AN/A1:11500 MHz1.40 V1.30 V
DDR5-6000Single-Rank / 4xYesYesNo1:12000 MHz1.30 V1.20 V
DDR5-6200Single-Rank / 4xYesNoNo1:12000 MHz1.35 V1.30 V
DDR5-6000Dual-Rank / 2xYesYesNo1:12000 MHz1.25 V1.20 V
Posted on Reply
#42
MarsM4N
MetroidI said this would happen and some people here said I was wrong. Now you trolls who said I was wrong can see it clear as a bright sky.
I mean that's just some basic common sense. :) If AMD is setting new maximum limits & RAM vendors selling RAM kits that run outside of spec, there will be incompatibility.
Just looked at the listenings over at heise.de. 170 kits listed with AMD EXPO, and their voltage specs:



If you narrow it down to kits that are specified for 6000MHz (AM5 sweet spot) there are left 65 kits. Their specified voltages are:



Which means you have only 5 kits that run within AMD's specs at 6000MHz (from TeamGroup, Apacer & Lexar). 60 kits are certified by RAM vendors to run outside of AMD's specs! Which btw. does not mean they won't run with lower voltages. It's just not guaranteed to run at lower voltages. Each kit is of different qualitiy and RAM vendors just set higher voltages to guarantee compatibility across the board.

I guess the solution would be to use/develop RAM kits that run with lower voltages. It kinda reminds me of the DDR3 times when all vendors had kits running on 1.5+V and G.Skill came around the corner with their "G.Skill ECO Series" which did run on only 1.35V. It also marked the rise of the 1.35V kits.

Posted on Reply
#43
AusWolf
Dragam1337It's not an issue with the normal 2 dimm 32gb config. I have no issues running 6000cl30 with 1.0.0.7
This would have been my question to the article, thanks. :)
Posted on Reply
#44
btarunr
Editor & Senior Moderator
DavenAMD’s biggest weakness is the memory controller. It needs improvements across the board (pun intended).
Intel designs its own memory controllers that it extensively iterates and tests on FPGAs. AMD uses third-party IP blocks such as from Synopsis.
Posted on Reply
#46
MarsM4N
R-T-BMy man you are literally posting in the TPU thread on the exact same news piece.
He's just setting his flags for "Team Blue". :D

Posted on Reply
#47
R-T-B
MarsM4NHe's just setting his flags for "Team Blue". :D

Anyone who literally thinks either of these companies give two shits about you is extra special. To be a "team" requires them to well... notice you, and they do not care about you as an individual, I assure you.
Posted on Reply
#48
Why_Me
R-T-BAnyone who literally thinks either of these companies give two shits about you is extra special. To be a "team" requires them to well... notice you, and they do not care about you as an individual, I assure you.
My bad .. I deleted it.
Posted on Reply
#49
Minus Infinity
Zen 4 is the gift that just keeps on giving to Intel, So glad I didnt rush out and update my 3700X for 7800X(3D). Definitely hoping they get their crap together for Zen 5, but openSIL is years away so no guarantee AGESA won't continue to be a crap shoot for the next release. Arrow Lake is looking more and more appealing if those clowns can release on time.
Posted on Reply
#50
evernessince
R-T-BAnyone who literally thinks either of these companies give two shits about you is extra special. To be a "team" requires them to well... notice you, and they do not care about you as an individual, I assure you.
Yep, 100% agreed.


On a side note regarding the AMD burnout issues in general, my number one question is how will all this be wrapped up after the issue is fully resolved. The issue is rare but people don't want to be left hanging on a thread wondering if their motherboard could have degraded their CPU. AMD should make it clear to customers the scope of potentially affected CPUs, whether that be all AM5 CPUs on any AM5 board or just certain motherboard models and only if EXPO was enabled and offer an expedited RMA to all those potentially affected CPUs. I think the worst thing AMD could do is fix the issue but not clarify to customers who could have had their CPUs potentially degraded, especially for those that enabled EXPO.
Posted on Reply
Add your own comment
May 13th, 2024 14:49 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts