OBS Log Analyzer

The log contains an Auto-Config Wizard run. Results of this analysis are therefore inaccurate. Please post a link to a clean log file.
To make a clean log file, please follow these steps:

1) Restart OBS.
2) Start your stream/recording for about 30 seconds. Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your stream/recording.
4) Select Help > Log Files > Upload Current Log File. Send that link via this troubleshooting tool or whichever support chat you are using.

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): Main Audio

Warning Old Version (28.0.1)

You are running an old version of OBS Studio (28.0.1). Please update to version 30.1.2 by going to Help -> Check for updates in OBS or by downloading the latest installer from the downloads page and running it.

Warning Wi-Fi Streaming

In many cases, wireless connections can cause issues because of their unstable nature. Streaming really requires a stable connection. Often wireless connections are fine, but if you have problems, the first troubleshooting step would be to switch to wired. We highly recommend streaming on wired connections.

Warning Windows 10 21H2 (EOL)

You are running Windows 10 21H2, which has not been supported by Microsoft since June 2023. We recommend updating to the latest Windows release to ensure continued security, functionality, and compatibility.

Warning Windows 10 Game DVR

To ensure that OBS Studio has the hardware resources it needs for realtime streaming and recording, we recommend disabling the "Game DVR Background Recording" feature via these instructions.

Warning Capture Interference

Display and Game Capture Sources interfere with each other. Never put them in the same scene.

Warning Multiple Game Capture

Multiple Game Capture sources are usually not needed, and can sometimes interfere with each other. You can use the same Game Capture for all your games! If you change games often, try out the hotkey mode, which lets you press a key to select your active game. If you play games in fullscreen, use 'Capture any fullscreen application' mode.

Info Not Admin

OBS is not running as Administrator. This can lead to OBS not being able to Game Capture certain games. If you are not running into issues, you can ignore this.

Info Non-Default x264 Preset

A slower x264 preset than 'veryfast' is in use. It is recommended to leave this value on veryfast, as there are significant diminishing returns to setting it lower. It can also result in very poor gaming performance on the system if you're not using a 2 PC setup.

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 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.