Most guides for the kernel data inpage error on Windows 11 give you the same recycled list of steps that may or may not apply to your situation. Here's what actually matters: this BSOD has a handful of distinct causes, and the fix depends entirely on which one you've got. Run the wrong fix first and you'll waste an hour. This guide tells you how to identify your cause fast and go straight to the solution that works.
TL;DR
The kernel data inpage error BSOD on Windows 11 is most commonly caused by file system corruption, a known firmware bug in certain 2TB WD and SanDisk NVMe SSDs on Windows 11 24H2, faulty RAM, or outdated storage drivers. Run CHKDSK first (fixes 70 to 80% of cases), then check Event Viewer for stornvme errors. If you have an affected SSD, a firmware update from the manufacturer fixes it with a 95%+ success rate.
Key Takeaways
- The kernel data inpage error means Windows failed to read data from storage into RAM.
- Windows 11 24H2 has a documented bug with 2TB WD and SanDisk NVMe SSDs. A firmware update fixes it permanently.
- CHKDSK and SFC scans resolve file system corruption in most cases without reinstalling Windows.
- Check Event Viewer for stornvme Event ID 11 errors after each crash. That's your fastest diagnostic shortcut.
- Faulty RAM is a less common but often overlooked cause. Always run Windows Memory Diagnostic if CHKDSK comes back clean.
At a Glance
- Difficulty: Intermediate
- Time Required: 30 to 90 mins depending on cause
- Success Rate: Up to 95% with correct fix applied
What Causes the Kernel Data Inpage Error on Windows 11?
The kernel data inpage error is Windows telling you it tried to read a page of data from disk into memory and failed. That's the short version. The longer version is that this failure can happen for several different reasons, and they're not all equally likely.
The single biggest cause right now, in 2026, is a firmware incompatibility introduced with Windows 11 version 24H2. When 24H2 boots, it requests a larger Host Memory Buffer (HMB) allocation from NVMe SSDs. Certain 2TB WD and SanDisk drives can't handle that request reliably. The drive controller throws errors, Windows panics, and you get the blue screen. If this is your situation, you'll see Event ID 11 from source 'stornvme' in Event Viewer every time it happens. That's your smoking gun.
File system corruption is the second most common cause. This happens when Windows doesn't shut down cleanly, whether from a power cut, a forced restart, or a previous BSOD. The file system metadata gets out of sync and Windows can't reliably read certain files. CHKDSK is built exactly for this and it works well.
Faulty RAM is less common but genuinely nasty because it's intermittent. If your memory module has a bad cell, data paging fails unpredictably. You might go days without a crash, then get three in one afternoon. Windows Memory Diagnostic catches most RAM faults, though for serious cases you'd want to run MemTest86 overnight.
Outdated or corrupted storage controller drivers, particularly NVMe controller drivers, are another trigger. Device Manager sometimes shows these as up to date when they're actually behind. Always check the motherboard manufacturer's website directly rather than relying on Windows Update for chipset and storage drivers. And then there's the catch-all category: third-party software with kernel-mode drivers. Antivirus tools, VPN clients, and disk utilities all run at a low level and can destabilise the storage subsystem if they're buggy or incompatible with your current Windows build. Similar instability issues can appear in other forms too, like the ASUS ROG G513RC BSOD at idle which often traces back to driver conflicts as well.
Kernel Data Inpage Error Quick Fix: CHKDSK and System File Repair
Start here. This fixes the majority of kernel data inpage error cases and it costs you nothing but time. The process runs two scans: CHKDSK checks the disk itself for bad sectors and file system errors, and SFC checks Windows system files for corruption. Run them in sequence.
CHKDSK and SFC Scan Easy
- Open Command Prompt as administrator
Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin). Click Yes on the UAC prompt. - Schedule a CHKDSK scan
Typechkdsk /F /Rand press Enter. When asked if you want to schedule the scan for next restart, typeYand press Enter. - Restart and let it run
Close everything and restart. CHKDSK runs before Windows loads. Don't touch the machine until it's done. On a 500GB drive this takes roughly 10 to 20 minutes. Larger drives take longer. Do not power off mid-scan. - Run SFC after Windows boots
Open Command Prompt as administrator again. Typesfc /scannowand press Enter. Wait for it to finish (15 to 30 minutes on slower systems). - Run DISM to repair the Windows image
In the same Command Prompt window, typeDISM /Online /Cleanup-Image /RestoreHealthand press Enter. This pulls clean files from Windows Update to replace anything corrupted. - Restart and monitor
Restart the machine. Use it normally for a day. If the kernel data inpage error doesn't come back, you're sorted.
One thing worth knowing: if SFC comes back with 'Windows Resource Protection could not perform the requested operation', run the DISM command first, then re-run SFC. DISM repairs the repair tool, essentially. Took me three reboots on one client machine before this sequence finally stuck, but it did stick.
Kernel Data Inpage Error Fix for WD and SanDisk SSD Users
If you have a 2TB WD or SanDisk NVMe SSD and you're running Windows 11 24H2, there's a very specific fix for your situation and it has a 95%+ success rate. This is the one most generic guides miss entirely.
Here's how to confirm you're affected before you do anything else. Press Windows + X, open Event Viewer, go to Windows Logs > System, and look for Event ID 11 from the source 'stornvme'. The description will mention controller errors on something like '\Device\RaidPort1'. If you see that, the HMB allocation conflict is your problem. The firmware on your drive can't handle the buffer size Windows 11 24H2 requests, so the controller fails and Windows crashes.
SSD Firmware Update (WD / SanDisk 2TB NVMe) Advanced
- Confirm your SSD model
Right-click Start > Device Manager. Expand Disk drives. Check if you have a 2TB WD or SanDisk NVMe SSD listed. It must be internally installed (M.2 slot or internal PCIe adapter). External USB drives cannot be updated this way. - Check Event Viewer for stornvme errors
Press Windows + X > Event Viewer > Windows Logs > System. Filter for Event ID 11, source 'stornvme'. Confirm the HMB controller error is present. - Back up your data first
Copy anything important to an external drive or cloud storage. Firmware updates rarely cause data loss, but this is not the time to find out the hard way. - Download the firmware update tool
Go to the Western Digital support downloads page (or the SanDisk equivalent). Find your specific SSD model and download the firmware update utility for Windows. - Run the updater as administrator
Right-click the downloaded tool and select Run as administrator. Follow the on-screen steps carefully. Do not close the tool, restart the machine, or let the laptop battery die during this process. The update takes a few minutes. - Restart and verify
After the firmware update completes, restart. Monitor for 24 to 48 hours. Check Event Viewer again for stornvme errors. They should be gone.
More Kernel Data Inpage Error Solutions: RAM, Drivers, and Software Conflicts
If CHKDSK came back clean and you don't have an affected WD/SanDisk SSD, the next things to check are your RAM, your storage drivers, and whether a third-party application is causing trouble. These three are separate issues but they're worth working through in order because the RAM check comes first (it's quick and binary) and Clean Boot comes last (it takes longer).
Test RAM with Windows Memory Diagnostic Easy
- Open Windows Memory Diagnostic
Press the Windows key, type Windows Memory Diagnostic, and press Enter. Select Restart now and check for problems. Save any open work first. - Wait for the test to complete
The machine restarts and runs the memory test automatically. It takes roughly 10 to 20 minutes. You'll see a progress bar. Don't interrupt it. - Check results in Event Viewer
After Windows boots, press Windows + X > Event Viewer > Windows Logs > System. Look for 'MemoryDiagnostics-Results'. If it reports errors, your RAM module is faulty and needs replacing.
Update Storage Controller Drivers Intermediate
- Open Device Manager
Right-click Start > Device Manager. Expand Storage controllers and Disk drives. - Update each storage device driver
Right-click each device listed and select Update driver > Search automatically for drivers. Do this for all entries under Storage controllers. - Check the motherboard manufacturer's site
Windows Update doesn't always have the latest chipset and NVMe drivers. Go to your motherboard manufacturer's support page directly (ASUS, MSI, Gigabyte, etc.) and download the latest chipset and storage drivers for your board model. Install them and restart.
Clean Boot to Isolate Software Conflicts Intermediate
- Open System Configuration
Press Windows + R, typemsconfig, press Enter. Go to the Services tab. - Disable all non-Microsoft services
Check Hide all Microsoft services at the bottom, then click Disable all. This leaves Windows services running but disables everything third-party. - Disable startup apps
Go to the Startup tab and click Open Task Manager. Disable every startup item listed. Close Task Manager, click OK in msconfig, and restart. - Monitor for BSOD
Use the machine normally for several hours in this Clean Boot state. If the kernel data inpage error doesn't appear, a third-party service or app is the cause. - Re-enable services one by one
Go back into msconfig and re-enable services in small groups, restarting after each batch. When the BSOD returns, the last group you enabled contains the culprit. Narrow it down from there. - Return to normal startup
Once you've identified and removed or updated the problematic software, open msconfig, select Normal startup, and restart.
If you've been through all of the above and the crashes keep coming, there's a real chance your storage device is physically failing. Run the manufacturer's own diagnostic tool (WD Data Lifeguard, Samsung Magician, CrystalDiskInfo for third-party drives) and check the S.M.A.R.T. data. Reallocated sector counts climbing over time is a bad sign. At that point you're looking at a drive replacement, not a software fix. And if you've ever had a situation where Windows factory reset stops working mid-process, a dying drive is often the reason for that too.
One more thing. If you're seeing the kernel data inpage error alongside other odd Windows behaviour like copy and paste not working or random freezes, that points more strongly toward file system corruption or RAM issues rather than the SSD firmware bug. The firmware bug tends to produce clean crashes with consistent stornvme errors, not general system weirdness.
Preventing the Kernel Data Inpage Error Coming Back
Once you've fixed it, here's how to keep it fixed. The most important thing is staying on top of Windows updates and driver updates, particularly for storage. Microsoft patches known compatibility issues through Windows Update, and the WD/SanDisk HMB bug is a good example of what happens when firmware and OS updates fall out of sync.
Keep at least 10 to 15% free space on your system drive. A nearly full drive causes all sorts of file system stress and makes corruption more likely. Run CHKDSK every month or two as routine maintenance. You can schedule it in Task Scheduler so it runs during a quiet period without interrupting your work.
Shut down properly. Holding the power button to force-off a frozen machine is sometimes unavoidable, but it's one of the most reliable ways to corrupt a file system. If Windows is frozen, give it two or three minutes before reaching for the power button. And if your machine is running hot, sort the cooling out. Overheating storage and RAM both cause intermittent read errors that eventually show up as kernel data inpage error crashes. Clean the vents, check the thermal paste on older machines, and make sure the fans are actually spinning.
Finally, keep backups. Not because the kernel data inpage error itself destroys data (it mostly doesn't), but because the underlying causes, particularly a failing drive, absolutely can. An external drive or a cloud backup service like OneDrive is fine. Speaking of which, if you're using OneDrive and noticing OneDrive sync issues on Windows, that can sometimes be an early sign of file system problems worth investigating before they escalate to a BSOD.
Kernel Data Inpage Error on Windows 11: Summary
The kernel data inpage error BSOD on Windows 11 is fixable in the vast majority of cases without reinstalling Windows. Start with CHKDSK and SFC. If you have a 2TB WD or SanDisk NVMe SSD on Windows 11 24H2, check Event Viewer for stornvme errors and update the firmware. If those don't apply, test your RAM, update your storage drivers, and do a Clean Boot to rule out software conflicts. Work through the causes in order and you'll find it. The kernel data inpage error looks alarming, but it's usually telling you something specific and fixable.
