Discord Keeps Crashing or Closing: Startup, Calls, Sharing and Gaming Checks

Step 1｜Distinguish minimizing, call disconnection and app exit

A window disappearing is not enough to identify a crash.

Time: Compare one change at a time

1. Check whether voices continue and whether others saw you leave. Open hidden notification-area icons and try restoring the window through Discord’s icon.
2. If conversation continues and the window returns, inspect close/minimize behavior first; reinstalling is not the first step.
3. Open Task Manager with Ctrl+Shift+Esc and inspect Discord processes. A remaining process with an unresponsive window can still mean part of the app stalled.
4. If the app responds but the call disconnected, use the call-disconnects guide. If the window closes and a startup logo appears again, record the restart time and consult Step 6.

Discord normally uses multiple processes. Several entries are not inherently abnormal, and one remaining process does not prove the app is healthy.

Step 2｜For startup exits, fully quit and compare the browser

When settings cannot stay open, inspect launch behavior before looking for in-app switches.

Time: Compare one change at a time

1. Quit Discord from the notification area, end remaining Discord processes in Task Manager and restart Windows. Open Discord once from Start.
2. Allow an update to finish. If a specific message such as Update Failed appears, record it and use the update-failed guide.
3. On the same PC, open https://discord.com/app and check that the same account’s conversation list loads. A public introduction page is not an equivalent comparison.
4. If the browser works, prioritize the app and follow the cache-preservation procedure in the not-opening guide. If that does not help, continue to Step 7.
5. If the browser also fails, inspect Discord Status and the exact error. Distinguish sign-in failure, connection errors and app exits rather than assuming one shared cause.

Step 3｜For call-start crashes, compare audio devices with video off

Starting voice, camera and sharing together obscures which operation triggered the exit.

Time: Compare one change at a time

1. With camera and sharing off, join voice with the same person. If voice alone is stable, continue to Step 4 for the video trigger.
2. Record input/output choices under Voice & Video and select intended devices by name. If using virtual audio or voice effects, compare the physical microphone/headphones directly.
3. If alternatives are available, change input first, then output, testing the same call after each change. Record which device change affects the result; do not replace all devices at once.
4. If one device consistently triggers it, consult that manufacturer’s connection/driver guidance. If only the app keeps failing, compare the same voice call in the browser.
5. For app-only failure, record devices and keybinds before trying Reset Voice and Video Settings under the available Debugging section. Reselect devices and repeat the call; restore needed preferences afterward.

Step 4｜For camera/share crashes, compare the target and graphics setting

An exit when starting video does not establish a GPU fault.

Time: Compare one change at a time

1. Confirm voice-only stability, then start camera alone or screen sharing alone. Record exactly which operation precedes the exit.
2. For screen sharing, compare a blank Notepad window with the affected game using the same sharing method. If failure is target-specific, record the application and display mode.
3. In User Settings → Advanced, record Hardware Acceleration and compare its opposite state after restarting Discord. Keep the same target, settings and participant.
4. If the alternate state helps, compare for your normal usage duration. If not, restore it before checking drivers through the GPU/PC maker’s official procedure. Do not change setting and driver together.
5. If the issue began immediately after a driver update, record both versions and use the GPU-driver guide’s rollback guidance. If only the picture stops while Discord responds, use the screen-sharing guide.

This comparison concerns the Advanced graphics setting. Do not also change Voice & Video processing settings in the same comparison.

Step 5｜For gaming or later crashes, compare optional features and load

Change one companion feature and compare time to failure; high utilization alone is not a diagnosis.

Time: Compare one change at a time

1. Record the game, scene and elapsed time before failure. Inspect CPU, memory and GPU in Task Manager’s Processes view and note apps increasing load.
2. If recording and streaming are both active, stop only one and repeat the scene. Improvement prioritizes the conditions involving that feature.
3. In Discord User Settings, find Overlay/Game Overlay, record its state and disable the overlay for comparison with the same game. Restore it if unhelpful; if it helps, keep the observed working choice and record the conditions.
4. If failure normally occurs after about thirty minutes, two stable minutes do not establish recovery. Compare a similar duration where practical and explicitly record a shorter test as limited.
5. If the game/other apps also fail or the PC restarts, inspect Step 6’s history and investigate the PC. Do not repeatedly reinstall only Discord.

Step 6｜For silent exits, compare Windows reliability history

Use event times as evidence; a displayed filename alone is not a diagnosis.

Time: Compare one change at a time

1. Press Windows+R, enter perfmon /rel and press Enter. Select the date of the exit in Reliability Monitor.
2. Look for a Discord-related failure among critical events. Open available technical details and record the time, app, faulting module and exception code shown.
3. Match the time against your action immediately before the exit. Do not delete a named DLL or replace it with a copy from a download site.
4. Record simultaneous game/other-app failures and unexpected Windows shutdowns too. For whole-PC freezing, blue screens or restarts, use the corresponding common troubleshooting guides.
5. No entry does not prove nothing failed. Record the disappearance time, whether the call dropped and whether a startup logo returned, then compare the next occurrence.

Step 7｜For persistent app-only crashes, verify local folders before reinstalling

Use this later step when the browser performs the same action and the relevant feature checks have not helped.

Time: Compare one change at a time

1. Confirm access to your email, password and two-factor method; record needed device/keybind settings. Keep an already signed-in second device signed in. Stop if you cannot sign back in.
2. Fully quit Discord. Uninstall it through Windows Settings → Apps → Installed apps (Apps & features on Windows 10).
3. Use Windows+R to open %appdata%, then %localappdata%, separately. Identify only the remaining Discord folder in each location; do not delete AppData, Roaming or Local itself.
4. Copy needed local data elsewhere, keeping the two locations distinguishable, before following Discord’s reinstall procedure for those remaining Discord folders. If a folder is in use, inspect remaining Discord processes; stop if the target is uncertain.
5. Restart Windows and install from https://discord.com/download. After signing in, test normal startup, then the original failing call/share action. Do not restore the entire old folder over the fresh installation.

Server memberships and sent messages are associated with the account, but local preferences may need reconfiguration. Keep preserved folders/logs private and share only the support details required.