Home › Error codes › Blue screen and stop codesIndependent reference

UNWIND_ON_INVALID_STACK (0x000001AB): Stop Code Guide

0x000001AB is a kernel/debugger stop code result. It indicates that an attempt was made to access memory outside of the valid kernel stack range. In particular, this BugCheck indicates that stack unwinding crossed over into an invalid kernel stack. This might indicate that the kernel stack pointer has become corrupted during exception dispatch or unwind (e.g. due to stack corruption of a frame pointer), or that a driver is executing off of a stack that is not a legal kernel stack.

Code reference and safe checks

Read the exact screen and operation before selecting a repair. This page does not run commands or collect files, keys or logs.

What this value means

It indicates that an attempt was made to access memory outside of the valid kernel stack range. In particular, this BugCheck indicates that stack unwinding crossed over into an invalid kernel stack. This might indicate that the kernel stack pointer has become corrupted during exception dispatch or unwind (e.g. due to stack corruption of a frame pointer), or that a driver is executing off of a stack that is not a legal kernel stack.

UNWIND_ON_INVALID_STACK identifies a stop-code family. The four bug-check parameters and dump, if available, help distinguish the actual failure path.

Identity and provenance of 0x000001AB
Code0x000001AB
Short hex form0x1AB
SymbolUNWIND_ON_INVALID_STACK
Windows familyBlue screen and stop codes
Source levelMicrosoft bug-check page

Microsoft’s technical cause notes add: An attempt to access an invalid stack occurred. As kernel stack is limited in size, the developer needs to be careful with tracking it limits, for example when using it to copy blocks of video memory. For information about the Windows Kernel stack, see Using the Kernel Stack .

Safe next steps

  1. For 0x000001AB (UNWIND_ON_INVALID_STACK), record the exact stop code and parameters. Microsoft’s debugger reference may describe a kernel condition rather than a consumer fix.
  2. If crashes repeat, inspect the dump locally with official WinDbg and compare its parameters with this code’s Microsoft page.
  3. Do not enable Driver Verifier or change firmware as a generic first step; ask qualified support if the PC cannot start.

After one step, repeat the original operation and record whether this same code returns. A different code needs a fresh interpretation.

What this code cannot prove

The source establishes the identifier and reference meaning. It does not establish the cause on your specific PC.

If Windows no longer starts or the issue repeats with hardware warnings, protect files and use manufacturer or qualified support.

Related references

Advertisement

Official reference and verification

Source type: Microsoft bug-check page. Checked against the source set on Nov 2, 2026.

Open the source reference ↗

The reference gives the meaning of this identifier. It does not inspect your PC or guarantee that one repair will work.