Thanks, I tried it.
I do have a RX580 but the NVIDIA version still worked for me to rebar. But now the BIOS notice screen doesn’t even come up now. It just has an old Windows startup screen with the loading bar. Before the BIOS notice screen would come up but when you I tried to enter the BIOS it would blue screen like both of my screens but not full screen which is weird. Like 3/4 off to the right side.
so you do make sure that in the bios it is already set as UEFI only (CSM = Disabled) before doing anything else?
Sorry it took me so long. I had to spend a day trying different things. So, I was changing the CSM in the advance tab and it wasn’t working. I had to select Windows 8 and then CSM disabled in the regular area for some reason.
Did I do it right?
https://i.imgur.com/Pl0uNDQ.png
Modded BIOS file here:
Gigabyte GA-Z68XP-UD3 (Rev. 1.0)
BIOS U1j (I just added the file “NvmExpressDxe_Small.ffs”).
I lost over one hour trying to use UEFITool through ChatGPT instructions, but it seems that the correct software was “mmtool”.
“Smart” GPT and user…
Step 2 of the guide wasn’t clear enough??? Lets us know what wasn’t clear to you…
I noticed that you added “NvmExpressDxe_5”, “ReBarDxe” and “SAMSUNG_M2_DXE” into the Gigabyte GA-Z68XP-UD3 (Rev. 1.3) BIOS file:
https://i.imgur.com/t2jjpc5.png
I’m trying to inject the same files into my Rev. 1.0 BIOS file.
“ReBarDxe” can be injected “as is”, “SAMSUNG_M2_DXE” can be injected “compressed”, but “NvmExpressDxe_5” exceeds the volume size either as is or compressed.
https://i.imgur.com/Ty3dCgL.png
How did you do it?
By the way, upon upgrading to this BIOS version, I lost the setting “LLC”, rendering my overclock to 4.5 GHz unstable. It BSODs a lot regardless of Vcore.
Is it possible to patch LLC back the same way these modules are injected?
@Razzee
Each BIOS version is somehow different. So it is no wonder, that you cannot do the same modifacation the same way.
Another problem is the available space within the DXE Driver Volume of the BIOS. There is a compression limit for it. That means: The more modules have already been inserted into this Volume, the more problems the user has to get any additional module inserted.
I added only “ReBarDxe.ffs” and “NvmExpress_Small.ffs”. “SAMSUNG_M2_DXE.ffs” couldn’t fit at all either as is or compressed.
Question: if I change the NVMe M.2 drive between motherboards, the modules being different will create any incompatibility or it should boot just fine?
Gigabyte: GA-Z68XP-UD3 (Rev. 1.3): “NvmExpressDxe_5.ffs”
Gigabyte: GA-Z68XP-UD3 (Rev. 1.0): “NvmExpressDxe_Small.ffs”
There will be no difference regarding the booting capability.
Sorry for bothering again, but do you think it’s safe to revert to F10 BIOS using the same tool provided by Gigabyte to update to U1j? (FlashEFI.exe)
NVMe is working fine, but I’m now experiencing cold boot. It succeeds after several attempts, but it is still annoying, besides the lack of LLC.
These motherboards were known for cold boot back then, and I once had it in the past and don’t remember how I solved it.
Only someone, who has already done exactly this with a similar system, can give you an answer.