Question / Help MASS FRAME DROPS, NOT AN INTERNET ISSUE? (HELP)

[John Landgraf]

Here is my logs, somebody please help.

https://gist.github.com/3dc6d7ac5bef0f8c9b47f0f189e2db21

I know this can not be an internet issue, never had this problem before.

 

[Muelo1000]

I can't say this is the problem, but I personally see it being a problem...

How are you able to game on a PC that only has 2GB of RAM and on top of that trying to stream @ 60FPS
Yeah... I hope someone else has a better answer for you, cause I have nothing except a upgrade recommendation.

Its funny when I looked at my log it showed 4GB of ram but I have 16GB in my system so it might be an OBS error. Not sure just saying

 

[John Landgraf]

I can't say this is the problem, but I personally see it being a problem...

How are you able to game on a PC that only has 2GB of RAM and on top of that trying to stream @ 60FPS
Yeah... I hope someone else has a better answer for you, cause I have nothing except a upgrade recommendation.

I have 16gb of ram in my computer, i am a partnered streamer, trust me it has nothing to do with my "pc upgrade"

 

[John Landgraf]

WELL.....
In your log file that you gave us....
23:13:14.077: Physical Memory: 2047MB Total, 2047MB Free (NOTE: 2 or 4 gigs max is normal for 32bit programs)

Correct me if I'm wrong, but 2047MB doesn't equal 16GB. No need to lie homie, just trying to help.

Twitch.tv/Poison , computer has 16, not sure why it says 2, but this is clearly an issue.

 

[RytoEX]

To anyone who has more RAM than OBS reports (for example, you have 16 GB and OBS shows 2/4 GB), you're probably running a 64-bit version of Windows and running the 32-bit version of OBS. That is normal.

@John Landgraf
Please clear out your custom x264 encoder settings. If that does not help, please try running the Twitch Bandwith Test tool using a Medium Test Duration for your region with a 64k TCP Window Size, and post a screenshot of the results here so that we can see the results.

 

[sam686]

You may try running 64 bit OBS-Studio, but that will likely not fix anything other then malloc (memory allocation) crashes.

Log shows: Number of dropped frames due to insufficient bandwidth/connection stalls: 184 (33.9%)
Although this was run for only 543 frames (9 seconds at 60 fps), this is definitely a problem with either Twitch servers, your connection, or the connection route between server and your internet connection. Try streaming to different website like YouTube stream, as a test.

Your custom setting, opend=true failed... fix it or remove it. This is opencl, not openD.

 

[RytoEX]

Because I'm curious, why did you put "opend=true" into your custom x264 settings? I've seen it (or "opencl=true", which is what it's meant to be, but don't use that either - it doesn't usually help) more and more recently. Did you follow a tutorial or video guide somewhere that said this?

 

[Muelo1000]

OBS shows everything right in my log file. OBS doesn't lie to me :)



WELL.....
In your log file that you gave us....
23:13:14.077: Physical Memory: 2047MB Total, 2047MB Free (NOTE: 2 or 4 gigs max is normal for 32bit programs)

Correct me if I'm wrong, but 2047MB doesn't equal 16GB. No need to lie homie, just trying to help.

You are right my friend didn't realized OBS launches 32-bit as default ran 64-bit ..info shows correct