@fender - then yes, the one you mentioned Platform 12 0x2E is latest

@juanete - I did not see it, only said you/we need to find it in some BIOS

I have i3 3240 Ivy Bridge, can i change microcode to unlock multi ?

@laranje - no, CPU multiplier is locked by Intel, for this CPU that is 3.4Ghz is the max

hi lostnbios can you unlock a bios full acces on a laptop Lenovo e560?and if you can another one with microcode update and me firmware update .I send you the dump bios I make it with CH341A_programmer https://www.sendspace.com/file/cd9u5e thank you

@juanete - Is bootguard active on this system? Please run MEInfoWin from ME V11 system tools package, show me end of report, or check yourself does it show Measured and Verified boot "Enabled" on FPF/Left side?
Never mind, I see it's not set at the ME level, so even if enabled at the FPF it's not setup correctly, so cannot be active.

Measured and Verified boot are disabled, can you do something?thank you

@juanete - Yes, sorry if I was not clear above, after I asked about Measured/Verified Boot, I edited post after seeing Bootguard is not setup as enabled anyway, so even if Measured/Verfied boot was burned into FPF (Enabled) it wouldn't matter, bootguard could not be active.
So yes! I can do some things

I unlocked some things, overclock/memory menu, but this BIOS is not easy one click enable and all setup items is broken up and spread out through BIOS in many different files (half of which are empty IFR descriptions/names, so only value to enable/disable but no names to what they are).
But, there is a lot of settings from two menus in one setup IFR, I can send you if you want to dig through it and make a list one by one of things you want enabled?
If yes, you want to look through list and pick more settings, it's included with BIOS below, few setup changes and w/ update microcodes and ME
Microcode 406E2 Rev 28 - 4/15/2014 >> Update to Rev 2C - 5/21/2015
ME 11.8.50.3460 - 2/19/2018 >> Update to 11.8.59.3560 - 10/3/2018

But! After mod I see "checkProtectedRanges: Phoenix protected range [340000h:610000h] hash mismatch, opened image may refuse to boot" So be ready to recover May be OK, may not be OK
http://s000.tinyupload.com/index.php?fil...186901760711837

If it's not OK and doesn't boot, then we can only update ME/Microcodes, but not BIOS settings changes

Sorry, can i find bios modding for cpu coffeelake run on skylake mobo here? (giga z170)

@yeumanu - yes, see this threads - Revlaay's AIO Tool - [TOOL] Easy automated Mod tool for Coffee Lake bios
Svarmod's CoffeeTime AIO Tool - [GUIDE] Coffee Lake CPUs on Skylake and Kaby Lake motherboards (47)

I am having trouble understanding a couple of things with updating the microcode of the GA-Z97X-Gaming 7 beta bios (F9b). The problems are:

1. I cannot update the microcode with UBU as it runs out of space so I am trying to update them manually using the guides on here.
2. The guide says to use the FIT table, but in UEFITool (tried A55 and A40), the Fit table tab never becomes selectable. What am I missing?
3. I do not understand how to find the correct microcode in the BIOS file to replace. I have tried extracting the microcode section as a body and updating it, and just updating directly in the BIOS as they are shown as distinct microcodes in the BIOS. I try to search for the proper header of the old microcode in the source BIOS (since the offsets are off, starting with 00000000, in the extracted file and not in the source BIOS) but I never find the same HEX header I am using as a search.
4. Lastly, since the new microcodes are bigger, I assume I have to change the offset pointer for the section after the microcode. Since the file will be bigger, will it cause a problem flashing later?

Can someone point me in the right direction and help fill in the parts of the guide I am not understanding?

Here is the BIOS I am trying to mod - http://www.mediafire.com/file/dl08r98vo0irb2x/Z97XGAMING7.9b.zip

@digitalMedic - I think you already solved this, but I'll answer some of that for others reading later. #2 - FIT table only needs to be corrected once you are done with updating the microcodes, here is a guide on how to do that
If FIT tab is not selectable for you in UEFITool NE Alpha then FIT table is not used in the BIOS you're working on right then. I checked Z97X-Gaming 7, this BIOS does not utilize the FIT Table, so nothing to do here

#3, also see above guide. For Z97X-Gaming 7, and many other BIOS, but not all, you can search via GUID >> 17088572-377F-44EF-8F4E-B09FFF46A070 - extract body, and then edit. Before you edit, check end of file for footer, sometimes there is a footer that needs to be put back once you are done (not in this BIOS)
For this GUID Search, in this instance, only 2nd and 3rd results are actual microcode files, first one contains a header only (many BIOS like this too, but not all). Edit 2 microcode body, replace both bodies at search result 2-3. Watch pad-file above microcode at each location, this must be in place on your edited BIOS after saving, if you see it's gone then try other UEFITool for the re-insert (ie if 26 removes a padding file use version 25 instead) If both remove a padding file, then do not use UEFITool for this mod, use MMTool instead.

#4, nothing to do there, since _FIT_ is not used in this BIOS, otherwise yes you'd need to correct some things relating to what you asked

@Lost_N_BIOS

I am still confused I guess. I am not sure where or in what tool I would search for the GUID. I can see the microcode section in UEFITool and I extracted it as a body and got a file called File_Raw_Microcode_body.raw

@digitalMedic - GUID search can be ran via search on UEFITool, or manually/visually found via MMTool.
When you run a search for the microcode GUID 17088572-377F-44EF-8F4E-B09FFF46A070 in UEFITool, you will get results x3 in different volumes (three actual and separate GUID Modules, 2x that contain microcodes, 1x header only)
What you showed in the image above is actual microcodes individually shown, but this is only one microcode GUID Module, there is two others (one only contains a header), the other contains what should be an exact copy of the one you're looking at now
Here is example in UEFITool 51 NE, so individual microcodes are not shown, so it's less confusing and easier to see what I'm talking about.


Same will apply to UEFITool NE 53-55 too, but inside each you'll see the individual microcodes like shown in your image above. Don't expand it, extract as-is, or via body, then edit

Use UEFITool regular version (25 or 26) to replace both #2+3 GUID with updated microcode module. Extract entire GUID, or body, using any UEFITool, then replace same way you extracted using UEFITool regular version (not NE Alpha version)
Don't do this edit via hex, since headers and checksums will need corrected (UEFITool will do for you on save/rebuild)

@Lost_N_BIOS

I ran into a snag in the last bit of replacing the microcodes. Here is what I did:

1. I extracted the microcode files as a .raw file (extract body).
2. In the hex editor, I copied and pasted the new microcodes into the .raw file in their appropriate places (this increased each section of the microcode data and the whole .raw file). When I ran MCE.exe on the edited .raw file, it showed all the microcodes were updated correctly.
3. I replaced GUID 2 with "replace body" using the edited .raw file and saved the file, opening it after the save automatically.
4. Tried to replace GUID 3 with "replace body" with the same edited .raw file, but I got the following errors, "parseFile: invalid data checksum 26h, should be 67h" and "reconstructVolume: no space left to insert VTF, need F90h (3984) byte(s) more" (see the picture, please)

What did I miss?

Rick

@Lost_N_BIOS

I tried a couple more things. I tried to use MMTool and replace the microcodes with an updated microcode.ffs file (created from the UBU tool). Got the same out of space error. I also tried to alter the size of the padding file in the 3rd microcode area by deleting some FF bytes using a hex editor and then replacing it into the BIOS before trying to update the 3rd microcode. This time I got an invlaid UEFI file error.

I am kinda lost now.