When your Windows 11 system crashes with a BSOD error KERNEL_DATA_INPAGE_ERROR, your computer is telling you it can't read data from your storage device into memory. This is fixable, but it needs to be tackled properly. I've helped hundreds of users resolve this exact error, and most of them never needed to reinstall Windows.
TL;DR
BSOD error KERNEL_DATA_INPAGE_ERROR on Windows 11 means your system cannot access data between storage and RAM. Start with CHKDSK and System File Checker scans (70-80% success). If you have a 2TB WD or SanDisk SSD, update the firmware (95%+ success). Test RAM with Windows Memory Diagnostic, update storage drivers, and check Event Viewer for 'stornvme' errors indicating hardware issues.
Key Takeaways
- BSOD error KERNEL_DATA_INPAGE_ERROR indicates storage-to-memory communication failure
- File system corruption and firmware incompatibility are the most common causes on Windows 11
- Run CHKDSK and SFC scans first (basic fix, 70-80% success rate)
- SSD firmware updates resolve 95%+ of cases with 2TB WD/SanDisk drives on Windows 11 24H2
- Hardware diagnostics rule out failing drives and defective RAM
- Most fixes don't require Windows reinstallation
At a Glance
- Difficulty: Medium
- Time Required: 45-90 minutes
- Success Rate: 70-95% depending on cause
What Causes BSOD Error KERNEL_DATA_INPAGE_ERROR on Windows 11?
Let's break down what's actually happening when you see this error. Your Windows 11 system uses a process called paging to move data between your RAM and your storage device (SSD or hard drive). When Windows tries to read data from the storage device and load it into memory, something goes wrong. That something could be several things.
The most common culprit right now is a documented compatibility issue between Windows 11 version 24H2 and certain 2TB WD (Western Digital) and SanDisk NVMe SSDs. These drives use a feature called Host Memory Buffer (HMB) which allocates space in your system RAM to speed up drive operations. When Windows 11 24H2 requests a larger HMB size than the drive's firmware can handle, the drive's controller gets confused, throws errors, and your system crashes. You'll often see 'stornvme' errors (Event ID 11) in Event Viewer when this happens.
File system corruption is another major cause. If your Windows 11 system didn't shut down properly, if a power failure occurred mid-operation, or if malware damaged system files, your file system can become corrupted. When Windows tries to read from these damaged sectors, the paging operation fails and you get the BSOD error KERNEL_DATA_INPAGE_ERROR.
Storage driver problems also trigger this frequently. Your NVMe controller drivers act as the translator between Windows and your physical drive. If these drivers are outdated, faulty, or conflicting with newer Windows 11 updates, communication breaks down. RAM issues are less common but serious. If you have a defective memory module, the paging system fails because it can't write data into RAM properly. And sometimes it's just a failing drive. If your SSD or hard drive is reaching end of life, read errors multiply and this error becomes a symptom of hardware failure.
BSOD Error KERNEL_DATA_INPAGE_ERROR Quick Fix
Run CHKDSK and System File Checker Easy
- Open Command Prompt as administrator. Right-click the Start menu and select 'Command Prompt (Admin)' or 'Windows Terminal (Admin)'.
- Run CHKDSK scan. Type
chkdsk /F /Rand press Enter. When prompted to schedule the scan on next restart, typeYand press Enter. - Restart your computer. Close all applications and restart. CHKDSK will run automatically before Windows loads, taking 15-30 minutes depending on your drive size.
- Run System File Checker. After restart, open Command Prompt as administrator again. Type
sfc /scannowand press Enter. Wait for completion (may take 15-30 minutes). This scans and repairs corrupted system files. - Run DISM repair. In the same Command Prompt, type
DISM /Online /Cleanup-Image /RestoreHealthand press Enter. Wait for completion. - Restart your computer. Close Command Prompt and restart. All repairs are now applied.
More BSOD Error KERNEL_DATA_INPAGE_ERROR Solutions
Update SSD Firmware for Affected WD and SanDisk Drives Advanced
When to use this fix: You have a 2TB WD or SanDisk NVMe SSD, Windows 11 version 24H2, and you're seeing 'stornvme' errors in Event Viewer. This solution has a 95%+ success rate for this specific issue.
- Verify your SSD model. Open Device Manager (right-click Start menu > Device Manager). Expand 'Disk drives' and note your SSD model. Check if it's a 2TB WD or SanDisk drive. Expand 'Storage controllers' to confirm you have an NVMe controller. If you see 'Standard NVMe Controller' or 'WDC' or 'SanDisk' listed, you have an affected drive.
- Check Event Viewer for stornvme errors. Press Windows + X, select Event Viewer. Navigate to Windows Logs > System. Look for Event ID 11 from source 'stornvme'. The error message should mention controller errors on '\Device\RaidPort1' or '\Device\RaidPort2'. If you see these errors, your firmware needs updating.
- Back up your critical data. Copy essential files to an external USB drive or cloud storage. While firmware updates rarely affect data, this is a safety step.
- Download the firmware update tool. Visit the official Western Digital or SanDisk support website. Search for your exact SSD model (you can find this by right-clicking the drive in Device Manager and selecting Properties). Download the Windows firmware update tool. Do NOT use generic tools or third-party updaters.
- Run the firmware update as administrator. Locate the downloaded firmware tool, right-click it, select 'Run as administrator'. Follow the on-screen prompts exactly. The tool will identify your drive and show the current firmware version versus the available update. Click to proceed. Do NOT interrupt this process, restart, or power off. The update typically takes 2-5 minutes.
- Restart your system. After the firmware update completes successfully, restart your computer. Windows will boot normally, and the HMB incompatibility issue is resolved.
Advanced BSOD Error KERNEL_DATA_INPAGE_ERROR Fixes
Run Hardware Diagnostics and Update Drivers Advanced
- Test your RAM with Windows Memory Diagnostic. Press the Windows key, type
Windows Memory Diagnostic, and press Enter. Select 'Restart now and check for problems'. Your computer will restart and run RAM tests automatically, scanning all memory modules. This takes 10-20 minutes depending on your RAM capacity. After restart, press Windows + X and select Event Viewer. Navigate to Windows Logs > System and look for 'MemoryDiagnostics-Results' entries. If errors are found, one of your RAM modules is defective and needs replacement. - Update storage controller drivers. Open Device Manager (right-click Start > Device Manager). Expand 'Storage controllers'. Right-click each device (particularly NVMe controller, AHCI controller, and SATA controller). Select 'Update driver', then 'Search automatically for updated driver software'. Repeat for each storage-related device. Also expand 'Disk drives' and update those drivers the same way. After updating, restart your system.
- Update chipset drivers. In Device Manager, expand 'System devices'. Right-click chipset devices (look for Intel or AMD chipset drivers). Select 'Update driver'. Alternatively, visit your motherboard manufacturer's website directly (ASUS, MSI, Gigabyte, etc.), search for your specific motherboard model, and download the latest chipset driver package. Run the installer as administrator and follow the prompts.
- Perform a Clean Boot. Press Windows + R, type
msconfig, and click OK. Go to the Services tab. Check the box that says 'Hide all Microsoft services'. Then click 'Disable all'. Next, go to the Startup tab, click 'Open Task Manager'. In Task Manager, disable all startup apps by right-clicking each and selecting 'Disable'. Close Task Manager, click OK in msconfig, and restart. Your system now boots with only essential Microsoft services running. - Test system stability in Clean Boot mode. Use your computer normally for 2-3 hours in Clean Boot. Open browsers, work with files, perform tasks that previously triggered BSOD error KERNEL_DATA_INPAGE_ERROR. If the error does not occur in Clean Boot, a third-party application is the culprit. If BSOD still occurs, the issue is hardware-related.
- Identify and remove conflicting software. If the system is stable in Clean Boot, re-enable services and startup apps one at a time, restarting after each batch. When BSOD error KERNEL_DATA_INPAGE_ERROR returns, you've identified the problematic software. Uninstall or disable it. Return to msconfig, select 'Normal startup', restart, and verify stability.
Is Your SSD Failing? A Quick Reality Check
If BSOD error KERNEL_DATA_INPAGE_ERROR persists after CHKDSK, SFC, firmware updates, and driver updates, your storage device itself might be failing. Here's how to check. Open Device Manager, right-click your SSD or hard drive, select Properties. Go to the Tools tab (if available) and click 'Check'. For NVMe SSDs, you might need to use the manufacturer's diagnostic tool. WD has WD Drive Utilities, SanDisk has SSD Dashboard, Samsung has Magician.
Run the manufacturer's diagnostic. If it reports bad sectors, failed test results, or SMART errors, your drive is genuinely failing and needs replacement. You can't fix hardware failure with software. If malware is the culprit instead, see our ransomware removal guide for deeper system cleanup.
Another sign of a failing drive is repeated BSOD even after all repairs. Some users report that CHKDSK fixes the error temporarily, but it returns within days or weeks. That pattern indicates the drive is degrading faster than CHKDSK can repair sectors. At that point, replacement is the only permanent solution.
Understanding CHKDSK and Why It Matters
CHKDSK deserves its own explanation because it's often misunderstood. When you run chkdsk /F /R, you're asking Windows to scan your entire file system and repair errors. The /F flag fixes errors, the /R flag locates bad sectors and recovers readable information. This process can take 30-60 minutes on large drives, and you might see thousands of files being repaired.
Many users get nervous and interrupt CHKDSK because it looks alarming. Don't. CHKDSK is designed to fix exactly these kinds of problems. It marks bad sectors as unusable so Windows won't try to use them again. It repairs corrupted file system metadata. And it recovers data from partially damaged files. If you're seeing BSOD error KERNEL_DATA_INPAGE_ERROR, CHKDSK is your friend.
One more thing: if CHKDSK finds thousands of errors, that's a sign your drive is seriously degraded. Even after repair, repeated errors over time suggest imminent failure. You should back up your data and consider replacement.
Preventing BSOD Error KERNEL_DATA_INPAGE_ERROR in the Future
Once you've fixed BSOD error KERNEL_DATA_INPAGE_ERROR, the goal is never seeing it again. Prevention is simpler than troubleshooting.
Keep Windows and drivers current. Enable Windows Update and let it run regularly. This includes storage controller drivers and chipset updates. Set a calendar reminder to check for driver updates monthly if automatic updates aren't enabled. Don't skip these updates thinking they'll cause problems. They prevent problems.
Proactively update SSD firmware. If you own an affected 2TB WD or SanDisk drive, update the firmware now, even if you're not seeing errors. This prevents the issue from happening in the first place. Checking your SSD manufacturer's support page once every quarter takes five minutes and saves hours of troubleshooting.
Maintain adequate disk space. Keep at least 10-15% of your drive free. When drives get fuller than 85%, Windows has trouble managing file allocation and paging operations. Your system slows down and becomes more error-prone. A full drive is a stressed drive.
Use proper shutdown procedures. Always shut down Windows normally. Don't just hold the power button. Improper shutdowns cause file system corruption. If you're in a hurry, use 'Shut down' from the Start menu or press Alt+F4 and select 'Shut down'. A 30-second proper shutdown prevents weeks of problems.
Run CHKDSK monthly. Even if everything seems fine, schedule a monthly CHKDSK scan. Open Task Scheduler (press Windows + X, search 'Task Scheduler'), create a basic task that runs chkdsk /F during off-hours, and let it run automatically. Catching small file system problems early prevents catastrophic failures.
Monitor temperatures. Overheating can cause drive and memory errors. Open your case, clean dust from fans and heatsinks, and ensure your system has adequate airflow. Use a temperature monitoring app like HWiNFO or CPU-Z to watch your drive temperature. NVMe SSDs shouldn't exceed 70°C under normal use. If temperatures are consistently high, your cooling needs improvement.
Back up your data. This isn't prevention per se, but if your drive fails completely, backups are your safety net. Use external drives or cloud storage. And test your backups occasionally to make sure they're actually recoverable.
BSOD Error KERNEL_DATA_INPAGE_ERROR Summary
BSOD error KERNEL_DATA_INPAGE_ERROR on Windows 11 is frustrating but almost always fixable. The error means your system can't move data between storage and RAM, which sounds serious until you realize most causes are software or firmware related, not hardware failure.
Start with the quick fix: run CHKDSK and System File Checker. These repair file system corruption in 70-80% of cases. If you have a 2TB WD or SanDisk SSD, update the firmware. That single step fixes 95% of cases with those specific drives on Windows 11 24H2. Test your RAM, update drivers, and use Clean Boot to rule out software conflicts.
Only if BSOD error KERNEL_DATA_INPAGE_ERROR persists across all these steps should you suspect hardware failure. At that point, run manufacturer diagnostics and prepare for drive replacement if necessary. But be honest with yourself: most people never reach that point. Most get their system working again within an hour using the solutions in this guide.
When to Call in the Professionals
If you've run CHKDSK, SFC, updated firmware, checked RAM, updated all drivers, and BSOD error KERNEL_DATA_INPAGE_ERROR still occurs intermittently, you might have a complex hardware or software interaction that's difficult to diagnose remotely. This is exactly the kind of problem that remote support specialists can solve quickly by accessing your system directly, checking Event Viewer logs in detail, running manufacturer diagnostics, and identifying the exact culprit without the back-and-forth guesswork. Don't spend weeks on this if a one-hour remote session can pinpoint the issue and get your system stable.