@Fernando
I for once am quite shure my bios got correctly flashed, because my original bios did not contain SLIC, the one I am running does. Other than the microcode running at original version, there are no issues with running the modded bios for several days.

One thing I have not tried, in fear of bricking, is using P or D in-place of M in the update option here:
Will it brick my board if I try those options and they are wrong for my board?

@SoniX
It has come to my attention that I probably should have addressed you in post #4827. Any chance you could have a look at this problem?

@Fernando
If you take a look at my previous screenshots you can see that I have been using v1.70 rc20.1 all along. I did not know of any v1.71 version berfore you mention it here, this is the only version I got.
My modded and original BIOS is also attached to my first report. Anyway here is output from opening modded bios:

@Fernando
The date of my UBU.bat says 20-dec-18.

@Fernando
Dates and version for those files are:
drvver.exe 31-jan-19
mce.db 20-jan-19
mce.exe 12-jan-19 v1.24.4.0
uefifind.exe 20-jan-19

@Lost_N_BIOS + @SoniX - I tried your BIOS file for the ASUS Prime X299 Deluxe motherboard and while it booted into the BIOS, when I then try to load into Win 10, I get a consisten D4 error on my motherboard. It will hang and there won't be anything on my screen. The manual says D4 error means the following: PCI resource allocation error. Out of Resources

With the normal bios (no uCodes updates) everything works fine. Any idea how to fix this?

Hi Fernando!

I have similar question. The UBU seems just replace the SATA Raid Driver with GUID begin with 91B4D9C1-****.
But I am interested in VROC driver for an M.2 Raid on CPU. I searched bios, and found these two sections might related to VROC driver:
A0AD1682-AE5C-4A9C-9195-F271585CE07E RSTeRaidDriver
EFE92A04-F5D0-4E44-8757-25B3AFA3BFFF RSTeSataRaidEfi
Is it possible to replace these uefi drivers with latest version by UBU?
Thanks!

Zitat von Lost_N_BIOS im Beitrag #4815

---

@pokuly - open your stock before BIOS in UEFITool NE, on the "Parser tab at bottom", or may also possibly UBU shows it too, unsure - https://github.com/LongSoft/UEFITool/releases
If you see this message on stock BIOS, before modifications, you want to see same exact message and same number of those messages on stock and final mod BIOS >> parsefile: non-empty pad-file contents will be destroyed after volume modifications
Yyou want same before and after mod, if it's missing after mod but was there before, then don't flash BIOS (usually wont work properly, tiny chance sometimes it does)

---

@Fernando, @SoniX: Got a new data-point regarding the microcode not updating problem.
I tried another approach:
First I manually updated GOP and VBIOS with mmtool to have something verifiable updated.
Then I updated microcode manually, using [GUIDE] AMI INTEL CPU Microcode Update Guide as a reference. Only I could not find any FIT table at all in my BIOS.
After this I opened manually modded bios in UBU to verify and got this:

Then I flashed the new bios, result:
The updated VBIOS is detected. (Have not had time to check GOP, but as long as VBIOS is there I know I'm running the new BIOS)
The CPU is still running microcode rev. 353 (the old original one) according to bios and hwinfo64.

The resulting bios-file is attached.

Screenshot from BIOS Setup (CPU info)
If not load Win then check Core OS Linux.

@SoniX
BIOS Screen with CPU-microcode info:


Booting Windows is not a problem; except it refusing to update microcode everything works, not one single problem as of yet running with modded bios.

Edit: Found this while I was messing around trying too se if I could unlock more bios menus.