Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| Crash after a splash screen | Repair app data and inspect the crash record |
| Crash during video or 3D startup | Update the correct graphics driver and disable overlays |
| Crash after adding a plug-in | Remove or update that exact extension |
| Many apps close immediately | Check system files, security software and the user profile |
Diagnose app crashes at launch before making major changes
Launch the crashing app once and record how long it stays open, what action triggers the crash, and whether Windows shows an error. Note the exact time for Reliability Monitor.
Update the app, graphics/runtime dependencies, and Windows from official sources. Avoid downloading individual DLL files from third-party websites.
Test the app with extensions, overlays, or optional plugins disabled when possible, and compare with another app using similar graphics or runtime components.
Reliability Monitor is especially useful for immediate crashes. Record the faulting module and exception code, but verify the same module appears across repeated crashes before acting on it.
Back up projects, save files, profiles, and app settings before reset or reinstall. A crash-repair reinstall can remove local data depending on the app.
Capture the crash instead of repeatedly relaunching
Restart Windows, note the exact clock time and launch the app once. Open Reliability Monitor and look for the application failure at that time. Record the exception code and faulting module; do not delete files based only on an unfamiliar module name.
If the app creates its own safe mode, recovery launch or log, use it. A successful safe launch points to a plug-in, cached layout, hardware acceleration or user setting. Preserve projects before clearing configuration folders.
1Verification checkpoint
- Launch the app and reproduce the previous trigger.
- Confirm it stays open beyond the former crash point.
- If it crashes, compare the new module/code.
Remove the most likely conflict
Update the app from its official source. Temporarily disable game overlays, capture hooks, RGB utilities or third-party plug-ins one at a time. For graphics-heavy apps, install the device maker's supported driver and test hardware acceleration off only as a diagnosis.
Check Windows Security protection history before assuming antivirus interference. If a legitimate file was blocked, verify its signature and source before allowing it. Never create a broad antivirus exclusion for Downloads, the whole system drive or an unknown executable.
2Verification checkpoint
- Disable only the suspected overlay or extension if relevant.
- Retest the exact crash path.
- Restore unrelated add-ons that were not involved.
Repair dependencies and Windows components
Use Settings > Apps > Installed apps > Advanced options to Repair first and Reset only after backing up local data. Desktop software may offer Modify or Repair through its uninstaller. Reinstalling without removing corrupt user settings may reproduce the same crash.
Install Windows updates and restart. For failures across unrelated applications, run DISM before SFC and compare behavior in a clean boot or new local account. Escalate to an in-place Windows repair only after the crash remains system-wide.
3Verification checkpoint
- Restart and run the app again.
- Confirm stability survives reboot.
- Stop when the crash no longer reproduces.
Verify the repair and stop at the right point
Launch the app, reproduce the action that used to crash it, and keep it open for several minutes. Restart Windows and repeat once.
Once the crash no longer reproduces, stop changing runtimes or drivers. Keep note of the last successful change for future recurrence.
If the same app crashes in every account after clean reinstall and supported runtime/driver updates, use the publisher's logs or support path before altering Windows globally.
Technical order checked against Microsoft app repair guidance. Menus, policies and app options can vary by Windows edition, device management and publisher.
Frequently asked questions
Where can I see why an app crashed?
Reliability Monitor and Event Viewer can show the faulting application, module and exception code near the exact crash time.
Should I reinstall the app immediately?
Repair and isolate plug-ins or overlays first. A reinstall may not remove damaged settings stored in your profile.
Can a graphics driver crash a normal app?
Yes, especially apps using video, 3D rendering or hardware acceleration, but confirm the pattern before changing drivers.