Question / Help Stream drops connection randomly (FD_CLOSE error 10053)

[Brady Curtis]

Hello, trying to help my girlfriend with her stream and will provide as many details as I can here.

The overall: Stream will have days where there are no packets dropped and no issues with connection. Then some days, usually happens once or twice, but some bad days has happened 5+ times, the stream will stop. OBS itself will still show Green (like it's live) and after a minute it will reconnect but viewers will have to refresh the page to see the stream again. We have done all basic troubleshooting such as ping/tracert tests, changing bit rates (was 2500/2500, went to 2000/2000, and now 1500/2000), changing Twitch servers (Main is Dallas, tried Chicago and Seattle) with no changes, tried reinstalling OBS-Studio itself, etc. No results.

Here is the fine details for the last episode this happened with (6/4) :
Stream start time: 11:38 PM CST : https://www.twitch.tv/videos/149625890 (Can see where connection suddenly drops at the end)
Stream connection drops: 1:07 AM CST (ends video) with this error :
01:07:13.599: socket_thread_windows: Received FD_CLOSE, 16880 ms since last send (buffer: 209464 / 212480)
01:07:13.599: socket_thread_windows: Aborting due to FD_CLOSE, error 10053
Stream reconnects 1:08 AM CST (starts new Twitch video: https://www.twitch.tv/videos/149635629)

We've both scoured Google but couldn't really find anything concrete on what to do to resolve this. Log file attached, any help on how to resolve this would be much appreciated. For now the last thing that we've done today is change DNS to Google's for testing purposes.

Thanks!

 

[R1CH]

"16880 ms since last send" means no data got sent for over 16 seconds, causing the connection to be aborted by your system. This generally indicates a problem with your connection to Twitch.

See https://github.com/jp9000/obs-studio/wiki/Dropped-Frames-and-General-Connection-Issues

 

[Brady Curtis]

Thanks R1CH, I had pretty much surmised a network issue but was hoping that there may be a way to narrow down where the issue may lie, ie normally if i run a tracert i can see which hop is getting the packet drops so I have information to present the ISP if it is indeed with them, but if the drop is happening much later....say Dallas then my only option may be a VPN? Any suggestions there?

Or maybe if I ask another way, does "means no data got sent for over 16 seconds" imply within the local network or does that mean the packet is sent and reaches destination but receives nothing in return?