Apps crashing in Windows 11 — closing unexpectedly without any error message, throwing a “stopped working” dialog, or freezing until you force-close them — becomes diagnosable the moment you identify the pattern. The single most useful question: is it one specific app, or multiple apps crashing? For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
One app crashing: the problem is that app — corrupt installation, corrupted settings, or compatibility issue. Multiple unrelated apps crashing randomly: the problem is Windows itself, which usually means failing RAM, a corrupt system file, or a driver conflict. These two paths have completely different fixes, and knowing which you’re on saves hours.
If it’s one specific app
Reinstalling is almost never the right first step — it wastes time and often doesn’t fix the underlying cause. Try these first in order:
Clear the app’s settings or cache: many apps store cached data and configuration that can corrupt after updates. For Microsoft apps: run them as administrator to test permissions. For third-party apps: look for “Reset” in Settings → Apps → the app → Advanced options → Reset (this clears data but keeps the app installed). For browser-type apps: clear the profile or cache from within the app’s settings.
Repair first, reinstall second: Settings → Apps → find the app → click it → Modify or Repair if the option exists. Windows Store apps: click the app → Advanced options → Repair. This reinstalls app components without touching your data or settings.
Check for updates: if the app was working before and stopped after a Windows Update, the app itself may need an update to restore compatibility. Open the app’s own update mechanism or the Microsoft Store if it’s a Store app.
Event Viewer — the crash report you didn’t know Windows was keeping
Windows logs every application crash with details that point to the cause. Win+R → eventvwr.msc → Windows Logs → Application → look for “Error” entries with the application name. Click an error → see the “Faulting application name” and “Faulting module name.” The faulting module is the DLL or component that crashed:
- Faulting module
ntdll.dll: usually a heap corruption — the app has a memory management bug, but can sometimes be triggered by bad RAM or a conflicting DLL injection (some antivirus software does this) - Faulting module matching a GPU driver DLL (like
nvoglv64.dll): GPU driver issue — update or roll back the driver - Faulting module matching a Microsoft Visual C++ redistributable: redistributable is corrupted — reinstall the specific VC++ version shown
- Faulting module matching the app itself: the app has a code bug triggered by something specific in your configuration
The Event ID 1000 (Application Error) and ID 1001 (Windows Error Reporting) are the main ones to check. The module name in the error almost always tells you what to fix.
Microsoft Visual C++ redistributables
Most Windows desktop applications depend on one or more Visual C++ redistributable packages (2010, 2013, 2015-2022 x86 and x64). When a redistributable becomes corrupted: every app that depends on it starts crashing, often with no obvious error about which dependency failed.
Settings → Apps → search “Microsoft Visual C++” → you’ll see multiple versions installed. Right-click each → Repair. If repair fails: uninstall → go to microsoft.com → download and reinstall. The 2015-2022 redistributable covers the most modern apps; if you see a specific version mentioned in the Event Viewer crash log, prioritise that one.
Multiple apps crashing — Windows-level causes
If unrelated apps (a browser, a game, and a system utility all crashing independently within a short period): the problem is below the application layer. The three most common causes:
Failing RAM: run Windows Memory Diagnostic. Win+R → mdsched → restart and check. If errors found: one RAM module is failing. Remove sticks individually to identify the bad one, then replace it. Failing RAM causes unpredictable crashes across any software that uses that memory region.
Corrupted system files: open Command Prompt as Administrator → sfc /scannow. Wait for completion (15-30 minutes). If it reports repaired files: restart and test. If it can’t repair: DISM /Online /Cleanup-Image /RestoreHealth first, then sfc /scannow again. DISM restores the source files SFC uses to repair, so it needs to run when SFC can’t fix things on its own.
Driver crash propagating: a misbehaving driver (GPU, network, storage) can corrupt shared memory used by applications. Check Event Viewer → System log for “Kernel-Power” ID 41 events (unexpected reboots) or any driver-related errors near the times of crashes.
Our guide on Windows 11 freezing and stability covers the system-level causes that produce crashes alongside freezes, and our BSOD troubleshooting covers driver-level crashes that sometimes accompany app crashes as warnings. For reading Event Viewer crash logs and understanding Windows error codes, Microsoft’s Event Viewer documentation explains how to interpret Application and System event logs.
Antivirus and security software interference
Enterprise endpoint security (CrowdStrike, SentinelOne, Symantec) and consumer antivirus tools both inject code into running processes to monitor for threats. When this injection fails or conflicts with an app’s own code: the app crashes. The crash happens inside the AV’s injected code rather than the application’s own code, making the cause non-obvious.
Event Viewer often reveals this: the faulting module shows a DLL associated with a security product (e.g., a path inside the AV’s installation directory). The fix: add the crashing app to the AV’s exclusion list, or update the AV to a version compatible with the current Windows 11 build. Don’t disable the AV entirely — just exclude specific apps that are demonstrably crashing due to the interaction.
GPU driver impact on all apps
GPU drivers don’t just affect games — they affect any application that uses hardware-accelerated graphics, including browsers, video players, Office apps, and photo editors. A bad GPU driver can crash any of these, often with errors blaming the application when the actual failure is in the GPU driver beneath it.
Tell-tale signs: crashes are often accompanied by a brief black screen flash, or the graphics in the window look corrupted before it crashes. The faulting module in Event Viewer points to an NVIDIA/AMD/Intel DLL. Update the GPU driver from the manufacturer’s site — not Windows Update, which often has older versions. If the newest driver is the problem (just installed → crashes started): roll back via Device Manager.
Windows Compatibility troubleshooter
For older apps not designed for Windows 11: right-click the app’s shortcut → Properties → Compatibility tab → “Run compatibility troubleshooter.” This automatically tests the app with various older Windows version emulation settings and applies what works. For many legacy apps: running in Windows 8 or Windows 10 compatibility mode resolves crashes.
Manually: check “Run this program in compatibility mode for:” → select Windows 10 → Apply → test. Also try “Run as administrator” if the app needs elevated permissions for certain operations. These two together resolve most compatibility-related crashes for apps that worked fine on previous Windows versions.
.NET Framework issues
Apps built on .NET Framework (especially older .NET 4.x apps or newer .NET 6/7/8 apps) crash when the required runtime version isn’t installed or is corrupted. The error often mentions “CLR” or “Common Language Runtime” in the crash details.
Control Panel → Programs → Turn Windows features on or off → “.NET Framework 3.5 (includes .NET 2.0 and 3.0)” → ensure it’s enabled for legacy apps that need it. For newer .NET versions (6, 7, 8): download from dotnet.microsoft.com → install the runtime or SDK matching what the app requires. The app’s error message or its system requirements page specifies which version it needs.
Windows Store apps specifically
Apps installed from the Microsoft Store have their own repair and reset mechanism separate from traditional desktop apps. Settings → Apps → the Store app → Advanced options → Repair (tries to fix without data loss) → if Repair doesn’t work → Reset (clears app data, like a fresh install of the app).
If Store apps are crashing consistently: check if the Microsoft Store itself needs an update. Open the Store → Library → Updates → update Microsoft Store itself. Also try: PowerShell as Administrator → wsreset.exe → clears the Store cache. This fixes “Store app crashes at launch” situations where the Store’s cached data is corrupted rather than the app itself.
| Crash pattern | Most likely cause | First fix |
| One specific app only | Corrupted app data or install | App → Repair in Settings; clear cache |
| Multiple unrelated apps | RAM fault or system file corruption | Memory Diagnostic; sfc /scannow |
| After GPU driver update | Driver regression affecting all apps | Roll back GPU driver in Device Manager |
| Apps with “CLR” errors | .NET runtime missing or corrupt | Install/repair required .NET version |
| Old apps since Windows 11 upgrade | Compatibility issue | Compatibility troubleshooter; Windows 10 compat mode |
| Store apps crashing at launch | Store cache or app data corrupted | wsreset.exe; then App → Reset |
Pattern identification is the diagnostic shortcut here. “One app crashes” and “many apps crash” are fundamentally different problems with different fix paths. The Event Viewer faulting module then narrows the single-app case to a specific component. These two observations together will identify the cause of almost any app crash on Windows 11.
Crash dumps — advanced diagnosis
For persistent crashes that Event Viewer doesn’t explain clearly: enable Windows crash dumps. Win+R → SystemPropertiesAdvanced → Startup and Recovery → Settings → “Write debugging information” → select “Kernel memory dump” or “Complete memory dump.” After the next crash: a .dmp file appears in C:WindowsMEMORY.DMP (or %SystemRoot%Minidump for minidumps).
These dump files can be opened in WinDbg (free download from Microsoft Store) → “!analyze -v” command → it automatically analyzes the crash and identifies the root cause. If you’re comfortable with Windows internals: this is the gold standard for crash diagnosis. If not: sharing the dump file with the app’s support team or posting it to communities like r/techsupport gives experts the raw data they need to pinpoint the issue.
Minidumps (small, quick) capture just the crashing thread. Full dumps (large, slower) capture everything in memory at crash time. For diagnosing driver crashes or system-level issues: full dump. For app-specific crashes: minidump is usually sufficient.
Third-party DLL injection
Software that hooks into all running processes — game overlays (Steam, Discord, NVIDIA GeForce Experience), performance monitors, screenshot tools, some accessibility software — can cause crashes in any app they inject into. If an app crashes only when certain background tools are running but not otherwise: DLL injection is the cause.
Test: disable overlays. Steam: Settings → In-Game → disable “Enable the Steam Overlay while in-game.” Discord: Settings → Overlay → disable “Enable in-game overlay.” GeForce Experience: Settings → General → disable “In-Game Overlay.” Then test if the crashing app is stable. If it is: the overlay was conflicting. Re-enable them one at a time to find which.
Recent Windows Update causing crashes
If apps started crashing after a recent Windows Update: check whether rolling back the update resolves them. Settings → Windows Update → Update history → Uninstall updates → find and uninstall the most recent KB update from the last week.
Before doing this: note the KB number and check Microsoft’s Windows Health Dashboard for known issues. Sometimes Microsoft documents the crash behaviour and has a workaround, or the next cumulative update (typically pushed within a week or two for critical regressions) includes the fix. Rolling back a major update is disruptive; trying the known workaround first is less effort.
Clean boot for isolation
When you can’t determine which software is causing crashes: Clean Boot removes all non-Microsoft startup items and services, effectively testing Windows without third-party software running in the background. Win+R → msconfig → Services tab → “Hide all Microsoft services” → “Disable all” → Startup tab → “Open Task Manager” → disable all startup items → restart.
In Clean Boot state: if the app no longer crashes, one of the disabled third-party services or startup items was the cause. Re-enable them in groups of 5 → restart → test → crash returns → narrow down which group → enable one at a time. This binary search approach identifies the conflict efficiently without guessing.
After identifying the cause: look up that service or software for update or compatibility issues. Sometimes the fix is simply updating the conflicting software to a version that works with the current Windows 11 build. Restart normally after Clean Boot testing — Windows doesn’t stay in Clean Boot mode unless you explicitly keep it there.
One last thing worth mentioning: Windows 11’s error reporting system (Windows Error Reporting, WER) submits crash data to Microsoft automatically for most apps. For apps you develop or maintain: this data is accessible in the Microsoft Store Partner Center or Dev Portal. For consumer apps: it means Microsoft and the app developer have crash data from your machine even when you haven’t explicitly reported anything. When a widespread crash pattern exists, fixes often arrive through updates within days — keeping apps and Windows updated is often the most efficient resolution for app crash problems that started after a specific update. Our guide on Chrome Tab Keeps Crashing covers an adjacent issue.
