Yes, with UBU v1.69.16 and Intel Ivy Bridge-DT (CPUID=306A9) Core-I7-3770K modded BIOS with µC=x1F and W10 x64 RS3 Build 16299.251 the Meltdown and Spectre Vulnerability issue is fixed.

UBU 1.69.16/1.70.a15 outputs files that are slightly different from the files created by 1.69.15/1.70.a14. The difference is only in 3 bytes. Is this normal behavior?

Here's an example with two modified and one original file: http://www49.zippyshare.com/v/WULKvC02/file.html

@Fernando
First of all, thanks, I did it.
Used UBU_v1_69_16 with MMTool 5.02_patched.
Used microcode update function and "m" (manual) mode to prevent Ivy Bridge microcode update (I read here that it could result in random BSOD, now I can't find the source).
Flashed successfully.
Now the question is, re-opening the modified bios with UBU shows a microcode for Sandy Bridge CPUs only, no Ivy Bridge at all...
I did something wrong, my bad...
Here is the picture:

@thecrowler

The same thing happened on mine, but it isn't a problem - unless you have an Ivy Bridge processor, that mcode is unused. Are you really going to upgrade to an Ivy Bridge processor or would you just get a much newer generation platform? Even if you did upgrade to Ivy Bridge, you could re-flash with the Ivy Bridge mcode just before changing the CPU.

Zitat von Fernando im Beitrag #3780

---

My test verifies, that it is possible to fix the Meltdown and Spectre Vulnerability issue of an Intel SandyBridge CPU by simply updating the related Microcodes with UBU v1.69.16.

---

@ygbsm
You're right, of course, I'm just trying to understand if I did it wrong. Thank you very much for your answer.
The correct way to do the microcode update was to let UBU do it automatically using option "1" (both for Sandy and Ivy Bridge)?
"Even if you did upgrade to Ivy Bridge, you could re-flash with the Ivy Bridge mcode just before changing the CPU" - so you mean, to update both microcodes BEFORE using an Ivy Bridge CPU?
I'm asking, 'cause flashing a bios (with a Sandy Bridge inside) that contain an incorrect/not supported microcodes, sounds very risky, also when you plan an instant CPU change.

Zitat von thecrowler im Beitrag #3783

---

to prevent Ivy Bridge microcode update (I read here that it could result in random BSOD, now I can't find the source).

---

@Bugger Vance
Post #3743, author @ygbsm
Sandy and Ivy Bridge CPU microcodes on a Sandy Bridge Z68, they both use an share offset 0x347390.
and Post #3755, author @mictlan

Zitat von Fernando im Beitrag #3780

---

My test verifies, that it is possible to fix the Meltdown and Spectre Vulnerability issue of an Intel SandyBridge CPU by simply updating the related Microcodes with UBU v1.69.16.

---

Zitat von thecrowler im Beitrag #3788

---

Sandy and Ivy Bridge CPU microcodes on a Sandy Bridge Z68, they both use an share offset 0x347390.

---

@Bugger Vance
Of course, it could not be: but that's what UBU shows, you can clearly read it on the attached images on #3743.
That's also what I saw when I did it.
See also post #3755, author: @mictlan

Zitat von thecrowler im Beitrag #3791

---

you can clearly read it on the attached images on #3743.

---

Sorry, I read it too fast.
Anyway, microcode sizes doesn't match, and the "boot looping" described was the reason why I did a manual update.
Hope I did it right.

Good evening, sorry for the dumb question, I have an Asrock Z170 Extreme 4 mb, i'm trying once again to fully update my bios (irst, orom, video, lan and microcode) using UBU v1.69_16 everything seems ok until I update the microcodes (i'm actually vulnerable to spectre), this is the output:
Current New
01 mCode Address - FFE10280 != FFE10268
Fixed - FFE10268
mCode Size - 18000
02 mCode Address - FFE28280 != FFE28268
Fixed - FFE28268
mCode Size - 18400

Clearly the microcode address are different, should I try to flash this bios anyway or what can I do?

Thank you in advance.

Make sure you're using the latest version 7 of Inspectre which tests properly for CPUID
Previous versions of Inspectre didn't have that feature so could have given conflicting info...
Notice the offsets are clearly different for the range of CPUIDs in column 1 and 2 in my own case
and there is NO PERFORMANCE HIT!

Cheers


MB: Asus Z87-Deluxe