Hello

would it be possible to add the microcode for the platform 2066 (Skylake-X) ?

Thanks

Zitat von tistou77 im Beitrag #3407

---

would it be possible to add the microcode for the platform 2066 (Skylake-X) ?

---

Zitat von SoniX im Beitrag #3408

---

For LGA 2066/1151v2 will be in next version 1.70.

---

There are any new microcodes?

Read somewhere that microcodes from nov 17 were not stable for haswell cpu.

Question, I didn't see it in the release thread, and search hasn't been helpful.

Is it possible to update to the latest AGESA Microcode? (990fx board, ASRock is painfully outdated with AMD AGESA OrochiPIV1.2.9.0)

And if so, how... im so lost its depressing!

Hello Net7,

it should be possible & there some friendly guys in this forum, who can do this.
But for your special AGESA Microcode v1.2.9.0 I've seen some benchmarks in the internet, there this MC is faster than newer ones like v1.5.0.X.

Best regards, MiMo

may I suggest a small "cosmetic" addendum to the UBU tool?
what about the option to change the image in the BIOS splash screen with a customized one (maybe something Sonix or Win-Raid inspired)?

I created a Bios for my Z97-A / USB3.1 with the latest Haswell (23) microcode. I also added Broadwell (17) so the _FIT_ "fits" without needing a hexeditor since I propably will never have a Broadwell in this board.
UBU renamed it accordingly to the crashfree rules.
But I am not able to flash it. I formated an USB stick with Fat32 and placed the file Z97AU31.CAP in the root folder as it is on the mainboard dvd but no luck. I also created a DVD with it (since i have no cds left) and the result was the same (for the dvd version I also added new versions for all option roms)
When I try to flash it directly from the Bios I get a warning that this is not a proper Bios file, probably because of signature issues?
What can I do?

any USB flashback button on mobo?

@SoniX

I am trying to understand why this happen:

I have a mod version of my BIOS where the AGESA module (AmdAgesaDxeDriver) was updated from v1.5.0.0 to v1.5.0.7. When i open it with any regular version of UBU, i get a report that v1.5.0.7 is installed, but when i open it with the test version of UBU v1.69.10.1, i get a report that v1.5.0.0 is installed instead.

Any advice why this happen?

Here is my BIOS if you want to reproduce the reports with UBU yourself.

Because AGESA is placed in different files. If you open the BIOS in UEFITool and look for the string 'agesa', then several files will be found.
Also, if you scan these files, you can see that AGESA is going to the manufacturer for each motherboard individually. That is, you can see the model of the motherboard.

In UBU 1.69.10.2, for Aptio4, an AGESA file containing microcodes is extracted. Previous versions extracted any file? the contents of the string "agesa"

@Margus no I followed the guide on asus website and the same is also printed in the manual.
When I burned the DVD, I notice a spin up asap after the pc starts, so I guess the crashfree seems to access it but it does not accept my bios on the stick ...

maybe @SoniX can say something about it?

Thx SoniX, just used your test UBU v1.69.10_2 and updated to microcode version 23 along with the rest of the EFI drivers.
Ran like a champ!

Used the USB Flashback method on my trusty 'old' Asus Z87-Deluxe motherboard and it's running smooth as glass on the Windows 10 x64 Build 17025
Updating to build 17074 as we speak...

Cheers on all the hard work you and the rest of the crew do, in making this the 'go to' joint for Bios modding and updating.
So don't go having a "Meltdown" cause "In-Spectre" gadget has got you covered... :)

Hans

Zitat von General_Probe im Beitrag #3418

---

@Margus no I followed the guide on asus website and the same is also printed in the manual.
When I burned the DVD, I notice a spin up asap after the pc starts, so I guess the crashfree seems to access it but it does not accept my bios on the stick ...

---

@Fernando
Hi Dieter,
the VBIOS package link in the first post is broken