I've updated my bios using this file, but unfortunaly, it doesn't find my disk.
When i flash back my old modded bios, my disk if find and system boot up :(

I've made a fast sign of my system for information.

Zitat von Fernando im Beitrag #1890

---

@BrN:
Please test the attached NvmExpressDxE_3.ffs module. It has been finally customized by me today. Source file was the file named NvmExpressDxe-64.ffs, which had been presented by our Forum member e.v.o (look >here<).

---

@Fernando
Hi Fernando,
I attempted to test the NvmExpressDxE_3.ffs driver also. I had previously used the AMI Aptio MMTools v4.5 to insert the NvmExpressDxE_2.ffs module, but had to remove the network related drivers as CodeRush suggested. Using CodeRush's UEFITool I did not get the "File size exceeds the Volume size" error when inserting NvmExpressDxE_3.ffs or NvmExpressDxE_2.ffs. But, I did notice a difference after inserting NvmExpressDxE_3.ffs. After inserting the module "unknown section" is shown under "user interface section". Your screenshot in the first post did not show this, and I didn't want to take a chance without knowing exactly where the module came from. I attempted to attach a screenshot. Let me know what you think. For now I'll try the modded BIOS using NvmExpressDxE_2.ffs to see if it works, because I did not get the "File size exceeds the Volume size" error as I did using MMTools v4.5.

|addpics|f9m-2-28f9.jpg|/addpics|

@Fernando
I inserted the module and noticed that instead of "unknown section" I now have "version section", as your screenshot shows. I noticed that NvmExpressDxE_2.ffs does not add this line when it is inserted. Is this "version section" line expected?

Zitat von Fernando im Beitrag #1899

---

Yes, I had added the "version section" to be able to identify this module as version 3 by opening the modue with an Hex Editor

---

@Fernando
Well, I tried the "clean" module and it would not detect my 960 EVO in the BIOS or the boot menu (F11). The 960 EVO was available in Windows 7 as storage, even though it was not apparently seen in the BIOS. I had previously used MMTools 4.5 to insert NvmExpressDxE_2.ffs (after removing the network boot related files) and that has worked fine for the last two months. So I decided to do a fresh BIOS mod using UEFITool to insert the NvmExpressDxE_2.ffs module. This way I could clearly determine if it was the NvmExpressDxE_3 module that was the problem or something else in the modding process.

Again, using UEFITool I was not required to remove files to make room for the NvmExpressDxE_2.ffs module. After flashing this BIOS I had "PATA" in the Hard Drive boot priority section, and "Microsoft Windows" in the boot order. I don't recall seeing "Microsoft Windows" in the boot order, but it was there in the boot menu (F11) also. After booting into Windows 10 and back into the BIOS, it now showed "Windows Boot Manager" (no longer "Microsoft Windows") in the boot order and in the boot menu (F11). So, something is not right with the NvmExpressDxE_3.ffs module. If you figure something out and need me to test it again, I will.

Also, UEFITool was much easier to use than MMTools. At first I thought it would be more difficult (probably because of the learning curve), but it worked very well. Thanks for your UEFITools tutorial/screenshots, and thanks again to CodeRush for UEFITools!

Also one thing about the NVMe module and BIOS settings: Everything runs fine with CSM disabled completely and every FastBoot option turned on. Board: ASUS Z87 Gryphon.