Fix storport.sys Blue Screen Errors in Windows 11 & 10

A Storport.sys blue screen (or green screen on Insider builds) means Windows' storage driver lost communication with your hard drive, SSD, or RAID controller mid-operation — and in most cases, the fix has nothing to do with your drive itself. The counterintuitive part: the single most common cause isn't a failing disk at all, it's an outdated or mismatched storage driver that Windows Update itself installed, which means the "safe" automatic update that was supposed to protect your PC is very often the thing that's crashing it.

Jake nearly watched a friend buy a new PC over this one. Two blue screens a week, always storport.sys, and the verdict from the office know-it-all was already in: "storage driver crash — that SSD is dying, mate, don’t trust it with your photos." The friend had a cart open with a new drive in it when Jake asked one question: when did the crashes start? Answer: the week after a motherboard "driver booster" utility had helpfully updated the Intel storage driver. Jake rolled the driver back in Device Manager — two clicks — and the machine has not crashed in the months since. The SSD was never sick. The messenger between Windows and the SSD was. Money spent: zero.

Ethan: "Storport.sys is the warehouse foreman standing between the shop floor and the stockroom — every request for goods goes through him. When deliveries suddenly stop, everyone’s instinct is that the stockroom burned down. But walk back there and the shelves are usually fine; it’s the foreman’s paperwork that’s scrambled — a bad update, a form he can’t read. You don’t rebuild the stockroom for that. You fix the paperwork, and only if the shelves themselves creak do you start pricing new ones."

What Storport.sys actually is (and why it can take your whole PC down)

Every time Windows reads a file, saves a document, or loads a program, that request passes through a chain of drivers before it reaches your actual hard drive or SSD. Storport.sys is one of the last links in that chain — it's the driver Microsoft built specifically to talk to storage controllers, especially the higher-performance ones used by SATA, NVMe, and RAID setups. It replaced an older, slower driver (called the SCSI Port driver) years ago because it handles today's faster storage hardware more efficiently.

Because Storport.sys sits so close to the hardware and runs at the kernel level — meaning it has direct, low-level access to your system rather than running as an ordinary background app — Windows can't just quietly ignore it when something goes wrong. If Storport.sys hits an error it can't recover from, Windows has to stop everything immediately to avoid corrupting data on your drive. That's the blue screen (or, on Insider Preview builds specifically, the green screen you may remember from years past). It looks alarming, but it's Windows protecting your files, not destroying them.

The blue screen itself will usually name a stop code alongside Storport.sys, and that code narrows things down. SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED, and IRQL_NOT_LESS_OR_EQUAL most often point to a driver conflict or an outdated driver. KERNEL_DATA_INPAGE_ERROR and PAGE_FAULT_IN_NONPAGED_AREA lean more toward the drive itself — a bad sector, failing hardware, or a cable that isn't seated properly. None of these codes are a diagnosis on their own, but they tell you where to start looking, which matters because guessing wrong here just burns an evening.

First, figure out which situation you're actually in

There are really only two starting points, and they lead to different first steps.

You can still boot into Windows normally

Good — this is the easier case. Head straight to the driver-update section for your version of Windows below. You have full access to Device Manager, Command Prompt, and Windows Update, which is everything most fixes need.

Windows crashes before you reach the desktop, or won't boot at all

This is more common than you'd think with a storage-driver crash, since a bad driver can fail during the boot sequence itself, before your desktop ever loads. You'll need the Windows Recovery Environment (WinRE) to fix anything, and getting there doesn't require a working installation — it's built into every Windows 11 and Windows 10 setup and triggers automatically. Skip ahead to the section on fixing this without booting.

Fixing Storport.sys crashes on Windows 11

Step 1: Update your storage driver from the manufacturer, not just Windows Update

Open Device Manager — right-click the Start button and it's right there in the quick-access menu, or type devmgmt.msc into the Run box (Win + R, then type the command and hit Enter). Expand "Storage controllers" and, separately, "Disk drives." Right-click your controller, choose Update driver, then "Browse my computer for drivers" — but instead of letting Windows search automatically, go to your drive maker's (Samsung, WD, Crucial, Kingston) or motherboard maker's (ASUS, MSI, Gigabyte, ASRock) support page first, download their current chipset or storage driver package, and point Device Manager at that download. Manufacturer drivers are updated more often and more specifically than what Windows Update ships generically.

Step 2: If the crashes started right after an update, roll the driver back instead

Same Device Manager entry, but this time right-click, choose Properties, go to the Driver tab, and look for "Roll Back Driver." It's only available if Windows kept a copy of the previous version, which it usually does after an automatic update. This single click fixes more Storport.sys crashes than any other step on this page, specifically because it undoes the exact change that likely caused the problem.

Step 3: Run SFC and DISM to rule out corrupted system files

Right-click the Start button, choose Terminal (Admin), and run these two commands one after the other, letting each finish before starting the next:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

SFC checks Windows' own protected system files against a known-good copy and repairs anything that doesn't match. DISM does something similar but one layer deeper — it repairs the underlying Windows image that SFC's known-good copies are pulled from, which matters if SFC itself reports errors it can't fix. Run SFC again afterward to confirm it's clean. Both can take twenty minutes or more; let them finish uninterrupted.

Step 4: Uninstall a recent Windows update if the timing lines up

Settings > Windows Update > Update history > Uninstall updates. If a cumulative update installed the same day or the day before your first crash, remove it and pause updates for a week while you confirm the crashes have actually stopped, rather than assuming it worked after a single clean boot.

Fixing Storport.sys crashes on Windows 10

These steps are the same on both operating systems — the driver you're updating, the tools you run, and what they check for haven't changed. Only the paths to get there differ:

• Device Manager: right-click Start > Device Manager, or devmgmt.msc via Run, exactly as above.
• SFC and DISM: right-click Start > Command Prompt (Admin) instead of Terminal, then the same two commands.
• Update history: Settings > Update & Security > Windows Update > View update history > Uninstall updates.

If Windows won't boot at all

You don't need a working desktop to fix this, and you don't need a Windows installation USB either, though having one ready never hurts. Windows watches its own boot process, and if it fails to start cleanly three times in a row, it automatically drops you into the Windows Recovery Environment on the next attempt. To force that: turn the PC on, and the moment you see the Windows logo, hold the power button down until it shuts off completely. Repeat this two more times. On the fourth boot, Windows should show "Preparing Automatic Repair" and take you into WinRE on its own.

From inside WinRE, you have three useful paths, roughly in order of how disruptive they are:

• Startup Repair (Troubleshoot > Advanced options > Startup Repair) — Windows scans for and attempts to fix the specific thing preventing boot. Try this first; it's the least invasive option.
• Safe Mode (Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 or F4) — boots with only essential drivers loaded, which often succeeds even when a normal boot doesn't. Once inside, you can open Device Manager and roll back or uninstall the problem driver exactly as described above.
• System Restore (Troubleshoot > Advanced options > System Restore) — rolls your system files and drivers back to an earlier restore point, undoing whatever changed right before the crashes started, without touching your personal files.

If none of these work and System Restore has no points to choose from, that usually means System Protection was never turned on for that drive — a common default on new PCs. At that point, Safe Mode plus a manual driver rollback is your best remaining option before a full reset.

When it's genuinely a hardware problem, not a driver

If you've updated the driver, run SFC and DISM, and the crashes keep happening on a schedule that has nothing to do with anything you've changed, stop treating this as a software problem. Work through these in order:

Check your drive's actual health

Open PowerShell as admin and run Get-PhysicalDisk and read the HealthStatus column (the older wmic diskdrive get status command was removed from Windows 11 24H2 and later), or use a free SMART-reading tool for a fuller picture — SMART is the self-monitoring system built into virtually every hard drive and SSD, and it tracks warning signs like reallocated sectors or rising temperatures long before a drive actually fails. A drive reporting anything other than "OK" needs backing up immediately, not troubleshooting.

Reseat or replace your cables

For desktops, a loose or aging SATA cable is one of the most common and most overlooked causes of intermittent Storport.sys crashes — especially on PCs that get moved, cleaned, or had a component recently swapped. Power down, unplug, and firmly reseat both ends of every SATA and power cable connected to your drives. If a cable looks worn or has been in use for years, replace it; they're inexpensive and eliminate a whole category of guesswork.

Check for an unstable overclock

If you or a previous owner overclocked the CPU, RAM, or storage controller, an unstable profile can manifest as a Storport.sys crash under load rather than an obviously CPU-related one. Reset BIOS settings to their defaults (usually a "Load Optimized Defaults" or "Load UEFI Defaults" option) and see whether the crashes stop before you reintroduce any custom settings one at a time.

Test your RAM

Faulty memory produces a wide range of unpredictable crash signatures, including ones that point at storage drivers even though the memory is the actual cause. Search "Windows Memory Diagnostic" in the Start menu, or run mdsched.exe, and let it run overnight for the most thorough result.

Update your motherboard's BIOS/UEFI firmware

Storage controller behavior is partly governed by firmware, not just Windows drivers, and manufacturers occasionally patch BIOS-level storage bugs. Check your motherboard or laptop maker's support page for a BIOS update, and follow their instructions exactly — this is the one step here where a mistake (like losing power mid-flash) can cause a genuinely serious problem, so don't skip their specific guidance for generic advice.

RAID setups and Intel Rapid Storage Technology

If your PC uses RAID, or came from a system builder that pre-installed Intel Rapid Storage Technology (Intel RST), you're looking at a slightly different piece of the puzzle. Intel RST manages storage-controller behavior below the level of a normal driver, and a version mismatch between RST, your chipset driver, and your BIOS has a well-documented history of triggering exactly this kind of crash. Check Device Manager for "Intel Rapid Storage Technology" or a similar entry under Storage controllers, and update it from Intel's own site or your motherboard maker's support page — the same rule as everywhere else in this post, generic drivers first, manufacturer-specific ones when the generic one keeps failing.

If you're not actually running RAID and RST is installed anyway (common on pre-built desktops and some laptops), you can usually uninstall it entirely and let Windows fall back to its own native storage driver, which tends to be more stable for a plain single-drive setup. Don't do this if you are running RAID — RST is what keeps a RAID array functioning, and removing it can make your array inaccessible.

If you're on an NVMe SSD specifically (stornvme.sys)

If your crash dump or Event Viewer entry names stornvme.sys rather than storport.sys directly, that's not a different problem — stornvme.sys is Microsoft's NVMe-specific miniport driver, which sits on top of Storport the same way a SATA-specific driver would. Everything above still applies, but NVMe drives add one extra thing worth checking: drive firmware, which is separate from the Windows driver and updates through your manufacturer's own tool (Samsung Magician, WD Dashboard, Crucial Storage Executive, Kingston SSD Manager), not through Device Manager.

This isn't a theoretical suggestion. Western Digital shipped a firmware fix for specific 2TB WD and SanDisk NVMe drives after Windows 11's 24H2 update exposed an incompatibility in how those drives handled a memory-management feature, which was crashing affected systems with exactly this kind of storage error. If you're on 24H2 with a WD or SanDisk 2TB NVMe drive and started seeing crashes after updating, checking for a firmware update from WD's dashboard is worth doing before anything more involved.

One more NVMe-specific step: several independently reported fixes for stornvme.sys crashes trace back to Fast Startup, a hybrid shutdown mode that can conflict with how some NVMe controllers initialize. Turn it off via Control Panel > Power Options > Choose what the power buttons do > "Change settings that are currently unavailable" > uncheck "Turn on fast startup." It adds a few seconds to a full shutdown-and-start, but if you have an SSD as your boot drive you don't get much benefit from Fast Startup anyway.

Reading the crash details yourself (Event Viewer and minidumps)

If you want more certainty before you start changing things, Windows already logged what happened. Open Event Viewer (search for it in the Start menu, or run eventvwr.msc), navigate to Windows Logs > System, and look for a red Error entry timestamped right at your last crash. It won't always give you a plain-English answer, but it often names the specific driver file involved, which turns a guessing game into a targeted search.

For more detail than that, Windows saves a small memory dump to C:\Windows\Minidump after most crashes. Opening it requires Microsoft's free WinDbg tool (available through the Microsoft Store), and it's genuinely more technical than most people need — but if you've tried everything above and are still stuck, it's the most direct way to see exactly which driver Windows blames, rather than working through this list one guess at a time.

Cause, symptom, and fix at a glance

If you're on a laptop, not a desktop

Everything above still applies, but two of the hardware steps work differently. Most laptops built in the last several years use an NVMe SSD soldered or slotted directly to the motherboard, so "reseat the cable" isn't an option the way it is on a desktop — there usually isn't a separate cable to reseat. If you're comfortable opening the base panel and your laptop uses a removable M.2 SSD (many mainstream and gaming laptops do), reseating the drive itself in its slot is the equivalent step, and it's worth doing if the crashes started after the laptop was dropped, shipped, or had its base panel opened for any reason.

Overclocking is rare on laptops outside of a handful of gaming models, so you can usually skip that step entirely. What matters more on a laptop is thermal throttling and battery-related power delivery, since some storage controllers behave erratically when a laptop's power management aggressively throttles under low battery or poor cooling. If your crashes cluster around gaming, video export, or other sustained heavy use, check whether your laptop's fans and vents are clear of dust before chasing driver theories further.

Do you need a third-party driver-updater tool?

You'll see tools like Driver Booster or Driver Easy recommended for exactly this kind of problem, and to be fair, they do one genuinely useful thing: they scan your whole system and flag every outdated driver at once instead of you checking one at a time. For a Storport.sys crash specifically, though, you already know which single driver you need — your storage controller's — so the convenience they offer doesn't really apply here. Going directly to your drive or motherboard maker's support page gets you the same driver, usually a version newer than what a third-party scanner has indexed, without installing another background app or the free-version nag screens most of these tools ship with. Save this category of tool for a situation where you genuinely don't know which of a dozen drivers is out of date — it isn't the situation you're in right now.

Frequently asked questions

What is Storport.sys and why does it crash my PC?

Storport.sys is a Microsoft storage driver that sits between Windows and your disk controller, managing every read and write to your hard drive, SSD, NVMe drive, or RAID array. It crashes with a blue or green screen when something in that communication path fails: an outdated or corrupted storage driver, a failing drive or cable, a bad firmware update, or a conflict with a controller-management tool like Intel Rapid Storage Technology.

Is a Storport.sys error always a sign my drive is failing?

No. Most Storport.sys crashes trace back to a driver problem, not a dying drive. Software causes are more common than hardware failure. Still, check your drive's health with a SMART-reading tool early, since a failing drive is the one cause where waiting costs you data.

Can I fix a Storport.sys blue screen without being able to boot into Windows?

Yes. Force three interrupted boots in a row by holding the power button as soon as the Windows logo appears, and Windows will automatically drop you into the Windows Recovery Environment on the fourth attempt, where you can reach Safe Mode, System Restore, or Startup Repair without ever loading the desktop.

Should I update or roll back my storage driver to fix this?

Try both, in order. First update to the latest driver from your drive or motherboard maker's own support page, not Windows Update's generic version. If the crashes started right after an update, rolling back to the previous driver version through Device Manager is usually faster and just as effective.

Does Intel Rapid Storage Technology cause Storport.sys crashes?

It can. Intel RST manages RAID and some SATA/NVMe configurations and has a history of triggering Storport.sys instability when its version is mismatched with your chipset driver or BIOS. If you are not running RAID, you can usually uninstall it and let Windows use its native storage driver instead.

What does it mean if the crash keeps happening after I update every driver?

Repeated crashes after a clean driver update point away from software and toward hardware: a failing drive, a loose or damaged SATA/power cable, an unstable overclock, or a motherboard storage controller issue. At that point, run a SMART health check and reseat your cables before spending more time on software fixes.

Is Storport.sys the same on Windows 11 and Windows 10?

Yes, the driver's job is identical on both. The difference is where you go to fix it: Windows 11 moved driver updates, recovery, and troubleshooters into a reorganized Settings app, while Windows 10 keeps them under Update & Security. The underlying causes and fixes are the same on both.

Will resetting Windows fix a Storport.sys BSOD?

Usually, but it is a last resort, not a first step. A reset clears out corrupted drivers and system files that survive an SFC or DISM scan, but it also removes your installed programs. Try driver updates, SFC/DISM, and a hardware check first; keep Reset this PC for when nothing else stops the crashes.

What do I do if System Restore itself fails or has no restore points?

Skip straight to driver-level fixes: boot into Safe Mode, roll back or reinstall your storage driver from Device Manager, and run SFC and DISM. If Windows won't boot into Safe Mode either, use Startup Repair from the Windows Recovery Environment instead.

Can a Windows Update cause a Storport.sys crash?

Yes. Some cumulative and driver updates have shipped with storage-driver regressions that trigger Storport.sys crashes on specific chipsets, and this has happened on both Windows 10 and Windows 11 in the past. If the crashes started right after a Patch Tuesday update, uninstalling that specific update from Update history is a reasonable first move.

How do I know which driver actually caused the crash?

Open Event Viewer, go to Windows Logs > System, and look for a red Error entry logged at the exact time of your last crash, usually from source BugCheck or a specific driver name. If you're comfortable with more detail, the memory dump saved in C:\Windows\Minidump can be opened with Microsoft's free WinDbg tool, which usually names the exact faulting driver.

Is it safe to keep using my PC if this only happens occasionally?

An occasional Storport.sys crash is annoying but not automatically dangerous, as long as you save your work often and back up regularly. What is not safe is ignoring a pattern where crashes are getting more frequent, since that pattern is more consistent with a drive that is failing than with a one-off driver glitch.

Do I need to reinstall Windows if nothing else fixes the crash?

Only after you've ruled out drivers, corrupted system files, and hardware. A clean reinstall resolves crashes caused by deep software corruption that SFC, DISM, and driver reinstalls can't reach, but if the real cause is a failing drive or loose cable, reinstalling Windows will not stop the crashes.

What is stornvme.sys, and is it different from storport.sys?

Stornvme.sys is Microsoft's NVMe-specific miniport driver, which works on top of Storport the same way a SATA-specific driver would. If your crash log names stornvme.sys instead of storport.sys, the underlying troubleshooting is the same, with one addition: check for an NVMe drive firmware update from your manufacturer's own tool, since firmware bugs on NVMe drives have caused real, documented crashes after specific Windows feature updates.

Does a Storport.sys crash delete or corrupt my files?

The crash itself almost never touches your files — the blue screen exists precisely so Windows can halt before writing bad data. The real risk sits in the rare case where the cause is a genuinely failing drive, which is why this guide keeps repeating the same unglamorous advice: check SMART health early, back up first, then troubleshoot with nothing at stake.

Can a loose SATA cable really cause Storport.sys blue screens?

Yes — an intermittent data cable produces exactly the lost-communication timeouts Storport reports, and it’s the cheapest fix on this entire page. On a desktop, reseat or swap the SATA cable and try a different motherboard port; five minutes, and one whole category of causes is ruled out for good.

Keeping it from coming back

Once you've found and fixed the actual cause, a short list of habits keeps this from being a repeat visit to this page. Keep an eye on your drive's SMART status every few months rather than only after a crash — most manufacturer tools (Samsung Magician, WD Dashboard, Crucial Storage Executive) show this at a glance. Hold off installing brand-new Windows updates for a few days when you can, since driver regressions are usually caught and fixed within the first week. And if you're the kind of person who overclocks, keep a note of what you changed and when, since it's the single easiest thing to forget when you're troubleshooting a crash three weeks later.

An external backup remains the one thing that turns any of these causes from a crisis into an inconvenience. Whether the crashes end up being a driver, a cable, or a genuinely failing drive, having your files copied somewhere else means the worst-case outcome is buying a new drive, not losing years of photos and documents.

Revision note. Originally published January 20, 2017, when this page covered a specific, temporary bug in Windows 10 Insider Preview build 15014 that produced a green-screen Storport.sys rollback during upgrade. That build and its bug are long gone — the Insider Program itself has since been restructured more than once — so this page has been rewritten for the question that actually brings people here today: a genuine Storport.sys crash on a normal Windows 11 or Windows 10 PC. If you found your way here at 11pm with a blue screen staring back at you, we hope one of the steps above gets you back to a working machine tonight.