Constantly crashes, awful performance about 80% of the time

emele

New Member
It seems really random. SOMETIMES my stream works perfectly, but most of the time I get terrible encoding or rendering lag.

My system is:

Ryzen 9 5950X 16-core, 32-threads, 4.7ghz
32 Gb DDR-4 3600
GTX 1060 (sigh)

I use the CPU to encode, but clearly this CPU is plenty capable of encoding a stream at very high quality and play any game at the same time.

The log file is here: https://obsproject.com/logs/0G6VRlzQI8tLeqkB

Thanks!!!
 

Lawrence_SoCal

Active Member
Have you tested without the 3rd party OBS plugins (like background removal)
And possibly with ESET disabled (antivirus/security applications have caused problems before.. not saying it is the case this time, but.. )

This log doesn't include a recording/streaming session, and missing encoding performance data. Record or stream for a bit (a minute?) then post log
 

emele

New Member
Have you tested without the 3rd party OBS plugins (like background removal)
And possibly with ESET disabled (antivirus/security applications have caused problems before.. not saying it is the case this time, but.. )

This log doesn't include a recording/streaming session, and missing encoding performance data. Record or stream for a bit (a minute?) then post log
This one should have what you need: https://obsproject.com/logs/V1lgzP-GFLc7-wsc
 

emele

New Member
Also, bandwidth testing mode shows everything working perfectly, but when I start to actually stream, that's when I get encoding or rendering lag supreme.
 

PaiSand

Active Member
Always use the Analizer (accessible from within the upload log file feature in Help menu):
Please follow recommendations and directions.

You can also try lowering the fps to 30 and scale to 936p or 720p (with this can be 60fps). Do some tests to see if helps.
Also try NVENC instead of x264

To more accurately measure the quality of your internet connection against Twitch you may use this app:
Quality bellow 90 is bad.
 

emele

New Member
Always use the Analizer (accessible from within the upload log file feature in Help menu):
Please follow recommendations and directions.

You can also try lowering the fps to 30 and scale to 936p or 720p (with this can be 60fps). Do some tests to see if helps.
Also try NVENC instead of x264

To more accurately measure the quality of your internet connection against Twitch you may use this app:
Quality bellow 90 is bad.

Thank you for the reply. I have obtained the same results with hardware acceleration on and off. I've turned it off again and the problem persists.

As for the ping, I get 100 in my country (Canada) and most of the USA except the very southern locations. I just need >90 on the closest few locations, correct?
 

emele

New Member
Instead of capturing the game's launcher too, I tried with just a bitmap image. Same result.

And about NVENC, I use an old GTX 1060 and I think the quality is pretty bad. I got this extreme CPU *SPECIFICALLY* so as to be able to do the best possible encoding...
 

emele

New Member
Always use the Analizer (accessible from within the upload log file feature in Help menu):
Please follow recommendations and directions.

You can also try lowering the fps to 30 and scale to 936p or 720p (with this can be 60fps). Do some tests to see if helps.
Also try NVENC instead of x264

To more accurately measure the quality of your internet connection against Twitch you may use this app:
Quality bellow 90 is bad.
Again, reducing the quality is out of the question since about 20% of the time, the stream works perfectly on 1080p/60 and VerySlow X264 encoding. If it works part of the time, it should work all the time. And when it starts working, I can stream for hours and it will keep working perfectly with these settings. But about 80% of the time that I do stream, I get MASSIVE frame drop to encoding or rendering lag.

I mean, if my computer is able to do it, it's able to, right?
 

Lawrence_SoCal

Active Member
I mean, if my computer is able to do it, it's able to, right?
Uh, no, definitely not

If your PC can CPU encode under one workload, means it probably can do so under similar workloads (which are FAR more specific than a generic single CPU utilization metric). Change games.. change workload, and maybe yes, maybe no it will work, depending on your specific game, OS, and OBS settings, with OS meaning EVERYTHING else also running on the computer. Most folks don't pay attention to background processes, so from day to day, things change. Then there are OS, driver, and app updates that change things.
so... it depends and meaning
If it works part of the time, it should work all the time.​
is unmistakably NOT true. sorry
Now if you keep everything the same, then yes you are correct. BUT things are almost NEVER the same.

Hopefully you have the recently released AMD BIOS fix for CPU stuttering
 

emele

New Member
Uh, no, definitely not

If your PC can CPU encode under one workload, means it probably can do so under similar workloads (which are FAR more specific than a generic single CPU utilization metric). Change games.. change workload, and maybe yes, maybe no it will work, depending on your specific game, OS, and OBS settings, with OS meaning EVERYTHING else also running on the computer. Most folks don't pay attention to background processes, so from day to day, things change. Then there are OS, driver, and app updates that change things.
so... it depends and meaning
If it works part of the time, it should work all the time.​
is unmistakably NOT true. sorry
Now if you keep everything the same, then yes you are correct. BUT things are almost NEVER the same.

Hopefully you have the recently released AMD BIOS fix for CPU stuttering
OK, right, but the game I stream isn't that demanding and frankly running the game and encoding X264 at VerySlow use up a MAXIMUM of about 55% of my CPU total, from what I have seen. It is FAR from seriously taxed. So yes the game may have peaks but nothing like an additional 25% of my CPU.

I monitor my CPU usage both on-screen during gaming and on my secondary monitor, and the most I have ever seen during streaming has been below 60%.
 

emele

New Member
Thing is, I can stream on very slow 1080p/60 for many many many hours on end, in various matches, at all levels of demand from the game. It just works about 20% of the time. I need to restart OBS multiple times and start actually streaming very many times until it starts working correctly.

You can't tell me that some of my 4-hour and longer streams with perfect performance were all done during low demand from the game, which is very dynamic. Also, the game getting more demanding would explain dropping SOME frames, but if I let the OBS stream long enough, it ends up dropping >90% of frames. There is clearly something very wrong here.
 

emele

New Member
OK, right, but the game I stream isn't that demanding and frankly running the game and encoding X264 at VerySlow use up a MAXIMUM of about 55% of my CPU total, from what I have seen. It is FAR from seriously taxed. So yes the game may have peaks but nothing like an additional 25% of my CPU.

I monitor my CPU usage both on-screen during gaming and on my secondary monitor, and the most I have ever seen during streaming has been below 60%.
Actually I've been watching it streaming again, and it was under 40% the whole time, for hours, streaming on VerySlow at 1080p/60 with no lag, no dropped frames, UTTER PERFECTION.

Here's the log: https://obsproject.com/logs/bG1tE_HbWMf1eTwd
One thing that I have done differently is that I started the stream with NVENC and then switched it to X264 VerySlow. I might try that again!
 

emele

New Member
And actually, it looks like NVENC has much improved quality over what I remembered my GPU offering and even VerySlow X264 seems much worse. Am I hallucinating?
 

FerretBomb

Active Member
And actually, it looks like NVENC has much improved quality over what I remembered my GPU offering and even VerySlow X264 seems much worse. Am I hallucinating?
Modern NVENC on 20/30-series cards produces an encode quality on-par with x264 Slow, per VMAF testing. Older NVENC on 10-series was somewhere between Medium and Fast, and 9-series cards were around Veryfast to Ultrafast.
Modern NVENC has effectively rendered 2PC setups pointless, outside of a small number of edge-case scenarios, it's so good.

Most commonly the error in your crashlog occurs when an unstable or marginally-stable overclock is in play, or when using an AMD-based CPU where the motherboard's firmware needs a flash to update/patch the CPU microcode, from my experience. BIOS flashing has become much less of a risk in the last 10 years, and tends to only harbor minimal chance of bricking, so if there's an update available for your mobo, it may be worthwhile to pursue.
 

emele

New Member
Modern NVENC on 20/30-series cards produces an encode quality on-par with x264 Slow, per VMAF testing. Older NVENC on 10-series was somewhere between Medium and Fast, and 9-series cards were around Veryfast to Ultrafast.
Modern NVENC has effectively rendered 2PC setups pointless, outside of a small number of edge-case scenarios, it's so good.

Most commonly the error in your crashlog occurs when an unstable or marginally-stable overclock is in play, or when using an AMD-based CPU where the motherboard's firmware needs a flash to update/patch the CPU microcode, from my experience. BIOS flashing has become much less of a risk in the last 10 years, and tends to only harbor minimal chance of bricking, so if there's an update available for your mobo, it may be worthwhile to pursue.
Thanks, I've flashed it recently but I see they have a Beta BIOS that is newer. I guess I'll use the crappy GPU to encode (drops my framerate on an already undepowered part) while waiting for that new BIOS revision to exit Beta.
 

FerretBomb

Active Member
Thanks, I've flashed it recently but I see they have a Beta BIOS that is newer. I guess I'll use the crappy GPU to encode (drops my framerate on an already undepowered part) while waiting for that new BIOS revision to exit Beta.
If set up correctly, there should be zero in-game performance loss from using NVENC. It's an entirely separate part of the GPU die.
 

FerretBomb

Active Member
From your logfile, Lookahead and Psychovisual Tuning are both on. Turn them OFF. Those two, as well as the Max Quality preset, are problematic settings that will regularly cause 'encoding overloaded' problems. You're using the Quality preset, which is fine.

You're using a large number of individual per-game Game Captures, and should only have one. Multiple can conflict with each other to cause performance issues.
You're also using the 'background removal' plugin, which is known to both cause high system load and be unstable.

As far as the crashes, you'd need to post a crashlog rather than a session log.
 
Top