Crash loop on launch

Overview

OBS crash-loops during startup before you can change settings. This playbook is part of the crashes diagnostics family on OBS-Studio.net and focuses on concrete OBS Studio remediation rather than generic PC advice.

When you see symptoms matching Crash loop on launch, open Help → Log Files → Upload Current Log (or analyze a local log) and keep the Stats dock visible while reproducing. Note whether the problem is present in Preview only, Program output, a platform VOD, or a local recording. Those four observation points prevent chasing the wrong subsystem.

Work top-down: confirm OS permissions and device availability, then capture method, then scene complexity, then encoder capacity, then network delivery. Changing bitrate will not repair a black Game Capture hook, and reinstalling OBS will not repair a full disk. Each section below is written so you can apply fixes in order and stop when Stats and a short test recording look healthy.

Related OBS surfaces you will use repeatedly include Settings → Video (canvas, output, FPS, downscale filter), Settings → Output (encoder, rate control, recording format), Settings → Audio (devices and sample rate), source properties for Game/Display/Window Capture, Advanced Audio Properties for sync offsets and tracks, and the Stats dock counters for rendering lag, encoding lag, and network dropped frames.

If a plugin is in the blast radius, launch Safe Mode to prove stock OBS behavior, then reintroduce plugins one at a time. Keep scene collection backups before large rebuilds. Prefer MKV recordings with remux for crash-safe local files while you iterate.

Symptoms

Use this checklist against Crash loop on launch. Matching several items increases confidence you are in the right playbook.

• Crash immediately on open
• Reinstall alone does not help
• Log ends during plugin or GPU init

Also note what still works: mic versus desktop audio, Display Capture versus Game Capture, local recording versus live ingest, and whether Safe Mode changes the outcome. Those contrasts isolate hooks, permissions, encoders, and network paths quickly.

Fast checks

1. Reproduce once with the Stats dock open and write down rendering lag, encoding lag / skipped frames, and network dropped frames.
2. Create a 60-second local MKV recording of the failing scene to separate preview-only bugs from real output bugs.
3. Toggle to a minimal scene with a Color Source only; if the issue vanishes, scene complexity or a specific source is implicated.
4. For capture issues, A/B Game Capture, Window Capture, and Display Capture without changing encoder settings.
5. For encode issues, switch temporarily to a hardware encoder or a faster x264 preset and retest the same scene.
6. For network issues, lower bitrate 30% on Ethernet with dynamic bitrate enabled and compare dropped-frame counters.

These fast checks for Crash loop on launch usually identify the subsystem in under ten minutes before deeper repairs.

Likely causes

Common and occasional causes for this issue:

• Plugin crash at load
• GPU driver crash
• Corrupt configuration
• Broken graphics module

Do not assume a single cause. Multi-GPU laptops often combine affinity mistakes with Game Capture hooks; audio echo often combines Monitor and Output routing with open speakers; disconnects often combine Wi-Fi loss with an overly optimistic bitrate. Treat the list as a prioritized hypothesis set.

• Plugin crash at load (common) — Documented cause for Crash loop on launch: Plugin crash at load
• GPU driver crash (occasional) — Documented cause for Crash loop on launch: GPU driver crash
• Corrupt configuration (occasional) — Documented cause for Crash loop on launch: Corrupt configuration
• Broken graphics module (rare) — Documented cause for Crash loop on launch: Broken graphics module

Detailed fixes

Apply repairs in order. Retest after each major change so you know which step helped.

1. Step 1: Use Safe Mode
2. Step 2: Rename/move the plugins folder to test
3. Step 3: Update or roll back GPU drivers
4. Step 4: Start with a fresh profile/scene collection for testing
5. Step 5: Check OS reliability logs for GPU faults

After the primary fixes, remove temporary test changes you no longer need, document the final encoder and capture settings that worked, and keep a known-good scene collection backup. If nothing above moves Stats in the right direction, capture a fresh log during a failure window for pattern matching.

1. Repair: Use Safe Mode

   Use Safe Mode

   Retest the original trigger for Crash loop on launch before continuing to the next repair step.

   Change one major variable at a time and keep a scene collection backup.

2. Repair: Rename/move the plugins folder to test

   Rename/move the plugins folder to test

   Retest the original trigger for Crash loop on launch before continuing to the next repair step.

3. Repair: Update or roll back GPU drivers

   Update or roll back GPU drivers

   Retest the original trigger for Crash loop on launch before continuing to the next repair step.

Verification

• Stats counters that were elevated for this issue trend toward zero during a five-minute stress test.
• A local MKV recording reviewed in a player shows correct video and audio sync for the failing scenario.
• If this was a live issue, a platform preview or VOD confirms the repair beyond OBS preview.
• Safe Mode versus normal mode behave consistently after plugin cleanup (when plugins were involved).
• Reboot once and re-verify; some permission and driver changes only stick after a clean relaunch.

Verification for Crash loop on launch is not complete until you reproduce the original trigger (game launch, alert spam, long session, Wi-Fi idle, etc.) without regression.

1. Verify Stats and output for Crash loop on launch

   Run a five-minute reproduction with Stats visible. Confirm the counters associated with this issue improved, then review a local MKV and/or platform preview.

Common mistakes

• Raising bitrate to “fix” encoder overload or rendering lag.
• Reinstalling OBS repeatedly without isolating plugins via Safe Mode.
• Running everything as Administrator permanently on Windows without a documented need.
• Chasing preview artifacts when Program/VOD output was already correct (or the reverse).
• Ignoring disk free space and antivirus locks while debugging “corrupt” recordings.
• Pasting stream keys into public screenshots or unredacted logs.

Avoid shotgun changes. Change one variable at a time for Crash loop on launch so the working configuration is reproducible.

Operating-system notes

Windows crash dumps, macOS Consoles, and Linux coredumps/journals help pinpoint modules.

Regardless of OS, keep GPU drivers current from the vendor, prefer wired networking for live output, standardize audio on 48 kHz when possible, and treat permissions prompts as first-class failures rather than background noise.

Version notes

These guidance notes target current OBS Studio feature surfaces (Stats docks, Safe Mode, MKV remux, Browser Source shutdown-when-not-visible, hardware encoders, and PipeWire capture where applicable). If you are on a significantly older OBS build, update before deep troubleshooting—plugin ABIs and encoder UIs change across major versions.

After updating OBS, reinstall or update third-party plugins to builds that explicitly support your new version. Legacy encoder plugins are a frequent source of duplicate NVENC entries and init crashes.

FAQ

Delete scenes?

Back up first. Try Safe Mode and plugin isolation before destroying collections.

GPU drivers?

A clean driver install fixes a surprising number of launch crashes.