Question / Help Crashing constantly

[mattiace]

https://obsproject.com/logs/Nx92Pb8srcX12Bxo

I have had these consistent crashes over and over as I stream. The indicator in the lower right side changes color from green to red and yellow and when I click stop streaming (same button as starting) it never actually stops, OBS just keeps running though the stream has actually crashed and no video or sound is actually being broadcasted. The crashes always follow the same patters except sometimes I can stream for hours, sometimes just a few minutes. I had an older version of OBS studio until today but updating to 25.0.0 only let me stream for about an hour and then same issue as before

I run windows 7 (could this be the issue ?) on both computers. I do use a streaming PC for the stream and I play on my main computer.
Avermedia_HD capture card

I'm sure I need to add more info so if anyone have any suggestion that might help, please let my know

 

[FerretBomb]

The green/yellow/red indicator is a buffer fullness light, it does not indicate that the stream has crashed. Normally it means that your network connection to the remote server is unable to transmit data at the configured bitrate, which your logfile confirms.
You have a network connectivity issue where midstream your connection goes to crap. This would not be affected by your upgrade to OBS 25.

 

[mattiace]

The green/yellow/red indicator is a buffer fullness light, it does not indicate that the stream has crashed. Normally it means that your network connection to the remote server is unable to transmit data at the configured bitrate, which your logfile confirms.
You have a network connectivity issue where midstream your connection goes to crap. This would not be affected by your upgrade to OBS 25.

Ok so does that mean the issue is either coming from my main computer or capture card?

 

[FerretBomb]

It means your network connection to the remote streaming server (Twitch, YouTube, etc) is having a problem. It might be your home connection to your ISP, somewhere further up the connection chain in the middle of the route somewhere, or even an issue with the destination ingest server itself.