EXE Has Stopped Working | Fix Crashes With Clean Steps

You click a program and it closes right away. Or it runs, then drops you back to the desktop. That message means Windows detected a crash and logged what happened. Those logs often let you stop guessing and start fixing with less guesswork.

This guide walks you through an order for Windows 11 and Windows 10. If you’re seeing exe has stopped working more than once, follow the steps. You’ll learn how to read the crash record, test for background conflicts, repair Windows files, and narrow it to one program.

Why The Crash Message Keeps Appearing

“EXE” is just a program file type. When Windows says an exe stopped working, it means a process crashed and Windows Error Reporting captured it. The crash can come from the app itself, something it loads, or something Windows loads around it.

These are the most common patterns you’ll run into.

• Bad plug-in or add-on — The program loads extra modules at launch, then trips on one that’s outdated or corrupt.
• Corrupt app files — The install is missing pieces, or an update failed mid-way.
• Broken Windows files — System components the app relies on are damaged, so the app crashes even if it’s well-written.
• Driver clash — Display, audio, printer, or USB drivers can crash apps that call them.
• Security tool interference — Real-time scanning can block a file the app needs, then the app fails during startup.
• User profile quirks — A bad setting, a broken cache, or a permission issue can hit only one Windows account.

The good news is you can often sort these into two buckets fast. Either multiple apps crash and Windows needs repair, or one app crashes and that app needs attention. The steps below are built around that split.

EXE Has Stopped Working In Windows 11 And 10 With A Fast Triage

Start with a short triage so you don’t waste time on the wrong layer. Think of it as a quick sort, not a deep repair.

What You Notice	Likely Layer	First Move
Only one app crashes	App files, add-ons, settings	Reinstall or reset that app
Many apps crash	Windows files, drivers	Run DISM and SFC
Crashes after a driver update	Driver or device	Roll back or update again
Crashes only in one account	User profile data	Test with a new profile

Before you change anything, try the same action twice. If it crashes at the same spot each time, you have a repeatable trigger to test after each fix.

1. Restart Windows — A clean reboot clears stuck processes and reloads drivers.
2. Try a different app type — Launch a browser, a built-in app, and a desktop app to see if crashes are wide or narrow.
3. Check free storage — Keep a few GB free on the system drive so updates and temp files can write safely.
4. Update Windows — Install pending updates, then test again after a restart.

If the problem still shows up, grab the crash record next. That record tells you what module failed and often points at the real cause.

Find The Crash Record In Event Viewer

Event Viewer looks intimidating, yet you only need a few fields. You’re hunting for the crash entry around the time the app failed. Microsoft notes that repeated Event ID 1000 and 1001 in the Application log often indicate an app crash pattern you can work from.

Microsoft’s own crash log guidance for client Windows and Windows Server is here on learn.microsoft.com. Keep it open while you read your entry so the terms make sense.

1. Open Event Viewer — Press Win + R, type eventvwr.msc, then press Enter.
2. Go To Application Logs — Expand Windows Logs, then click Application.
3. Filter For Crashes — Use Filter Current Log and look for Event ID 1000 and 1001.
4. Open The Matching Entry — Pick the entry with the same timestamp as the crash.

In the Event 1000 details, pay attention to the faulting application name, faulting module name, and exception code. The module name matters because it can be the app, a DLL the app loads, or a Windows component.

• If the module is the app’s EXE — The app itself is crashing, often from a bug or corrupt install.
• If the module is a third-party DLL — Add-ons, overlays, injectors, printer tools, and audio tools are common culprits.
• If the module is a Windows DLL — Treat it as a Windows integrity or driver issue until proven otherwise.

Write down the module name and exception code. Then search that pair with the app name. You’ll often spot a known conflict with a driver, a plug-in, or an older build of the app.

Microsoft describes System File Checker (Sfc.exe) on learn.microsoft.com.

If more than one program is crashing, or the event log points at Windows modules, repair Windows before you chase app settings. Two built-in tools do most of the heavy lifting: DISM checks the Windows image, and SFC checks protected system files.

1. Open Terminal As Admin — Right-click Start, then choose Windows Terminal (Admin) or Command Prompt (Admin).
2. Run DISM RestoreHealth — Enter DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
3. Run System File Checker — Enter sfc /scannow and let it reach 100%.
4. Restart And Retest — Reboot, then try the program again.

If DISM or SFC reports it fixed files, that’s a good sign. Test the crash again right after the reboot. If the crash message is gone, you’re done.

Disk issues can also cause random crashes, especially if the drive has file system errors. Run a disk check when crashes feel random across apps.

1. Schedule A Disk Scan — In an admin terminal, run chkdsk C: /f, then accept the restart prompt.
2. Let The Scan Finish — Restart and let Windows complete the scan before you open apps.

Test For Background Conflicts With A Clean Boot

If the crash log points at a third-party module, or the crash only happens when certain tools are running, a clean boot is the fastest way to prove a background clash. A clean boot starts Windows with most non-Microsoft services and startup items turned off, so you can see if the crash disappears.

A clear clean boot walkthrough is available on Pureinfotech if you want screenshots.

1. Open System Configuration — Press Win + R, type msconfig, then press Enter.
2. Hide Microsoft Services — On the Services tab, tick Hide all Microsoft services.
3. Disable Non-Microsoft Services — Click Disable all, then click Apply.
4. Disable Startup Apps — Open Task Manager from the Startup tab, then disable startup items.
5. Restart And Test — Reboot, then launch the crashing app and repeat the trigger.

If the crash stops in a clean boot, you’ve proven a background conflict. Now turn items back on in small batches until the crash returns. When it does, the last batch contains the culprit.

Turn items back on in batches, restart, and test. When the crash returns, the last batch contains the culprit.

This step catches common crash triggers like overlays, screen recorders, RGB tools, printer helpers, audio enhancers, and some security tools. If you remove the conflict and the app stays stable, you’ve solved it without touching Windows files.

Fix A Single Program That Keeps Crashing

If only one app is failing, treat it like an app problem first. You still can use the event log to steer, yet the fastest wins are often reinstalling cleanly and resetting the app’s own data.

Reinstall Cleanly

1. Uninstall The App — Use Settings, then Apps, then Installed apps to remove it.
2. Restart Before Reinstall — A reboot clears old files that stay locked during uninstall.
3. Install The Latest Build — Use the vendor’s site or the Microsoft Store, then test.

Reset Cache And Settings

Some apps crash because a cache file is corrupt. Clearing the cache is safe when you follow the app’s own reset option, or when you rename its local data folder so the app rebuilds it.

1. Close The App Fully — End it in Task Manager if it lingers after closing.
2. Rename The App Data Folder — In File Explorer, open %appdata% or %localappdata%, find the app folder, then rename it with “.old”.
3. Launch And Recheck — Start the app so it creates a fresh folder, then test the crash trigger.

Try Compatibility And Graphics Settings

Older programs can crash on modern Windows builds, especially around display modes and DPI scaling.

1. Run As Admin — Right-click the app shortcut, then pick Run as administrator.
2. Set Compatibility Mode — Right-click the EXE, open Properties, then Compatibility, then try Windows 8 or Windows 7 mode.
3. Change GPU Preference — In Settings, go to System, Display, Graphics, pick the app, then set it to Power saving or High performance, then retest.

If the crash message shows up only when you open files, check file associations too. A broken association can crash a handler app. Reassign the default app, then try again.

When The Crash Only Happens In One Windows Account

Sometimes the app is fine and Windows is fine, yet one account keeps crashing. This points to a profile-level setting, cache, or permission issue. The fastest proof is testing with a fresh user account.

1. Create A Test Account — In Settings, go to Accounts, then Other users, then add a new local user.
2. Sign In And Test — Log into the new account, install or run the app, then repeat the crash trigger.
3. Move Only Needed Data — If the app works in the new profile, copy documents and browser data, then rebuild the old profile slowly.

Last Steps That Keep Your Files

If you’ve repaired Windows files, ruled out background conflicts, and the crash still happens across apps, you’re down to bigger system fixes. Two options often solve stubborn cases without wiping personal files.

1. Run An In-Place Repair Install — Use the official Windows installer to repair the system while keeping apps and files. It replaces Windows components and can clear deep corruption.
2. Update Or Roll Back Drivers — Use Device Manager for display, audio, and chipset drivers. If the crash started right after a driver update, roll back, restart, then test.
3. Check RAM And Heat — Run Windows Memory Diagnostic and watch temps during a crash-prone task. Hardware faults can mimic software crashes.

When you reach this point, use your notes from Event Viewer. The faulting module name and exception code are your best clues about whether you’re facing a driver problem, a Windows component issue, or a single vendor bug. If you keep seeing “exe has stopped working” after every step, those details will steer the next move far better than guesswork.