Thursday, April 27th 2023
AMD Releases Second Official Statement Regarding Ryzen 7000X3D Issues
AMD has today released another statement to the press, following on from controversy surrounding faulty Ryzen 7000X3D series processors - unlucky users are reporting hardware burnouts resulting from voltage-assisted overclocking. TPU has provided coverage of this matter this week, and made light of AMD's first statement yesterday. AMD ensures customers that it has fully informed ODM partners (motherboard manufacturers) about up-to-date and correct voltages for the Ryzen processor family - yet user feedback (via online hardware discussions) suggests that standard Ryzen 7000 models are also being affected by the burnout issue - this side topic has not been addressed by AMD (at the time of writing). This second statement repeats the previous one's recommendation that affected users should absolutely make contact with AMD Support personnel:
AMD has released AGESA updates to involved hardware parties, in hopes that motherboard vendors will distribute newly overhauled BIOS firmware updates to end users. AMD recommends that customers keep a watchful eye on mainboard download pages, reflecting advice already given by its many board partners.
Source:
Anandtech
AMD Statement"We have root caused the issue and have already distributed a new AGESA that puts measures in place on certain power rails on AM5 motherboards to prevent the CPU from operating beyond its specification limits, including a cap on SOC voltage at 1.3 V. None of these changes affect the ability of our Ryzen 7000 Series processors to overclock memory using EXPO or XMP kits or boost performance using PBO technology. We expect all of our ODM partners to release new BIOS for their AM5 boards over the next few days. We recommend all users to check their motherboard manufacturers website and update their BIOS to ensure their system has the most up to date software for their processor.
Anyone whose CPU may have been impacted by this issue should contact AMD customer support. Our customer service team is aware of the situation and prioritizing these cases."
136 Comments on AMD Releases Second Official Statement Regarding Ryzen 7000X3D Issues
If you have an AM5 Asus board, i'd worry.
And you do. I'd keep PBO disabled, enable EXPO but keep RAM clocks 'low' (5600 or lower) and manually lock SoC to something safe, like 1.20v
You could get answers and a BIOS fix in a week, your board may not even be affected - but keep the hardware alive by running the DRAM and SoC lower until you know for sure.It's been confirmed that the software readings are not accurate on asus boards at least, when they failed they showed 1.10v to the SoC while a hardware probe read 1.80v
The newer BIOSes have limits that should prevent the over-voltage happening, even if the software reading is bugged out
Asus Gigabyte and MSI have all had problems with high end motherboards, Now we wait and see if its an AMD issue, the board makers, or a hardware problem (specific VRM's they all had in common with a fault, etc)I've seen this on AM4 in the past too, you can set voltages in the "AMD overclocking" section of the BIOSes, but the 'vendor' sections (asus, giga etc) always has priority and their setting is chosen
LLC settings could also be involved here, and might be a way to keep things safer by avoiding automatic LLC and setting it to the droopiest values, if it's stable for you
//
So, is ASUS hardware crappy or only their BIOS ??
According to GN, if you set the SoC voltage to auto in the asus side of things and then manually set it on the AMD overclocking section, you get accurate locked SoC voltages and not random overvolting based on the RAM speed/EXPO being enabled.
This may apply to your gigabyte board, as well.
The software readings are often in more than one place - you could be finding a software reading for the requested voltage, vs the actual voltage.
Try Zentimings as it tends to show a live voltage that will vary if you fire up benchmarks etc - then use that value to find out which reading is accurate on your board in HWinfo, from the CPU and motherboards readings.
For example the HWinfo value on my board has a voltage for the SoC that seems to be the 'original' voltage, VIN6
1.15V in the BIOS becomes 1.136V here, somehow. This value does not vary at all.
Zentimings varies between 1.1313v and 1.375v while running CPU-Z's benchmark
HWinfo is more or less the same, and shows that it at least gets close to the 1.15v i set under certain conditions
When a load is applied, the LLC counter causes the voltage to rise.
[A] fluctuates greatly, and [C] hardly fluctuates.
is the composite voltage of [A] and [C], not the actual sensor voltage.
If you want to know the true voltage, use a tester to measure the voltage across the capacitor legs on back of motherboard.
*Since voltage drop varies depending on number of capacitors and routing of wiring pattern, etc. characteristics differ for each PCB product.
*If you want faster transient response, set a faster SOC VRM switching frequency. Instead, set the voltage and LLC weaker. (ASUS/MSI)
Digital Multi Meter detects [A].
M/B usually shows .
CPU Sensor usually shows [C].
Example
A=1.400v # SOC VRM capacitor voltage (VID_SOC + Offset + LLC)
B=1.350v # (A+B)/2 # Calculated Virtual SOC Voltage
C=1.300v # SOC Internal Voltage (CPU_vSOC)