• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DigiTimes: AMD market share may hit record low in Q1-16

Page 5 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Most of the consumer board bioses are built with so outdated AGESA that the microcode isn't even affected. For example the newest bios for the newest ASUS boards (970 GAMING/Aura) is based on V1.5.0.2 AGESA and uses 06000822 version microcode. ASUS isn't even remotely the most sloppy company when it comes to updating their bioses. The newest bioses for ASRock newest AM3+ boards are built with V1.2.9.0 AGESA, which dates back to 2H/2012 😀
 
Last edited:
William Gaatjes said:
Here is an English version :

http://www.theregister.co.uk/2016/03/06/amd_microcode_6000836_fix/

Question :
I have an A10-6700. I have a piledriver core too. Is this bug happening with server cpu's only or do richland cpu's also suffer from this bug ?
Click to expand...

Despite both Richland and Orochi Rev. C being based on the same microarchitecture (Piledriver), the cores are not exactly the same. Piledriver APU cores should not be affected by errata #815, of which fix caused this issue.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top