@Lost_N_BIOS


I know the NVME module exist in the 5th volume in BIOS region.But you can't find the 5th volume in BIOS region in 8MB bios file or 4MB bios file.

As I said above "So I think the data of biosregion.bin's excess "GUID 8A3D-4F1C-9935-896185C32DD3" is exist in 100000h date hiding in the q77_8MB.bin and Padding in the q77_4MB.bin." (The excess "GUID 8A3D-4F1C-9935-896185C32DD3" that is the 5th volume in BIOS region you mention)

After spliting the complete 12MB image,the pic above show the NVME module was located in Padding of 4MB bios file.

That's because you can't properly open the files in UEFITool unless the image is compiled, this is a split image, same as why you can't open both files in UEFITool (8MB will tell you file is truncated).
There is no padding, I showed you in image exactly where and in what volume (not padding) the NVME Mod is inserted, there's no other way to explain this.
This BIOS is split at an odd place, in the middle of BIOS volumes and directly in the middle of live data, and this is why I said it's best for you to program in both files I sent.

No padding in 4MB BIOS, what you see like that as padding is an actual BIOS volume (Split in two, so you see half there, broken volume, appears as padding etc), but the tool is just seeing at it improperly (Because that "Volume" Not padding, is split in the middle, so UEFITool thinks it's a padding or broken volume, similar to non-UEFI-Data)
It only looks that way because the volume isn't parsed properly because it's split in the middle and you only have half the volume in that 4MB file. And because correct way is to not open this file, as it's a partial image, split right in the middle of data
This should be huge sign to your eyes, confirming on why it's VERY important that you program in both files I sent you. Otherwise you have half of the volume from old/original and half from what I edited, and the data does not match in each file at this split location
I'm really surprised it boot and surely something is going to corrupt eventually if you don't write it in there properly.

* edit - Here @gloobox - I show you better way, I hope This BIOS is split right in the middle of compressed CMSCore file, very important you flash both.
Here, now you can see the split directly at your "padding" or in the exact location in the middle of the BIOS volume, and right in the middle of the CMSCore module
This volume is "broken" when viewed as a 4MB file due to this split mid-volume, that's why it looks like that If opened this way (not proper way to view or edit this BIOS, or any split BIOS, but especially this way due to the split location)

@Lost_N_BIOS
Actually I didn't know what "padding" mean.But I just think that NVME module exist in the part of "padding" which was showed in UEFITOOL.
Haha,thanks for your explaining and I finally konw what padding really mean.

But the way,what way did you mod NVME module? UEFITOOL or MMTOOL?
I found that it wouldn't change the file header code of ASUS CAP file with UEFITOOL,but it's would change with MMTOOL.(So we could just add the NVME module to the M5A97 R2.0 with UEFITOOL,and usbflashback it!)

I'm glad you see now, hopefully you do anyway! Yes, this is not normal padding, like you see in other BIOS, or even in this BIOS in other places maybe, this Padding you are talking about is only due to BIOS cut in half and then opened wrong by UEFITool due to split.
I did NVME mod with UEFITool 25, this is what I always use unless there is an issue and I'm forced to use MMTool (VERY RARE, really do not like using that tool, luckily it's rare occasion where I have to)

For Capsule BIOS, I always extract body of those BIOS, edit, then manually put back inside capsule with hex editor = signed BIOS always and USB Flashback no problem, this is my standard procedure for any Asus BIOS (Which this is not Asus, so not sure how we're talking Asus now )