STATUS_STACK_BUFFER_OVERRUN 0xC0000409

Hex 0xC0000409 · Decimal -1073740791 · Type NTSTATUS

WINDOWS

The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

Also searched as: 0xc0000409, exception code 0xc0000409, error 0xc0000409, stack buffer overrun

Windows troubleshooting diagram: Device Manager warning and a system file scan
Windows errors: check drivers, system files and Event Viewer, in that order.

What it means

0xC0000409 is reported when a program detects a stack buffer overrun or triggers a fast-fail security stop. You see it as an exception code in game crash reports, Event Viewer application errors and crashes of explorer.exe or other apps. Windows terminates the process deliberately to prevent memory corruption.

Applies to: Windows 10, Windows 11

How to fix STATUS_STACK_BUFFER_OVERRUN

  1. Update the crashing application or game to the latest version
  2. Update graphics drivers and remove overlays or mods that inject into the process
  3. Verify game files in Steam, the Xbox app or your launcher
  4. Install pending Windows updates and the latest Visual C++ Redistributables
  5. Remove CPU, GPU or RAM overclocks, including XMP/EXPO profiles, and test stability
  6. Repair system files from an elevated Command Prompt or Terminal (Admin): run DISM /Online /Cleanup-Image /RestoreHealth first, then sfc /scannow, and restart when both finish
  7. Check Event Viewer > Windows Logs > Application for the faulting module name, which tells you which DLL or driver to update

Why it happens

Despite the name, modern code also uses this status for intentional fail-fast exits. Causes include application bugs, incompatible plugins or overlays, corrupted files, and unstable hardware that corrupts memory.

FAQ

Is 0xc0000409 a hacking attempt?

Almost never on home PCs. It is a crash code triggered by a program's own safety checks.

Why do games crash with 0xc0000409?

Common causes are mods, overlays, outdated drivers and unstable overclocks.

Related errors

Source: Microsoft ntstatus.h · fixes written and reviewed by the editors (see our editorial policy)

Last updated: