How to Read OBS Studio Crash Logs for Plugins

OBS Studio crashes are often caused by outdated, corrupted, or incompatible third-party plugins. This guide will walk you through locating your OBS Studio crash logs, identifying the specific crashed thread, pinpointing the faulty plugin file, and resolving the issue to restore your software’s stability.

Step 1: Locate and Open the Crash Log

To diagnose the issue, you must first access the log file generated during the crash.

  1. Open OBS Studio (if it is able to open).
  2. Go to the top menu and select Help > Crash Reports > Show Crash Reports. This opens the folder containing your crash files.
  3. If OBS Studio will not open, press Win + R on your keyboard, type %APPDATA%\obs-studio\crashes, and press Enter.
  4. Open the most recent crash log file (usually named with a date and timestamp) using a standard text editor like Notepad.

Step 2: Identify the Crashed Thread

The top section of the crash log contains essential metadata about the crash, including the “Crashed Thread.”

  1. Look near the top of the file for a line that reads Crashed Thread: [Number] (for example, Crashed Thread: 14).
  2. Scroll down through the log until you find the section corresponding to that specific thread, labeled as Thread [Number] (for example, Thread 14 (crashed):).

Step 3: Analyze the Stack Trace for Plugin Files

Under the crashed thread header, you will see a list of files and memory addresses known as a “stack trace.” The software reads this list from bottom to top (or top to bottom, depending on the error) to show the sequence of events leading to the failure.

  1. Look at the names of the dynamic link library (.dll on Windows, .so on Linux, or .dylib on macOS) files listed in the crashed thread.
  2. Standard OBS files typically start with obs, libobs, or w32-pthreads. Ignore these initially.
  3. Search for third-party file names. Common examples of plugin-related files include:
    • obs-ndi.dll (NDI Integration)
    • obs-virtualcam.dll (Virtual Camera)
    • streamelements.dll or obs-se.dll (StreamElements SE.Live)
    • move-transition.dll (Move Transition plugin)
    • win-capture-audio.dll (Application Audio Capture)

The file name listed at the very top of the crashed thread’s stack trace is almost always the direct cause of the crash.

Step 4: Resolve the Faulty Plugin Issue

Once you have identified the filename of the problematic plugin, you can resolve the crash using one of the following methods: