Blue Screen Storage Error Codes WHEA and INACCESSIBLE BOOT DEVICE Diagnosis
Not every blue screen is a storage problem - but a handful of stop codes speak directly about your drive, its cable, or its controller settings. Reading them properly saves you from reinstalling Windows for a hardware fault, or replacing a drive for a settings change.
A blue screen shows a stop code for a few seconds, and that code is evidence — if you know its language. Three codes concern this page: WHEA_UNCORRECTABLE_ERROR, INACCESSIBLE_BOOT_DEVICE and KERNEL_DATA_INPAGE_ERROR (plus its cousin CRITICAL_PROCESS_DIED). Each has a distinct personality: one says 'hardware reported a fault', one says 'Windows lost sight of its own boot drive', and one says 'data the kernel needed could not be read from disk'. Here is how to decode yours and what to check, in order.
👆 The three stop codes that belong in a storage investigation — plus where their paper trail lives after the reboot.
WHEA_UNCORRECTABLE_ERROR — Hardware Is Reporting the Fault
- WHEA is Windows' hardware error architecture: this code means a component — CPU, RAM, motherboard, or a PCIe/storage device — reported a fault it could not correct. It is not a software bug code
- Find the paper trail: Event Viewer → Windows Logs → System, source WHEA-Logger, Event ID 18 (fatal) or 19 (corrected). The details name the component class involved
- If WHEA errors began alongside drive symptoms (freezes, Event 129/153, slow reads), the storage device or its slot/controller is a prime suspect — test the drive in another PC to isolate it
- Honest scope note: WHEA errors also come from failing RAM, overheating or unstable overclocks, and a CPU undervolt gone wrong. If storage checks come back clean, the investigation moves to memory and thermals — do not replace a healthy drive on WHEA alone
INACCESSIBLE_BOOT_DEVICE — Windows Lost Its Own Drive
- This code (0x7B) appears during boot: Windows loaded, then could no longer see or read the drive it booted from
- Most common cause is a settings change, not death: someone switched the SATA mode in BIOS between RAID/IDE and AHCI, a BIOS update reset it, or Windows Update changed the storage driver. If the timing matches ("it broke right after I changed a BIOS setting / updated"), restore the original SATA mode first — this fixes a large share of cases instantly
- Check detection: enter BIOS and confirm the drive is listed at all. Not listed → reseat/replace the cable, try another port; still not listed in two machines → the drive has failed electronically
- Listed but still 0x7B: boot a WinPE/recovery USB, run the SMART health check from there, and inspect the drive's contents. A drive that reads fine from WinPE but blue-screens its own Windows points back to drivers/settings, not hardware
KERNEL_DATA_INPAGE_ERROR — The Disk Could Not Deliver
- Code 0x7A: the kernel needed data from the page file (or a memory-mapped file) and the read failed. The second parameter on the blue screen often narrows it — an I/O status like 0xC000009C means a bad block was hit; 0xC0000185 means a cabling/termination or controller problem
- This is one of the strongest blue-screen pointers at a failing drive or its connection. The diagnosis order: back up data if the PC still boots at all, then SMART check, then Event Viewer for disk IDs 7/51/153, then cable and port swap
- Its cousin CRITICAL_PROCESS_DIED can appear when a critical system process cannot read its files from a failing disk — same storage check order applies before blaming Windows
- Also recreate the page file once storage health is proven (System Properties → Advanced → Performance → Virtual memory) — a page file sitting on damaged sectors manufactures this error even after other fixes
The Check Order That Settles It
- Note the exact code (phone photo of the blue screen) and what changed recently — BIOS settings, updates, new hardware
- Is the drive visible in BIOS? No → physical path: cable, port, another PC
- Boot WinPE/USB and run SMART + browse the drive. Healthy and readable → settings/drivers (SATA mode, storage driver rollback). Caution/Bad or unreadable → rescue data, replace drive
- Read the System log for WHEA-Logger 18s and disk 7/51/129/153 around the crash times — logs turn a guess into a pattern
This is one branch of the full diagnosis in the video above — start there if your PC shows a mixture of symptoms.
🎥 Watch the Complete Process in the Video
Watch the video for the complete method - separating Windows faults from drive faults before you lose data or time.
▶️ Watch Full VideoMy blue screen shows a different code every time. What does that mean?
Random, changing stop codes usually mean the corruption is happening at a low level - data being damaged on its way through the system. The main suspects are failing RAM, a dying drive corrupting different system files on different days, or an unstable overclock. Test in this order: drive health (SMART and event log), then RAM (MemTest86 overnight), then remove overclocks. A single repeated code is a clue; a lottery of codes is a symptom of bad data itself.
INACCESSIBLE BOOT DEVICE appeared right after a Windows update. Is my drive dead?
Probably not - that timing strongly suggests the update changed the storage driver or the boot configuration rather than the hardware dying overnight. First check the BIOS SATA mode has not reset (RAID vs AHCI). Then use recovery options: boot into the Windows Recovery Environment and try Startup Repair, or roll back the update from there. Only if the drive is also invisible in BIOS or fails SMART checks from a WinPE boot should you treat it as hardware.
Where can I find the stop code after the PC has already restarted?
Event Viewer keeps it. In Windows Logs - System, look for source BugCheck, Event ID 1001, which records the stop code and parameters, and WHEA-Logger ID 18 if hardware reported the fault. The minidump files in C:\Windows\Minidump hold the full crash records that tools like BlueScreenView can summarise - but the event log entries alone are usually enough to start the storage checks in this guide.