Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →nvraid.sys is a legacy NVIDIA RAID storage-stack component. A blue screen that names it does not prove that this file is damaged or that a hard drive has failed. The same stop-error context can result from a wrong or corrupted storage driver, a BIOS storage-mode change, firmware, memory, a disk, or another device driver.
The safest fix is evidence-led: protect any RAID data, record the complete stop error, boot into Safe Mode or Windows Recovery if necessary, install the exact RAID/SATA/AHCI/VMD package for your motherboard or computer model, roll back a recent change when appropriate, and test the array and hardware before replacing anything.
As an Amazon Associate I earn from qualifying purchases.
What nvraid.sys is
nvraid.sys is associated with NVIDIA RAID support supplied in older NVIDIA chipset driver packages. Motherboard vendors commonly distributed the RAID component as part of an all-in-one driver package rather than as a universal download. An ASRock NVIDIA RAID manual, for example, documents the RAID driver media and the NVRAIDMAN management utility. That history matters because the correct replacement is tied to the motherboard chipset and storage configuration.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The filename identifies a layer in the storage path, not the root cause. Windows stop errors can be caused by a hardware device, its driver, or software. A crash that displays nvraid.sys may therefore reflect a failing disk, a bad memory module, firmware, an interrupted array operation, a recent update, or another driver that corrupted storage activity.
#1 Best Overall
- 6-PORT SATA EXPANSION CARD: Adds 6 SATA III (6Gbps) drives to your desktop at once, turning one PCIe x4 slot into a 6-bay storage pool for unRAID, TrueNAS, ZFS, Proxmox or Windows Storage Spaces software RAID. Hardware RAID is not supported.
- 277MB/S ON EVERY PORT: PCIe 3.0 X2 upstream runs at 16GT/s, and each of the 6 SATA ports delivers up to 277MB/s, so large multi-drive transfers, media libraries and backup jobs finish fast with no bottleneck.
- NO DRIVER, WIDE COMPATIBILITY: Plug and play on Windows (except XP), Mac OS, Linux and NAS systems. Set SATA mode to AHCI in BIOS or UEFI before first install. This is a data storage HBA and does not boot an operating system.
- 6 BUILT-IN LED INDICATORS: A steady red LED means the drive is powered, a flashing LED means it is reading or writing, so you can check every SATA drive at a glance without opening the case.
- FITS X4/X8/X16 SLOTS, FULL KIT INCLUDED: Ships with 6 x SATA III cables (350mm/13.5in), a 1:5 SATA power splitter cable, and both a 12cm regular and an 8cm low-profile bracket for any PC or NAS case.
Do these safety checks before changing a RAID system
RAID changes can affect every disk in an array. If a drive is offline or an array is rebuilding, avoid experimenting until data is protected.
- Confirm that you have a current, verified backup of important files. A backup is verified only when you can open or restore representative files from it.
- Do not reboot or interrupt a rebuild, and do not power-cycle a system while a drive is offline unless the platform documentation or support team directs you to do so. Intel’s RAID guidance specifically warns against rebooting during a rebuild or while a drive is offline until the issue is understood or other troubleshooting is exhausted.
- Record the array state, the member disks shown by the RAID utility, and any warnings before uninstalling a driver or changing BIOS settings.
- Collect Windows, application, and RAID-controller logs while the system is still available. Save them to another drive if the machine is unstable.
- If the system is used for work or contains irreplaceable saves, stop after the evidence-collection stage and involve the computer or motherboard manufacturer before attempting a mode conversion.
Choose the first path from the symptoms
| Situation | First action | Why this path fits |
|---|---|---|
| Windows still reaches the desktop | Record the stop code, inspect the storage controller in Device Manager, and obtain the exact vendor package. | You can preserve logs and driver details before making a change. |
| Windows repeatedly crashes during startup | Use Windows Recovery to enter Safe Mode, then undo a recent driver, hardware, or BIOS change. | Safe Mode loads a reduced set of drivers and gives you a controlled way to revert changes. |
| The crash started immediately after a driver or Windows update | Roll back the affected driver or restore the last known working state. | The timing makes a rollback more informative than installing an unrelated package. |
| The BIOS was changed from RAID to AHCI, AHCI to RAID, or to a VMD setting | Return to the documented configuration or follow the motherboard’s transition procedure. | Changing storage mode casually can make an existing Windows installation unbootable. |
| A RAID member is offline or rebuilding | Protect the data and consult the platform documentation or support team before rebooting. | Interrupting recovery can make an already degraded array harder to recover. |
| Crashes continue after a correct driver reinstall | Run memory, storage, firmware, and other hardware diagnostics and preserve dump files. | The named file may be reporting a fault elsewhere in the storage path. |
Step 1: Capture the complete crash details
Write down the entire blue-screen message before restarting. Include the stop code, every file name shown, and whether the crash happened while booting, installing Windows, resuming from sleep, or using the computer normally. Note the exact date the problem began and list any Windows update, chipset or storage-driver installation, BIOS change, new disk, memory upgrade, or peripheral added just beforehand.
Also record the computer or motherboard model, Windows edition and version, whether storage is configured as RAID, AHCI, or VMD, and the current RAID state. If Windows starts, open Event Viewer and review Windows Logs and the relevant System entries around the crash. Preserve minidumps and any RAID-management logs instead of deleting them during cleanup. A second module name or a storage warning can change the diagnosis completely.
Step 2: Reach Safe Mode or Windows Recovery
If normal startup works, you can perform the next steps from the desktop. If it loops or blue-screens, use Windows Recovery:
- From the sign-in screen or Start menu, hold Shift while selecting Restart. If Windows never reaches that screen, allow the recovery environment to appear after repeated failed starts or boot from Windows installation media.
- Select Troubleshoot, then Advanced options, and choose Startup Settings followed by Restart.
- Choose Safe Mode. Use Safe Mode with Networking only when you need network access to obtain the vendor package; otherwise the smaller driver set is preferable.
- Remove hardware that was added immediately before the crashes, if it can be removed without disturbing the array. Undo a recent BIOS change rather than making another unverified change.
Safe Mode is a diagnostic state, not a permanent repair. If the machine remains stable there, the difference in loaded drivers is useful evidence. If it also crashes in Safe Mode, give hardware, firmware, and the storage configuration more weight.
Rank #2
- Compatible with: LSI 9300-8i; Controller: LSI/Broadcom SAS3008 (12Gb/s SAS)
- Firmware (FW): HBA IT Mode (Non-RAID); Data Transfer Rate: up to 12Gbps SAS, SATA 6Gbps
- Host Interface: PCIe 3.0 x8; Internal Connectors: 2× Mini-SAS HD SFF-8643. --Direct attach up to 8 drives, and expand via external SAS Expander for large arrays
- PERFECT FOR: ZFS, FreeNAS/TrueNAS, unRAID, Proxmox, ESXi home-lab & NAS storage
- Packing List: HBA Card ×1; 2× SFF-8643 to 4× SATA cables (8× SATA ends). --Cables in box are for SATA drives. They are not compatible with SAS drives. To connect SAS drives, use SFF-8643 to 8482 SAS cables (sold separately) or our matched HBA + cable kit.
Step 3: Identify the exact platform and storage mode
Find the complete model number on the computer’s chassis, motherboard documentation, or firmware screen. A product family name is not enough: revisions can use different chipsets and driver packages. Record the Windows version and whether the system is 32-bit or 64-bit when the vendor lists separate downloads.
In Device Manager, inspect Storage controllers and, on older systems, IDE ATA/ATAPI controllers. Open the suspected controller’s Properties and note the provider, driver date, version, and hardware IDs. In firmware setup, record whether the controller is set to RAID, AHCI, or a vendor-specific VMD mode. Do not infer the mode from the presence of a single disk; a system can be configured for RAID even when an array is not currently degraded.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use the RAID utility supplied for that platform to check whether an array is healthy, rebuilding, or reporting an offline member. The legacy NVIDIA package may refer to NVRAIDMAN, while other platforms use different management tools. The utility name does not make an Intel, AMD, or NVIDIA package interchangeable.
Step 4: Get the correct storage driver
Download the RAID, SATA, AHCI, or VMD/RST package from the support page for the exact motherboard or computer model and the installed Windows version. If the manufacturer’s page provides a chipset bundle and a separate storage package, follow its installation order and choose the storage package that matches the controller shown in Device Manager.
- Prefer the motherboard or system manufacturer’s package over a generic file-hosting site or a driver intended for another chipset.
- Check release notes for supported Windows editions, controller modes, and whether the package is intended for a fresh installation or an existing system.
- Keep the downloaded installer and release notes on removable media or another computer in case the affected system cannot boot.
- Do not substitute a similarly named NVIDIA, Intel, or third-party package. A storage driver that loads on the wrong controller can prevent Windows from starting.
Microsoft’s stop-code guidance recommends contacting the hardware vendor when a named driver is implicated. That is especially important for nvraid.sys, because the component is tied to a legacy chipset and there is no universal current download that fits every motherboard.
Rank #3
- 🚀 4-Port SATA 3.0 Expansion – 💾Add 4 high-speed SATA III (6Gbps) ports to your desktop PC via PCIe x1 slot, perfect for connecting additional SSDs or HDDs. Ideal for gamers, content creators, and professionals needing extra storage.
- 🖥️ Marvell88SE9215 Chipset for Reliable Performance – ⚡Powered by the advanced Marvell 9215 controller, this card ensures stable data transfer and broad compatibility with both modern SSDs and traditional HDDs. Enjoy faster boot times and seamless file access.
- ⚙️Boot as System Disk & Plug and Play – 🔧Use any connected SSD/HDD as a bootable system drive—great for upgrading older PCs without built-in SATA ports. Compatible with Windows XP /2003 / 7 / 8 / 10 / MAC / NAS / Linux OS. (driver-free installation for most systems).
- 💡 Low-Profile Design with Included Bracket – ✔️Includes both full-height and low-profile brackets, fitting most desktop cases (mini-ITX, small form factor, or standard towers). Comes with 4 high-quality 6Gbps SATA data cables for immediate setup—no extra purchases needed!
- ❄️ Cool & Quiet Operation – 🔌Fanless design eliminates noise while advanced heat dissipation ensures reliable performance during long workloads—perfect for home offices or gaming rigs across. Any question please connect us: [email protected]
Step 5: Reinstall the supplied driver through Device Manager
Use this procedure when Windows is stable enough to run Device Manager and you have already obtained the correct package.
- Open Device Manager and expand Storage controllers. If the controller is listed elsewhere, use the category shown by the vendor documentation.
- Open the controller’s Properties and save the current driver provider and version. This gives you a reference if the new package behaves worse.
- Choose Uninstall device. If Windows offers to remove the driver software, select that option only when the vendor package is ready and the platform documentation supports a clean replacement. Do not remove a functioning controller blindly on an array that is rebuilding.
- Restart Windows. If the controller is not detected automatically, return to Device Manager and select Action followed by Scan for hardware changes.
- Run the exact RAID or storage installer from the motherboard or computer manufacturer. Restart when prompted, even if the installer does not appear to require it.
- Recheck the controller’s provider and version, then open the RAID utility and confirm that the array state has not changed.
If the installer refuses to run, stop rather than forcing it with compatibility settings. Recheck the model, Windows version, storage mode, and package type with the vendor’s support documentation.
Step 6: Roll back a change that clearly triggered the crash
When the first crash follows a driver or Windows update, a rollback is often safer than trying several new packages. In Device Manager, open the controller’s Properties, select the Driver tab, and use Roll Back Driver when Windows makes that option available. If the button is unavailable, use a Windows restore point created before the change or the recovery option supplied by the computer manufacturer.
Record what was rolled back and test several cold starts and normal workloads. If the problem returns after a later update, do not repeatedly alternate packages without preserving logs; the pattern can indicate firmware, hardware, or an incompatibility that needs the vendor’s attention.
Step 7: Apply Windows, firmware, and BIOS checks carefully
Install pending Windows updates only after the system is backed up and the array is in a safe state. Check the motherboard or computer manufacturer’s support page for BIOS and storage-firmware advisories that match the exact model. Firmware updates can change storage behavior, so follow the vendor’s power and recovery instructions and do not interrupt an update.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #4
- Controller: LSI SAS 2008 6Gbps SAS/SATA HBA RAID Controller Card
- PCIE 2.0 (6.0 Gb/s), (NOT support hot swaping! ), X8 Lane; 2x Mini SAS SFF-8087 Ports
- Up to 6 G SATA and SAS link rates, SAS 2.0 complian; Support 256 SAS and SATA device;
- Driver CD is included natively, you also can download it from 10Gtek website
- What You Get: 10Gtek LSI-2008-8I HBA Card x1, Driver CD x1, Low-profile Bracket x1. Backed by 10Gtek 30 Days Free-returned, 3 Year Free Warranty and Lifetime Technology Support.
Pay special attention to the RAID/AHCI/VMD setting in firmware. A mode change can make an existing Windows installation unbootable unless the correct transition procedure and driver are used. There is no universal safe sequence for every motherboard. Use the model’s manual; if it does not document a transition, leave the current mode unchanged and ask the vendor before proceeding.
Step 8: Test memory, disks, and firmware when the driver is not the whole problem
A correct driver reinstall does not rule out a failing component. Run Windows Memory Diagnostic or the memory test provided by the computer manufacturer. Run the OEM’s storage diagnostics for each disk and review the reported health, error, and firmware information. Follow the hardware tests recommended by Microsoft, Intel, or the system vendor rather than repeatedly booting a degraded array.
- A memory error can corrupt data structures and make a storage driver appear responsible.
- A disk with read, write, or communication errors can trigger a stop error while the driver is processing I/O.
- Outdated or damaged firmware can create failures that persist across driver versions.
- Another device driver can produce the fault while
nvraid.sysis the module that finally reports it.
Document the test name, date, result, and any error code. A single pass that reports no fault is useful evidence but is not proof that an intermittent failure is impossible; use the OEM’s recommended duration and procedure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Step 9: Understand the Intel RST advisory without misapplying it
Intel documented a specific issue in RST versions 19.5, 20.0, and 20.1: after a SATA drive was unplugged during active I/O, the software could report a RAID 1, 5, or 10 failure incorrectly. Intel states that RST 20.2 includes a fix. This advisory applies to Intel Rapid Storage Technology systems, not automatically to NVIDIA systems that display nvraid.sys.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The practical lesson is to identify the entire storage stack and its version before applying a fix. Do not install Intel RST merely because an Intel advisory mentions RAID, and do not assume that an NVIDIA filename proves the Intel issue. Match the package and workaround to the controller actually installed in the computer.
Best Value
- 【4 Port SATA PCIE 3.0 Card】The PCIE SATA card allows you to add 4 SATA 3.0 6Gbps devices to your computer. If your motherboard has RAID function, you could make a RAID with this SATA Card. (WARM TIPS: Can not Support Hardware RAID)
- 【Powerful Chipest】This SATA controller card adopts Marvell 88SE9215 chip, making this card more stable and compatible. Port Multiplier FIS-based and Command-based switching supported.
- 【Advance Heatsink】The SATA card uses heat sink technology to disperse heat away from the core components to improve reliability and performance.
- 【Compatibility】with a low profile Bracket System Compatible with Windows XP /2003 / 7 / 8 / 10 / MAC / NAS / Linux OS. Support PCIe X1 / X4 / X8 / X16 slot. It also comes with a low profile bracket to fit different sizes of desktop computers.
- 【Includes All Required Accessories】Kit includes: 1 X 4-port SATA expansion card, 4 X SATA cable(40cm/15.8in), 1 X low-profile bracket, 1 X screwdriver, 2 X screw kit, 1 X anti-static bag.
Step 10: Escalate with a useful evidence bundle
Contact the motherboard or computer manufacturer, Microsoft support, or a qualified technician when the crashes continue after the documented rollback and exact-package reinstall, when a RAID member is offline, or when diagnostics report errors. Send a concise bundle:
- Complete stop code and every file name shown on the blue screen.
- Minidump files and the relevant Event Viewer entries.
- Computer or motherboard model, BIOS version, Windows edition and version, and storage mode.
- RAID utility status, member-disk information, and whether a rebuild was in progress.
- Driver provider, version, and installation date before and after the change.
- Memory, storage, and firmware diagnostic results.
- A timeline of updates, BIOS changes, new hardware, and the first crash.
Do not delete dumps or reset the BIOS before copying this information. Support can use the dump and system logs to determine whether the named module is the failing component or only the point at which a different fault became visible.
Common mistakes that make nvraid.sys problems worse
Downloading a standalone nvraid.sys file
Replacing one file from an unrelated website can introduce a mismatched version, malware, or an incorrect architecture. Storage drivers include more than a single file and must match the controller, firmware, and Windows build. Use the complete package supplied for the exact platform.
Assuming the hard drive is dead because the filename says RAID
The filename is evidence about the storage path, not a disk-health verdict. Test the disks and memory, inspect the array state, and correlate the crash with logs before buying replacement hardware.
Switching RAID, AHCI, and VMD as a trial
Changing the mode without the documented transition procedure can make Windows unbootable and can obscure the original fault. Restore the known configuration and obtain model-specific instructions first.
Rebooting during a rebuild
An interrupted rebuild can increase data loss risk. Treat an offline or rebuilding array as a data-recovery situation until its status is understood.
Installing a driver for a similar model
Adjacent motherboard revisions and computer variants can use different controllers. Verify the exact model and hardware ID rather than relying on a product-family name.
Wiping Windows before collecting evidence
A clean installation may remove the logs, dumps, and driver history needed to identify the cause, while a BIOS-mode mismatch can make the fresh installation fail as well. Preserve data and diagnostics first.
Quick Recap
As an optional shortcut after the manual checks, Outbyte Driver Updater can scan more than 100 devices for outdated, corrupted, or missing drivers, install official drivers, show the current and recommended versions, and provide driver backup, restore, and scheduled scans. It runs on Windows 11, 10, 8, and 7; its 2-day free trial requires no credit card and is followed by a subscription. Results vary, and no tool repairs every crash.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
