Fix ERROR_FATAL_APP_EXIT 0X000002C9 on Windows

That app crash is annoying — let's get it fixed.

You're working, then boom — app closes and you see ERROR_FATAL_APP_EXIT (0X000002C9). It's a generic Windows error that says the program had a fatal problem and had to shut down. But generic doesn't mean hopeless. I've seen this in Outlook, Chrome, and several business apps on Windows 10 22H2 and Windows 11 23H2. Here's the fix that works most of the time.

First, run System File Checker (SFC) and DISM

This should be your first move. Corrupted system files cause this error more often than anything else. You'll need an admin account. Here's what to do:

Press Windows + X, then click Windows Terminal (Admin) or Command Prompt (Admin) — depending on your Windows version.
Type this and press Enter:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
After you press Enter, you'll see a progress bar. It looks stuck at 20% for a minute — that's normal. Let it finish. It might take 5–15 minutes.
Once DISM says it's done, type this and press Enter:
```
SFC /SCANNOW
```
Again, wait. It'll say "Windows Resource Protection found corrupt files and successfully repaired them." If it says it couldn't fix some, run DISM again, then SFC again.
Restart your computer.

After reboot: Try opening the app that crashed. If it works, you're done. If not, move to the next step.

Check your RAM with Windows Memory Diagnostic

Bad memory can trigger 0X000002C9. I've seen faulty RAM cause apps to crash with this exact code. Windows has a built-in tool to check it.

Press Windows + R, type mdsched.exe, then hit Enter.
Choose Restart now and check for problems (recommended). Your PC will reboot immediately — save any open work first.
The tool runs when Windows starts up. It takes about 10–15 minutes. Let it finish. You'll see a progress bar and status messages. If it finds errors, it'll tell you at the bottom.
After the test, Windows boots normally. The results show up in a notification after you log in. If you miss it, check Event Viewer under Windows Logs > System, looking for source MemoryDiagnostics-Results.

If errors were found: Your RAM is bad. You'll need to replace it. Run the test again with one stick at a time to find the faulty module. Until then, the app crashes will keep happening.

Clean boot to rule out software conflicts

Sometimes a third-party service or startup program messes with your app. A clean boot starts Windows with only Microsoft services — it's a great diagnostic step.

Press Windows + R, type msconfig, and press Enter.
Go to the Services tab. Check Hide all Microsoft services at the bottom. Then click Disable all.
Go to the Startup tab. Click Open Task Manager. In Task Manager, disable every startup item by right-clicking and choosing Disable.
Close Task Manager, click OK in System Configuration, then restart your PC.

After reboot: Try the app again. If it works, you've got a software conflict. Slowly re-enable services and startup items (rebooting each time) until the crash comes back. That's your culprit — uninstall or update that software.

Why these steps work

ERROR_FATAL_APP_EXIT means the app tried to write to a protected memory location, or some critical file it needed was corrupted. SFC and DISM fix the system files that might've been causing that corruption. Memory diagnostics catch the hardware side — bad RAM writes bad data, period. Clean boot eliminates the noise so you can find the real problem without guessing.

Less common variations

Sometimes this error shows up in a specific program like Adobe Acrobat or Microsoft Teams. In those cases:

Adobe Acrobat: Go to Help > Repair Installation. Then run SFC as above. I've seen a corrupted PDF trigger this in Acrobat only.
Microsoft Teams: Clear the cache. Close Teams, then delete everything in %appdata%\Microsoft\Teams. Restart Teams. The error often comes from a bad local cache file.
Any app you installed recently: Reinstall it. A bad installer can cause this error. Uninstall from Settings > Apps, reboot, then install fresh.

How to prevent it from coming back

You can't stop every crash, but you can make them rare. Do these once a month:

Run Windows Update regularly — driver updates often fix these bugs.
Use Disk Cleanup to clear temp files. Click Start, type cleanmgr, select your system drive (usually C:), and clean everything.
Keep your RAM healthy — don't overclock it unless you know what you're doing. Overclocking is the #1 cause of memory errors I see in help desk tickets.
If you're on a laptop, make sure it's not overheating. Dust buildup causes thermal throttling, which can corrupt data in memory. Blow out the vents every 6 months.

If you still get the error after all this, check the Event Viewer for more clues. Open Event Viewer (eventvwr.msc), go to Windows Logs > Application, and look for a red error timestamped with your crash. The details often point you right to the problematic file or driver.