JK_DC
The big question is why it won't boot in PE4 with VROC enabled, but it will boot with non-VROC enabled? Both are bifurcated.

Try removing all but one drive from the Hyper M.2 card and test by adding them back in one by one. It seems like the VROC UEFI module has a problem with the drives. I have manually updated the VROC UEFI modules in my BIOS using the UEFI BIOS Updater (UBU) tool. The version that comes with the X299 DARK is very outdated.
 

JK_DC
The other interesting thing is I can create a raid in the rst page in bios on pe4, but only if computer attached storage is on. I believe you said rst doesn't work on pe4?

Strange, as it does not work for me. I can create RST RAID only on PE6 / PM2 / PU2, but not with my Hyper M.2 card in PE4. The drives in PE4 are not detected in RST even with CPU Attached Storage enabled. However both bifurcation and VROC work fine on PE4.
 
If it works for you then I recommend just creating RST RAID0 with CPU Attached Storage enabled. VROC RAID0 is unstable with non-Intel drives and is no longer recommended by Intel on X299 even for previously supported configurations. The RAID0 performance is identical between RST and VROC. The arrays are even compatible with each other so you can swap between them without losing data.

JK_DC

Monstieur
The VROC device which requires the VROC v7 or v8 driver will show up only when VROC is enabled in the BIOS. You don't need a VROC key and don't need to create an array for this. While VROC is enabled, the NVMe drives will not show up in Windows until you install the driver. You cannot install the VROC VMD driver for any other device. Merely enabling VROC will replace each NVMe drive with a VROC device. When you create a VROC RAID array, the individual VROC devices will be replaced with a single VROC device.
 
Error 94 is a PCI device enumeration error. It could be a compatibility issue with other devices sharing the PCIe lanes that belong to the same VMD on which VROC is enabled. If you have the Hyper M.2 in PE4, disconnect PE3 even if you use only x8 lanes in PE4. You can view the VMD grouping in the BIOS. The same applies to PE1 / PE2, and PM1 / PU1 / PE6 / PM2 / PU2.
 
I have used the Hyper M.2 card with 4x non-bootable non-Intel drives in PE4 in VROC mode. I have also used 2x bootable Intel Optane drives in PE6 and PU2 in VROC mode.

OK I was able to get the driver to install by enabling VROC on PE3 which has nothing in it, but it doesn't help since it has to enabled for the slot the card is in. I can not boot it in PE4 with VROC enabled. It gives a 94 error. I will try it again, but I disabled all other slots from bifurcation except PE4 and it won't boot. I only have a video card, the hyper card and a wireless card in PE5. None of those should conflict with PE4. The big question is why it won't boot in PE4 with VROC enabled, but it will boot with non-VROC enabled? Both are bifurcated.
 
The other interesting thing is I can create a raid in the rst page in bios on pe4, but only if computer attached storage is on. I believe you said rst doesn't work on pe4?

Don't get me wrong but seeing how you go through all of the expense and effort trying to make this work makes me wonder what are you hoping to gain by having VROC RAID that would make it worth it?

Monstieur

JK_DC
The big question is why it won't boot in PE4 with VROC enabled, but it will boot with non-VROC enabled? Both are bifurcated.

Try removing all but one drive from the Hyper M.2 card and test by adding them back in one by one. It seems like the VROC UEFI module has a problem with the drives. I have manually updated the VROC UEFI modules in my BIOS using the UEFI BIOS Updater (UBU) tool. The version that comes with the X299 DARK is very outdated.
 

JK_DC
The other interesting thing is I can create a raid in the rst page in bios on pe4, but only if computer attached storage is on. I believe you said rst doesn't work on pe4?

Strange, as it does not work for me. I can create RST RAID only on PE6 / PM2 / PU2, but not with my Hyper M.2 card in PE4. The drives in PE4 are not detected in RST even with CPU Attached Storage enabled. However both bifurcation and VROC work fine on PE4.
 
If it works for you then I recommend just creating RST RAID0 with CPU Attached Storage enabled. VROC RAID0 is unstable with non-Intel drives and is no longer recommended by Intel on X299 even for previously supported configurations. The RAID0 performance is identical between RST and VROC. The arrays are even compatible with each other so you can swap between them without losing data.

I have the card in PE6 now. I have PM2 set to CPU. CPU attached storage is on. RST only sees 1 drive in the Windows application and I can't create a PCIe raid. Disk and device manager sees both drives. The bios sees both drives as well. I can create the raid but I can't use it in Windows as it doesn't see it. I can't boot off of a regular sata ssd since I turned it to raid mode. It will not see any sata drives in the boot menu. I think my board is just defective for a raid setup. It is fine for a basic setup. My AsRock worked straight away. I created a array in windows with rste with samsung drives and the trial popped up. It couldn't have been much easier. I am getting an Asus board to replace this one. I'll stick with EVGA on video cards and power supplies, but motherboards are too highly developed for them. 

ZoranC

JK_DC

Monstieur
The VROC device which requires the VROC v7 or v8 driver will show up only when VROC is enabled in the BIOS. You don't need a VROC key and don't need to create an array for this. While VROC is enabled, the NVMe drives will not show up in Windows until you install the driver. You cannot install the VROC VMD driver for any other device. Merely enabling VROC will replace each NVMe drive with a VROC device. When you create a VROC RAID array, the individual VROC devices will be replaced with a single VROC device.
 
Error 94 is a PCI device enumeration error. It could be a compatibility issue with other devices sharing the PCIe lanes that belong to the same VMD on which VROC is enabled. If you have the Hyper M.2 in PE4, disconnect PE3 even if you use only x8 lanes in PE4. You can view the VMD grouping in the BIOS. The same applies to PE1 / PE2, and PM1 / PU1 / PE6 / PM2 / PU2.
 
I have used the Hyper M.2 card with 4x non-bootable non-Intel drives in PE4 in VROC mode. I have also used 2x bootable Intel Optane drives in PE6 and PU2 in VROC mode.

OK I was able to get the driver to install by enabling VROC on PE3 which has nothing in it, but it doesn't help since it has to enabled for the slot the card is in. I can not boot it in PE4 with VROC enabled. It gives a 94 error. I will try it again, but I disabled all other slots from bifurcation except PE4 and it won't boot. I only have a video card, the hyper card and a wireless card in PE5. None of those should conflict with PE4. The big question is why it won't boot in PE4 with VROC enabled, but it will boot with non-VROC enabled? Both are bifurcated.
 
The other interesting thing is I can create a raid in the rst page in bios on pe4, but only if computer attached storage is on. I believe you said rst doesn't work on pe4?

Don't get me wrong but seeing how you go through all of the expense and effort trying to make this work makes me wonder what are you hoping to gain by having VROC RAID that would make it worth it?

I was just trying to get this motherboard to work since it works on my other pc. I am planning on replacing the dark soon with the Asus board and maybe everything will work fine then. I can't create a nvme raid at all right now, unless maybe if I replaced the PM1 and PM2 with Intel drives they might be bootable. I can reuse the drives I bought with the new motherboard and sell this one at some point so the expense won't be too much of a problem.

I can't read your full message as it's not approved by the mods.
 
PE6 has x8 CPU lanes. The first x4 lanes are shared with PM2 and the last x4 lanes are shared with PU2. PM2 and PU2 are not mutually exclusive like PM1 and PU1 - they can be enabled simultaneously.
If PM2 is set to CPU, then PE6 will always use x4 PCH lanes. You can't use CPU Attached Storage with PE6 in this configuration. If the drive shows up in RST, it's through the chipset.
If PM2 is set to PCH and PU2 is enabled, then PE6 will use x4 CPU lanes.
If PM2 is set to PCH and PU2 is disabled, then PE6 will use x8 CPU lanes. You can use a Hyper M.2 card with at most 2 drives in this configuration for CPU Attached Storage.

JK_DC

ZoranC

JK_DC

Monstieur
The VROC device which requires the VROC v7 or v8 driver will show up only when VROC is enabled in the BIOS. You don't need a VROC key and don't need to create an array for this. While VROC is enabled, the NVMe drives will not show up in Windows until you install the driver. You cannot install the VROC VMD driver for any other device. Merely enabling VROC will replace each NVMe drive with a VROC device. When you create a VROC RAID array, the individual VROC devices will be replaced with a single VROC device.
 
Error 94 is a PCI device enumeration error. It could be a compatibility issue with other devices sharing the PCIe lanes that belong to the same VMD on which VROC is enabled. If you have the Hyper M.2 in PE4, disconnect PE3 even if you use only x8 lanes in PE4. You can view the VMD grouping in the BIOS. The same applies to PE1 / PE2, and PM1 / PU1 / PE6 / PM2 / PU2.
 
I have used the Hyper M.2 card with 4x non-bootable non-Intel drives in PE4 in VROC mode. I have also used 2x bootable Intel Optane drives in PE6 and PU2 in VROC mode.

OK I was able to get the driver to install by enabling VROC on PE3 which has nothing in it, but it doesn't help since it has to enabled for the slot the card is in. I can not boot it in PE4 with VROC enabled. It gives a 94 error. I will try it again, but I disabled all other slots from bifurcation except PE4 and it won't boot. I only have a video card, the hyper card and a wireless card in PE5. None of those should conflict with PE4. The big question is why it won't boot in PE4 with VROC enabled, but it will boot with non-VROC enabled? Both are bifurcated.
 
The other interesting thing is I can create a raid in the rst page in bios on pe4, but only if computer attached storage is on. I believe you said rst doesn't work on pe4?

Don't get me wrong but seeing how you go through all of the expense and effort trying to make this work makes me wonder what are you hoping to gain by having VROC RAID that would make it worth it?

I was just trying to get this motherboard to work since it works on my other pc. I am planning on replacing the dark soon with the Asus board and maybe everything will work fine then. I can't create a nvme raid at all right now, unless maybe if I replaced the PM1 and PM2 with Intel drives they might be bootable. I can reuse the drives I bought with the new motherboard and sell this one at some point so the expense won't be too much of a problem.

What I am trying to say is that one can use RAID for data drive or boot drive to either get speed or mirroring. If you are trying to use it as data drive then you don't have to jump through hoops with VROC, Storage Spaces will serve you equally well. And if you are trying to use it as boot drive I personally don't see much benefit to it, it is a road I did long ago and realized there is too much hassle to it, just isn't worth it and that I can do things differently in much simpler manner.

JK_DC
I have the card in PE6 now. I have PM2 set to CPU. CPU attached storage is on. RST only sees 1 drive in the Windows application and I can't create a PCIe raid. Disk and device manager sees both drives. The bios sees both drives as well. I can create the raid but I can't use it in Windows as it doesn't see it. I can't boot off of a regular sata ssd since I turned it to raid mode. It will not see any sata drives in the boot menu. I think my board is just defective for a raid setup. It is fine for a basic setup. My AsRock worked straight away. I created a array in windows with rste with samsung drives and the trial popped up. It couldn't have been much easier. I am getting an Asus board to replace this one. I'll stick with EVGA on video cards and power supplies, but motherboards are too highly developed for them. 

You cannot use PM2 and PE6 for CPU Attached Storage together as they share CPU lanes. For all drives to use CPU lanes you can use only PM1 / PM2 / PU2 or PM1 / PE6 / PU2.
 
If you change to RAID mode after installing Windows, you need to reboot into safe mode at least once. Install the driver manually while RAID is disabled, then enable RAID and boot into safe mode so Windows picks up the new driver for the boot device.
 
The probability of the board being defective in this way is very low. It's most likely misconfigured.

In the news: Intel is officially killing Optane https://www.youtube.com/w...unW0vRMk_Y&t=1228s

ZoranC
In the news: Intel is officially killing Optane https://www.youtube.com/w...unW0vRMk_Y&t=1228s

Doesn’t matter. Optane Memory Acceleration is still the best hybrid SSD solution. There’s nothing else which caches ALL wires all the time. It’s also the only one which doesn’t lose cached data on a system crash. The 900p was discontinued long ago. The driver will continue to be supported.

Monstieur

ZoranC
In the news: Intel is officially killing Optane https://www.youtube.com/w...unW0vRMk_Y&t=1228s

Doesn’t matter. Optane Memory Acceleration is still the best hybrid SSD solution.

Was it technologically best? Yes, no debate there. But discontinuing IMHO does matter. Discontinued products die off. Driver might be supported now but there is no guarantee it will exist and continue being supported with next releases of operating systems. Not being able to use something anymore down the road does matter, especially at such an astronomical price. Betamax was technologically best yet it ended up very expensive brick down the road after discontinuing.