OBS Keeps Crashing - How to Fix It

"OBS keeps crashing" is four words covering about six unrelated faults. That is why generic fix lists so often fail: they hand you ten things to try, you try all ten, and you never learn which one mattered or whether it will happen again tomorrow.

There is a better way, and it takes about two minutes. OBS writes a crash report every single time it dies, naming the exact component that killed it. Almost nobody opens it. Once you do, you stop guessing and start fixing one specific thing.

This guide is the triage hub. We will read the report, identify your fault, then fix it here or send you to the guide that covers it properly.

Step 1: Read the Crash Report

Every crash leaves a dated report behind.

1. Press Windows Key + R, enter %appdata%\obs-studio\crashes, and press Enter. On macOS, open Help > Log Files > Show Log Files.
2. Open the newest file by timestamp.
3. Read the top block, headed Thread stack. Ignore the hexadecimal noise. You are looking only for filenames in the first ten or so lines.

Whatever is named at the top was executing when OBS died. Match it here:

That last row is the most common mistake. A frozen window and a crashed process are different failures with different fixes, and there is no crash report for a freeze because the process never died.

Step 2: Confirm With Safe Mode

Safe Mode loads OBS with zero third-party plugins, scripts or custom overlays, which makes it a clean one-shot test for the most likely culprit.

If OBS crashed last session it offers Safe Mode automatically on next launch. Say yes. To force it, right-click your OBS shortcut, choose Properties, and add --safe-mode to the end of the Target field.

• Stable in Safe Mode: your hardware and drivers are fine. It is a plugin. Continue to Step 3.
• Crashes in Safe Mode too: skip to Step 4.

While you are here, run Help > Check File Integrity. It verifies your install against the official manifest and re-downloads anything corrupted, which is a genuine fix after a failed update, though a rare one.

Step 3: Isolate the Plugin (The Canonical Procedure)

Plugins cause more OBS crashes than everything else combined, and they cluster hard right after an OBS update. A plugin compiled against OBS 30 does not politely decline to load in OBS 31. It executes against an API that moved and takes the process down with it.

Plugins live in two places, and people forget the second one:

• C:\Program Files\obs-studio\obs-plugins\64bit for system-wide installs
• %appdata%\obs-studio\plugins for per-user installs

With one suspect from the crash report, move that plugin's files out of the folder to your desktop, relaunch, and confirm.

With no clear suspect, bisect rather than remove them one at a time. Move half your plugins out and relaunch. If it is stable, the culprit is in the half you moved. If it still crashes, it is in the half you kept. Halve again. Eight plugins takes three tests this way rather than eight.

Once identified, check the developer's page for a build matching your OBS version. If there is not one, that plugin is not compatible with the OBS you are running, and no amount of configuration changes that.

Step 4: When Safe Mode Crashes Too

If OBS dies with every plugin disabled, the fault is in your configuration or your graphics stack.

Reset the configuration. Close OBS, press Windows Key + R, enter %appdata%, and rename the obs-studio folder to obs-studio-backup. Relaunch, and OBS builds a clean profile. If that fixes it, your old settings were corrupt, and you can copy basic\scenes back from the backup to recover your scene collections. (If OBS never draws a window at all, the startup guide maps this more precisely: OBS Freezes on Startup.)

Give OBS a fair share of the GPU. Open Settings > System > Display > Graphics in Windows, find OBS Studio or browse to obs64.exe, click Options, and set High performance. On a laptop this stops OBS being handed the integrated GPU while your dedicated card idles.

Run as administrator only if you are capturing an app that itself runs elevated. It is not a general-purpose fix, despite how often it is repeated. An unelevated OBS captures a black frame from an elevated app rather than crashing, so if that is your symptom you want the black screen guide instead: OBS Recording Black Screen Fix.

If It Crashed Mid-Recording

Fixing the crash does not bring back the take. Whether that file is recoverable depends entirely on the container you recorded into, and the answer is decided in seconds by looking at its extension.

Go to OBS Crashed Mid Recording: Is the File Recoverable? first, before you touch anything, then come back here to stop it happening again.

The Question Underneath All of This

Work back through what this guide asked of you. Read a stack trace. Bisect a plugin folder. Reason about GPU assignment on a hybrid laptop. Those are systems administration skills, and OBS asks for them because it is a broadcast platform with an open plugin architecture. That openness is exactly why it is unbeatable for live production, and the crashes are the direct cost of it.

The question is whether you are getting anything for that cost. If you are recording product demos, onboarding videos or course modules, you are paying a live broadcaster's maintenance bill for features you never load. Cubix Capture has no plugin API to break against an update, because it does one job and ships the pieces to do it.

Time spent reading crash reports is time not spent recording.

Keep Reading

• OBS Freezes on Startup: Fix Guide maps a launch freeze to its exact stage.
• OBS Not Responding: What to Do for a hang rather than a crash.
• OBS Keeps Freezing on Windows 11 for OS-level graphics causes.
• OBS Crashed Mid Recording: Is the File Recoverable? to rescue the take you lost.
• OBS Crashed and Recording Corrupted: Can You Recover It? for the full file repair bench.