Hi,

Thanks for all your job.
I've done everything (motherboard Asus Maximus IV Extreme-Z and Samsung 960 Pro NVME).
After the upload of the new bios, I'm able to install Windows 10 on the NVME SSD.
But after the installation, at the first reboot, I have an error: winload.exe error code: 0xc000000e
I can't do anything, the repair procedure doesn't work.

If you have an idea.

Thanks.

Thanks again Fernando,
The BIOS is set as here.

I allready try this, but it doesn't work, it says: unable to repair.
I try the installation several times, but I allways get the same result

@agentx007,

What’s this modified bootx64 for inclusion into Rufus?

Please detail where and how it was used?

Thanks

@Wincvlav,

I had a similar problem trying to install windows onto a nvme on a z87. Ultimately I fixed it unplugging every usb device external hard drive and internal sata drives that were hosting OSX as the hfs partitions were throwing off the installation process.

Because Rufus creates faulty/bugged efi boot file when it's trying to do a UEFI type pendrive from a vannilla Win 7 SP1 image.
I used updated file in my NVMe on PGA 478 project.
However instead of writing how I did it, you can simply watch how I used it.
I uploaded a video with whole thing to my Youtube channel :)
Video link : LINK.
Of course, you don't need the Clover or Hiren's boot part - simply skip to Windows 7 pendrive creation near the begining.

Without the file, I always got "red code of fail" on manual Clover boot (and black screen when doing things from GUI).
I also checked if this file helps with native UEFI boards, and it worked fine for my Sabertooth X79.

PS. There is also another way of doing this.
However this one involves downloading a updater program for ISO image (it will only work on original/not modified Win 7 ISOs).
Here's programs thread on PCLab forum : LINK.
This program can update Windows Installer on Win 7 to that from Win 8/10, on top of downloading all the updates and integrating them together with USB 3.0/NVMe drivers into a single ISO file.
Downside is ammount of time it takes to create a finished file.
I highly recommend doing this with SSD only (ie. source ISO file + this program + whole OS, should be on SSDs).

I recently managed to get my 960 EVO to work with Windows 7 and both Intel RAID and Asmedia AHCI controllers enabled on my ASRock Fatal1ty Z77 Professional motherboard (finally), whereas back in January I could only get Windows 10 to install without any controller issues. It even shows up as “Samsung 960 EVO 250GB” in the “Boot” section of the BIOS and in the Boot Manager menu (in the past it has always been shown as “PATA”).

Originally, I had modded the latest ASRock BIOS (1.70) by injecting the NvmExpressDxE_2.ffs module, and I discovered that I could only boot into Windows 7 on the 960 EVO if I disabled the Intel RAID controller and the Asmedia controller (Intel AHCI was okay). But because I have two RAID0 arrays on the Intel controller, and other drives connected to the Asmedia controller, my only option was to install Windows 10 (which I rarely ever use). So, for the last 8 months I have had a 960 EVO in my system that I could not use because I don’t like Windows 10.

Back in May, I sent my modded BIOS to another forum member that had the same motherboard as mine, and he later sent me a newer BIOS (1.70F) that he said he had just received from ASRock. I finally got around to testing it, and I noticed that it had a “SAMSUNG_M2_DXE.ffs” module like the 1.70D BIOS I had received from ASRock (no NVMe support). So, out of curiosity, I searched the 1.70F BIOS and my modded BIOS (using UEFITool) for the text “nvme” instead of “dxe” as Fernando’s tutorial mentions. My modded BIOS had one search hit, which was the NvmExpressDxE_2.ffs module I had injected. But the 1.70F BIOS from ASRock had nine search hits for “nvme”, so I immediately installed it and found that it worked with the Intel RAID controller and the Asmedia controller enabled with Windows 7 installed.

It appears that the additional functionality of this 1.70F BIOS is due to the nine instances of the text “nvme”, which my modded BIOS obviously lacks. Or is it just the module, and the nine “nvme” entries have nothing to do with it? The additional “nvme” entries are in the modules “nvme”, “nvmesmm”, “nvmeint13”, and “setup”. I can follow tutorials and research on the internet to figure out how to mod BIOS’, etc, but I don’t have a clue regarding the actual coding of a BIOS file. I opened several modules in a hex editor, but it was all Greek to me.

So, for those of you watching this thread that have some knowledge of BIOS coding, can these nine “nvme” BIOS entries contain important code for NVMe support (regarding Windows 7 and RAID, etc) that the “NvmExpressDxE_2.ffs” module does not have? I also noticed that the “NvmExpressDxE_2.ffs” and “NvmExpressDxE_3.ffs” modules are larger files with more code, but have less functionality than the 1.70F ASRock BIOS with the “SAMSUNG_M2_DXE.ffs” module and nine extra “nvme” entries.

Don’t misunderstand me, I’m really happy to finally have the 960 EVO fully functional with Intel RAID and Asmedia AHCI in Windows 7, and I wouldn’t have it working now without the help of this forum (thanks again for everyone’s help). But it appears that there may be more involved in getting full NVMe support for Windows 7 (with Intel RAID and Asmedia AHCI controllers enabled) than simply adding the one module.

For those of you having problems getting Windows 7 to boot after installing it (like I did), try disabling on-board Intel RAID (Intel AHCI is okay) and any Asmedia or other disk controllers. I have CSM enabled. The two Microsoft NVMe hot fixes must be integrated into the Windows 7 install media. Initially, I had to manually format my 960 EVO for GTP partition scheme at the beginning of the Win7 install using “Diskpart”, so make sure your SSD is formatted for GPT partition scheme (not MBR), and Win7 is installed in UEFI mode.

Out of curiosity I contacted ASRock support here in the US to see if they had the 1.70F BIOS. They still only had 1.70D (no NVMe support). So I contacted ASRock Europe, and they only had 1.70E (still no NVMe support). So I contacted ASRock Taiwan, and though it took them a while to respond, they had the 1.70F (with full NVMe support for my Z77 board, no modding necessary). So, when checking with the manufacturer of your motherboard for an NVMe supported BIOS (for older motherboards), check with all the different worldwide branches.

"The EFI module named "SAMSUNG_M2_DXE" is necessary to get Samsung's AHCI mode M.2/PCIe connected SSDs working."

@Fernando
I assumed that the Samsung_M2_DXE.FFS file was responsible for NVMe support, as the NvmExpressDxE_2.ffs file is when injected into a non-NVMe supported BIOS. I thought that perhaps the name had been changed to "NvmExpressDxE_x.ffs" from one of the original unmodded Samsung_M2_dxe files. So, if the Samsung_M2_DXE.ffs file is only for Samsung AHCI M.2/PCIe, theoretically I could remove it using UEFITool and it would in no way affect the 960 EVO installed in my system, correct?

I updated the BIOS P9X79LE to a modified one, but how do I see the changes in it? I have not found NVME support anywhere ...
And another question: when creating a bootable USB HDD with UEFI Windows, the utility Rufus does not allow to format USB HDD in FAT32. The files exceed the size limit for this file system. Will the installation be correct with NTFS?

I tried again to make a boot disk using a flash drive 16GB. The file system chose fat32, but when you press the start button, the file system itself changes to NTFS, but at the same time on the flash drive another partition "UEFI_NTFS" was created. It was the same with the USB HDD.
When I try to select FAT32 it write: this image contains a file larger than 4GB, which is not acceptable when using the FAT or FAT32 file system.
It can be impossible to use FAT32 with images of Windows 10?