Question / Help SOLVED: OBS random disconnect/connect

Mosaver Bandri

New Member
"Try changing server"
- I tried every possible server in EU. Some times (I cant tell what I did), I have been having LONG streams with no crashes at all. Those were the times I chose Italy/London, but when I tried these servers again, my stream were laggy for the viewers. Therefore I went back to the three locations that are the most stable for me: Stockholm, Frankfurt and Amsterdam.

"Try lowering bitrate"
- Tried everything between 1500-3500. I am using 3300 atm.

"Try another program"
- I tried XSplit but that program got its own problems, so I didnt use that.

"Check your firewall / router"
- I disabled my firewall, I added OBS' port as an exception and I also bought a new router specific for gaming (100$). None worked.

"Check your antivirus"
- I disabled this. Didnt work.

"Update network driver"
- I also did this. Unintalled it and installed it again. Didn't work.

Other than that, I tried resetting my router, getting a new IP, my ISP told me that there has been no disturbances on my line for more than 3-4-5 months.

I tried a new GPU (even though im streaming via my CPU, 15-6600k Skylake), didnt help so I returned it. I tried a new internet cable. I had this problem in OBS Classic aswell, but changed to Studio a long time ago hoping it would fix.

None of these solutions work :-( ...
 

R1CH

Forum Admin
Developer
You can try the "Enable new network code" option in advanced settings, this will provide more detailed information in the event of disconnects.
 

Mosaver Bandri

New Member
You can try the "Enable new network code" option in advanced settings, this will provide more detailed information in the event of disconnects.
Alright, I will enable it and post a log in here when I crash during the stream tommorow. Appreciate your fast answers, you will probably hear from me tommorow!
 

R1CH

Forum Admin
Developer
That log only seems to show you stopping the stream manually:

"13:13:50.578: [rtmp stream: 'adv_stream'] User stopped the stream"
 

R1CH

Forum Admin
Developer
14:32:13.904: socket_thread_windows: Received FD_CLOSE, 19270 ms since last send (buffer: 442111 / 442880)

This means OBS wasn't able to send any data for almost 20 seconds, and was disconnected by Twitch because of that. Unfortunately this is probably an issue with the path between your ISP and Twitch dropping out sporadically, or other transient network issues.
 

Mosaver Bandri

New Member
14:32:13.904: socket_thread_windows: Received FD_CLOSE, 19270 ms since last send (buffer: 442111 / 442880)

This means OBS wasn't able to send any data for almost 20 seconds, and was disconnected by Twitch because of that. Unfortunately this is probably an issue with the path between your ISP and Twitch dropping out sporadically, or other transient network issues.
Yeah, some Twitch Partner in Discord told me this aswell.. Since I have tried everything, I guess the only thing left to try is changing my ISP.. Even though its more expensive, I guess its worth it if it gets fixed by changing. Thanks for your time, R1CH.
 

Mosaver Bandri

New Member
14:32:13.904: socket_thread_windows: Received FD_CLOSE, 19270 ms since last send (buffer: 442111 / 442880)

This means OBS wasn't able to send any data for almost 20 seconds, and was disconnected by Twitch because of that. Unfortunately this is probably an issue with the path between your ISP and Twitch dropping out sporadically, or other transient network issues.
Hey again, sir.

So Sunday I changed the DSL cable from my modem into the phonestick in the wall and I havent crashed since. I did a 12 hour stream yesterday and I streamed 4 hours today. The bar, which shows how stable the connection is in OBS, was green during the entire 12 hours. Maybe you could put that in the troubleshoot topic.
 

Hulo

New Member
I was having the same issue. However when I tried streaming it off through USB tethered Phone that was connected to the same WiFi as the PC was through Ethernet, the streaming actually worked without a hitch. Now I suspect that there might be a problem with the Ethernet Driver Update by Intel. Currently I have a B360 board from Gigabyte.
 
Same issue,with a twist. This problem is specific to No One Lives Forever. I encountered the problem today after I used Nvidia Inspector to cap the framerate of the game at 60 (since otherwise the game would run too fast, cutting off dialogue [before this I had used vsync in the Nvidia Control Panel, but had this flashing strobe-like glitch when in menus on the stream; I wanted to run the game in a window, so I had to cap the framerate some other way]). I ran into this problem a few times. Then I streamed some Quake Live (ten minutes, maybe) with no trouble; switched back to NOLF; instant connection problem, OBS gobbling up 60-80% of my CPU according to Task Manager, and the stream either buffering or flat out dying with an error 2000.
 

Attachments

  • 2019-08-03 10-15-24.txt
    12.8 KB · Views: 258
  • 2019-08-03 09-59-25.txt
    18.4 KB · Views: 97

ramonzeira

New Member
I have the exact same problem. Tried everything. But here it happens every 5 minutes, making it impossible to stream. Don't know what to do anymore.
 

ramonzeira

New Member
Hey again, sir.

So Sunday I changed the DSL cable from my modem into the phonestick in the wall and I havent crashed since. I did a 12 hour stream yesterday and I streamed 4 hours today. The bar, which shows how stable the connection is in OBS, was green during the entire 12 hours. Maybe you could put that in the troubleshoot topic.

Can you take a pic of that? I think I dont have this option.
 
Top