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): EW

Critical 34.2% 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.

Warning Old Version (27.2.4)

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

Warning Integrated GPU

OBS is running on an Intel iGPU. This hardware is generally not powerful enough to be used for both gaming and running obs. Situations where only sources from e.g. cameras and capture cards are used might work.

Warning Windows 10 21H1 (EOL)

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

Warning Not Admin

OBS is not running as Administrator. Because of this, OBS will not be able to Game Capture certain games, and it will not be able to request a higher GPU priority for itself -- which is the likely cause of the render lag you are currently experincing. Run OBS as Administrator to help alleviate this problem.

Warning 9.4% 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.

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
Microphone (DroidCam Virtual Audio): 16000 Hz

Info Dynamic Bitrate

Dynamic Bitrate is enabled. Instead of dropping frames when network issues are detected, OBS will automatically reduce the stream quality to compensate. The bitrate will adjust back to normal once the connection becomes stable. In some (very specific) situations, Dynamic Bitrate can get stuck at a low bitrate. If this happens frequently, it is recommended to turn off Dynamic Bitrate in Settings -> Advanced -> Network.

Info Third-Party Plugins (2)

You have the following third-party plugins installed:

obs-ndi
droidcam-obs