OBS freezes and kill the live streaming

[TheEnigmist]

Hello,

I've a strange problem with OBS v28/29 . I was able to play RE8 during streaming w/o any problem using NVIDIA Broadcast with virtual greenscreen + mic noise cancelling.
After I updated to OBS 28 (and now to 29) I've really a bad behaviour from OBS.

I added on Virtual Greenscreen directly on webcam source. I use it so I can do some advanced scenes during streaming.
I added noice reduction on mic source too so I get rid off nvidia broadcast. Now everything is living on OBS.

Now the problem. When using OBS during gameplay sessions sometimes it completly freezes, the live freezes as well and only audio can be heard. As soon as I click on OBS it stop working and I need to force kill it.
From logs it doesn't appear error or some message that address to some crashes.

I read here a fix, turning off Windows GPU scheduling, but it doens't fixed the problem.

What I see on task manager is that GPU/CPU goes to 100%.
My system is:
- Ryzen 5 3600
- RTX 3070
- 16GB RAM

I'm wondering to move on a better system, but I want to be sure is related to my low system instead of some internal bug of OBS

 

[TheEnigmist]

Last crash was yesterday during Dead Space Remake stream.
The behaviour is this:
It runs well for 30/60 min, then it start lags, then it freezes and I need to force quit OBS. What could be the problem? Broken GPU or CPU?

 

[psyf]

And my OBS just turns off the broadcast and then reconnects again, too, I can't solve the problem for a week

 

[Mr Faust]

Last crash was yesterday during Dead Space Remake stream.
The behaviour is this:
It runs well for 30/60 min, then it start lags, then it freezes and I need to force quit OBS. What could be the problem? Broken GPU or CPU?

Try to check this information in system log and update video drivers. I recommended reinstall system and try to check how work OBS.

 

[Lawrence_SoCal]

Have you run your OBS log through the OBS log analyzer on this site?
Notice the pinned post in this forum regarding posting your OBS log when asking for support (link in my .sig)

OBS can use much older hardware than you have, or it can cripple a much more powerful system... all depending on what else you have running, and your OBS settings (and plugins). so there is NO simple (easy button meme) answer. it depends. Over the last 3 years, most of the time from what I've seen, the issue is end-user's OBS settings (following awful youtube advice) or poor quality plugins (streamelements comes to mind) along with lack of care regarding settings, combined with a lack of performing, much less analyzing/understanding the output of, real-time hardware resource utilization monitoring

 

[TheEnigmist]

Try to check this information in system log and update video drivers. I recommended reinstall system and try to check how work OBS.

I missed to check system log. For system and obs I reinstalled windows 11 and OBS, I'm on fresh system, but the problem is still here.

Have you run your OBS log through the OBS log analyzer on this site?
Notice the pinned post in this forum regarding posting your OBS log when asking for support (link in my .sig)

OBS can use much older hardware than you have, or it can cripple a much more powerful system... all depending on what else you have running, and your OBS settings (and plugins). so there is NO simple (easy button meme) answer. it depends. Over the last 3 years, most of the time from what I've seen, the issue is end-user's OBS settings (following awful youtube advice) or poor quality plugins (streamelements comes to mind) along with lack of care regarding settings, combined with a lack of performing, much less analyzing/understanding the output of, real-time hardware resource utilization monitoring

Alredy uploaded all the logs I've in the folder, none of them give an error or point some info about fails
About plugins I use only Move transistion and StreamFX (not now since it doesn't support obs 29)
For settings I use NVEC to send stream online, and increased only the bandwitch, all the settings are default.
The problem is that before october it worked like a charm