• 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.

AGESA 1.2.0.A update

Sitkam

Sitkam

Joined
Mar 30, 2023
Messages
20 (0.02/day)
System Specs
Processor AMD Ryzen 5 5600
Motherboard MSI B450 TOMAHAWK MAX
Cooling Arctic Freezer 34 eSports DUO
Memory Team Group 32GB (2 x 16GB) DDR4 3600MHz Dark Za CL18
Video Card(s) MSI NVIDIA GeForce GTX 1660 Super Gaming X
Storage Samsung SSD 860 EVO 500GB / INTEL SSDSC2BW120A4 120GB / Seagate ST4000DM004-2CV104 / WDC WD40EZRZ-22
Display(s) AOC 24G2U IPS 23.8" 144Hz
Case Coolmaster N300
Power Supply Seasonic PRIME Ultra 550W Platinum
Mouse Razer Basilisk V2
Keyboard Corsair K55 RGB Pro
Software Windows 10 Pro 64
How things are going after AGESA 1.2.0.A update?

I own a b450 tomahawk max, my oc ram profile was working good without issues with agesa 1.2.0.7 and after 1.2.0.A update, a mess with my RAM OC. Tried several configs that worked in agesa 1.2.0.7
but no luck at all. so I flashed back 1.2.0.7 and all running good now again.

1685460046588.png
 
I don't know what might have changed. Not having pushed the RAM oc to its limit at previous UEFI versions and the same settings are stable on the latest 1.2.0.A for days now using the same board as yours. Different CPU & RAM sticks though and settings for sure.
 
HD64G said:
I don't know what might have changed. Not having pushed the RAM oc to its limit at previous UEFI versions and the same settings are stable on the latest 1.2.0.A for days now using the same board as yours. Different CPU & RAM sticks though and settings for sure.
Click to expand...
I see, but I'm not even using any CO config. My CPU is at stock settings. I don't understand. Thanks a lot for your feedback
 
Mine f***** up as well - got it stable at 3666 MHz.....odd with that BIOS update

2023-05-30_20-34-59.png
 
AFAIK AGESA 120A removed the EDC voltage cap which was introduced ages ago.
 
No update for my mobo yet :(
 
Ok, so after a lot of time dealing with RTT's, CAD's and procODT I got this! Stable with the latest BIOS (1.2.0.A) for my board. I guess for c-dies is not bad at all. And no WHEA errors found. That's enough for me.
 

Attachments

  • 2023-07-25 22_54_37-Window.png
    2023-07-25 22_54_37-Window.png
    52.4 KB · Views: 860
  • 2023-07-25 23_04_18-Window.png
    2023-07-25 23_04_18-Window.png
    111.4 KB · Views: 993
  • 2023-07-25 23_07_36-Window.png
    2023-07-25 23_07_36-Window.png
    37.6 KB · Views: 839
This new Agesa update was only ment as a solution for the TPM, it contains a LOT of security fixes and mitigations.
 
I'm still on bios 4403 AGESA 1.2.0.7. (2022/05/31). Is this latest version worth it?
I'm on a Asus x570 TUF plus with stock 5800X3D and Crucial Ballistix Elite @4000mhz
 
ice_v said:
I'm still on bios 4403 AGESA 1.2.0.7. (2022/05/31). Is this latest version worth it?
I'm on a Asus x570 TUF plus with stock 5800X3D and Crucial Ballistix Elite @4000mhz
Click to expand...
From the perfomance point of view, i don't think so. I did it whithout any reason, in spite of the latest one come out to solve security issues as explained by ice_v. so if you are good with that one, just keep it.
 
Sitkam said:
How things are going after AGESA 1.2.0.A update?
I own a b450 tomahawk max
Click to expand...
I have b450 tomahawk and I am unable to update any BIOS after 7C02v1E (AGESA 1.0.0.6), I get BSOD at boot due an invalid signature.
I have tried every single BIOS ever since, but nothing helped. I have a standalone TPM, so I have "the bad" fTPM disabled to avoid issues.
 
TairikuOkami, did you tryed to use the usb flash back procedure? I did it myself twice, and works like a charm
 
ice_v said:
I'm still on bios 4403 AGESA 1.2.0.7. (2022/05/31). Is this latest version worth it?
I'm on a Asus x570 TUF plus with stock 5800X3D and Crucial Ballistix Elite @4000mhz
Click to expand...
Nope, it will not change anything. As said it was only to close some loopholes in the fTPM, if you use Bitlocker Encryption then YES you should update.
Don't forget then to set Bitlocker to Suspend Protection BEFORE you update! If not, it will ask your 48 digit Recovery key on boot. If you don't have this, you can kiss your data goodbye.

Screenshot 2023-08-01 020919.png
 
Last edited:
After updating to the 1.2.0.A I cannot see latency dropping below 60ns while being ~58ns with the previous versions. I think that something have changed relative to security that made that decrease in latency. Anyone who have seen that change?
 
No problems before and no problems now, as long MCLK/FCLK/UCLK is not above 1867.
3GUEc5g.png
qlJaG3V.png
 
It is really nice using this version. I flip back and forth between my 5900X and 58X3D and not having to flash back and forth for certain performance benefits/advantages is super nice.

I think I will just wait a bit :laugh:
 
Return address fault?? So i can send my flawed ZEN 3 back to the return address?:laugh:

Anyway better then the latest fault for Intel, where you lose 30 percent power again...
 
SPDIF said:
where you lose 30 percent power again...
Click to expand...
I had my 3770K for 1 month before they started rolling out mitigations. I lost 100MHz off the top, and I think around 8-10 GFlops. in performance. And then later on a microcode update raised the base voltage.. like it didn't run hot enough as it was :D
 
Intel says again it's better to TURN OFF hyper-threading... :banghead:

A senior research scientist at Google has devised new CPU attacks to exploit a vulnerability dubbed Downfall that affects multiple Intel microprocessor families and allows stealing passwords, encryption keys, and private data like emails, messages, or banking info from users that share the same computer.:shadedshu:
 
Last edited:
SPDIF said:
Intel says again it's better to TURN OFF hyper-threading... :banghead:

A senior research scientist at Google has devised new CPU attacks to exploit a vulnerability dubbed Downfall that affects multiple Intel microprocessor families and allows stealing passwords, encryption keys, and private data like emails, messages, or banking info from users that share the same computer.:shadedshu:
Click to expand...

Isn't this only for people who can access your computer physically? If you are the only user of your pc, then you have nothing to worry about from what I understand
 
SPDIF said:
Anyway better then the latest fault for Intel, where you lose 30 percent power again...
Click to expand...
Not saying I don't believe you but I'd like to see supporting evidence for that. I am intensely curious about how these security updates have changed performance however this would need to be carried to a different thread.
 
Last edited:
HD64G said:
After updating to the 1.2.0.A I cannot see latency dropping below 60ns while being ~58ns with the previous versions. I think that something have changed relative to security that made that decrease in latency. Anyone who have seen that change?
Click to expand...
no, on mine is around same latency than before. to make it work i changed procODT, drvstr's and vddp/ccd/iod/soc

SPDIF said:
New AGESA update coming soon this month... AGESA 1.2.0.B and again... Yeah you guessed it... Mitigations. :cry:

Click to expand...
omg , then the party will start over again...jesus christ!
 
This BIOS update will not be available to everyone, some manufacturers will choose to leave it as an OS Microcode update, with loads every time at boot.
 
You must log in or register to reply here.
Back
Top