AMD AGESA 1.0.0.3ABA Buggy, Company Pulls it from Motherboard Vendors

[bug]

Bc it's not new AGESA and the original update for zen 2 works fine. They broke a working version.

Ah, updating stuff that works. Gotcha.

 

[Manu_PT]

If Intel did crap like that the internet would bash the heck out of them. double standard

If Intel or Nvidia had these type of bugs, bloated and cahotic bios, a staff member telling you that 1,5v voltages are "normal" at stock, CPUs not working with some operating systems (mainly Linux distros) and games, CPUs not reaching the advertised turbo boost clocks, etc, internet would simply go wild; simple as that.

But as it is AMD and they present objectively more value, no one complains as much. They are easier to defend. You know how it works.

I already said on another thread that we are having a nightmare on the store with this release. Most B450 motherboards have huge problems. They either don´t boot and you have to clear CMOS, when they boot you have a 65w TDP chip hitting 1,5v just by watching an youtube video and you need to manually change 3 or 4 voltage values to calm things down, just to see your CPU not hitting even close to the turbo boost, with 1 core only!!!

Then you can imagine the amount of customers that are complaining and returning their chips/mobos and the amount of work and troubleshoot the staff has, because you have a "warranty" that the new shiny AMD CPUs work on every motherboard chipset... Total nightmare.

 

[Mussels]

A BIOS update was released, that had a bug.
This was not an auto update, or forced update. Very few people ever installed this update, and had issues from it.
It was recalled, before it caused major issues.

AMD are smashing out updates incredibly fast to iron out bugs on a newly launched platform, if you arent fixing a bug you simply have no need to be on these beta BIOSes in the first place.

 

[Crackong]

If Intel did crap like that the internet would bash the heck out of them. double standard

No they won't, because next gen is LGA1200, you can't even fit the new CPUs in a z390 MB.

 

[Manu_PT]

No they won't, because next gen is LGA1200, you can't even fit the new CPUs in a z390 MB.

But you could fit the 9th gen CPUs in a z370, b360 and h370.

 

[Crackong]

But you could fit the 9th gen CPUs in a z370, b360 and h370.

But Intel 8th and 9th gen are in the same architecture (Coffee Lake)
While Zen2 is not the same architecture as Zen(+).
Ryzen 3000 can run on 2 generations-old x370 / B350 MBs which is optimized for a different architecture.
Can a 9900k run on a z270 MB?
Someone did that with BIOS / physical modifications, you can check how buggy it is.

 

[Octopuss]

Because you botched the implementation of a hardware instruction that's supposed to generate random numbers. And because, you didn't test properly because releasing.

How do microcode updates work anyway? If it's physically wrong in the CPU, how can that be fixed?

 

[bug]

How do microcode updates work anyway? If it's physically wrong in the CPU, how can that be fixed?

Microcode control part of the way the CPU does things. It is written in BIOS/UEFI and loaded at every boot. The OS can also do this, this is how you get newer firmware before your motherboard manufacturer starts distributing newer versions or if you have no idea how to update the BIOS/UEFI. It obviously can't fix defective hardware (it could, best case scenario provide a workaround).
For example, let me get back to Intel's FDIV bug. Floating point division is one of the more expensive operations you can do at hardware level. So instead of figuring out everything from scratch at every computation, the CPU does what you did in school: it "learns" the results of the most common computation by heart. Just like you learned the multiplication table, it too knows a table of common results, but for division. The FDIV bug meant this table was incorrectly written in silicon, thus some operations would return wrong results. Because this was all written in silicon, Intel had to physically replace affected CPUs. Nowadays, this is written in microcode and is fixable by simply giving the CPU an updated table to work with.
I don't know how that works for RDRAND, because I have seen no technical documentation describing the bug. Just its symptoms.

 

[eidairaman1]

A BIOS update was released, that had a bug.
This was not an auto update, or forced update. Very few people ever installed this update, and had issues from it.
It was recalled, before it caused major issues.

AMD are smashing out updates incredibly fast to iron out bugs on a newly launched platform, if you arent fixing a bug you simply have no need to be on these beta BIOSes in the first place.

And beta bios always have disclaimers.

If Intel or Nvidia had these type of bugs, bloated and cahotic bios, a staff member telling you that 1,5v voltages are "normal" at stock, CPUs not working with some operating systems (mainly Linux distros) and games, CPUs not reaching the advertised turbo boost clocks, etc, internet would simply go wild; simple as that.

But as it is AMD and they present objectively more value, no one complains as much. They are easier to defend. You know how it works.

I already said on another thread that we are having a nightmare on the store with this release. Most B450 motherboards have huge problems. They either don´t boot and you have to clear CMOS, when they boot you have a 65w TDP chip hitting 1,5v just by watching an youtube video and you need to manually change 3 or 4 voltage values to calm things down, just to see your CPU not hitting even close to the turbo boost, with 1 core only!!!

Then you can imagine the amount of customers that are complaining and returning their chips/mobos and the amount of work and troubleshoot the staff has, because you have a "warranty" that the new shiny AMD CPUs work on every motherboard chipset... Total nightmare.

Give it a rest will you. You troll all amd threads i noticed.

 

[Dave65]

If Intel did crap like that the internet would bash the heck out of them. double standard

Yeah, Intel has never done anything like this, right?

 

[TheoneandonlyMrK]

I change bios like they are underware , for get my clocks up , bios before and after are fine.