@Sonix

Can you please add -- 1.70.xxx's LGA2011 206D6 - 61C, 206D7 - 713, 306E4 - 42C microcode info data to 1.69.xxx version please?

Yes I know, I consciously put it there to immediately catch your attention.
There is also CPUID 306A9 --> 0x1F new microcode for i7-4960X, i7-4820K, i7-4930K has to be added for socket 2011 too.
Waiting for new 1.69.xxx version, have a successful good work on it, there are lots of work to do.

Thank you....

I have come across some odd behavior. I can update Sandy Bridge microcodes without issue using UBU 1.69.15 or UBU 1.70.a14 DEV. However, Haswell microcodes appear to show twice and update twice, throwing an incompatible file size error. But if I go back to UBU 1.69.14, then the Haswell microcodes only show once and microcode updates OK.

@Sonix,

UBU v1.70.a14_DEV_incl-Update2 --> Can not successfully initialize and add 42C version, still inserts 42A!

UBU_v1.70.a15-DEV_without-MMTool --> Problem fixed. Thank you again!

Thanks for all the good work with UBU

Updated my Uefi Bios IVB to microcode 1F and the SNB to microcode 2D flawlessly with "UBU_v1.69.15.2_incl-Update2_without-MMTool" (used MMTool v5.0.0.7). Now i'm waiting Microsoft to patch "mcupdate_GenuineIntel.dll" because it's still the 2015 .dll with microcode 1C listed inside, so it does not match it anymore.





Thanks again to the developpers of UBU Tools.

My attempts to update my CPU microcode for my Sandy Bridge Z68 / i5-2500K were finally successful!

I ended up using UBU v1.69.15+Update2 resp. 1.69.15.2_incl-Update2 (3/7/18) along with MMTool 5.02.0024. I also used option "m" (User Select Microcode File) and browsed to the correct .bin file as opposed to using option "1" (Update CPU) like I have done in the past.


Here is the microcode list BEFORE the update:




Here is the microcode list as it appeared when I tried using option "1" (Update CPU) - this version caused boot looping:




This is the microcode list that was produced by using option "m" (User Select) - this version worked:




Here's the proof! Note the newest "2D" microcode listed!





My working theory is that option "1" had worked (a long time ago) when I previously updated the microcode because the sizes matched, thus the offsets remained constant. These new microcodes (Ivy Bridge / Sandy Bridge) changed size; thus, I think my BIOS was trying to load whatever microcode it found at offset 0x347390. The option "1" update placed the Ivy Bridge mcode there, but option "m" user select update allowed me to only place the Sandy Bridge mcode, which placed it of course at 0x347390.

I'm not sure why my BIOS was previously OK with the Ivy mcode at 0x347390 and the Sandy mcode at 0x34CB90. My wild guess is maybe it was coded to look for mcode at specific offsets? In any case, I'm good to go! Hopefully this helps someone trying to update a similar platform.

Thanks to Fernando and SoniX for UBU!

Zitat von karakarga im Beitrag #3722

---

Latest microcode revision guidance March 06 2018 released!
Horrah! Ivy Bridge and Sandy Bridge CPU's patched this time....

Ivy Bridge:
CPUID 306A9 --> 0x1F new microcode for i7-4960X, i7-4820K, i7-4930K and notebook processor serie
CPUID 306E4 --> 0x42C new microcode for Xeon E5 v2 serie (instead & update for buggy 42A)
CPUID 306E7 --> 0x713 new microcode for Xeon 4 CPU serie

---

@aiocr

I know there is a huge list....

3rd Generation Intel® Core™ Mobile Processor Family,
Intel® Pentium® Mobile Processor Family, and Intel®
Celeron® Mobile Processor Family

and

Socket 1155 processors got this code as well....

I have updated my post, thank you.

Zitat von HaswellHeat im Beitrag #3739

---

I have come across some odd behavior. I can update Sandy Bridge microcodes without issue using UBU 1.69.15 or UBU 1.70.a14 DEV. However, Haswell microcodes appear to show twice and update twice, throwing an incompatible file size error. But if I go back to UBU 1.69.14, then the Haswell microcodes only show once and microcode updates OK.

---

@Sonix

I have long ago, (6-8 months) updated my Sony Vaio VPCF21Z1E with UBU_v1_69_5 to the Ivy Bridge "1C" and Sandy Bridge "29" microcodes.
But with "UBU_v1.69.15.2_incl-Update2_without-MMTool" it can not update to Ivy Bridge "1F" and Sandy Bridge "2D" microcodes,

it wrote:
Checksum correct.
Checksum correct.
Generate FFS Microcode
Preparing for replacement
Update Microcode Patch...

but waits, at the other window it said:
Invalid FFS File

I have used MMTOOL_v5.0.0.7, What can I do?

n/a

Thank you for reply,
But, I have Realtek ethernet on my notebook?

It said "Cannot install drivers. No Intel(R) Adapters are present in this computer."

I will try on my desktop, I have lately made a clean install and yet do not installed Driver Max, but I have done the previous update on my notebook as well. Interesting!

By the way, I have managed to manually replace and insert the new files with using old MMTOOL_v4.50

Both latest UBUs need updating to Intel Ethernet Adapter Complete Driver Pack v23.1 for everybody

https://downloadcenter.intel.com/search?...Adapter+windows

Image versions in BootIMG.FLB

Combo Image Version Name 1.1876.0

Combo Rules v4.67.00
Clp-Loader Option ROM v3.0.90
40G Interface Module v1.0.53
iSCSI Option ROM v3.1.30
iSCSI Setup Option ROM v3.1.30
FCoE Option ROM v1.8.29
Intel(R) Boot Agent FE v4.2.08
Intel(R) Boot Agent GE v1.5.85
Intel(R) Boot Agent XE v2.4.16
Intel(R) Boot Agent XE (X550) v2.4.16
Intel(R) Boot Agent I40E v1.0.66
Intel(R) Boot Agent CL v0.1.13
UEFI x64 PCI gigabit driver v3.5.22
> UEFI x64 PCI-E gigabit driver v8.3.04 <
> UEFI x64 10 gigabit driver v6.7.04 <
UEFI x64 40 gigabit driver v3.0.05
UEFI IA64 PCI gigabit driver v3.5.22
UEFI IA64 PCI-E gigabit driver v8.3.04
UEFI IA64 10 gigabit driver v6.7.04
UEFI IA64 40 gigabit driver v3.0.05
OCD Option ROM v0.9.04
UEFI x64 FCoE Driver v1.2.21

Thanks !