KERNEL_STACK_INPAGE_ERROR BSOD Fix for Windows 11

KERNEL_STACK_INPAGE_ERROR in Windows 11 means the requested page of kernel data from the paging file could not be read into memory. The bug check has a value of 0x00000077. It can happen during startup or later, and the first parameter can help narrow whether the stack signature was not found, the driver stack returned an inconsistent status for the page read, or the system is running into hardware trouble such as a RAM error.

This guide is part of our Windows BSOD stop codes: full list and fixes series.

Windows 11 comes in Home, Pro, Pro for Workstations, Education, and Enterprise editions. The same triage applies across them. The main split is not edition; it is whether the pattern looks like storage, RAM, or a driver that broke the read path.

KERNEL_STACK_INPAGE_ERROR in Windows 11: what it usually points to

According to Windows 11 Help: Learn How to Fix It Yourself. — Windows 11 includes Home, Pro, Pro for Workstations, Education, and Enterprise editions.

Which subsystem is most likely? Start with this triage table

Use the symptom pattern first. That keeps you from replacing a good SSD when the real issue is a bad driver, or from chasing drivers when the disk is throwing read errors. Boot timing matters a lot here, especially when Windows will not reach the desktop.

A one-off crash can still be storage, but repeat failures that shift with workload often point away from a single dead drive. A crash after update is different again; those cases usually track a recent driver or security change, not random hardware decay.

What causes KERNEL_STACK_INPAGE_ERROR in Windows 11?

The common causes are storage trouble, RAM instability, and driver faults that disrupt a page read. Microsoft notes this bug check can also show a defective hardware condition such as a RAM error, and the first parameter can point to a driver stack inconsistency or a stack signature problem. The error can appear during startup or later under load, per Windows Central.

Check the pattern before you touch settings

1. Note whether the crash happens at boot, after sign-in, or only under load.
2. Check whether the machine started failing after a Windows update, driver install, or new app.
3. If the machine still boots, copy the stop code parameters from the blue screen or from C:\Windows\Minidump.

If the same behavior repeats on startup, storage rises to the top. If the system survives idle time but falls over during gaming, large copies, or browser spikes, RAM or a driver conflict becomes more plausible.

Could your system drive or paging file be failing?

Yes. The paging file sits on system storage, so corruption, access failures, or disk trouble can trigger in-page errors. If you see disk I/O warnings, slow boots, missing files, or Event ID 7/51, treat the SSD or HDD as suspect before you reset Windows.

Check SSD or HDD health in the safest order

1. Open Windows Terminal as admin and run chkdsk C: /scan.
2. Open Event Viewer and review Windows Logs > System for disk, storahci, iaStor, or controller errors.
3. Check the drive in the BIOS or firmware utility for SMART warnings.
4. If it is a desktop or SATA laptop, shut down the PC, disconnect power, reseat the cable, and try a different SATA port.
5. If it is an M.2 drive, power the PC off, reseat the module, and make sure the slot is clean and the drive is fully seated.

Test the paging file and file system for access errors

1. Open System Properties > Advanced > Performance > Settings > Advanced.
2. Under Virtual memory, set the paging file to System managed size on the system drive.
3. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
4. Restart and test again. If the crash returns, do not move on to bigger changes yet.

chkdsk C: /scan
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Is RAM causing the in-page error?

It can. Microsoft says the bug check is probably caused by defective hardware such as a RAM error, and repeated crashes that change location or workload often fit memory instability better than a dead disk. That is especially true when the machine passes some boots and fails under pressure.

Run Windows Memory Diagnostic and read the result correctly

1. Press Win+R, type mdsched.exe, and choose Restart now and check for problems.
2. After the reboot, open Event Viewer, then check Windows Logs > System for the MemoryDiagnostics-Results entry.
3. If errors appear, test each stick separately.

Reseat memory and retest one stick at a time

1. Shut down, unplug power, and remove AC or battery where possible.
2. Reseat the memory module or modules.
3. Boot with one stick installed, then swap to the other stick.
4. Move the module to another slot if the board has more than one.

When repeated failures point to replacement

1. If the same stick fails in multiple slots, replace that module.
2. If both sticks fail separately, test the board or memory controller next.
3. Do not keep reinstalling Windows when the same memory fault returns.

Could a driver update have started the crash loop?

Yes. Recent storage, chipset, and antivirus driver changes are high-risk here, because they sit in the path that reads the page back into memory. A bad driver update can also return an inconsistent status for the read, which fits Microsoft’s bug-check notes.