OBS Log Analyzer

This analyzer will review an OBS log file for common issues and problems and provide suggestions for how to solve them.


In OBS select Help > Log Files > Upload last Log File. Copy the URL and paste it here.

Upload a log file to check for configuration problems, incorrect settings, network issues and many other diagnostics.




Log Analysis

View entire log file
Critical Max Audio Buffering
Audio buffering hit the maximum value. This is an indicator of very high system load, will affect stream latency, and may even cause individual audio sources to stop working. Keep an eye on CPU usage especially, and close background programs if needed.

Occasionally, this can be caused by incorrect device timestamps. Restart OBS to reset buffering.

Source affected (potential cause): Urządzenie audio
Critical Hardware-accelerated GPU Scheduler
The Hardware-accelerated GPU scheduling ("HAGS") feature added with Windows 10 is currently known to cause performance and capture issues with OBS, games and overlay tools. It's an experimental feature and we recommend disabling it via this screen or these instructions.
Warning Browser Not Accelerated
Browser hardware acceleration is currently disabled. Enabling acceleration is highly recommended due to the improvements to performance and significantly lower CPU usage for browser sources. This can be enabled in Settings -> Advanced.
Warning Mismatched Sample Rates
At least one of your audio devices has a sample rate that doesn't match the rest. This can result in audio drift over time or sound distortion. Check your audio devices in Windows settings (both Playback and Recording) and ensure the Default Format (under Advanced) is consistent. 48000 Hz is recommended.
OBS Sample Rate: 48000 Hz
IN 1-2 (BEHRINGER UMC 204HD 192k): 44100 Hz
OUT 1-2 (BEHRINGER UMC 204HD 192k): 44100 Hz
Info Windows 11 24H2 (OK)
You are running Windows 11 24H2, which will be supported by Microsoft until October 2026.
Info 0.1% Rendering Lag
Your GPU is maxed out and OBS can't render scenes fast enough. Running a game without vertical sync or a frame rate limiter will frequently cause performance issues with OBS because your GPU will be maxed out. OBS requires a little GPU to render your scene.

Enable Vsync or set a reasonable frame rate limit that your GPU can handle without hitting 100% usage.

If that's not enough you may also need to turn down some of the video quality options in the game. If you are experiencing issues in general while using OBS, your GPU may be overloaded for the settings you are trying to use.

Please check our guide for ideas why this may be happening, and steps you can take to correct it: GPU Overload Issues.
Info Encoder start error
An encoder failed to start. This could result in a bitrate stuck at 0 or OBS stuck on "Stopping Recording". Depending on your encoder, try updating your drivers. If you're using QSV, make sure your iGPU is enabled. If that still doesn't help, try switching to a different encoder in Settings -> Output.
Info 0.1% Encoder Overload
Encoder overload may be related to your CPU or GPU being overloaded, depending on the encoder in question. If you are using a software encoder (x264) please see the CPU Overload Guide. If you are using a hardware encoder (AMF, QSV/Quicksync, NVENC) please see the GPU Overload Guide.
Info Windows Game Mode
In Windows 10 versions 1809 and newer, we recommend that "Game Mode" be enabled for maximum gaming performance. Game Mode can be enabled via the Windows 10 "Settings" app, under Gaming > Game Mode.