OBS keeps crashing on startup, while streaming, or during recording?
✓ Reviewed & substantially updated July 30, 2026First identify what actually failed. If only OBS closes, collect its log and crash report. If OBS says Not Responding but Windows still works, test the active scene and external conflicts. If the entire PC freezes, restarts, or shows a blue-screen stop code, treat that as a Windows system crash rather than assuming the OBS app itself is broken.
The crash stage is the fastest clue. A failure on startup, while selecting a scene, when recording or streaming begins, or only on exit can involve different plugins, sources, graphics hooks, encoders or drivers. This guide follows OBS Project's support workflow: preserve the setup, reproduce once in a controlled test, collect the relevant evidence, then change one branch at a time.
Quick diagnostic route
- Back up profiles and scene collections
- Classify an OBS crash, hang, overload, or full-PC restart
- Collect the matching log or crash report
- Update OBS and compatible plugins
- Force OBS Safe Mode for a controlled test
- Test scenes, overlays, GPU and drivers separately
- Reduce encoder load only when the evidence fits
- Compare with a blank portable OBS instance
Match the symptom before changing settings
| What you see | Best first check | What it means |
|---|---|---|
| OBS closes or disappears but Windows remains usable | Save the OBS log and crash report | This is an OBS application-crash path |
| OBS is Not Responding but the rest of Windows works | Save the session log; test the active scene and conflicts | This is a hang and may not create an OBS crash report |
| OBS crashes on startup before the main window is usable | Force OBS Safe Mode and open the log folders directly | A third-party component, configuration, source, or external conflict |
| Crash begins when recording or streaming starts | Run one short private test and inspect the log | An encoder, GPU, driver, source, or resource branch |
| OBS stays open but shows “Encoding overloaded” or choppy output | Follow the performance branch, not the crash branch | A workload problem; this alone is not an application crash |
| The whole PC freezes, restarts, or shows a stop code | Stop repeat testing and record the Windows stop code/module | This is a system-stability path, not a normal OBS-only crash |
The 8 checks, from lowest to highest impact
Back up and describe the exact trigger
Export profiles and scene collections from OBS where possible. Write down whether the failure occurs on startup, a specific scene, recording start, stream start, source activation or exit. Note the last plugin, driver, Windows update, overlay or source changed.
Collect the correct log and crash report
After reproducing an app-only failure, use Help → Log Files to upload the current or previous log. For an actual crash, also use Help → Crash Reports → Show Crash Reports when available. If OBS will not stay open, press Win + R and open %APPDATA%\obs-studio\logs for session logs or %APPDATA%\obs-studio\crashes for crash reports.
Update OBS, plugins, and conflicting capture tools
Install the current supported OBS release from the official project and verify every third-party plugin against its publisher's compatibility information. Then close overlays and other capture tools for one comparison. OBS lists graphics-hook conflicts such as MSI Afterburner/RivaTuner, Discord overlays, Overwolf, FRAPS and simultaneous recorders. Disable one overlay or tool at a time; do not turn off all device security as a generic fix.
OBS crashes on startup: force Safe Mode and find the logs
Run OBS in its own Safe Mode
OBS Safe Mode is different from Windows Safe Mode. If OBS offers it after an abnormal close, choose it and reproduce the same action. If the prompt never appears, copy the OBS shortcut, open Properties, and add --safe-mode after the closing quote in the Target field. A typical target ends like obs64.exe" --safe-mode. OBS documents that this mode disables third-party plugins, scripts and WebSockets.
Test the suspect scene or source separately
Duplicate the scene collection, then disable sources in the scene that triggers the crash. Test browser sources, media files, capture devices and scripts individually. Leave the original collection intact.
Verify GPU selection and update its driver
On multi-GPU systems, follow OBS Project's GPU Selection Guide so OBS and the captured app use a compatible GPU arrangement. Install the graphics driver from the PC or GPU manufacturer, restart, and repeat the same controlled test.
Reduce encoding load only when it matches the symptom
Use this branch when the crash begins as recording or streaming starts, or when the log shows GPU or encoder pressure. For one private comparison, close only GPU-heavy apps you opened, cap the game's frame rate, reduce output from 60 to 30 fps, and simplify large browser/media sources. Change one item at a time and save the new log.
Test a blank OBS Portable Mode instance
A normal reinstall can reuse the same user configuration, so it is not always a clean comparison. Instead, download the official OBS ZIP, extract it to a user folder - not Program Files - and create an empty portable_mode.txt file in its root. Open bin\64bit\obs64.exe and test a blank scene without importing profiles, scenes or plugins. You can also start the ZIP build with --portable.
Why does OBS crash my PC? App crash vs Windows crash
If the entire computer freezes, reboots, or shows a blue/black stop-code screen, OBS may have exposed a hardware device, driver, software or another Windows system problem - but that event alone does not prove OBS caused it. Stop repeated recording tests. Photograph or write down the exact stop code and any “What failed” module, note new hardware or drivers, check that Windows has free disk space and current updates, then follow Microsoft's official unexpected-restart guidance.
Primary references: OBS Project's Launch Parameters, Portable Mode, Known Application Conflicts, Plugins Guide, Encoding Performance Troubleshooting, GPU Selection Guide, the official forum's log and crash-dump instructions, and Microsoft's unexpected restart and stop-code guidance.
Frequently asked questions
How do I open OBS in Safe Mode if it crashes on startup?
Copy the OBS shortcut, open Properties, and add --safe-mode after the executable path in the Target field. This is OBS Safe Mode - not Windows Safe Mode - and it disables third-party plugins, scripts and WebSockets for the test.
Where are OBS logs if OBS will not open?
Press Win + R and open %APPDATA%\obs-studio\logs. Crash reports, when OBS creates them, are in %APPDATA%\obs-studio\crashes. A session log and a crash report serve different purposes, so support may need both.
Why does OBS crash my whole PC?
A full freeze, restart or stop-code screen is a Windows system crash, not a normal OBS-only crash. Stop repeat testing, record the exact stop code and module, then check system and driver evidence using Microsoft's guidance.
Why does OBS crash when I start streaming or recording?
The timing points first to the active encoder, GPU load, driver, capture source or graphics-hook conflict. Save the problem-session log and run one lower-load private test before changing unrelated settings.
Does “Encoding overloaded” mean OBS crashed?
No. If OBS stays open, that message describes a performance problem. Cap game FPS, reduce output FPS or resolution, simplify costly sources, and compare logs. Use the crash branch only if the app closes or generates a crash report.
Why does OBS crash only when I close it?
Test OBS Safe Mode and update third-party plugins first. A shutdown-only crash does not normally justify resetting encoder settings or deleting every scene.
Still stuck? Send the exact crash stage, OBS version, Windows build, GPU/driver, relevant log and crash report - after removing personal details.
Send us the details →