Question / Help "Not Responding" When Starting or Stopping Stream

MadVaper

MadVaper

New Member
I'm having an issue with OBS. Using 64-bit version, but it happens with the 32-bit version as well. About 9 out of 10 times when I click "Start Streaming" or "Stop Streaming", there is a 10-30 second period where OBS stops responding and looks like it's about to crash. Eventually, it starts, or stops, but it's very annoying and inconsistent. This sometimes also happens when I try to "Preview Stream". I've tried re-installing, but this issue persists.

I'm not sure if this is related, but about 25% of the time when I start a stream, my bitrate is about half of what I have it set to and I get nothing but dropped frames. This doesn't stop until I stop the stream and start it again. Right now my bitrate is 2000kbps, and when this problem decides to kick in, the bitrate hovers around 1000kbps and drops frames like crazy. I have no idea what's wrong.

I've been using OBS for about 2 months, and this only started about a month ago. I've just been dealing with it, but apparently this isn't a widespread issue and it's not going away without some help.

Thanks.
 
Videophile

Videophile

Elgato
Getting same issue.

However, I only notice it when I set my X264 preset too high(As in, my CPU usage is around 90%).

What I think is causing it is that the CPU will run at a lower clock speed when not streaming, and once you activate the stream, it notices it needs to clock up, so it does, but in the mean time, OBS is dropping frames(this happens to me).

When I force my CPU to run at 100% all the time, it does not happen.
 
MadVaper

MadVaper

New Member
My problem may be related, but I've experienced some differences. This happens on the "faster" and "veryfast" presets. If I'm using "faster" and playing a demanding game, my CPU usage floats around 75-90%. "Veryfast" is more like 45-60%. I have my CPU set to 100% minimum and maximum under Power Options, but it's overridden by my BIOS. Are you forcing your CPU through the OS or through the BIOS? If I can force 100% through the BIOS, I'll give it a shot and see if it fixes the problem, although I'm not sure I'm comfortable doing that long-term. Even at 100% for extended periods, my temp never goes above 70 degrees, but it just seems like unnecessary stress on the CPU.

However, I did notice something strange when perusing the log file. It says my processor is "@3.7 GHz" when you look at "CPU name" which is what most apps will say when they don't actually read the clock speed, as that is how my CPU comes, stock. I'm overclocked to 4.4GHz, yet in the log file, it not only says "@3.7GHz" but also that "CPU Speed" is 3699MHz, which I know for a fact is incorrect. I monitor my clock speed, temp and load with CoreTemp which is telling me that I'm running at 4400MHz. OCCT confirms this. So could it be a problem with OBS assuming the wrong clock speed? I don't really want to set it back to 3.7. I overclocked specifically to try and offset the load taken up by streaming, being that I don't use a capture card.

I tried recreating the issue before posting the log file, but I couldn't get it to hang upon starting the stream. Later that night, I figured out why. It will always hang when I click "Stop Streaming". However, it will only hang when the stream starts if I clicked "Preview Stream" then "Stop Preview" then "Start Streaming". I'll upload that log file later today.

As for the bitrate issue, that hasn't been popping up in the last few days. I ticked "Minimize Network Impact" and that seemed to resolve it, and although the bitrate was more consistent, the little square indicator would pulse between red and green constantly, which made me skeptical. I unticked that option and lowered my buffer size, and that seems to work better. The indicator is solid green, although my bitrate fluctuates a bit more. If it happens again, I'll post that log file as well. So far, no buffering for my viewers with either of these solutions.

Thanks for the help.
 
Videophile

Videophile

Elgato
MadVaper said:
My problem may be related, but I've experienced some differences. This happens on the "faster" and "veryfast" presets. If I'm using "faster" and playing a demanding game, my CPU usage floats around 75-90%. "Veryfast" is more like 45-60%. I have my CPU set to 100% minimum and maximum under Power Options, but it's overridden by my BIOS. Are you forcing your CPU through the OS or through the BIOS? If I can force 100% through the BIOS, I'll give it a shot and see if it fixes the problem, although I'm not sure I'm comfortable doing that long-term. Even at 100% for extended periods, my temp never goes above 70 degrees, but it just seems like unnecessary stress on the CPU.

However, I did notice something strange when perusing the log file. It says my processor is "@3.7 GHz" when you look at "CPU name" which is what most apps will say when they don't actually read the clock speed, as that is how my CPU comes, stock. I'm overclocked to 4.4GHz, yet in the log file, it not only says "@3.7GHz" but also that "CPU Speed" is 3699MHz, which I know for a fact is incorrect. I monitor my clock speed, temp and load with CoreTemp which is telling me that I'm running at 4400MHz. OCCT confirms this. So could it be a problem with OBS assuming the wrong clock speed? I don't really want to set it back to 3.7. I overclocked specifically to try and offset the load taken up by streaming, being that I don't use a capture card.

I tried recreating the issue before posting the log file, but I couldn't get it to hang upon starting the stream. Later that night, I figured out why. It will always hang when I click "Stop Streaming". However, it will only hang when the stream starts if I clicked "Preview Stream" then "Stop Preview" then "Start Streaming". I'll upload that log file later today.

As for the bitrate issue, that hasn't been popping up in the last few days. I ticked "Minimize Network Impact" and that seemed to resolve it, and although the bitrate was more consistent, the little square indicator would pulse between red and green constantly, which made me skeptical. I unticked that option and lowered my buffer size, and that seems to work better. The indicator is solid green, although my bitrate fluctuates a bit more. If it happens again, I'll post that log file as well. So far, no buffering for my viewers with either of these solutions.

Thanks for the help.
Click to expand...
OBS gets the stock info based on your CPU model. It does not take into account overclocks. If you look at your PC properties, windows will also report the stock speed, but if you go to task manager, you will see you actual clock speed.
 
You must log in or register to reply here.
Top