@guru3d - Please test all three BIOS, and give report of all three at once, thanks. Do not worry about overclocking/XMP for now, only that BIOS is bootable.
Sorry, not sure what this means >> lan 1 no code 1 << These modules are ONLY used for Wake on LAN or Boot on LAN, so use/function of LAN should not be affected other than in those instances (however, I'm not 100% sure, UBU option 1/2 one may break LAN function if wrong one?)
Also, when you report back, please give report per folder name (ie #3 tells me nothing in your previous comments, since there is two folders named #3)

@Lost_N_BIOS

test7

1) 83-UBUIntelLANONLY boot ok, overclock broken
2) #3-UBUIntelLAN1 boot ok,overclock broken
3) #3-UBUIntelLAN2 boot ok, overclock broken, few times I did get error code 01 and MB rebooted and I needed to clear bios and after few reboots, I did ger error code 01 again

@guru3d - Thanks! So, this confirms replacement of Intel LAN OK, either way. To know which version UBU offers (#1/2) is correct/usable, someone would need to test Wake on LAN / Boot on LAN with #2 and 1 or 3 of that set
As to the OC issues, please ignore/don't worry about that for now, this is common with broken BIOS and this was only meant as test scenario.
As long as BIOS from post #83 and or BIOS #3 from post #116 is OK in this regard, all will be fine once all sorted out here

Now, to the issue about EFI RST update causing brick - I know the issue here now, and I've mentioned it since issues were noted, but kept forgetting to go back and accept it then work past it
I should have realized and remember this once guru3d said Intel LAN module updates via UBU also caused boot failure (Which we now just proved they do not, so not sure what that means here?)
Neither of these things, EFI RST module, nor LAN Modules should cause boot failure, even if wrong, removed, completely corrupted (except in load-use case), since they would not be loaded at first bootup and even if so would only cause RAID or Wake/Boot on LAN Issues.
The problem is the padding issue I mentioned since issue noted the get-go here, and I noticed it mid edit too but thought would either be OK or RAID would just fail.
I should have known better and did this all properly from the start of notice of issue, instead of trying to narrow down some random cause. But, I guess that did help remind me, and of course rule out other possible things first too.

After a long time of trying to explain, and show this problem to Fernando, I finally convinced him over the past year or two, and he's added warnings about this to the NVME mod guide (And I think UBU one too, if not, it should be noted there as well)
I have never been able to explain, or convince SoniX about it, since it does not happen always, and when it does happen it does not always = bricked BIOS on all boards
So due to random and not always critical to function, I think he's never been convinced by me that this can be a critical issue, or maybe he does realize and accept it, but is unsure how to code UBU to work around this (especially since random, and not always CTF)
I am 100% sure this is one of the cases, where added or removed padding in a touched volume = brick. In this case, it's added padding at the location you see below. This happens with UBU, MMTool 4.5, 5.07, 5.02, UEFITool 25/28 etc (all do it in this case)


I will now work around this, and give you test BIOS as soon as I can! Please be patient, sometimes it takes me hours to work around this issue
Hopefully this is the issue with EFI RST and bricking BIOS anyway, if not I will teach myself to create new modified FFS and replace this with MMTool and I'm sure that will fix the issue if this does not.

@Fernando - Thanks for your thoughts on this, but there is plenty of free space here in this volume >> 11DA28h (around 1.1MB)
+ why would "padding" file be created, taking up more space, in a spatially limited BIOS? That would be counter-productive and I'd be mad if tools did that to me due to limited space
But, no worries, I shall work around the issue, nothing needs removed, except while I work past the issue

@guru3d - OK, I taught myself how to make new updated and compiled .FFS with the updated EFI RST module
Sorry to ask, and hope you don't mind, but it could possibly save me a few hours if I don't have to work around that padding issue, would you please test these three BIOS?
https://ufile.io/c4o80jhh

Please let me know, do they boot OK, can you enter BIOS OK, and can you while in UEFI mode, use RAID RST UI
Legacy RST checking does not matter here, never any issue with replacing that, so don't waste your time looking.
I assume OC may be broke on the UEFI25, but possibly not, the other MM ones it should be OK (if past run-in's with that are related in any way)

I promise, if these all fail too, then I will take the time needed to work around this padding issue
All three BIOS above still have this padding concern, this test set will confirm for sure if this is cause of the issue, or previous invalid RST update methods due to lack of FFS update as a whole

@Lost_N_BIOS:

tested last 3
renamed the to X79DLX.CAP

non of them worked

@guru3d - Sorry, I forgot to put those into signed capsule. Do you mean you could not flash them? If yes, I assume so, renaming to cap is not how that is done.
Sorry about this, here is repack - https://ufile.io/xhcqtllu

@Lost_N_BIOS
Testuefi25 -> no overclock ,raid ok, few codes 01
testmm52-> restarts every time
testmm45-5007->all ok

@guru3d - Yes, as I mentioned OC may be an issue with the exact file you mentioned
testmm52-> restarts every time << What does this mean?? Restarts every time, what?? I don't get what you're saying, but due to below it's not important

Great!! We have a winner >> testmm45-5007 << I will use this as base, which includes my newly created EFI RST .FFS update, and do the rest of the edit now
Thanks for your continued testing

@Kwstas - Sorry for the delay here, but at least now we know what was causing the issue finally! Big thanks to all the testing to guru3d
I will get this BIOS redone soon, and make secondary package for you with RSTe instead of RST, and yes, I will update ASMedia this time too

@Kwstas - OK, I will try to do soon as I can, maybe tonight because I don't have time right now, about to leave in few minutes