Yes, I noticed, see my edit above

Ok cool! let me know if you need anything else

Do you want latest microcodes used, or PRE-Spectre/Meltdown ones (windows will still replace/use it's own latest, unless you stop it via This Method)

To be honest, i don't really care about that, anything will work for me

@Shana - here, please test LatestuCME.bin first, if that fails to boot w/ Sky/Kaby, then put in other modern CPU and flash in OlderuCME.bin and try again with Sky/Kaby
Flash via >> FPTw.exe -f filename.bin

Before you reboot after above flash, close all files and be ready for a shutdown, then enter this command >> FPTw.exe -greset

If system does not automatically reboot, please shut down, remove PSU Cables (24+8) and then press and hold case power on switch for 10 seconds or short pins, then let system sit for one minute without power. << This, or -grest above, only needs done once, since ME FW is same in both BIOS
After that, boot to BIOS with modern CPU still in there and load optimized and save, boot to windows and shut down, then put in Sky/Kaby CPU for test. << Do this each time, if you end up having to test both BIOS.

http://s000.tinyupload.com/index.php?fil...451408063235791

* Edit, forgot to include change log!

1. Added microcodes for 506E3 + 906E9 (+ additional BIOS with old ones from F2 if latest version fails)
2. Downgrade ME FW with settings transferred 11.8.60.3561 >> Downgrade to >> 11.6.29.3287
3. Fixed FIT Table

* Edit 2 - I just noticed, your LAN MAC ID is missing in the SPI.bin file you sent! You didn't (EVER) flash stock BIOS with FPT did you??
We can fix, but you'll need to give me your LAN MAC ID off sticker.

@Lost_N_BIOS I have never used FPT before, the first time was the flashback that you told me to do hehe,

Should I flash it, ir should I wait?,

Also, I'm having hard time downloading from tinyupload 😔

Picture of the LAN Code added

EDIT: In case you need, the code is: E0D55E490C20

@Lost_N_BIOS

When I did this myself, one year ago, used ME 11.7.0.1261.

Is version 11.6.29.3287 better?

Just downloaded the stock BIOS (at the time, included SKL/KBL microcodes), downgraded the ME and flashed with modded EFIFLASH.

@Shana - It's OK, we can fix! Did you get the board used, or new? Or, have you ever sent it off, or had anyone, recover the BIOS for you?
This usually happens when someone programs in stock BIOS with FPT, but can also happen with other BIOS recovery methods, or sometimes it can be normal if there is no Intel Gigabit LAN on the board
Usually there is no GbE region when there is no Gigabit LAN, but sometimes they may be too lazy to remove, or forget etc. Does your Ethernet LAN work, please test? If it works, then no issue, they forgot or left in place due to lazy

I checked your BIOS, and that ID is not in there anywhere, so MAC must be stored in chip and if you can use Ethernet then no Intel Gigabit LAN On this board
It's OK to go ahead, sorry for late reply, it was always OK, we could fix this if needed anytime by flashing GbE only, but it's not used in your case I think

* Edit - Sorry! I forgot, here is another upload to different site in case you never got the tinyupload file (Sometimes that site doesn't' work well with Proxy or VPN, so could be the issue you're having) - https://ufile.io/284t1aor

@daniel_k - Thanks for the info, and good to know! No, there is no reason I used the ME FW I did, only due to I know that one works and was not 100% sure about if 11.7.0.12xx worked in all cases or not.
Now that we know from your info I can later update this to that one if Shana wants. Did you try others above that one and they failed?

I'm not sure what all BIOS has the Sky/Kaby microcodes needed for this instance (506E3/906E9), F2 did, but F14 didn't, I thought best to use latest BIOS for performance/bug issues being worked out much better there vs older BIOS.
Which version are you using now?

Also thank you, good to know EFIFlash will downgrade the ME FW, I suspected Qflash wouldn't which is why I had her use FPT here

Ok, everything looks to be working good (i can't test LAN for now).

Really thanks for that, now, i kinda want to do it myself, i have one more Gigabyte z370 and one H310 (not sure if it is supported),

May i know which guide i need to use? Or what i need to do?

Thanks 😁 @Lost_N_BIOS


EDIT: Some images added

@Shana - great to see it's working smoothly, thanks for quick report back!

This will only work on Z370, H310C, and B365, so I think only your Z370 is candidate for this kind of mod BIOS

Here is guide on how to change the ME FW - [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
And here is my guide on how to do microcodes and fix the FIT Table once you are done - [GUIDE] Update CPU Microcode + Fix FIT Using UEFITool / Hex

Certain BIOS you must use MMTool to the microcode updates, others you can do with UEFITool version 25, how to know which depends on below information.
And, sometimes more involved methods must be used in conjunction with either of those tools, to work around/avoid the issues outlined below.

Extra care must be taken with microcode updates that is not covered in this or any other microcode update guide that I've ever seen.
In many BIOS now, there is padding modules above microcode volumes, and many tools/methods either add or remove these when doing updates, and that can lead to bricked BIOS (but not always). So, best practice is to make sure your before and after BIOS match in this regard
This also applies to any padding or Non-UEFI modules in other areas of BIOS, this are usually shown in the "Parser" tab of UEFITool 51-55 (Don't rely on 25 or 26, sometimes it does not show all these in parser tab).
So you always need to compare stock/before BIOS with after/mod BIOS, with UEFITool 51-55 NA Alpha, side by side and check the general padding/Non-UEFI modules, as well as any above and below the microcode volume entries too.

Neither of the edits to do this are what one would call simple, and risk is higher than usual for bricked BIOS when updating microcodes too, caution is required or have someone check your edit before you flash,

Your Ethernet LAN is probably OK, I think MAC ID is stored in chip FW on that model, because the ID you showed is not in the BIOS.