OBS Hang after closing a game

westk

New Member
Hello, again I´m having issues with OBS and games. The new issue is even worst because I just want to close a game in full screen and OBS freeze and the stream ends. Usually this happen with alt tabbing games but this is too much already.
 

Attachments

Thank you for providing a log.

1. In Windows, we recommend that "Game Mode" be enabled. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
2. The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. We recommend disabling it via these instructions as a troubleshooting step. Be sure to restart after disabling it.
3. Multiple Game Capture sources are usually not needed, and can sometimes interfere with each other (scenes Stream, HLL-Script2 and HLL-Script). 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.

I would also recommend lowering the resolution on your Elgato Facecam 4K from 3840x2160 to 2560x1440 or lower.

If still having issues, please provide a new log as your log contains no streaming session. Results of this log analysis are limited. 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 for at least 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.
4) Select Help > Log Files > Upload Current Log File. Send that link here.
 
If I disable HAGS is even worst. The OBS program is slow and laggy like any other task on PC depending on GPU. This issue also happen without the camera.
 
You've an extreme excess of game sources and browser sources.
Normally you don't need more than one game source per scene. If a game needs an special treatment, like a color filter, then create a new scene for this game with it's own separated game capture.

Also, 16 Gb of RAM is too low for streaming/recording at 1440p while gaming at 4k. You need no less than 32Gb. Or reduce the Windows resolution to 1440p and stream/record at 1080p.
 
Last edited:
Yesterday happened again. This time with a new game (ready or not). I just close the game and OBS crash. "Failed to recreate D3D11: Failed to create swap RTV (80070057)"

I have 32GB and never had any issues with previous versions of OBS/GPU driver.
 

Attachments

You've an extreme excess of game sources and browser sources.
Normally you don't need more than one game source per scene. If a game needs an special treatment, like a color filter, then create a new scene for this game with it's own separated game capture.
 
Last night I was playing HLL perfectly, I closed the game, open Ready or not, played one round and I want to see something in the desktop so I press the WIN key and everything crashed (OBS mainly). I started to use fullscreen windowed and seems to be very effective.
 

Attachments

Windows Game Mode do help so you should enable it.
HAGS is known to cause issues. Disabling it is recommended.
You're stuck on an old Windows version with no updates, which may cause troubles with newer GPU drivers.
Try removing aitum-multistream and see if this helps.
 
Crashed in the log posted today as well.
23:09:06.806: Device Remove/Reset! Rebuilding all assets...

23:11:12.229: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 1897 (0.4%)
23:11:12.229: Video stopped, number of skipped frames due to encoding lag: 747/479817 (0.2%)

Rendering lag is GPU overload, plain & simple.

Your Main monitor is running in HDR using far more resources than it would if it was in SDR.
20:53:12.958: name=Q27G3XMN
20:53:12.958: pos={0, 0}
20:53:12.958: size={2560, 1440}
20:53:12.958: attached=true
20:53:12.958: refresh=180
20:53:12.958: bits_per_color=10
20:53:12.958: space=RGB_FULL_G2084_NONE_P2020

HAGS was mentioned as a possible cause. I would also check for a driver conflict. Make sure there not something hanging around that should be long gone.
 
Back
Top