@Lost_N_BIOS: Jackpot!! Sorry for double posting but _this_ deserves a separate post:
Your idea of swapping the Advanced in for Security and an unexpected and very positive side-effect; when I press Escape-key in the Advanced menu you swapped in, i get the hidden root menu with access to all menus.

@h_celine - great it's working, thanks for testing Very cool to see that kind of side-effect! Here is other BIOS I made with same edit, with chipset switched to security tab instead, if you want to test and see if same occurs then too.
http://s000.tinyupload.com/index.php?fil...981121371413780

Hope you have time to test, would be interesting to know if both edits produce this side-effect

@Lost_N_BIOS: Yes, it has same effect; pressing Escape-key in Chipset menu goes to the hidden Main menu.

Thanks for checking, that's cool trick I suppose!
I wonder if it will always happen with MSI BIOS? They're so hard to edit, and I never noticed this way to change previously, so now I can't wait to see if it applies to other BIOS from them too.

Logically I believe it would work on all MSI BIOS that has similar menu-tree-structure when opened in AmiBCP. It seems to be an effect of the standard hidden menus being left i their original unedited state by MSI and thus navigating as sub-menus of the hidden root.

@Lost_N_BIOS: Well, there had to be a catch. With both biosSWADV.bin and biosSWChip.bin my edits with AmiBCP to unlock the last hidden options in Advanced->CPU Configuration has no effect for some reason. After setting hidden options to USER it looks like this in the swapped-out-Security versions:

While the same menu running my version where Advanced is swapped in for ACPI sub-menu in original Advanced looks like this:


Also after testing I can conclude that we have another case of GOP Driver CherryView 8.0.1040 hangs at init with no picture. The original BIOS had version 8.0.1038, went back to that and got picture back.

Did you test Supervisor instead of User?

If yes and same, instead of AMIBCP edit, unsuppress items in setup module via hex Do this by taking xxx setting outside of the "gray out if" and "suppress if" constraints, by moving "End If's" to immediately following the suppress/gray, that way actual setting is not contained within their constraints
Or, you can also FF the causes of the constraints, either method usually works, but if one fails try the other.

Example with "Active Processor Cores" setting (Please note, this is example, if you do for real, edit the one with the core settings "All / 1-9 option" or whichever you want to expose, I just grabbed the first one at top for this example)

@Lost_N_BIOS: Did not test Supervisor, I'll try that later(PC on stability test again, so it will take a while.. ).
Regarding the GOP driver. I just mention it because I updated GOP before start this thread, and if anyone with same motherboard find this they should be warned that all BIOS posted in thread up until this point is with non-working GOP-driver.

I know what you mean, I used to run those often too, whenever you can it would be good to test and see if that changes things or not.. Thanks for the info on GOP, good thing to point out for others in case anyone uses BIOS later.
Did you confirm it's that file, by testing your own mod/insert of some other than/lower version than stock vBIOS aside from this one (Such as 1030-1036)? That way you know your transfer of settings/method is OK, and it's just the 1040 vBIOS not compatible
If you had not considered this, I would test that as well when time permits, so you know 100% for sure if the issue is 1040 or something went wrong during process used to transfer settings/mod/insert.

@Lost_N_BIOS: I'm using the 1014 vBIOS, was unable to use the vBIOS that came with 1040 from this post, the size do not mach my vBIOS and setting transfer procedure gave shitloads of errors. Original vBIOS was 1012. The vBIOS has been working all the time. I've not done anything settings transfer on GOP driver, should I have? I did double-check that I have not messed up insert mixing body/as-is by extracting both original and modified and comparing beginning of files in Hex-editor though.

Sorry, I was only talking vBIOS, if you change or update that in any way, you need to pick correct files and transfer settings using Intel BMP. I was mainly thinking vBIOS, not GOP, sorry for any confusion I caused there
However, looking at that thread, yes Plutomaniac says you need to edit and transfer GOP settings in the same way as vBIOS settings too. I think you can only use certain GOP with certain vBIOS, but I'm not certain what those restrictions are, that would best be discussed in the vBIOS/BMP thread.

But, even plutomaniac said in that thread, GOP pending due to issues, several times.
Since he mentioned GOP also need settings transfer with BMP (I think), I tried, and am not able to open the GOP same way I can the vBIOS (VBT) in BMP (Due to no VBT block), so I'm not sure what he meant or if that is even possible for the GOP driver.

But, I did see there is three major vBT entries in your BIOS, did you see that? Then the main vBIOS at at GUID 06767E64-19BF-459F-8564-5F25D4896FB0
And then two 5KB VBT blocks at GUID 878AC2CC-5343-46F2-B563-51F89DAF56BA + GUID EE62C785-3CF3-4027-8672-6DE4E7FF4317 I think this may be the other ones that needs settings transferred, I can open this in BMP as expected with the script like you normally do with the vBIOS
Maybe those two above plus GUID 06767E64-19BF-459F-8564-5F25D4896FB0 all three need updated/settings transferred at same time, before 1040 can work?

@Lost_N_BIOS: Just checking in to inform that there will be a long while before I get any more testing done. Had to make warranty return on memory-chips, and need to wait for them to return new ones.

Memory chips? Do you mean RAM, or did you mean something happened with the BIOS chips?

Yes, the RAM.

@Lost_N_BIOS

what is the actual purpose option rom serves? I removed all, exept one associated with graphics controller and didn't find any performance loss ...

P.S.

.. don't remove sata controller ..