Hallo a quick question.
when i replace broadwell and haswell microcodes in bios i need only this?

Check the Address in the _FIT_
Address 01 mCode + Size 01 mCode = Address 02 mCode

or also
Address 02 mCode + Size 02 mCode = Address 03 mCode

Or the size of haswell microcode dont matters?

@SoniX
Can I suggest a change in UBU.bat?
I did change UBU locally to be able to process bin-file with newest microcode for 2011 platform CPU (IB-E 4930). Option for selection of bin-file for 2011 platform doesn`t work with bin-files, because there is no code for bin-files - only code for pre-processed ffs-files. So I just brutally forced to get needed bin-file completely bypassing the code for 2011 platform microcode file selection and execution (and it worked normally).
It would be nice if manual selection of bin-file (menu item "m") with microcode was processed in same way for all processors.

@mbk1969
In UBU v1.70, for microcodes LGA2011, another mechanism will be implemented. Similarly for other platforms.
You can, in all versions, make changes for yourself.

@SoniX

I did. But for users who are not experienced with bat-files it will be impossible.
Anyway thank you for this work. I was greatly impressed by the things this bat-file can do, and by the clean syntax too. (Although nowadays I prefer PowerShell scripts since I am .Net programmer...)

Zitat von mbk1969 im Beitrag #3380

---

But for users who are not experienced with bat-files it will be impossible.

---

@Sonix
I have not used the Microcode Update feature of UBU v1.69.7 for my CPU Haswell-E on BIOS AMI Aptio 5 ASUS Sabertooth X99 v3801 because you warm: "There may be problems with updating the CPU microcode"

Do I have to understand that with the future UBU v1.70.x this problem will be fixed ?

In my case, for the current UBU version (v1.69.7) I observe you display the Current Microcode Update Revision = "3A".
Is it correct to understand that does reflect the "3A" Revision embedded into the BIOS ?
Is it correct to understand that W10 can ignore it and does apply another one (for various criteria) ?

Tools such as HWINFO64 or SIV64 does display also "3A" but I ignore if it is the BIOS "3A" or the Windows "3A".

I observe that Intel CPU Identification Tool does use different CPUID "datas" such as (for i7-5930K):
Type= 0
Gamme= 6 = Family
Model= 3F
Stepping= 2
Revision= 3A

It is confusing for me to understand what UBU "Platform ID" = "6F" does refer.
Please, can you clarify me ?

Here are attached HWINFO64 and SIV64 screenshots related to "CPUID".

Zitat von 100PIER im Beitrag #3382

---

Do I have to understand that with the future UBU v1.70.x this problem will be fixed ?

---

Some questions.
I successfully updated CPU microcode on ASRock H87 Pro4. Ubu had no warning and PC works fine.
No I wanted to do the same for ASRock H97 Pro4, but I am a little afraid to do. It contains Microcode for Broadwell and Haswell, so I get a message:

  Attention!
If you select two microcode may require an adjustment in the _FIT_
 

and after update the code, I get:

   Attention!!!
Check the Address in the _FIT_
Address 01 mCode + Size 01 mCode = Address 02 mCode
0xFFF36D30  + 0x00002C00  = 0xFFF39930
 

Is this something I need to worry about? How do I adjust and check the _FIT_? What do I need to care if everything is correct?

Also, why many modules get stuck in mmtool ending with:

file size exceeds the volume size
 

Thanks a lot.

Zitat von Morku im Beitrag #3384

---

Some questions.
I successfully updated CPU microcode on ASRock H87 Pro4. Ubu had no warning and PC works fine.
No I wanted to do the same for ASRock H97 Pro4, but I am a little afraid to do. It contains Microcode for Broadwell and Haswell, so I get a message:

1
2
 

  Attention!
If you select two microcode may require an adjustment in the _FIT_
 

and after update the code, I get:

1
2
3
4
 

   Attention!!!
Check the Address in the _FIT_
Address 01 mCode + Size 01 mCode = Address 02 mCode
0xFFF36D30  + 0x00002C00  = 0xFFF39930
 

Is this something I need to worry about? How do I adjust and check the _FIT_? What do I need to care if everything is correct?

---

Zitat

---

Also, why many modules get stuck in mmtool ending with:

1
 

file size exceeds the volume size
 

---

This means that there is no free space in the volume. And for updating you need to use UEFITool.

Thank you for the quick answer.
Before starting to chose a new microcode, I have

Current version - GUID 17088572-377F-44EF-8F4E-B09FFF46A070
 +-----------------------------------------------------------+
 |No|   CPUID  | Platform |  Version |    Date    | Size Hex |
 +--+----------+----------+----------+------------+----------+
 |01| 00040671 |    22    | 0000000B | 17-02-2015 | 00002400 |
 |02| 000306C3 |    32    | 00000019 | 26-02-2014 | 00005000 |
 |03| 000306C2 |    32    | FFFF0006 | 17-10-2012 | 00005800 |
 |04| 000306C1 |    32    | FFFF0013 | 14-06-2012 | 00006000 |
 +-----------------------------------------------------------+
   MPDT None
 _FIT_ in GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1
 01 mCode Address - FFF36D30
 02 mCode Address - FFF39130
 03 mCode Address - FFF3E130
 04 mCode Address - FFF43930
 

After update to latest microcode, mCode Address is still the same:

 +-----------------------------------------------------------+
 |No|   CPUID  | Platform |  Version |    Date    | Size Hex |
 +--+----------+----------+----------+------------+----------+
 |01| 00040671 |    22    | 0000001B | 17-11-2017 | 00003400 |
 |02| 000306C3 |    32    | 00000023 | 20-11-2017 | 00005C00 |
 +-----------------------------------------------------------+
   MPDT None
 _FIT_ in GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1
 01 mCode Address - FFF36D30
 02 mCode Address - FFF39130
 03 mCode Address - FFF3E130
 04 mCode Address - FFF43930
 
   Attention!!!
Check the Address in the _FIT_
Address 01 mCode + Size 01 mCode = Address 02 mCode
0xFFF36D30  + 0x00003400  = 0xFFF3A130
 

So if I am right, everything is fine.
I will check UEFITool.

No u are not:
Check the Address in the _FIT_
Address 01 mCode + Size 01 mCode = Address 02 mCode
0xFFF36D30 + 0x00003400 = 0xFFF3A130 not the same as 02 mCode Address - FFF39130

If u want to be the same for easy use broadwell microcode 17 it has the same size hex as 00002400.
In few word use broadwell microcode 17 and haswell 23 and tell me the numbers.

DONT FLASH THE ABOVE ONE

@ Morku
_FIT_ in GUID B52282EE-9B66-44B9-B1CF-7E5040F787C1
01 mCode Address - FFF36D30
>> 02 mCode Address - FFF39130 <<

Address 01 mCode + Size 01 mCode = Address 02 mCode
0xFFF36D30 + 0x00003400 = >> 0xFFF3A130 <<

Did not match.
In UEFITool we look for the string _FIT_ (as Text, no Unicode) or GUID - see above.
Extract as body..
Open the file in the Hex editor.
Editing FFF39130 on FFF3A130, and Save
In UEFITool - Replace as body..

Sonix the 03 mCode Address0 , 04 mCode Address has no microcodes after using UBU. It safe to leave them always there?

Zitat von boombastik im Beitrag #3389

---

Sonix the 03 mCode Address0 , 04 mCode Address has no microcodes after using UBU. It safe to leave them always there?

---

Oh, thank you for saving me for a bad decission.
Now I am looking into fix the Address 02 mCode. Do I have to do on original BIOS before I copy CPU microcode or on the modded one?
I loaded the modded in UEFITool, searched for _FIT_, found in B52282EE-9B66-44B9-B1CF-7E5040F787C1, extract body... as raw file. Loaded the raw file into hex editor, but I have trouble to find "FFF39130".
Did I extract the wrong file?