sirmonkey1985
[H]ard|DCer of the Month - July 2010
- Joined
- Sep 13, 2008
- Messages
- 22,414
1.0.0.6 was a temporary fix by setting a hard voltage limit that manufactures can't bypass, 1.0.0.7 is the actual fix. AGESA 1.0.0.7 takes control away from the AIB's bios settings and puts a hard temperature limit within the cpu microcode so that whether or not the AIB bios protections trip the cpu will automatically trigger an SOC temperature limit protection by reducing the SOC voltage. mostly because it looks like ASUS and potentially others are cheating it by having the controller report the SOC voltage incorrectly to the bios.. for example why even with the 1.3v limit in place with the AGESA 1.0.0.6 the ASUS boards were still pushing 1.4v to the SOC. the temperature limit protection "should" keep that from damaging the cpu even if asus and other AIB's don't fix the voltage reporting. as far as agesa code goes, it's always been a platform wide update because it's easier on AMD and the AIB's.I don’t have a lot of AMD 7000 series on site but all our x670 based boards received AGESA bios updates to fix the issue regardless of which brand they were. If it was only Asus why would Gigabyte need to patch for it?
The “fix” is in AGESA 1.0.0.6, and if the fix is there it would stand that the flaw was there as well. As AMD provides the AGESA and it comes pre compiled it could be many places not all boards may use the effected code the same way though.
I use the term fix loosely here because independent tests are still out on weather it fixes anything or not.
now should the protection of always been there? yes, but if manufactures had stuck to the specifications AMD gave them it possibly wouldn't of mattered. end of the day the AGESA update is AMD doing what they need to do to protect themselves which now puts the liability on the AIB's if failures continue to happen after the update.