Karadigne - thanks. Would be very interested for you to read the article whose link I posted above - is the author using those raid drivers? Over at Dell support forums, that maniac (but knowledgeable) Speedstep was ranting that the Raid0 drivers are somehow dangerous or unstable (but then look who's talking). See his post at
< THIS LINK > (And I have only one M.2, not dual.)
Ah, confusion. Windows7+ has native support for NVMe, which uses the raid drivers. 3rd gen Intel was built before NVMe was a thing, so your choice for storage was either Raid or AHCI in bios. To use a Raid setup, requires a minimum of 2 drives, kinda like SLI. So if you only have 1 drive, or multiple different drives, Raid isn't an option, only AHCI.
Loading AHCI you get the AHCI drivers, the Raid drivers don't load. You don't get Raid support until Windows loads, so you could use NVMe as storage, same as regular Sata, but unlike Sata, no boot.
The work around for that is modifying the bios so that it loads the Raid drivers regardless of choice, which enables the NVMe to be recognised as a boot device before loading Windows. This only applies to that old stuff, modern bios already have NVMe support at boot since they have on-board M.2 ports.
And yes, Raid 0, using just 2 drives is somewhat chancy. It seperates the data across both drives. If you saved ABCXYZ, what you'd get on drive:1 would be ACY, drive:2 would get BDZ. If one drive gets buggy, corrupted, dies, you loose all the data on both, because you've intrinsically lost half, making the remaining half useless.
But that's very different from using an NVMe as boot drive in AHCI, that uses the identifiers inherent in raid drivers to recognise the drive in bios as a boot drive.