AMD's Ryzen 7 7800X3D Selling Nearly Twice as Fast as 5800X3D in Some Regions

[R0H1T]

It wasn't mostly ASUS, it was quite literally everyone pumping the poor things full of juice.

That's just wrong!

Voltage Lockdown: Investigating AMD's Recent AM5 AGESA Updates on ASRock's X670E Taichi​

Spoiler

 

[Dr. Dro]

No it was mostly ASUS.

GN flat out stated the others were typically under 1.3v but had other bugs that could come together to cause problems.

Gigabyte for instance had a bug where BIOS volt settings were being ignored but also that getting to overvolt SOC to over 1.3v wasn't something that typically happened. They had to try and force it to occur....except with ASUS.

My own Gigabyte mobo never went over 1.25v for instance and that was when overclocking the RAM as much as possible.

None of those bugs were related to AGESA though. That was mobo vendors screwing things up which they've done before in the past. GN did a video years ago about the mobo vendors doing the same stuff with Intel motherboards.

AMD's mistake was not clamping down it like Intel did years ago before it turned into a mess. They let the mobo guys do what they wanted and now they get at least some of the blame for that error.

The keyword is "typically" BTW, over at Intel land, they are still overvolting things beyond what they need to do. I think this is a general ill at this point, mobo makers are overdoing it hard in an attempt to ensure that even the worst setups boot and run at stock settings. I had to reduce SA voltage by 0.3v (from 1.2 to 0.9) to get my i9-13900KS to be stable with my RAM kit at the settings I'm currently running on my MSI Z690 Ace.

My reason to state "hopefully the AGESA team gets it together" is reflecting my own poor experience with socket AM4. Horrorshow as far as AGESA went. So many high severity bugs late into the socket's lifetime, at least they got mostly everything (except the EDC bug) fixed, so it should be 99% good (and 100% good if you have the 5800X3D) at this point.

That's just wrong!

Voltage Lockdown: Investigating AMD's Recent AM5 AGESA Updates on ASRock's X670E Taichi​

I've watched GN's video mate. ASUS may have been putting more voltage in than everyone else, but they were far from the only motherboard vendor that had a CPU blow up on them. They are owning up to their mistakes and ensuring warranties are honored, so ultimately that is what matters.

 

[R0H1T]

And can GN testify every motherboard out there was pumping more voltage than 1.3~1.35v for the SoC even at stock? Come on we have facts about two motherboard vendors (just 2 models?) & then you'd like to claim it's everyone who's at fault

 

[Dr. Dro]

And can GN testify every motherboard out there was pumping more voltage than 1.3~1.35v for the SoC even at stock? Come on we have facts about two motherboard vendors & then you'd like to claim it's everyone who's at fault

I don't think it matters, really. If a CPU blew up using mostly automatic settings, such as enabling a memory profile, that is a fatality that would be perhaps understandable in some sort of in-development engineering sample, not on a product that's been validated, shipped and in-market for almost a year. ASUS rightfully caught the most flak, by doing it worse than everyone else, being dismissive and facetious when it came to their stance on warranty (which got them burned good, I loved to see that), but it was obvious that it was an industry-wide, collective communication failure between the IHVs and AMD.

My only dig at AMD here is that they have to review this habit they have of releasing unproven software to the public. They have an excellent community of dedicated fans willing to beta test for them, so honestly, they need to push stable far behind and introduce more layers of stability, "rings" like Microsoft does.

 

[phubar]

The keyword is "typically"

Typically as in "virtually never happens outside of unusual circumstances and can be largely ignored".

BTW, over at Intel land, they are still overvolting things beyond what they need to do.

They don't seem to be killing any chips yet and that goes a long way.

Apparently very very few people had their CPU's get killed but that is enough to taint the whole AM5 platform going by other's comments.

IMO its a dumb but overall minor mistake that is getting or has been fixed by a BIOS update. Intel's FDIV bug was probably a bigger deal then this is.

My reason to state "hopefully the AGESA team gets it together" is reflecting my own poor experience with socket AM4.

Early AM4 BIOS'es were a mess but around the 2000 series Ryzens its been pretty solid for most people.

I've built lots of AM4 systems for family and work since then and they've been boring and reliable. Just the way I like a family or work PC to be.

 

[Dr. Dro]

Typically as in "virtually never happens outside of unusual circumstances and can be largely ignored".

They don't seem to be killing any chips yet and that goes a long way.

Apparently very very few people had their CPU's get killed but that is enough to taint the whole AM5 platform going by other's comments.

IMO its a dumb but overall minor mistake that is getting or has been fixed by a BIOS update. Intel's FDIV bug was probably a bigger deal then this is.

Early AM4 BIOS'es were a mess but around the 2000 series Ryzens its been pretty solid for most people.

I've built lots of AM4 systems for family and work since then and they've been boring and reliable. Just the way I like a family or work PC to be.

Agreed, I wish I could say the same about AM4's bugs though... Ugh I got hit by them all. The USB dropout thing was one I consider completely unforgivable

 

[Bomby569]

What incentive is there for developers to release finished games or hardware manufacturers to truly test their products before launch if people keep awarding them with sales for buggy, unfinished messes.
You get what you deserve.

 

[R-T-B]

What incentive is there for developers to release finished games or hardware manufacturers to truly test their products before launch if people keep awarding them with sales for buggy, unfinished messes.
You get what you deserve.

Mainly that (most) of us devs like to do quality work.

Publishers couldn't give two shits about that however, and they sign the paycheck.

 

[A&P211]

Typically with ambient cooling it is very difficult to kill a CPU.. but not impossible

This comment sounds like my ex-wife and a headless coach-roach.

 

[Ownedtbh]

Mainly that (most) of us devs like to do quality work.

Publishers couldn't give two shits about that however, and they sign the paycheck.

probably because the money runs out

 

[chrcoluk]

On one hand this proves that it was a mistake from their side to delay the X3D chips. If they had released the X3D chips in day 1 of the AM5 release, the platform cost would have been easier for consumers to swallow. Of course I mean with normal pricing for the CPUs, not like $449 for 7700X and $599 for 7800X3D.

On the other hand the problems with voltages and burn ups prove that they might were correct to wait and probably if they had released the X3D chips in 6 months from now they could have spotted the stupidity of motherboard makers of overvolting the chips like noobs.

I can agree with this.

I got the 13700k based on 7000X data and AM5 platform cost (somehow missed the 7000X3D data), although I am happy with my upgrade, I think I "may" (not sure) have paid the AM5 premium for a 7800X3D as truly a beast for gaming.

13700K is also a beast of course for gaming, just a smaller one.

 

[maxfly]

I can agree with this.

I got the 13700k based on 7000X data and AM5 platform cost (somehow missed the 7000X3D data), although I am happy with my upgrade, I think I "may" (not sure) have paid the AM5 premium for a 7800X3D as truly a beast for gaming.

13700K is also a beast of course for gaming, just a smaller one.

My plan was to go with something 7000x3d...until I saw the mb prices. That's what finally pushed me into going 13700k.

 

[wheresmycar]

I can agree with this.

I got the 13700k based on 7000X data and AM5 platform cost (somehow missed the 7000X3D data), although I am happy with my upgrade, I think I "may" (not sure) have paid the AM5 premium for a 7800X3D as truly a beast for gaming.

13700K is also a beast of course for gaming, just a smaller one.

My plan was to go with something 7000x3d...until I saw the mb prices. That's what finally pushed me into going 13700k.

At least you boys bought something comparably great!

I'm a mess with upgrades. 12600K, then 5800X3D (skipped 13th Gen) and since launch thinking about the 7800X3D but i have to admit lost momentum from launch prices. I guess the 9700K is getting the job done and i'm not really trying any newer titles which beg for something snappier or more resourceful with a multi-threaded palette

 

[Deleted member 232534]

My plan was to go with something 7000x3d...until I saw the mb prices. That's what finally pushed me into going 13700k.

Situation with motherboards is very different now.

I finally upgraded my 4670k after i saw the am5 motherboards.

I bought $125 mb which will run pcie5 nvme drives and GPU in a pcie 4x16 mode. I guess you paid $250 for a mb that can only run pcie5 nvme in an adapter if you put your gpu in a pcie4x4 slot?