0x00000077 KERNEL_STACK_INPAGE_ERROR fixes and checks
0x00000077 is KERNEL_STACK_INPAGE_ERROR. The fix path is to split storage, cabling, RAM, and driver-stack faults by testing disk health first, then SATA/NVMe power and data paths, then memory, then drivers; printer error hits are unrelated. Guess wrong and you can swap the wrong part, keep losing boots, and miss a failing drive before data is gone. I use a Windows 11 diagnosis path, the tests to run, and the order that saves time.
What 0x00000077 means
Bug Check 0x77 means Windows tried to read a requested page of kernel data from the paging file and could not get it into memory, per Microsoft support. On a live BSOD, that usually points to a storage read problem, a bad path to the drive, a memory fault, or a storage driver that returned a misleading result. (Microsoft Learn)
Read the four bug check parameters first. They tell you whether to start with disk surface checks, cable and controller checks, RAM testing, or driver-stack work. That is faster than guessing from the stop code alone.
not the printer error
Search results also show a printer-related 0x00000077 page. That one describes a broken pipe and applies to Windows 11 and Windows 10 22H2, which is a different problem entirely. This BSOD is about the paging file and kernel data, not a print job. (howfixes.com)
How do the four parameters point to the cause?
The first parameter is the best place to start. It can be an NTSTATUS code, or it can be one of the special values Microsoft uses to flag where the read failed. The second parameter is often the I/O status code. The third often shows the paging-file offset or a related address, and the fourth can help identify the failing path when the first three are ambiguous.
Use the parameters to separate hardware from software. A bad disk sector, loose cable, or missing drive usually leaves a different fingerprint than a driver stack that reported success before the page was actually read.
| Parameter pattern | Likely root cause | First checks | Escalation |
|---|---|---|---|
| Parameter 1 = 0 or 1 | Defective hardware, often RAM; the stack signature was not found (per Microsoft support) | Run Windows Memory Diagnostic or the drive or memory maker’s diagnostic tool. | Reseat or replace memory, then retest the boot path |
| Parameter 1 = 2 | Driver stack returned SUCCESS without reading the whole page | Inspect storage and chipset drivers in Device Manager | Rollback or update the storage driver, then test under a clean boot |
Parameter 1 = 0xC000009C or 0xC000016A | Bad blocks or sectors on the hard disk | Run chkdsk /f /r on the system partition | Back up data, then test the drive in another system or replace it |
Parameter 1 = 0xC000009D or 0xC0000185 | Loose or defective cabling, disconnected drive, or bad SCSI termination | Inspect data and power connections; check the port and seating | Move the drive to another cable, port, or controller path |
| Parameter 1 is another NTSTATUS value | Driver-stack failure or storage-stack error | Check Event Viewer and storage logs for the failing device | Update, roll back, or remove the storage/controller driver |
Likely causes, ranked
Most often, the problem is storage hardware or the path to it. Less often, the drive is fine and the memory subsystem or storage driver breaks the read. Malware is possible, but it should stay lower on the list unless the system also shows other corruption signs.
Storage drive errors and bad sectors
Bad sectors and read failures are the first thing to test when the status code points to the disk. 0xC000009C and 0xC000016A both point to bad blocks on the hard disk. That makes the drive itself a prime suspect.
- Open an elevated Command Prompt.
- Run
chkdskC: /f /r on the Windows volume. - Restart and let Autochk run if Windows schedules it after reboot; it can map a bad sector automatically when the system can reboot.
- After Windows loads, open Event Viewer > Windows Logs > System and look for disk or storage errors around the crash time.
- If the same status returns, back up data and test the drive in vendor diagnostics or replace it.
Loose or bad SATA, NVMe, or power cabling
0xC000009D points to a drive the controller cannot see. 0xC0000185 points to improper termination or defective cabling on SCSI devices, and it can also point to an IRQ conflict on older or unusual storage setups. That is a cable, connector, or controller-path problem until proven otherwise.
- Shut the PC down and remove power.
- Reseat the SATA data cable and power lead, or reseat the NVMe module if the system uses M.2 storage.
- Move the drive to a different port or use a different cable.
- Check BIOS/UEFI storage detection and confirm the drive is visible.
- Open Device Manager and inspect storage controllers for warning icons, then check Event Viewer for disconnect or reset events.
RAM faults and memory instability
When parameter 1 is 0 or 1, defective hardware such as RAM is a common cause, per Microsoft support. A memory read failure can look like a disk problem because the page never makes it cleanly through the read path.
- Press Win+R, run mdsched.exe, and restart into Windows Memory Diagnostic.
- If the machine still boots, run a longer memory scanner from a USB or bootable medium.
- Power down, reseat each stick, then test one module at a time.
- Remove any overclock or XMP setting in BIOS/UEFI before retesting.
- If a single stick fails again, replace it.
Driver stack or controller issues
When parameter 1 is 2, the driver stack returned an inconsistent status for the page read, per Microsoft support. That means the storage path may have reported SUCCESS even though the full page was not read. In that case, the drive can be fine and the driver path is the real problem.
- Open Device Manager.
- Expand IDE ATA/ATAPI controllers or Storage controllers.
- Use Properties > Driver to try Roll Back Driver first, then Update driver if rollback is unavailable.
- Boot into Safe Mode or perform a clean boot with msconfig to see whether the crash stops.
- Check Event Viewer for repeated storage resets, controller errors, or device-not-ready messages.
Malware as a less common cause
Malware can corrupt system files or interfere with storage drivers. That is less common than a bad disk, cable, or RAM stick, but it is still worth checking if the machine also shows other unexplained failures.
