• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

AMD Ryzen 7000X3D Processors Prone to Physical Damage with Voltage-assisted Overclocking, Motherboard Vendors Rush BIOS Updates with Voltage Limiters

Guess what, genius? If the article says "it was overclocked", I'm gonna assume that it was overclocked.

And also, ASUS already had 2 x3D CPUs that blew that showed up on Reddit. There's a thread about some extremely shady behaviour there too:

But I'm sure I'll hear more sarcasm from you in about 10 seconds and it'll be all about AMD's fault and not ASUS or anything.

In my first post I explicitly state that I think the issue was with mobo makers with some responsibility from AMD due to communication issues (which they have always had). I don't buy the "brainded users" argument -- because it's a waste of time.

You can blame the users all you want (you're holding the iphone wrong! you didn't plug your dongle all the way in!) -- but if the hardware functions inconsistently across boards, or in extreme cases explodes with incorrect bios settings, there's no amount of user blaming that will make that go away. The "holding iphone wrong/dongle not all the way in" crowd has never been correct - that reasoning just doesn't work.
 
oh look now even derbauer is reporting about the damage on his cpu


Yeah, not just X3D's or Asus boards.

Edit: He seems to think it's coming mostly from running AMD Expo - SoC voltage.
 
Last edited:
After reading about all the bugs that came with AM4 this latest news doesn't surprise me in the least. AMD is known for releasing unfinished products.
 
He also reached out to ASUS and got the following response. :) So the issue is officially confirmed.

ASUS Statement.JPG
 
let's hope ASUS (and others) aren't removing ability to underclock / undervolt alongside, for X3Ds
that would be very sad,bad and facepalmish
 
Then I might want to turn off EXPO mode on my 7700X.

How long have you been running it for?

He did test 1.5v on the SoC for half n hour and his CPU didn't kill itself but he's waiting for GN for more detailed info on this matter.
 
I did read recently a post from a PC builder who said the same thing. :D Had tons of RMA's for ASUS boards, he's now only using mainly MSI boards, AsRock (2nd pick) & some GigaByte boards for his builds.

He also mentioned that MindFactory (a major German reseller) isn't selling ASUS boards anymore because dealing with all the RMA's was way too costly for them. Couldn't believe it, checked their homepage and sure enough, there is no ASUS mainboard to be seen, LOL.
How the mighty fall...I always saw ASUS as the highest tier of mobo makers. Never had any problems with them, and been using ASUS and Gigabyte since pretty much forever.
 
How the mighty fall...I always saw ASUS as the highest tier of mobo makers. Never had any problems with them, and been using ASUS and Gigabyte since pretty much forever.
It isn't limited to Asus boards ^^
 
It isn't limited to Asus boards ^^
It's clearly them far more than others.

Now I have to find a new mobo master for my future builds. MSI maybe...?
 
How long have you been running it for?

He did test 1.5v on the SoC for half n hour and his CPU didn't kill itself but he's waiting for GN for more detailed info on this matter.
I've been running EXPO mode on my system for about three months, ever since I built the system.
 
Because, in others, it is under an octocore (7700X and even 7700).
Because you know they have protections that prevent destruction.

A much better question: did AMD provide the correct technical data to motherboard manufacturers? It seems not.

I believe AMD did provide the correct tech data to the mobo manufacturers. The mobo manufacturers just don't give a shit. All they care about is that their board "won" in benchmarks/reviews.
 
I've been running EXPO mode on my system for about three months, ever since I built the system.

6000Mhz on the mem?

If your keen i would take the cpu out and have a look see for the so called “burn mark” on the cpu . If you cant see anything your probably ok and this could be due to just bad batches or maybe even mobo related. More info is needed at this time.
 
If your keen i would take the cpu out and have a look see for the so called “burn mark” on the cpu .
I really don't want to do that. That would involve cleaning the CPU and heatsink and applying new paste. Not at all something that I want to do on a Monday evening.

I've since disabled EXPO on my memory and from here on out, hope that nothing bad happened.
 
I really don't want to do that. That would involve cleaning the CPU and heatsink and applying new paste. Not at all something that I want to do on a Monday evening.

I've since disabled EXPO on my memory and from here on out, hope that nothing bad happened.

You could have also just checked what EXPO had set your SoC voltage to and adjusted down if needed.

Setting EXPO for my 7700x (at launch) on an MSI X670 pushed SoC to 1.35v. I adjusted it back down to default (1.02v) and ran that way without issue until I sold it.
 
Setting EXPO for my 7700x (at launch) on an MSI X670 pushed SoC to 1.35v. I adjusted it back down to default (1.02v) and ran that way without issue until I sold it.
I will check that. Be back in a few.
 
I’m going to assume that the setting I’m looking for is VCORE SOC?

Edit: Posting from my phone.
 
I’m going to assume that the setting I’m looking for is VCORE SOC?

Edit: Posting from my phone.

I'm not sure what Gigabyte calls it, but that sounds right.

I'd set EXPO, boot into windows and see what SoC shows using HWinfo. Then compare to what disabling EXPO shows.

*edit*

Found one of my old posts. Here's where it shows up on an MSI board in HWinfo

1682376026241.png
 
Last edited by a moderator:
OK, this is with EXPO enabled.
1682376094685.png
 
Not at all something that I want to do on a Monday evening.

Yes ofc, in your leisurely time. Sounds like your cpu is fine.

Would just be interesting to have a look see that's all.
 
And this is after putting the CPU through its paces with a C/C++ project compile using Microsoft's Visual Studio C++ Compiler. Yes, EXPO was enabled.
1682376282472.png

It looks like VDDCR_VDD reached a maximum voltage of 1.377 volts while VDDCR_SOC only reached 1.245 volts.

A ran a Cinebench R23 test and the only change was that the VDDCR_SOC only reached 1.246 volts.
 
Last edited:
How long have you been running it for?

He did test 1.5v on the SoC for half n hour and his CPU didn't kill itself but he's waiting for GN for more detailed info on this matter.

The problem with derbauer drawing conclusions from that "test" is that you actually need to be running current through the appropriate rail to see whether VSOC is safe for VDDCR_SOC. All Cinebench is doing is running current through VDDCR_CPU. I can just as easily set a ridiculous VSOC on my APUs and call it tentatively "safe" by running CPU-only loads for an hour.

Same idea why 1.5V Vcore on Zen 2 and later is "safe" in the hands of the stock Precision Boost algorithm, but certainly unsafe once you manually punch in the same 1.5V in the static Vcore box.

Traditionally the only Zen CPUs that can actually run a shitload of current through SOC are the APUs. On AM5 you can also get close since it has an iGPU, but that involves OCing the shit out of the iGPU and running heavy 3D load on the iGPU, something derbauer definitely didn't do by running Cinebench. Through normal memory controller loads alone, the most you can hope for is maybe 20W-ish flowing through SOC.

Given the time he spends around these platforms I thought he'd know some basic fundamentals of Ryzen topology.

1.35V is pretty standard for an EXPO VSOC auto-rule and people have been one-click set-and-forget for months with no problems; I honestly doubt that's what's going on, probably something else in the firmware given Asus' statement and pulling all their old BIOSes.
 
Back
Top