cpu206D7_plat6D_ver00000714_2018-05-08

Many thank you.

Tried updating the microcode for my MSI X299 SLI Plus bios (E7A93IMS.1A0) with UBU 1.70b5, and the board got bricked after flashing (fyi, i'm using modified MMTool v5.2.0.24) . Rollback via secondary bios chip went fine, but i'm not sure if trying again with the latest beta will improve anything.

What i will try right now is updating the microcode for my Asus P8Z68-V Pro (v3603) for the first time with UBU 1.70b8, was using v1.6x for this board up until now.

@javanse For your X299, try b8 and chose to update with MMtool (SoniX has added this possibility in UBU)

I've never been able to update MSI x299 microcode with MMTOOL, manually or with UBU - Always get "Error in saving" error from MMTOOL. (5.0.2.24)

And with earlier UBU (using UEFITool), new bios is created which looks ok (can read back into UBU, and it shows updated microcode), but results in brick when flashed.

I'm now loading latest microcode (4D for 7820x) at boot with https://labs.vmware.com/flings/vmware-cp...e-update-driver until new bios is released.

(Latest bios 1A has microcode 43, which covers some of the speculative execution CVEs, but not all.)


Edit: Just tried updating latest gigabyte x299 UD4 bios with MMTOOL and I do not get the same "Error in saving" message (seems to update successfully) - so this seems to only be a problem with MSI bios...

Updating the P8Z68-V Pro bios v3603 with UBU v1.70b8 went fine, now running microcode 2E. I've used UBU v1.69.17.2 to update everything but the microcode, then used the resulting file in UBU v1.70b8 to update the microcode, and finally flashed the file in DOS via bupdater.exe. FYI, i've modded the bios two times, 1st time with UEFIReplace and 2nd time with MMTool, and the resulting files are bit-identical.

Updating the MSI X299 SLI Plus v1A with UBU v170b8 still doesn't look good to me. When using MMTool, i get the same "Error in saving" error in MMTool as @lettermand99 reports. Using UEFIReplace does work, but produces tons of errors messages while doing its work (see attached screenshots). I haven't flashed the updated file yet.

@lettermand99: the VMware tool doesn't work for the Spectre microcode updates, it simply gets loaded too late in the boot process. You can check for yourself via this script https://gallery.technet.microsoft.com/sc...ontrol-e36f0050

@Fernando

Thank you. :) I already understood this situation. In your case, for i211, version 8 will not work, only compatible 6.6.04.

In BIOSes MSI x299, the PEI volume, where the container with microcodes is located, has a fixed size, and any change thereof leads to a brick.

There are two ideas, but they require testing.
[Method 1]
The first idea is to delete all microcodes, and put new ones in the "Empty" that is in DXE-volume.
[Method 2]
The second idea is known. With the help of MMTool, first remove all the microdots, and then insert new ones. But you will not be able to return all microcodes if their total size is larger than that already exists in the BIOS.

PS I hope that the method 1 will be a working option.

Add:
These methods are available in UBU v1.70 b12.

Only for bios MSI X299 ? For Asus it's always ok with MMTool ?

Zitat von tistou77 im Beitrag #4104

---

Only for bios MSI X299 ? For Asus it's always ok with MMTool ?

---

U - with UEFIReplace - All models
A - with MMTool - Asus x299 or if brick with "U"
[for MSI x299]
M1 - Method 1 - Replace "Empty"
M2 - Method 2 - Delete/Insert microcode
 
 

#

The 4D for Skylake-X (x299) increases the TJMax from 105 to 110°C, and thus the temperatures of the cores, is also increased by 5°C
I stay with 49 for the moment

hi guys, i would like to update microcode on my asrock Z77pro4 using UBU v1.70 b12, when i apply the update i receive this message:

║ Intel ║
╟─┬─────┬───────────┬────────┬──────────┬────┬──────┬──────┬────╢
║#│CPUID│Platform ID│Revision│ Date │Type│ Size │Offset│Last║
╟─┼─────┼───────────┼────────┼──────────┼────┼──────┼──────┼────╢
║1│306A9│ 12 (1,4) │ 20 │2018-04-10│PRD │0x3400│ 0x18 │Yes ║
╟─┼─────┼───────────┼────────┼──────────┼────┼──────┼──────┼────╢
║2│206A7│ 12 (1,4) │ 2E │2018-04-10│PRD │0x3000│0x3418│Yes ║
╚═╧═════╧═══════════╧════════╧══════════╧════╧══════╧══════╧════╝

U - Used UEFIReplace - All models
A - Used MMTool - Asus x299 or if previous option makes a brick.
[Only MSI x299 Seties TEST]
M1 -- Method 1 - Replace "Empty" - Please report
M2 -- Method 2 - Delete/Insert mCode
0 - Cancel
Choice:a
[Preparing for replacement]
Empty GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
patchVtf: PEI Core entry point can't be found in VTF. VTF not patched.
File replaced
[Replacement]
mCode FFS: File replaced
mCode FFS: File replaced
Empty FFS: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
Premere un tasto per continuare . . .

is it safe to flash ?

Thank you for your work

With 1.70b12, option A (Used MMTool) for microcode, it's the same as the option M (Update with MMTool) in the b8 ?

Thanks

With 1.70b12, they dont update the network modules.
Mainboard: ASRock Z370m-ITX/ac
BIOS: v2.10 (>Download link<)

Details about the UBU messages: