Two identical NVMe drives, one BIOS menu, and a promise of doubled throughput: NVMe RAID 0 has been a PC-building rabbit hole since the first M.2 slots shipped, and it is back in builder forums again now that PCIe 5.0 drives like the Samsung 9100 Pro and Crucial T710 have pushed single-drive sequential speeds past 14,000 MB/s. The pitch sounds simple, stripe two drives together in Intel Rapid Storage Technology (RST) or AMD RAIDXpert2 and watch your storage bandwidth climb. The reality, as this guide walks through step by step, is more complicated, and the BIOS menu that gets you there is not forgiving of mistakes.
This tutorial covers the full process on both Intel and AMD platforms: confirming your motherboard actually supports NVMe RAID, picking two matched SSDs, enabling VMD or AMD’s NVMe RAID mode, building the array, injecting the correct driver into a Windows 11 installer, and verifying the array survives a reboot with TRIM intact. It also covers the parts most tutorials skip, why RAID 0 barely moves the needle on game loading times, and why losing one drive means losing everything on the array.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What NVMe RAID 0 Actually Does for a Gaming PC in 2026
RAID 0 splits data into stripes and writes it across two or more drives at once, so the controller can read and write to both simultaneously instead of waiting on a single drive’s queue. On paper, two drives rated for 7,450 MB/s sequential read each should combine for something close to 14,000 MB/s under the right conditions. In practice, the gain only shows up in workloads that can actually saturate both drives at once, large sequential transfers, video scratch disks, big dataset copies, and it does not show up proportionally in random, low-queue-depth access patterns, which is most of what a game engine actually does while loading a level.
That distinction matters because NVMe RAID 0 for gaming has a reputation problem: it was popularized by marketing slides showing sequential benchmark charts, not by independent testing of real game load screens. A single current-generation drive like the Crucial T710 already pushes roughly 14,500 MB/s read and 13,800 MB/s write on its own, which is far beyond what any shipped PC game can currently consume during a load screen. Stacking a second drive in RAID 0 adds synthetic headroom you are unlikely to use, while adding real risk you will definitely carry: if either drive in the array fails, drops a firmware update, or gets disconnected, the entire volume is gone, not half of it.
None of that means RAID 0 is pointless. It is a legitimate tool for a specific kind of build: a scratch volume for video editing, a dataset drive for machine learning work, or a secondary non-boot array where capacity and throughput matter more than survivability. This guide treats it as exactly that, a capacity-and-throughput configuration for builders who understand the trade-off, not a guaranteed frame-rate or load-time upgrade.
NVMe RAID 0 vs RAID 1 vs RAID 10: Which Level Actually Fits a Gaming PC
RAID 0 is only one of several array types Intel RST and AMD RAIDXpert2 expose, and builders chasing “faster storage” often default to it without checking whether a different level actually matches their goal better. RAID 1 mirrors the same data across two drives instead of striping it, which means no capacity gain and no meaningful speed gain on writes, but it survives the failure of either drive without data loss, the opposite trade-off from RAID 0. RAID 10 combines both approaches across four drives, mirroring two striped pairs, which delivers some of RAID 0’s throughput benefit alongside real redundancy, at the cost of needing twice as many drives for the same usable capacity.
| RAID Level | Minimum Drives | Usable Capacity | Redundancy | Best Fit |
|---|---|---|---|---|
| RAID 0 | 2 | 100% of combined capacity | None: any drive failure loses everything | Scratch/working volumes where speed and capacity matter more than safety |
| RAID 1 | 2 | 50% of combined capacity | Survives failure of either drive | Critical data that must stay available with minimal setup complexity |
| RAID 10 | 4 | 50% of combined capacity | Survives failure of at least one drive per mirrored pair | Builders who want RAID 0-like throughput without RAID 0’s total-loss risk |
| RAID 5 | 3 | Combined capacity minus one drive | Survives failure of any single drive | NAS and server-style builds prioritizing capacity efficiency over speed |
For most gaming PCs, the honest recommendation is RAID 1 or no RAID at all for anything irreplaceable, and RAID 0 reserved strictly for a secondary volume you have already planned to back up. RAID 10 is worth considering only if you already own four matched drives and have M.2 or SATA connectivity to spare, which is uncommon on consumer gaming motherboards that typically offer two to four total M.2 sockets shared with other features. RAID 5 rarely makes sense on NVMe drives in a gaming context at all, it is a capacity-and-redundancy compromise built for spinning disks and SATA SSD arrays in NAS boxes, not for squeezing extra frame-rate-adjacent performance out of a desktop.
External Enclosures and Adapters as an Alternative to Motherboard RAID
Builders whose boards lack RAID-capable M.2 sockets have another route. OWC launched the Express 4M2 Ultra in April 2026, a 4-slot Thunderbolt 5 NVMe enclosure supporting RAID 0 and speeds up to 6,622 MB/s. OWC’s newest 4-slot NVMe RAID enclosure supports 6 modes: RAID 0/1/4/5/10 and JBOD. OWC also announced four-drive support for both M.2 2280 and 2242 NVMe SSDs in its latest RAID enclosure, and priced the Express 4M2 Ultra at $399.99 without SoftRAID and $549.99 with SoftRAID.
Internal adapters exist too. In March 2026 Raidon introduced PC05M-42, a dual-M.2 PCIe Gen3 x4 NVMe adapter. It provides each of 2 NVMe drives a dedicated PCIe Gen3 x2 link, and Raidon stated PC05M-42 needs 0 motherboard PCIe-bifurcation support for dual-drive operation.
For a gaming PC, these options mainly solve a slot-wiring problem rather than a speed problem. A Gen3 link per drive sits well below the Gen4 and Gen5 drives discussed above, so an adapter like this suits capacity and convenience more than peak throughput. An external enclosure moves the array off the motherboard, but RAID 0 still means a single drive failure destroys the array and its data, so the backup routine in Step 13 applies in exactly the same way. If you want an external array that survives a drive failure, choose one of the redundant modes the enclosure offers instead of striping.
Prerequisites: Motherboard, Driver, and SSD Requirements
Before touching a BIOS menu, confirm every item on this list. NVMe RAID is a feature that varies by motherboard model, not just by chipset family, and skipping this step is the single most common reason builders end up with an inaccessible boot drive.
- A motherboard whose manual explicitly lists NVMe/PCIe RAID support for the specific M.2 sockets you intend to use, not just a chipset that theoretically supports it.
- Two identical NVMe SSDs: same model, same capacity, same firmware revision where possible. Mixed drives will run at the speed of the slowest, weakest member.
- Current Intel RST driver (version 20.2.6.1025.3 for Windows 11 25H2 on standard Z790/Z890 platforms, or 21.1.0.1006.2 specifically for Intel Core Ultra Series 3 platforms) or the current AMD chipset package (8.03.24.733, which bundles AMD RAID driver 9.3.2.158 and the RAIDXpert2 utility 9.3.2.162) downloaded from your motherboard vendor’s support page.
- A spare USB flash drive (8GB+) formatted FAT32, used to carry the RAID driver into the Windows installer.
- A second USB flash drive (8GB+) for the Windows 11 installation media itself.
- A full backup of anything currently on the target drives, this process is destructive to existing data on both SSDs.
- Windows 11, ideally the 25H2 release, since Intel’s current RST package is validated against it.
Chipset support is necessary but not sufficient. Even on boards that list RAID support, the feature is usually restricted to specific M.2 sockets, typically the ones wired directly to the CPU rather than through the chipset. Check your specific board’s manual for which sockets qualify before buying drives.
| Chipset | Platform | NVMe RAID Support | Current Driver Package |
|---|---|---|---|
| Intel Z890 | Core Ultra Series 2/3 (LGA1851) | RAID 0/1/5/10 on CPU-connected M.2 slots (board-dependent) | RST 21.1.0.1006.2 |
| Intel Z790 | 13th/14th Gen Core (LGA1700) | RAID 0/1/5/10 on select boards, varies by model | RST 20.2.6.1025.3 |
| AMD X870 / X870E | Ryzen 9000/9000X3D (AM5) | NVMe RAID 0/1/5/10 | Chipset package 8.03.24.733 |
| AMD X670 / X670E | Ryzen 7000/9000 (AM5) | NVMe + SATA RAID 0/1/10 | Chipset package 8.03.24.733 |
| AMD B850 / B650 | Ryzen 7000/9000 (AM5) | NVMe + SATA RAID 0/1/10 (board-dependent) | Chipset package 8.03.24.733 |
Treat every “board-dependent” note in that table as a hard verification step, not a footnote. ASUS’s own documentation for the ROG Strix Z890-E, for instance, states that Intel RST supports PCIe RAID 0/1/5/10 but restricts which CPU-connected M.2 slots can participate, a detail only visible in the manual’s storage block diagram, not in chipset marketing copy.
Phase 1: Confirm Compatibility and Back Up Your Data (Steps 1-3)
Step 1: Confirm Your Motherboard’s RAID-Capable M.2 Slots
Open your motherboard manual’s storage section and find the block diagram showing which M.2 sockets connect directly to the CPU versus through the chipset. Boards frequently disable one M.2 slot, drop it to a lower PCIe lane count, or reduce your graphics card slot from x16 to x8 when a second CPU-connected M.2 socket is populated. This single step prevents the most common RAID-0 disappointment: building the array, then discovering one of your two “RAID-capable” slots was never actually eligible.
Step 2: Buy Two Matched NVMe SSDs
Buy both drives from the same product line and capacity. A Gen4 pairing using two Samsung 990 Pro drives (7,450/6,900 MB/s each) is the mature, widely compatible choice and currently runs about $160-$165 per 2TB drive at US retail. Builders chasing Gen5 throughput can pair two Samsung 9100 Pro drives (up to roughly 14,800/13,400 MB/s each, around $280-$300 per 2TB) or two Crucial T710 drives (14,500/13,800 MB/s, around $263-$280 per 2TB), but Gen5 drives run hot enough that you should confirm your board has heatsinks or airflow for both sockets before committing to the pairing.
Step 3: Back Up Everything on Both Target Drives
Building a RAID 0 array destroys any existing partitions and data on both drives the moment the array is created in BIOS. Copy anything you need to an external drive or cloud storage first. A simple way to confirm what is actually on each drive before you wipe it is to list volumes from an elevated command prompt:
diskpart
list disk
select disk 1
list partition
exitRun this before you touch BIOS so you know exactly which physical disk numbers correspond to the drives you are about to stripe.
Phase 2: Enable RAID Mode and Build the Array in BIOS (Steps 4-7)
Step 4: Download the Correct Driver Package for Your Platform
Go to your motherboard vendor’s support page (not Intel’s or AMD’s generic download page) and grab the platform-specific package, since board vendors sometimes bundle a customized RST or RAIDXpert2 build that differs from the generic one. For Intel platforms on Windows 11 25H2, confirm you are getting RST 20.2.6.1025.3 (or 21.1.0.1006.2 if you are on a Core Ultra Series 3 board). For AMD AM5 platforms, confirm you are getting chipset package 8.03.24.733 or newer, which includes AMD RAID driver 9.3.2.158 and the RAIDXpert2 management utility 9.3.2.162. Extract the downloaded package to the root of your FAT32 USB drive now, you will need it twice, once inside BIOS and once during Windows setup.
Step 5: Enable VMD (Intel) or NVMe RAID Mode (AMD) in BIOS
Reboot into BIOS/UEFI setup. On Intel boards, look for a setting named Intel VMD Controller, sometimes listed under Advanced > PCH Storage Configuration or similar. Enable it. On AMD boards, look for NVMe RAID Mode or RAID Mode under the chipset/storage configuration menu, sometimes labeled simply “SATA Mode: RAID” for the SATA controller and a separate NVMe RAID toggle for M.2 sockets.
Do not confuse this with CSM (Compatibility Support Module). CSM governs legacy BIOS boot compatibility and has nothing to do with enabling the RAID engine; for a modern Windows 11 UEFI install, CSM should normally stay disabled. Save and reboot into BIOS again to confirm the VMD or RAID toggle actually stuck before proceeding.
Step 6: Build the Array in Intel RST (Intel Platforms)
With VMD enabled, a new menu appears in BIOS, usually called Intel Rapid Storage Technology or PCIe RAID. Enter it, select “Create RAID Volume,” choose RAID 0, select both target NVMe drives from the list, set a stripe size (128K is a reasonable default for large sequential files; 64K if you expect more mixed workloads), name the volume, and confirm creation. The BIOS will warn that this erases all data on both drives, this is expected and is why Step 3 exists.
Step 7: Build the Array in AMD RAIDXpert2 (AMD Platforms)
On AMD boards, the equivalent menu is typically under Advanced > AMD RAIDXpert2 Configuration Utility, reachable after NVMe RAID Mode is enabled and the system has rebooted. Select Create Array, choose RAID 0, pick both NVMe drives, set the stripe size, and confirm. ASUS lists AMD RAIDXpert2 support for RAID 0/1/5/10 with Ryzen 9000, RAID 0/1 with Ryzen 8000, and RAID 0/1/10 with Ryzen 7000 on its current boards, but double-check your specific board’s manual for which M.2 sockets can be combined. The CPU generation in your build affects which array types you can create, not just the motherboard model.
Phase 3: Install Windows 11 on the RAID 0 Volume (Steps 8-10)
Step 8: Build a Windows 11 Installer and a Separate Driver USB
Use the Media Creation Tool on another PC to build a bootable Windows 11 USB drive. Keep the RAID driver files on a second, separate FAT32 USB drive (not combined with the Windows installer media), this avoids path confusion during the “Load driver” step and matches how Intel and AMD document the process.
Step 9: Load the RAID Driver During Windows Setup
Boot from the Windows 11 installer in UEFI mode. When you reach the “Where do you want to install Windows?” screen, your RAID 0 volume will not appear in the list, this is expected, not a failure. Click Load driver, insert the separate driver USB, browse to the extracted folder, and select the correct .inf file for your platform and Windows architecture (not just any file with “NVMe” in the name, it must be the specific RST or AMD RAID controller driver). The sequence looks like this:
1. Windows Setup -> "Where do you want to install Windows?"
2. Click "Load driver"
3. Insert USB containing extracted RST or RAIDXpert2 driver package
4. Browse to \RST\ (or \RAIDXpert2\) folder on the USB
5. Select the matching .inf for your CPU platform + Windows build
6. Confirm the RAID volume now appears in the drive list
7. Select the RAID volume and click NextStep 10: Install Windows 11 Onto the Array
Once the array appears and is selected, installation proceeds like any normal Windows install. Do not change the VMD/RAID BIOS setting after this point without reinstalling the matching driver first, flipping that toggle post-install is one of the fastest ways to produce an unbootable system, since Windows will no longer recognize the storage controller it was installed under.
Phase 4: Verify, Benchmark, and Protect the Array (Steps 11-13)
Step 11: Verify the Array and Check TRIM Status
After Windows boots, open Disk Management or run diskpart to confirm the array shows up as a single volume at the combined capacity of both drives (minus formatting overhead). Then check whether Windows’ delete-notification mechanism, which underlies TRIM, is active:
fsutil behavior query DisableDeleteNotifyA result of 0 means delete notifications are enabled at the filesystem level. That alone does not guarantee TRIM is reaching both physical SSDs through the RAID controller, whether that happens depends on the specific RST or RAIDXpert2 version and the drive firmware. Some configurations pass TRIM through correctly, others have limited or uncertain support, so treat this as a thing to monitor over months of use (watch for sustained write-speed degradation) rather than a one-time checkbox.
Step 12: Benchmark the Array
Run a sequential read/write benchmark against the new volume and compare it to the rated speed of a single drive. A quick built-in option from an elevated command prompt:
winsat disk -drive C -seq -ranFor a more complete picture, use a dedicated SSD benchmarking tool and test at multiple queue depths, not just the single high-queue-depth sequential number most tools highlight by default. The gap between sequential and random/low-queue-depth performance is exactly where RAID 0’s real-world gains shrink.
Step 13: Set Up a Backup Routine Immediately
Because RAID 0 has zero redundancy, set up an automated backup of anything irreplaceable on the array the same day you finish the build, not “eventually.” A simple scheduled mirror to a separate physical drive covers the basics:
robocopy D:\Projects E:\Backup\Projects /MIR /R:2 /W:5 /LOG:E:\Backup\backup_log.txtSchedule that command through Task Scheduler for a daily or weekly run, and point it at a drive that is physically separate from the RAID 0 array.
Beyond the one-time backup script, build a habit of checking array health rather than assuming it will quietly keep working. Open the Intel RST or AMD RAIDXpert2 management utility inside Windows every few weeks and confirm the array still reports as “Normal” or “Healthy” rather than “Rebuilding,” “Degraded,” or any error state. Both utilities also expose SMART data for each physical drive in the array individually, which is worth glancing at the same way you would check a single drive’s health, a rising reallocated-sector count or climbing temperature on either member is an early warning that is much more useful before a failure than after one.
Real Benchmark Numbers: RAID 0 vs a Single Gen4/Gen5 SSD
Treat any RAID 0 benchmark claim with a reflexive amount of skepticism unless it specifies the exact drives, stripe size, motherboard, PCIe generation, driver version, and whether the array was the boot volume during the test, those variables change the result enough that a number without them is close to meaningless. With that caveat, the technically defensible expectation looks like this:
| Configuration | Rated Sequential Read | Rated Sequential Write | Realistic RAID 0 Scaling |
|---|---|---|---|
| Single Samsung 990 Pro (PCIe 4.0) | 7,450 MB/s | 6,900 MB/s | Baseline |
| 2x Samsung 990 Pro in RAID 0 | Approaching 2x under ideal conditions | Approaching 2x under ideal conditions | Scaling drops sharply outside sequential, high-queue-depth transfers |
| Single Samsung 9100 Pro (PCIe 5.0) | ~14,800 MB/s | ~13,400 MB/s | Baseline |
| 2x Samsung 9100 Pro in RAID 0 | Limited by chipset uplink / CPU lane topology on most boards | Limited by chipset uplink / CPU lane topology on most boards | Linear scaling not guaranteed at this tier: check your board’s lane diagram |
Two identical PCIe 4.0 drives can approach roughly double the sequential throughput of one drive when the array, controller path, and workload are all capable of saturating both devices at once. Two PCIe 5.0 drives can produce very high synthetic sequential numbers in isolated tests, but motherboard lane topology and chipset uplink bandwidth frequently prevent that scaling from being linear, a second M.2 socket wired through the chipset, rather than directly to the CPU, shares bandwidth with everything else on that chipset bus. Random-access and low-queue-depth performance, which matters far more for day-to-day responsiveness, improves by a much smaller margin than the sequential chart implies.
Does RAID 0 Actually Cut Game Loading Times?
Usually not by an amount a player would notice. Game loading is bottlenecked by small-file access patterns, decompression, shader compilation, and engine initialization far more than by raw sequential SSD bandwidth. Independent testing comparing high-end single drives has already shown this ceiling: in cold-load comparisons between a Crucial T710 and a Samsung 990 Pro, the newer, dramatically faster-on-paper PCIe 5.0 drive shaved off well under a second against a drive rated at roughly half its sequential speed. If doubling single-drive bandwidth barely moves a load screen, striping two drives for even more headroom you already were not using moves it even less.
Where RAID 0 does help on a gaming rig is adjacent to gaming, not inside it: faster game-install and update downloads when writing large sequential patch files, faster video export if you also record and edit clips from the same machine, and faster transfers when migrating an entire Steam or other game library between drives. If your actual goal is shorter load screens, a single current-generation NVMe drive plus more system RAM will do more for you than a RAID 0 array ever will. For a deeper look at how NVMe compares to older SATA drives in real workloads, see this site’s NVMe vs SATA SSD comparison.
5 Pitfalls That Wreck NVMe RAID 0 Builds
- Assuming chipset support means every M.2 slot qualifies. Many boards wire one M.2 socket to the CPU and another through the chipset, or disable a slot entirely when certain SATA ports or PCIe slots are populated. Chipset-level RAID support says nothing about your specific board’s slot wiring.
- Mixing drive models or capacities. A RAID 0 array built from mismatched drives runs at the pace of its slowest, smallest member, and troubleshooting a mixed array is harder than troubleshooting a matched one.
- Flipping the VMD/RAID BIOS toggle after Windows is already installed. This is close to guaranteed to produce an inaccessible boot volume, since the OS was installed against a different storage controller mode.
- Treating RAID 0 as a backup-free storage tier for irreplaceable files. The array has two independent drive-failure points and no redundancy at all, losing either drive loses the whole volume, including save files, projects, and anything else stored there.
- Loading the wrong driver file during Windows Setup. Picking any .inf file containing the word “NVMe” rather than the specific RST or AMD RAID controller driver for your exact platform and Windows build will either fail to show the array or produce an unstable install.
Troubleshooting: 8 Common NVMe RAID 0 Problems and Fixes
Most RAID 0 problems trace back to one of three root causes: a BIOS setting that didn’t actually save, a driver mismatch between what Windows expects and what you loaded, or a motherboard lane limitation that was never actually capable of what the chipset name implied. Work through these eight before assuming a drive itself has failed.
- RAID volume doesn’t appear in BIOS after enabling VMD/RAID mode. Save and reboot a second time, some boards need two restarts before the RAID configuration utility populates with detected drives.
- Windows Setup still can’t see the array after loading the driver. You likely loaded a generic NVMe storage driver instead of the platform-specific RST or RAIDXpert2 controller driver. Re-download directly from your motherboard vendor’s support page and confirm the .inf matches your exact chipset and CPU generation.
- System won’t boot after a BIOS update. Some BIOS updates reset VMD/RAID settings to disabled by default. Re-enter BIOS, confirm VMD or RAID mode is still enabled, and re-save before rebooting into Windows.
- Array shows as “degraded” or “failed” unexpectedly. Check physical connections and drive temperatures first, Gen5 drives without adequate heatsinking can thermal-throttle hard enough to briefly drop from the array on some controllers.
- Benchmarks show far less than double a single drive’s speed. Confirm both M.2 sockets are actually running at full PCIe lane width and generation, check your board’s manual for lane-sharing rules, since a shared GPU slot or additional populated M.2 socket can silently downgrade one drive’s connection.
- Uncertain whether TRIM is working. Running
fsutil behavior query DisableDeleteNotifyonly confirms the filesystem-level setting, not whether TRIM commands are successfully reaching both physical drives through the RAID controller. Monitor write performance over several weeks as the more reliable real-world signal. - Can’t find the “Load driver” option during Windows Setup. It only appears on the “Where do you want to install Windows?” screen, and only if you booted the installer in UEFI mode with Secure Boot settings matching your BIOS RAID configuration.
- One drive runs noticeably hotter than its paired drive. Check whether both M.2 sockets have equivalent heatsinks or airflow, many boards only heatsink the primary CPU-connected slot, leaving a secondary chipset-connected slot to throttle under sustained RAID 0 load.
Advanced Tips: Stripe Size, PCIe Lane Sharing, and Mixed-Gen Arrays
Stripe size has a real, measurable effect on which workloads benefit. A 128K or 256K stripe generally favors large sequential files, game installs, video exports, big asset libraries, while a smaller 64K stripe spreads more evenly across mixed read/write patterns at some cost to peak sequential numbers. There is no universally correct setting; match it to what you actually store on the array.
PCIe lane sharing is the detail most builders discover too late. Common constraints include a CPU-connected M.2 socket running at full PCIe 5.0 x4 while a second socket on the same board only reaches PCIe 4.0 x4; an M.2 socket that shares lanes with the primary graphics card slot, dropping the GPU to x8 when populated; and two chipset-connected M.2 sockets that share a single uplink back to the CPU, capping their combined bandwidth well below what either drive is individually rated for. ASUS documents one such case on the ROG Crosshair X870E Dark Hero: when PCIEX16_1 runs at PCIe 5.0 x16, PCIEX16_2 will run at PCIe 3.0 x4, and the bandwidth can be altered in the BIOS. The same board features five onboard M.2 slots, two of which are PCIe 5.0-ready to offer 16 GB/s speeds, while the others offer 8 GB/s over PCIe 4.0 interfaces, which shows how unevenly slots on a single board can perform. The motherboard manual’s storage block diagram is the only reliable source for this, chipset name alone tells you almost nothing.
Mixing a PCIe 4.0 drive with a PCIe 5.0 drive in the same array is technically possible on some controllers but defeats the purpose: the array will run at the slower drive’s ceiling, so you paid Gen5 pricing for Gen4 real-world throughput. If you are building around current flagship drives, a matched pair of either the Samsung 9100 Pro or the Crucial T710 avoids this trap entirely; see this site’s side-by-side look at the 990 Pro vs 9100 Pro vs Crucial T710 comparison for the full spec breakdown before buying a pair.
A Complete Working Build: Parts List and Full Walkthrough
Putting the whole process together, here is a realistic example build for a secondary non-boot RAID 0 scratch volume on an AMD AM5 system, which is the safer and more common real-world use case than striping a boot drive.
| Component | Example Part | Approx. Price (2TB tier where applicable) |
|---|---|---|
| Motherboard | AM5 board with two CPU-connected M.2 slots rated for NVMe RAID (confirm in manual) | Varies by model |
| SSD #1 | Samsung 990 Pro 2TB | ~$160-$165 |
| SSD #2 | Samsung 990 Pro 2TB (matched) | ~$160-$165 |
| RAID driver package | AMD chipset package 8.03.24.733 | Free, from motherboard vendor site |
| Driver USB drive | 8GB+ FAT32-formatted USB flash drive | Under $10 |
| Backup destination | Separate external drive or NAS, sized to cover array contents | Varies |
Walkthrough: enable NVMe RAID Mode in BIOS, confirm it survives a reboot, enter the AMD RAIDXpert2 configuration utility, create a RAID 0 array from the two 990 Pro drives using a 128K stripe (good for a media/scratch volume storing large game installs or video files), save, boot into Windows, open Disk Management, initialize the new array as GPT, format it as a single NTFS volume, and label it clearly as “RAID0 – No Backup Redundancy” so nobody on a shared PC mistakes it for a protected drive. Finish by scheduling the robocopy backup command from Step 13 against anything on that volume you cannot afford to lose. This configuration keeps your Windows boot drive on a single, simple, easily recoverable SSD while giving you a genuinely useful high-capacity, high-throughput scratch volume for everything else. If you are assembling this inside a brand-new build rather than retrofitting an existing PC, this site’s step-by-step gaming PC build guide covers the rest of the assembly process.
When RAID 0 Is the Wrong Choice
If your primary goal is faster game load times, skip RAID 0 entirely and put the budget toward a single current-generation NVMe drive and more system RAM instead, the combination does more for real-world responsiveness than striping two drives ever will. If your goal is data safety alongside speed, look at RAID 1 or RAID 10 instead, which sacrifice some capacity for redundancy. If your goal is simply “more storage” without any performance requirement, two separate drives used independently are both safer and simpler to manage than a striped array, and losing one only costs you what was on that one drive. For a plain single-drive install without any RAID complexity, this site’s guide to installing a single NVMe SSD covers the simpler path end to end. RAID 0 earns its place only when you specifically need combined throughput and capacity for a non-critical scratch or working volume, and you have already planned for how you will back it up.
The builders who get the most genuine value out of NVMe RAID 0 tend not to be pure gamers at all, they are streamers recording multi-track 4K footage while playing, hobbyist video editors cutting game-capture highlight reels on the same machine, or AI/ML tinkerers who need a fast local scratch disk for datasets that don’t fit comfortably on a single drive. In each of those cases the workload genuinely issues the kind of large, sustained, high-queue-depth transfers that let a striped array show its rated numbers instead of shrinking back down toward single-drive performance. If your use case is “I play games and want them to load faster,” you are very likely better served by the money going toward a GPU upgrade, more RAM, or simply a bigger single SSD, all of which touch frame rates and load times more directly than a RAID controller ever will.
Frequently Asked Questions
Does NVMe RAID 0 actually double my SSD speed?
Sequential throughput can approach double under ideal conditions with matched drives on a fully capable motherboard path. Random and low-queue-depth performance, which affects day-to-day responsiveness far more, improves by a much smaller margin.
Will RAID 0 make my games load faster?
Usually not by a noticeable amount. Game loading is limited more by small-file access, decompression, and engine initialization than by raw sequential bandwidth, and current single drives already exceed what shipped games can use during a load screen.
Is it safe to put my Windows boot drive on RAID 0?
It is possible but adds real risk: a RAID 0 boot volume has zero redundancy, so a single drive failure takes down your entire operating system. Most builders are better served keeping Windows on a single drive and reserving RAID 0 for a secondary scratch volume.
What happens if one drive in my RAID 0 array fails?
The entire array becomes inaccessible. RAID 0 has no redundancy or parity, so there is no partial data recovery path built into the array itself, only a prior backup protects you.
Do I need identical SSDs for RAID 0?
You don’t strictly need identical drives, but the array runs at the pace of its slowest, smallest member, and mismatched drives make troubleshooting and firmware management noticeably harder. Matched pairs are the practical standard.
Does TRIM work properly on an NVMe RAID 0 array in Windows 11?
It depends on the specific RST or RAIDXpert2 driver version and drive firmware. Some configurations pass TRIM through to both physical drives correctly; others have limited or uncertain support. Checking the filesystem-level DisableDeleteNotify setting confirms only part of the picture, monitoring sustained write performance over time is the more reliable signal.
Can I mix a PCIe 4.0 drive with a PCIe 5.0 drive in the same RAID 0 array?
Some controllers allow it, but the array will run at the slower drive’s ceiling, which defeats the point of paying for a faster Gen5 drive. Matched-generation pairs are the better approach.
What BIOS setting do I need to enable before building an NVMe RAID array?
On Intel platforms, enable the Intel VMD Controller. On AMD platforms, enable NVMe RAID Mode (sometimes listed as RAID Mode) under the chipset storage configuration menu. Neither is the same setting as CSM, which governs legacy boot compatibility and should typically stay disabled on a modern UEFI Windows 11 install.
