- Sep 28, 2005
- 20,882
- 3,230
- 126
I have 5 was my point. And yes, untested and stopgap apply. But why are the "whiners" the non-AMD owners ?
you NEED to stop.
Please just stand up.. and go take a walk.
I have 5 was my point. And yes, untested and stopgap apply. But why are the "whiners" the non-AMD owners ?
I have 5 was my point. And yes, untested and stopgap apply. But why are the "whiners" the non-AMD owners ?
An ASUS X670E board lists on specs:So AMD designed EXPO memory. The motherboard manufacturer, in support of this design, includes a setting that uses the MEMORY MANUFACTURER'S design frequency specification. So if you use that, you are not exceeding the design spec. Also, right at the bottom of the AMD spec page is this:
" Supported Technologies AMD EXPO™ Technology"
But then AMD says their chip runs at DDR-5200 max listed. So which is it ? You can can make the argument either way IMO. BUT when you consider "excessive SoC voltages destroy the chips' thermal sensors" then you definitely are going outside then spec.
and that the board supports EXPO.Memory: 4 x DIMM, Max. 128GB, DDR5 6400+(OC)/6200(OC)/ 6000(OC)/ 5800(OC)/ 5600(OC)/ 5400(OC)/ 5200/ 5000/ 4800 ECC and Non-ECC, Un-buffered Memory
First, a question. Do you have an AM5 motherboard ? Or is all this out of thin air ?An ASUS X670E board lists on specs:
and that the board supports EXPO.
Is it true that motherboard (through UEFI or drivers) provides all the tools that are used to modify clocks, voltages, etc?
Obviously the CPU and memory manufacturers have to play along -- there were "cannot overclock" CPUs?
The motherboard has tools to adjust memory specs. XMP and EXPO are some of those tools.
Similarly, one can hit the pedal to the metal in a car and it will go faster than the speed limit. Why do car manufacturers "support" speeding?
Granted, having a "standard" way to exceed the speed limit (XMP/EXPO profile) is not something that I recall seeing in a car.
Why do motherboard manufacturers add the tools for overclocking? Why some cars have way stronger engine than needed for normal use?
Customers that pay? Besides, all these "warranty void" customers have no option but to buy more, which sounds like "profit".
Apparently AMD and motherboard manufacturers did not have the EXPO "standard" nailed down properly.
I knew GN was on it after finding out they had bought one or more damaged CPUs to investigate. This will be very interesting.The plot thickens? GN has been testing the affected mobos/cpus apparently. Video being put together he says.
You know you guys NEED to chill out with all the Anti-Anti AMD.
I am hearing the same thing as tamz_msc in people reporting the cpu is bricked or board is bricking after updates.
So you guys are going to call me liar as well?
Really?
You guys wanna attack him instead of doing a little debugging on reddit and the web?
Here... new bios's are BRICKING some boards or killing CPU's.
And what useful info do those that do have AMD CPUs have to provide? "Mine didn't blow up (yet) " ?Those who do not own an AMD CPU have no usefull info to provide, basically they are just here to re hash whatever they found in the net that suit their taste and/or agenda, as aknowledged by some usual suspects s behaviour...
With the amount of press this is getting, there is a silver lining. The legendarily horrific Asus customer service won't be able to screw over customers without facing the wrath of the internet mob.The plot thickens? GN has been testing the affected mobos/cpus apparently. Video being put together he says.
"GN asking questions:
Asus: attempts to throw AMD under the bus
Also ASUS: trips over own deceit while trying to throw AMD under bus and accidentally throws itself under the bus
GN: is the bus
Still putting the videos together, but there's been a lot of progress."
And what useful info do those that do have AMD CPUs have to provide? "Mine didn't blow up (yet) " ?
Nobody said that all 7000 CPUs will blow up so that info is useless as well.
Maybe I should be glad I haven't brought my 7950X3D online yet.
Do we have any actual numbers on how many people have been affected by this problem?
Saw your comment and immediately checked to see whether you had a MSI board. That's something "normal" for MSI, if I may be allowed to write without actually owning a Zen 4 system. (not a jab at you @In2Photos)Something to note was that when manually setting vSOC if I put it anything at 1.300V or higher the value is RED indicating the value is over the safe range, yet the motherboard still applied 1.350V in auto. I'm not on my system nearly as much as my daughter or someone like Mark using it 24/7, but I have not experienced any issues either.
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.3V. 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.
The cap on SoC voltages looks to be the primary change in the AGESA firmware rollout, although AMD has identified a possible voltage rail within the CPU that is causing the burnouts. Along with SoC voltages, AMD has put a limit within the firmware that prevents the Ryzen 7000 CPUs from going beyond specification.
Statements from AMD and various MBs manufacturers can be found here :
AMD Identifies Root Cause of Ryzen 7000 CPU Burnout Issue, Related To Higher Chip Voltages
AMD has identified the root cause of the Ryzen 7000 CPU burnout issues which happen to be higher voltage on the chip.wccftech.com
Where are you reading this?So no Auto settings causing those few CPU deads but manual oced settings increasing some voltajes too high. It was pretty obvious.
Yeah I've seen this behavior all the way back to my X58 build (MSI X58 Pro).Saw your comment and immediately checked to see whether you had a MSI board. That's something "normal" for MSI, if I may be allowed to write without actually owning a Zen 4 system. (not a jab at you @In2Photos)
MSI and probably other mobo makers have this "we know better" approach in which they caution the user not to increase a parameter beyond a certain value. Then they go ahead and increase that value themselves. For example, on my current MSI board, the Auto value for System Agent is 1.35V and yet attempting to manually set VCCSA above 1.2V will turn the value RED.
Imagine the confusion this creates for a beginner. Is the system going to burst into flames? Is the RED indicator just a lie? "Fortunately" it's the latter, although this sets the stage for the day when the RED indicator will be true and the user will simply ignore it.
I don't know about anyone else but I'm planning to wait a few days/weeks to make sure these new BIOS don't have some other quirk since they were rolled out so fast.
Statement from AMD:
It looks like it was a bit more than VSOC:
With the amount of press this is getting, there is a silver lining. The legendarily horrific Asus customer service won't be able to screw over customers without facing the wrath of the internet mob.
Maybe I should be glad I haven't brought my 7950X3D online yet.
Do we have any actual numbers on how many people have been affected by this problem?
Yeah I've seen this behavior all the way back to my X58 build (MSI X58 Pro).
Where are you reading this?
BIOSTAR's statement came before AMD's second statement.For example, Biostar official statement: