Fix 0x00000077 KERNEL_STACK_INPAGE_ERROR in Windows

Quick Answer

KERNEL_STACK_INPAGE_ERROR, bug check 0x00000077, indicates that Windows could not read a requested page of kernel data from the paging file into memory. Some parameter combinations instead identify a missing stack signature or an inconsistent storage-read result. Microsoft Learn

Back up important data first. Then inspect the crash parameters to decide whether to prioritize storage, memory, or driver investigation. Do not assume that enlarging the paging file will repair the problem.

Understand the Bug-Check Parameters

When Parameter 1 is 0, 1, or 2

Values 0 or 1 indicate a missing signature; Microsoft identifies defective hardware, including RAM, as a likely cause. Value 2 indicates an inconsistent storage-stack result. Microsoft Learn

When Parameter 1 has another value

Use the I/O status to guide investigation. Microsoft Learn

Common I/O Status Codes

The following are useful NTSTATUS values to recognize:

These meanings identify the reported failure category. Further testing is needed to establish the responsible component. Microsoft Learn

Before You Begin

1. Back up important files while the drive remains accessible.
2. Record the crash time and all four parameters.
3. Note recent storage, driver, hardware, or firmware changes.
4. Preserve existing crash dumps.
5. Have administrator access available for diagnostics.

If the drive repeatedly disappears or files become unreadable, prioritize data recovery before lengthy repair scans.

How to Troubleshoot 0x00000077

1. Review the system history

Determine whether the first crash followed a specific change. Check whether failures occur during the same workload or after the same device activity.

Microsoft’s general stop-error guidance recommends reviewing recent changes, updating implicated components, and using relevant hardware tests. learn.microsoft.com

Make one targeted change at a time and record the result.

2. Investigate the storage path when indicated

If the status suggests a disconnected or inaccessible device:

• Check whether firmware and the operating system consistently detect the drive.
• Follow the manufacturer’s procedure for checking the drive and controller.
• Have a qualified person inspect applicable power and data connections with the computer shut down and power disconnected.
• Use termination checks only for hardware that actually requires termination.

A device-access error can involve the drive, connection, or controller. Avoid selecting replacement hardware solely from the stop-code name.

3. Check the file system

After backing up important data, an online scan is a reasonable starting point for an accessible NTFS volume.

Open Command Prompt as administrator and run:

chkdsk C: /scan

Replace C: with the affected volume’s actual drive letter. The /scan option performs an online NTFS scan. Review the result before choosing a repair operation. learn.microsoft.com

If the findings justify file-system repair and bad-sector checking:

chkdsk C: /r

The /r option includes /f, checks for bad sectors, and attempts to recover readable information. It requires exclusive volume access and may need to run at restart. It can take considerable time; avoid interrupting it. learn.microsoft.com

CHKDSK does not physically repair a failing drive. Recurring errors require further storage diagnostics.

4. Test memory when the evidence points there

Run the computer manufacturer’s hardware diagnostics, including its memory test. Record the results before replacing components. This is especially relevant when the parameter interpretation points toward hardware corruption. Microsoft Learn

Have a qualified technician perform internal component checks using the device’s service instructions.

5. Roll back or update an implicated driver

If crashes began after a relevant driver update:

1. Open Device Manager.
2. Locate the device and open Properties.
3. Select Driver → Roll Back Driver, if available.
4. Follow the prompts and restart.

Administrator privileges are required. If rollback is unsuitable, obtain a compatible package through Windows Update or the manufacturer’s official support site. support.microsoft.com

Record the old and new versions so the change can be reversed if necessary.

Analyze the Crash Dump with WinDbg

1. Preserve the dump

Common default locations are:

If Windows remains usable, future collection can be configured under Advanced system settings → Advanced → Startup and Recovery → Settings → Automatic memory dump. Restart after saving the setting. A dump is available only if Windows successfully writes it. learn.microsoft.com

2. Run the initial analysis

Open the dump in WinDbg with appropriate symbols configured:

!analyze -v

Record the parameters and available stack information. learn.microsoft.com

3. Decode the I/O status only for the applicable case

When Parameter 1 is neither 0, 1, nor 2, decode Parameter 2:

!error <I-O-status-from-Arg2> 1

Replace the entire placeholder with the hexadecimal status value. The final 1 selects NTSTATUS interpretation. learn.microsoft.com

Do not apply this decoding step to the stack-signature cases, where Parameter 2 has a different meaning.

How to Verify the Fix

1. Confirm the intended driver or hardware change.
2. Restart Windows normally.
3. Repeat the affected workload using noncritical data.
4. Review diagnostic results for recurring storage or memory errors.
5. Preserve any new dump if the crash returns.

A clean file-system scan or one successful restart does not establish that every underlying hardware or driver problem has been resolved.

Frequently Asked Questions

Will increasing the paging file fix this error?

Not necessarily. Investigate the failed read, returned status, and hardware evidence before changing its size.

Does 0x00000077 always mean the drive has failed?

No. The parameters distinguish different failure paths, so the investigation must follow the specific crash evidence.

Should I run CHKDSK before backing up?

Protect important data first, especially when the drive is unreliable. Repair scans modify file-system structures and cannot substitute for a backup.

Can I decode Parameter 2 as an error code in every crash?

No. Its meaning depends on Parameter 1. Follow the parameter tables above.

What should I provide to technical support?

Provide the dump, all four parameters, decoded status where applicable, hardware model, storage-driver versions, diagnostic results, and recent change history.

Conclusion

For 0x00000077, preserve data and interpret the parameters before choosing a repair. Use the resulting evidence to investigate storage access, memory integrity, or the relevant driver, then verify the correction against the original failure.

Sources

• Microsoft Learn — Bug Check 0x77: KERNEL_STACK_INPAGE_ERROR
• Microsoft Learn — NTSTATUS Values
• Microsoft Learn — CHKDSK command reference
• Microsoft Learn — !error debugger extension
• Microsoft Learn — Advanced troubleshooting for stop code errors
• Microsoft Support — Update drivers through Device Manager in Windows