@Lost_N_BIOS Thanks! I'll give it a go and will report back my findings. Yes did see that RD Mode support earlier on, I'll definitely give that a try because like you say, a lot of the If statements are referring to it.

I am a programmer by occupation, just not with straight up hex! But it does help me more quickly understand some of this stuff.

----------------------------


@Lost_N_BIOS

Changing access level on the missing settings inside the overclocking menu didn't have any effect. But that's fine because when I unsuppressed the RD Mode Support option and changed it to Enabled, it had a dramatic effect (in a good way).

As far as I can tell, everything inside overclocking menu is now visible when enabling this option, an absolute ton of other menus/options have also been revealed. I've zipped up screenshots of all main menus (Main, Advanced, Chipset etc.) and everything in the overclocking menu so you can see the difference (attached to this post).

I do also see System Agent in Chipset.

Question is, can I now see everything possible? I get that some menus may be purposely hidden/suppressed because of hardware limitations so happy for them to remain that way if that is the case.

The other thing I want to do is update CPU Microcode, but I should be able to use UBU for that? [Tool Guide+News] "UEFI BIOS Updater" (UBU)

Appreciate your help and thanks again,
Darren

@tdarren - Once you play around in hex/BIOS for a while you will start keeping more and more of it in mind and be able to more quickly move through edits, which I'm sure you know being a programmer

Great to hear it, I thought that was some kind of R/D mode switch, probably in their case they meant for it to be called "Razer Dev Mode" I will check your images, vs what's possible, and see if you have anything missing.

UBU may or may not update microcode safely, sometimes there is issue with microcode edit specifically, so I always do that manually (same as everything else too ).
If you want, dump your BIOS region with FPT again so I have new/current one, and send to me I can update them for you. If you'd rather do it with UBU let me know and I will check and see if UBU does it properly for this BIOS.
Actually, I went ahead and checked this now and it's OK, at least with UBU_v1_76_2_3, if you have CPU with 806xx CPUID you will need to replace those individually or edit UBU MCUpdate.txt to make sure those remain and get updated (it removes those and leaved only updated 906xx uCodes)
"R" (UEFIReplace) Method = FIT Table poorly edited, but OK. BIOS May be broken and may brick board, due to padding file removed above microcode volume. It could be OK but only test and possible brick would let you know either way, I advise you do not use this method!
"A" (MMtool) Method = leaves 3x old 906Ex (B/C/D) microcode in place, adds the 4x new >> BIOS looks OK, not broken due to uCode edit - Not ideal BIOS to use here either, if you have 906E (B/C/D) because old left in place, so new may or may not be used.

I advise you to update these manually, or let me do for you. If you do it, be sure to fix FIT table once you are done and be sure padding file is left in place above/below both ucode and FIT modules.

I will check images vs possible tonight when I have more time. If you want me to update microcodes for you post a new BIOSreg dump from FPT

@tdarren - * Edit - I checked the images, what parts of the BIOS you uploaded (can't see it all), and looks like everything is there in the areas you showed
Except, I see CSM Submenu is missing from Boot page, but you now know how to make it visible Same goes for Command Rate Support in Memory at bottom, you can make it visible now too Or, due to it's help text, I think maybe it will be appear when you set CMD Rate 1 (NM Mode = 1)

*** WARNING - To ANYONE with laptop and unlocked BIOS!!!! ***
DO NOT try to enable this graphics card or disable that card, switch cards etc. Otherwise you will end up with no display output (ie black screen) and no way to recover except by blind flash or with flash programmer.
You can change graphics related settings, like changing memory sizes, or core speeds etc, just don't try to disable one card or change which is main etc.
Additionally, be very careful when trying to undervolt CPU, you can leave BIOS unbootable due to CPU voltage too low (Sometimes even 0.05 is too much)

Hi @Lost_N_BIOS,

Thanks for replying, I'm just in the middle of updating CPU microcode manually and once done will ask you to check it. Currently working out the FIT table and how it is structured etc.

I'm following this tutorial: [GUIDE] AMI INTEL CPU Microcode Update Guide

Ill get back to you a little later or when I've managed to get the FIT table sorted with my updates so you can check.

Thanks again, Darren

---------

Edit

Ok, I've now finished my edits for updating the Microcode for my CPU platform, which is 906EA (i7-9750H), please see the attached BIOS region dump with my edits applied.

biosreg_mod.bin is before I updated any Microcode
biosreg_mod_newMC.bin is after I updated the Microcode for my CPU platform

Steps taken:

1. I downloaded this Microcode from here -> https://github.com/platomav/CPUMicrocode...RD_711B4326.bin
2. Following the tutorial that I linked to above, extracted body of Microcodes (GUID '17088572-377F-44EF-8F4E-B09FFF46A070')
3. Opened extracted body in Hex Editor, found that beginning of the old MC for my CPU platform and the end of the old MC for my CPU platform, selected this entire block.
4. Opened new CPU microcode downloaded in Step 1 above in Hex Editor, pressed CTRL + A to select all, copied it and then pasted it over my old MC in the extracted body and added additional bytes to accommodate the new MC.
5. As per the following advice in that tutorial, I then removed 'FF' values at the end of the microcode body to match the size of original microcode body

Zitat von davidm71 im Beitrag [GUIDE] AMI INTEL CPU Microcode Update Guide

---

VERY IMPORTANT TO REMOVE EMPTY 'FF' VALUES CORRESPONDING TO SIZE DISCREPANCY OR ADD 'FF' VALUES TO MATCH ORIGINAL MICROCODE MASTER BIOS FILE SIZE

---

@tdarren - I wrote FIT guide, but it needs updated (There is much easier way now) not sure if you've seen - [GUIDE] Update CPU Microcode + Fix FIT Using UEFITool / Hex
Ahh, I see, you found my recent discussion about this much needed update to guide that I haven't had time to do yet, nice!

You didn't use old UEFITools linked there in that guide did you? You should use version 25 (not 25.1, or not any older either) for insertions.
I ask because on rebuild you lost a critical module at end of BIOS in PEI Volume. In the parser tab, check side by side, you see missing "Non-UEFI Found in pad-file" on your mod BIOS, this needs to remain in place
Usually, if you do not edit that volume at all, it shouldn't be touched, this is why I asked if you used that very old version of UEFITool mentioned in the guide, if so it may have cause this

* Edit - Yes, this must be the issue, I redid your mod using your mod ucode body, and version 25, replaced body and this file remains as it should (of course FIT needs fixed again after that )
But anyway, this must be due to you using the old version mentioned in that guide (unless you did or used something else not mentioned above)

Other than that is looks good, FIT is done correctly and padding files remain in place above/below FIT/uCocde - But >> DO NOT FLASH THAT BIOS Due to above is critical to function ^^

@Lost_N_BIOS Good spot! Good thing I asked you to check it for me.

I was using version 0.26 for insertions, but I've now re-done the ucode update using 0.25 as you suggested and it seems to have worked correctly now as I can see the "parsePadFileBody: non-UEFI data found in pad-file" message when opening the rebuilt image in UEFITools NE.

Just as a precaution, would you be able to check the BIOS region dump I have attached which includes my microcode updates using UEFITools version 0.25?

Let me know if all is good and okay to flash now.

Many thanks for your help,
Darren

@tdarren - Looks good now