Fix STATUS_FATAL_APP_EXIT (0x40000015) on Hard Drives

Quick answer

Run chkdsk /f /r on the drive where the crashing app lives, then do sfc /scannow. That fixes 80% of these.

What's going on here?

STATUS_FATAL_APP_EXIT (0x40000015) is a Windows error that says a program shut down hard—like it hit a wall. The message reads: "{Fatal Application Exit} %hs". I've seen this most often when a hard drive has bad sectors or corrupted system files. Users report it after a power outage or a sudden crash while copying files. The app itself isn't always the culprit—the drive underneath is failing to read or write what the program needs.

If you're getting this on a specific program, check Event Viewer first. I'll show you how.

Step 1: Check Event Viewer for the culprit

1. Press Windows + R, type eventvwr.msc, hit Enter.
2. Go to Windows Logs > Application.
3. Look for a red Error with Source like Application Error or .NET Runtime. Click it.
4. Read the Faulting application name. That's the program crashing. Write it down.
5. Expected: You'll see a timestamp and path like C:\Program Files\ExampleApp\app.exe.

Step 2: Run chkdsk on the drive

This is the real fix for hard-drive-related errors. chkdsk scans for bad sectors and fixes file system corruption.

1. Open Command Prompt as admin: press Windows + X, choose Command Prompt (Admin) or Windows PowerShell (Admin).
2. Type chkdsk /f /r and press Enter. The /f fixes errors, /r finds bad sectors.
3. You'll see: "Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?" Type Y and press Enter.
4. Restart your computer. Windows will scan the drive before booting—this can take an hour or more on a big drive.
5. After it finishes, it logs the results. You can check them later in Event Viewer under Windows Logs > Application, source Wininit.
6. Expected: A reboot, a blue screen with a progress bar during chkdsk, then normal boot.

Step 3: Run System File Checker

Corrupted system files can trigger this error too. SFC repairs them.

1. Open Command Prompt as admin again.
2. Type sfc /scannow and press Enter.
3. Expected: A progress bar that takes 15–30 minutes. At the end, you'll see "Windows Resource Protection found corrupt files and successfully repaired them" or "did not find any integrity violations".

Step 4: Check the drive's health

If chkdsk found bad sectors, the drive might be failing. Use a tool like CrystalDiskInfo to check SMART data.

1. Download and run CrystalDiskInfo (free, portable version works fine).
2. Look at the Health Status field. Caution or Bad means replace the drive soon.
3. Also check the Reallocated Sectors Count and Current Pending Sector Count. High numbers mean trouble.

Step 5: Reinstall the crashing app

If the drive checks out, the app itself might be corrupt. Uninstall it, then reinstall fresh.

1. Go to Settings > Apps > Apps & features.
2. Find the app from Step 1, click it, choose Uninstall.
3. Reboot.
4. Download the latest version from the official site and install it.

Alternative fixes if the main ones fail

Sometimes the error is tricky. Try these in order.

Option A: DISM for deeper system repair

If SFC found files it couldn't fix, DISM can repair the system image.

1. Open Command Prompt as admin.
2. Type DISM /Online /Cleanup-Image /RestoreHealth, press Enter.
3. Expected: A progress bar that runs for 20–30 minutes. It may say "The restoration completed successfully".
4. Then run sfc /scannow again.

Option B: Check for memory issues

Faulty RAM can mimic hard drive errors. Run Windows Memory Diagnostic.

1. Press Windows + R, type mdsched.exe, press Enter.
2. Choose Restart now and check for problems.
3. Expected: A blue screen with a memory test. It takes 20–40 minutes. After boot, check the results in Event Viewer under Windows Logs > System, source MemoryDiagnostics-Results.

Option C: Update drivers and Windows

Outdated storage drivers can cause app crashes.

1. Press Windows + I for Settings, go to Update & Security > Windows Update, click Check for updates.
2. Install all updates, then reboot.
3. Open Device Manager, expand Disk drives, right-click your drive, choose Update driver > Search automatically for drivers.

Prevention tip

This error usually means the drive is on its way out or the app got corrupted. To avoid it, run chkdsk every few months on mechanical drives—especially if you hear clicking noises. Back up important data weekly. For SSDs, keep the firmware updated and avoid filling them past 90%—that triggers write errors. And always shut down Windows properly. Power cuts corrupt files fast.

If you've tried all this and the error keeps coming back, replace the drive. There's no software fix for dying hardware.