Could you please review the logs and let me know what else you're considering trying?
Could you please review the logs and let me know what else you're considering trying?
Hello there! I’d be happy to take a look at your logs. You can find the information below with a link as well. This is what I currently understand. I’m experiencing connection problems with the RTMP server when connecting to Twitch. I frequently encounter errors such as RTMP send error 10054, 10053, and 10038. I assumed it might be an internet issue, but I used ping plotter to check my internet connection—it didn’t show any problems. I also tried streaming to both Twitch and YouTube; Twitch had issues with the specified errors, while YouTube worked perfectly without any problems. I checked Windows updates, drivers, firewall settings, opened the necessary TCP ports for RTMP, reset my streaming key, and reviewed other potential factors. I hope someone can help me with this.
Link to logs: https://obsproject.com/logs/BIm4XgwudZOF0HHJ
the main problem is that NVENC isn’t available (“NVENC not supported”), causing OBS to revert to x264/AMF. When paired with an excessively high bitrate, Twitch’s RTMP server becomes overloaded and you encounter send errors (10054/10053/10038).
To resolve: reduce your bitrate by 1000–1500 kbps and retest.
Choose the nearest Twitch ingest server manually instead of using Auto.
Consider changing the encoder to x264 or AMF if NVENC is unavailable to find a more stable option.
sorry where did you see that in that in the logs cause I don't have the option for NVENC, I have an amd card tho i did do what you mentioned and seemed to have no worked, its really really weird and been working this since early last week, im really stumped.
Ah, thanks for clarifying I assumed NVENC because the log line looked like OBS falling back, but on AMD you’re right, it should be using AMF.
If lowering bitrate didn’t help,a couple of things to try:
In OBS, under Output → Streaming, set encoder explicitly to x264 instead of AMF and test if it’s more stable.
On AMD/AMF, try reducing B-frames set to 0 or 2 – Twitch sometimes rejects streams with higher B-frames.
Double-check your keyframe interval = 2 Twitch requirement.
Set the network bind IP in OBS to your actual adapter instead of “Default” (Settings → Advanced → Network).
Since YouTube works fine, it’s very likely a Twitch ingest or encoder setting mismatch. Try manually choosing a different Twitch ingest server not Auto.
So you're onto something, it looks like the AMD encoder (AMD HW H.264 (AVC)) is the issue. After switching to the CPU's x264 and adjusting other settings, there were no more problems. The AMD version was still giving errors, which is a bit surprising since the logs didn't indicate a render problem. Thanks again for your help—it really makes a difference. Now I'm curious why the AMD one started causing this issue despite the logs.
It’s good to hear the stability with x264 confirms it’s an AMF issue, not a problem with your setup. AMD’s AMF encoder in OBS can be sensitive to driver updates, sometimes causing sync problems or frame drops even when the GPU is loaded. If you need to continue using AMF, consider reverting to the earlier stable AMD driver version where AMF worked well. Alternatively, keep using x264 until AMD or OBS releases an update for the encoder. Your system appears fine; the concern lies with the AMF implementation itself. Choosing x264 is acceptable if your CPU can manage it.
I sadly talked to soon, it looked like it kept crashing. I just don't know what changed. I went on a vacation for a week, and now everything is a mess related to obs when I've been using Go to Setup for months ;x;
If it began crashing again without any configuration adjustments, it likely indicates either a recent driver update or Windows update that disrupted AMF stability, or an OBS background update. Consider reverting to the previous AMD driver version where AMF functioned properly, or install an earlier OBS release to verify. Also, clear the OBS cache and settings folder—export your profile first, as corrupted configurations can trigger crashes after updates. Since x264 operates correctly, the issue points toward software or driver changes during your absence.
Sounds great! I'm glad you found it helpful. Thank you once more!
I wrote this because it was really frustrating trying to solve the problem, and I really hope this helps anyone who reads it.
In short, the problem was related to routing. I combined ping-plotter and restream to identify the issue, then resolved it using proton vpn.
For a more direct solution, you should verify there are no bandwidth restrictions—run speed tests, ensure you're on Ethernet, and check your adapter settings. Once confirmed it's not a bandwidth problem, try using Restream with the whip connection type. If streaming works, it’s likely routing. To confirm, test streaming via RTMP. If still no issues, it’s probably a routing concern.
To work around this, connect through a VPN to reach a different ingestion server. Make sure you connect to a nearby server in Obs or use Twitch Inspector to see which one you’re using. Then test by streaming and checking if the connection drops.
Don’t hesitate to search for more info on Google—this is how I solved it. Good luck!