OBS is buggy, everything freezes and then becomes "not responding"

1

11closed

New Member
I installed OBS and configured it according to my needs, but in the last few days OBS started showing me a bug that I can't solve at all.

It keeps crashing all the time, the "preview" freezes, I can't see the scenes I'm putting in, when I ACTIVATE a song and then deactivate it, it keeps playing, until OBS crashes completely and becomes "not responding". All these bugs, without even recording, and this with OBS stopped.

I don't know what to do with this program anymore, it's really frustrating to work with OBS, every week a new bug, every update a different bug.

Does anyone know how to solve this problem? I've already reinstalled the program and it didn't work.
 
L

Lawrence_SoCal

Active Member
1. you describe having a problem, not necessarily bugs... and you ignored the pinned post in this forum about posting your OBS Studio log when asking for help/support (link in my .sig)

it is entirely possible to configure settings ('to your needs') which your rig is NOT capable of supporting, either at all, or with other processes running.

Best guesses include PoS plugins like streamelements (especially if not properly configured, and not even sure that is possible), Operating System 'issues', under-powered computer for desired OBS Studio output, and/or wrong OBS Studio settings for systems capabilities.

Using auto-config for settings is best placed to start with OBS Studio. After that, you pretty much need to know what you are doing, and there are LOTS of bad tutorials out there, so beware. OBS Studio can have a fairly steep learning curve
 
1

11closed

New Member
ok, I found the log here: https://obsproject.com/logs/SXiShMy8oaBOZCCy

in "%APPDATA%\obs-studio\logs" everything is empty

When I'm working on OBS it freezes and doesn't come back, anything I do it freezes, without even recording or doing live, it freezes.

I recently formatted my PC and reinstalled it completely, before OBS worked normally on my PC, without freezing.

my PC configuration

Xeon E5-2640 v3 @ 2.60GH
RAM: 80.0 GB
RTX 3060TI 8gb

there at the end of the log, everything was fine, when I tried to create a "Game Capture 2" in "Scene 2" OBS froze, this happens several times trying to create other sources too

How do I fix it?
 
Last edited:
1

11closed

New Member
I did a new test here and the log gave these errors


03:33:04.188: device_vertexbuffer_create (D3D11): Failed to create buffer (887A0005)
03:33:04.188: Device Removed Reason: 887A0006
03:33:04.188: device_draw (D3D11): No vertex buffer specified
03:33:04.188: device_vertexbuffer_create (D3D11): Failed to create buffer (887A0005)
03:33:04.188: Device Removed Reason: 887A0006
03:33:04.188: device_draw (D3D11): No vertex buffer specified
03:33:04.188: Device Remove/Reset! Rebuilding all assets...
03:33:12.933: Failed to rebuild shared texture: 0x80070057
03:33:12.934: Failed to rebuild shared texture: 0x80070057
03:33:12.938: Failed to rebuild shared texture: 0x80070057

Is there a program or driver missing, because my PC was recently formatted and apparently I have all the drivers installed?
 
koala

koala

Active Member
This "Device Remove/Reset! Rebuilding all assets.." indicates a graphics driver crash.

Make sure you installed the most current supported driver for your GPU. If you already did that, it's a sign of hardware failure. Revert overclocking, check overheating, check power supply, check cabling and seating. It may be some incompatibility between GPU and mainboard (the CPU is a 10 year old server CPU, not the best partner for a RTX 3060). Or the GPU has simply become defective.
 
koala

koala

Active Member
As far as I understand that article, it's all about the driver, not the user software using the driver. If a timeout happens, it's the driver's fault, or the hardware's fault the driver is choking upon. Not the app's fault.

Otherwise, since a driver is doing its work not on its own but always due to some app calling its API, it could always be said it's the app's fault, and send the app developer on a fool's errand, because he cannot do anything about it if the hardware or the driver is faulty. And you would send the OP on a fool's errand with this assertion, making him looking for software updates and configuration changes, which doesn't exist and will never exist, when the only way to fix the issue is to fix the hardware.

The issue being a hardware defect on the user device is supported by the fact it's not a widely seen issue from all kind of OBS users using some specific hardware build. Such ting has happened before, and was fixed in some GPU driver update, but in this case there are not enough reports to assume it's a similar case. It's a rather old hardware, if it was a general issue with that hardware, we would have seen it before.
 
R

rockbottom

Active Member
That log is a shitshow & HAGS is enabled, disable it. There's more crap in the way that needs to be eliminated.
23:16:17.425: HAGS Status: Enabled (Default: No, Driver status: Supported)

Create a New Scene Collection for testing, add just (1) Scene/Source & see what happens.
 
R

rockbottom

Active Member
When was the 3060 installed? Did you use DDU prior to removing the old GPU or at any point since it's been installed?
 
R

rockbottom

Active Member
Your current driver is from August 2024. It's new enough to run OBS but if you need to try DDU, you're going to need to install a new driver. I would avoid installing any of the 572.xx drivers, they have proven to be unreliable. Use 566.36 if needed. It's the last driver released before the 5000 series hit the scene.
 
You must log in or register to reply here.
Top