Latest Asus bios (like ones on similar motherboards) has the ME both in the "ME Region" and as a module at that detected GUID. I don’t know why Asus chose to add it "twice" but is so.
@ rmongiovi:
It’s probably used for what I briefly mentioned here, point 3. Usually such GUIDs hold either a partial or full “backup” of the ME firmware but it depends on the given OEM’s implementation. ASUS started doing that since Skylake but I don’t know exactly how they utilize it. It’s probably related to that custom FWUpdate efi module found in another GUID. Maybe BIOS FlashBack or something else.
So it sounds like the takeaway for this, if we need to update the ME in the future, is to compare what’s in the ME region with what’s under that GUID. If they’re the same then we can replace both with the updated module after copying over the settings, but if they’re different we’d need to understand the difference before attempting to update. Does that sound right?
How do folks identify those GUIDs? Is there an official master index somewhere? I’d presume there would have to be if they’re really globally unique…
No, not at all. Just use FWUpdate for quick updating. For manual ME region replacement (fix settings first via FIT), only the actual ME region needs to be updated. The GUID has other purposes which I don’t know exactly. From what I’ve seen from user reports, replacing the actual ME region and leaving the GUID intact works just fine. Not all ASUS SKL boards have that GUID either way. No there is no GUID index, just manual scanning and experience. MEA checks 9 GUID which are usually Engine-related and reports their existence for the user to investigate if he/she wants.
Sylar,
Can you mod this BIOS to include the new logo?
I’ve heard 2D has better latencies then 37 and seems to be true for me. 
Another new BIOS 3101 is out, Asus must really be farking things up to release this many!
Added the 3101 MOD1 and MOD2 file in the Google Drive folder.
I’ve updated only sata modules and left CPUIDs untouched.
MOD2 has the same modules updated as well as the CPU ID microcodes.
Does anyone have any insight into why the new 3101 has two different version RAID OROMs - 13.1.0.2126 and 14.8.0.2377? I’ve never understood why there are two, since MMTool shows them both with the same device ID, but at least in the past they’ve been the same version…
All I get after flashing 3101 is a boot loop saying bios is updating do not turn off?
It does it twice, then you can enter into bios and change settings.
I was coming from 2101 (i think it was a 21**) and it boot looped the updating BIOS 4 times before crapping out and switching back to the other BIOS.
I tried it several times and reflashed mod1 but no joy.
What did work was flashing the untouched release via ez-flash, it did 1 BIOS and 1 ME update then booted. then it took the mod1 custom without any update after the flash, confirmed it is the mod as the RAID changed build number from 14.8.2377 to the newer build that I didn’t make note of apart from it being a higher number 
Help me ObieWan, Im confused…
In the modded thread, Skylar posts:
"Added the 3101 MOD1 and MOD2 file in the Google Drive folder.
I’ve updated only sata modules and left CPUIDs untouched.
MOD2 has the same modules updated as well as the CPU ID microcodes."
Well which one do I want? Why did he bother to make 2 x modded versions of the same BIOS?
If I plan on buying a 6950X in the near future does it matter which modded version I DL?
Thanks for any clarification!
Well, I don’t think it’s possible to tell you which one you want. That’s up for you to decide.
MOD1 has the original CPU microcode from the BIOS - version 2D.
MOD2 has updated the CPU microcode to (I presume) version 37 (the latest).
If you use MOD1, Windows will update the microcode to version 36.
If you want the latest greatest CPU microcode from the beginning of the boot, use MOD2.
If you’re happy with a bit older version and only once you get into Windows, use MOD1.
I guess Im confused because I dont know what CPU microcode means
Why would the Dev bother to create mod 1 with old codes in the first place? What would be the advantage of giving users the option to use old codes?
Thanks for any further info
Edit:
having the same problem as Gonzo, modded 3101 MOD 2 is stuck in an “updating BIOS do not shut down” loop and eventually crashes back to the other BIOS slot.
Update:
Had same problem Gonzo had, stuck in the infinite loop (modded 3101 MOD2) until eventually crashing with 4 long morse-code type beeps and switching back to the other BIOS slot. I flashed the slot I was trying to put modded 3101 with the regular Asus 3101, and it boots and works fine. (Only thing I notice is what some people on the Asus ROG forums were saying is that it takes noticeably longer to get from the black screen after pressing the power button to the first “beep” where it displays the Asus logo).
I will likely not attempt to install a modded 3101, but not for the reason that one poster suggested (i.e., I dont know what CPU microcodes were). The reason several of us ran a modded BIOS was because we were running SSDs in Raid 0 and often times a drive would “drop” from the RAID under heavy use. Gonzo was having the same problem with a factory BIOS a while back. He suggested we try one of the modded versions, since they included newer Intel RST rom versions. This solved the SSD dropping from the RAID0 issue for many of us.
Since I no longer run SSDs in RAID (went to a single SSD for my Steam drive), I will settle for the factory 3101 since the main benefit of the modded ones appear to be the newer RST roms which as far as I know aren’t needed in a non raid config.
Thanks for the support guys!
Don’t take this the wrong way, but if you don’t know what CPU microcode means, and you can’t google it, then it might be best for you to stick with the ASUS BIOS. At least if something goes wrong they’ll back you up.
To be fair the stock BIOS has a 14 series Raid Rom anyway so you are not really missing out on anything, I only flashed the modded over the top of 3101 out of curiosity after the boot loop.
Based on this I would advise people to steer clear of the modded ones now more than one person has had a boot loop, the stock now cover the new chips so no need for microcode updates and the Raid roms on 14 series.
Only die hard overclockers seem to gain a couple of % on synthetic benchmarks that we all know mean naff all in the real world
Asus probably just took the modded BIOS as a sign it was safe to put 14 series Raid roms on anyway.
Thanks again Gonzo!
Well, 13 and 14 actually, as I questioned earlier. In the locked thread about the R5E, Lordkag commented: "E095AFFE-D4CD-4289-9B48-28F64E3D781D appears to be linked to a device EVSS, while 20FEEBDE-E739-420E-AE31-77E2876508C0 is linked to SAT1 (SATA1)". Unfortunately, as seems typical here, it’s difficult to translate exactly what he’s trying to communicate. SATA seems clear, but google doesn’t help me with EVSS. That makes it a bit problematic to decipher why ASUS would make one 13.1.0.2126 and the other 14.8.0.2377.
In the ROG forum for this BIOS, raceitchris comments that he couldn’t boot with the MOD2 version of the BIOS that Skylar posted but that the MOD1 worked fine. The difference between those two is that MOD2 include the version 37 microcode. That seems like an odd difference to cause a problem unless 37 is glitched.