I successfully updated my bios with new microcode, vbios and lan drivers, now I have two questions:
I am on a gigabyte z97x-sli v1.2 (bios F10 beta) with an i5-4690k
My RTS(e) satadriver is at 13.5.0.2164. Can I update to v15?
I updated "haswell" microcode to revision 24, the official bios has more microcode when I scan it with MCextractor.
I know that some microcodes are for other cpus, but I wonder if I can swap to a 5th gen cpu without remodding the bios.

Is there a way to update the current codes without removing the others that are present?

Zitat von FPSUsername im Beitrag #3947

---

.....I know that some microcodes are for other cpus, but I wonder if I can swap to a 5th gen cpu without remodding the bios.
Is there a way to update the current codes without removing the others that are present?

---

@karakarga:

Thanks for reply. You said "those 2 files includes all necessary information....", did you mean these 2 microcode included updates for ALL cpu that this MB support?

If not, doesn't it worse if I changed the CPU because there's no microcode at all?

I have the same question as @FPSUsername. Why UBU remove other microcodes in UEFI file?

Zitat von vinix im Beitrag #3950

---

I have the same question as @FPSUsername. Why UBU remove other microcodes in UEFI file?

---

Yes, one of them includes 32nm processors, the other 22nm processors. In the beğinning, those were different, celeron, pentium etc. They all gathered together in just one file, as l stated above.

@lfb6:
I won't swap, but I want to know why ubu removes other microcodes when updating one.
For RST, I don't use RAID, but I don't know if firmware/microcode v15 is compatible with z97 chipsets. For drivers, I have v15.0.0.1031, the latest that install.

Edit:
Anyway, I updated microcode to v15 and it works. I noticed that station-drivers also has v15.2, v15.5, v16.0 and v16.3. I wonder if those are compatible with z97 chipsets or that ubu hides those if they aren't.

EDIT by Fernando: Unneeded fully quoted post replaced by directly addressing (to save space)

Ubu asks for Haswell/ Broadwell chipsets for both architectures- that's 'good enough' for me (actually I'm completely happy with it!). I even don't know which processors use 306C1 and 306C2 microcodes (engineering samples)?

@FPSUsername

Yes there is. Just look at UBU.bat how UBU does it.
A VERY short guide to do it:

GenFFS -t EFI_FV_FILETYPE_RAW -g x-x-x-x-x -i 001 -i 002 -i pad -i 003 -i 004 -s -o test.ffs

GenFFS (located in UBU/UDK2014 directory)
-t EFI_FV_FILETYPE_RAW (Check ffs type with MMTool -> 'Create Report')
-g x-x-x-x-x (Check GUID type with MMTool -> 'Create Report') there exist two (2) GUID's
-i 001 (first microcode file)
-i 002 -i pad (second microcode file following padding 0xff to keep 0x800 alignement)
-i 003 (third microcode file)
-i 004 (fourth microcode file)
-s (create + update checksum)
-o (output filename

A word of precaution: If you DO NOT KNOW hot to handle a hex editor, DO NOT KNOW about hex offsets, DO NOT KNOW THE OFFSET required for your board - 0x400 or 0x800 -, etc etc. etc.' DO NOT FIDDLE WITH IT. !!! YOU WILL BRICK YOUR MAINBOARD !!!
Again: !!! YOU WILL BRICK YOUR MAINBOARD !!!
Use UBU!

Current spectre patches are completely not working on Windows Server 2016 that I discovered!

Even current spectre patches will be re-done completely by Intel, because new bugs found named spectre new generation (spectre ng).

New patches start to roll out beginning of August seemingly....

@mictlan Yeah, I won't fiddle around with hex editors. I do have dual bios, so in theory, it shouldn't brick my board, since it will return to the backup bios if something goes wrong.

@FPSUsername
Do you happen to have the latest microcode for 306C1, see attached picture?
I can't find it @plutomaniac ucode repo.

@mictlan I only use microcode 306C3, so I have no clue.

@FPSUsername
Now it looks good

I PM'ed you a link with the updated bios file - only ucodes updated @alignement 0x800.
Use at your own risk!