Skip to content
0x000001AAEXCEPTION_ON_INVALID_STACKStop codeWidely reported

EXCEPTION_ON_INVALID_STACK (0x1AA): what it means and how to fix it

Updated Nov 14, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Stop code 0x000001AA occurs when Windows encounters an exception while referencing an invalid or corrupted kernel stack. This error is typically triggered by a malfunctioning device driver corrupting frame pointers or exhausting stack memory limits. Updating unstable device drivers and reviewing critical logs in Event Viewer are the first steps to resolve it.

What it means

Windows reserves a small, strictly bounded segment of memory called the kernel stack for the operating system and drivers to store context, local variables, and execution frames. Because kernel stacks have fixed limits, software running in kernel mode must carefully monitor stack usage, especially when handling heavy tasks like moving blocks of video memory.

When a program or driver triggers an exception, the operating system initiates exception dispatch. During this sequence, Windows unwinds stack frames to handle the error properly. The EXCEPTION_ON_INVALID_STACK bug check occurs when the kernel discovers that this dispatch process crossed over into an illegal stack address. This indicates that the kernel stack pointer was corrupted—often due to an overwritten frame pointer—or that an active driver attempted to execute routines from memory that is not designated as an authentic kernel stack.

Stack Limits and Driver Conflict

The operating system tracks multiple stack limit categories, including normal kernel thread stacks, processor deferred procedure call (DPC) stacks, and interrupt service routine (ISR) stacks. If a driver miscalculates memory boundaries, it can overwrite adjacent memory registers. In crash dumps analyzed with tools like WinDbg, this issue often presents alongside an access violation (error code c0000005) when a system thread tries to read from an unmapped address.

Display and graphics subsystems, such as the video memory management component dxgmms2, are common participants in these stack overruns. When a driver corrupts stack boundaries, Windows halts immediately with this blue screen to safeguard the machine from deeper memory damage and structural corruption.

Common causes

  • A kernel-mode driver corrupted stack frame pointers during execution or exception unwinding.
  • A device driver exceeded kernel stack memory boundaries while transferring data, such as video memory blocks.
  • A driver attempted to execute operations from an unauthorized or non-kernel stack region.
  • Recently added or failing physical hardware caused memory read violations.
  • Corrupted system files or Master Boot Record data disrupted low-level driver execution.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Update or roll back graphics and device drivers

    Use this first, as graphics drivers and third-party hardware modules are the most common source of kernel stack corruption.

    1. Right-click the Start button and select Device Manager.
    2. Expand the Display adapters category.
    3. Right-click your graphics card and select Update driver, then choose Search automatically for drivers.
    4. If the crashes started after a recent driver installation, right-click the device, select Properties, open the Driver tab, and click Roll Back Driver.
    5. Review Device Manager for any other hardware marked with a yellow exclamation point and update those devices as well.
    Did this fix it?
  2. Inspect the System Log in Event Viewer

    Use this to identify which driver or service failed immediately before the operating system crashed.

    1. Press Windows Key + X and select Event Viewer.
    2. Expand Windows Logs on the left panel and click System.
    3. Scan the log for Error or Critical level events recorded at the exact time the blue screen occurred.
    4. Select the relevant event and inspect the General tab below to find the specific driver, service, or faulting module name.
    5. Reinstall or remove the driver associated with that module name.
    Did this fix it?
  3. Disconnect recently added hardware

    Use this if the stop code began appearing shortly after installing new physical components or external peripherals.

    1. Shut down the computer and unplug the power cable.
    2. Disconnect any recently attached external devices, adapters, or docking stations.
    3. If you recently installed internal components like extra memory or an expansion card, remove or reseat the hardware.
    4. Start the computer to check if stability is restored without the device connected.
    5. Visit the hardware manufacturer website to check for firmware updates or system patches.
    Did this fix it?
  4. Run a full malware scan

    Use this to eliminate the possibility that disk or boot sector corruption is altering kernel structures.

    1. Open the Start menu, type Windows Security, and open the app.
    2. Click Virus & threat protection.
    3. Select Scan options.
    4. Choose Full scan to ensure the scan checks system memory and the Master Boot Record.
    5. Click Scan now and follow the prompts to clean any detected items.
    Did this fix it?
  5. Isolate drivers using Driver Verifier

    Use this testing tool only if the faulting driver remains unidentified, keeping in mind that Verifier intentionally crashes unstable systems to isolate errors.

    1. Right-click the Start menu and select Terminal (Admin) or Command Prompt (Admin).
    2. Type verifier and press Enter to launch Driver Verifier Manager.
    3. Select Create standard settings and click Next.
    4. Choose Select driver names from a list and click Next.
    5. Select the non-Microsoft drivers installed on the system and click Finish.
    6. Restart the PC to run the test; if a driver causes a crash, the resulting dump file will isolate the culprit.
    7. To stop testing and return to normal operation, open an administrator command prompt, run verifier /reset, and restart the computer.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Nov 10, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does EXCEPTION_ON_INVALID_STACK mean?

It is a Windows stop code indicating that the kernel encountered an error while trying to process an exception on an invalid or corrupted stack pointer address.

Can a graphics card trigger bug check 0x000001AA?

Yes. Graphic management components such as dxgmms2 can exhaust stack limits while processing video memory, leading to stack pointer errors.

How do I turn off Driver Verifier if my PC will not boot?

Start Windows in Safe Mode, open Command Prompt as an administrator, enter verifier /reset, and restart your computer.