Big Slappy
New Member
hello! i've been using obs for little over 2 years now and i find it to be a very reliable capturing program, but i've run into a problem semi-recently where i instantly get an encoding overload error message, and obs appears to use up to and over 70% of my resources, with that number very quickly fluctuating. previously i was able to record at 1080p60 at maybe 10% maximum cpu usage and little to no problems there, and now i am attempting 720p60 with my usual canvas size of 1600x900 but obs will overload any device i attempt to use to record.
so far, i have tried:
- switching the encoder over to gpu encoding, which crashed my video card the second after i hit the record button, and gave me a bluescreen less than a minute later (so i'm not trying that again),
- removing all of my other profiles and captures,
- quadruple-checking my options to make sure i didn't accidentally change something that might be influencing obs' resource usage,
- updating obs,
- doing a complete reinstall of obs (wiping the options) and switching to the 64-bit version (because for some reason i had the 32-bit one),
- updating drivers (that didn't have any updates available),
- recording different, less tasking programs (resulting in basically the same cpu usage on obs' part),
- clocking my system differently through the wattman it came installed with,
- and many restarts and lots of research into other potential causes of encoding overloads, including messing with custom mixer settings and looking into dealing with an igpu.
my pc has not had any major software or hardware changes that i am aware of in the time between obs' last successfully exported recording and the first recording that i had problems on, although it has a habit of updating with no notifications or anything whatsoever telling me that it did. i also obviously did not update obs itself in this time, so the only possibility i can really think of is a windows update potentially causing a problem between my hardware and the program.
i have a log of a recording i did for ~3 minutes attached as well as my system specs, more than half of the latter document likely being unnecessary to this post, and i am ok with attaching the resulting recording and screenshots of my obs settings if i need to. i will not be surprised if the cause is something hiding in complete plain sight.
i don't know the complete ins and outs of how the program works, or if by any chance i need to do something from the bios or command line, but i can follow detailed instructions.
thank you for your time!
so far, i have tried:
- switching the encoder over to gpu encoding, which crashed my video card the second after i hit the record button, and gave me a bluescreen less than a minute later (so i'm not trying that again),
- removing all of my other profiles and captures,
- quadruple-checking my options to make sure i didn't accidentally change something that might be influencing obs' resource usage,
- updating obs,
- doing a complete reinstall of obs (wiping the options) and switching to the 64-bit version (because for some reason i had the 32-bit one),
- updating drivers (that didn't have any updates available),
- recording different, less tasking programs (resulting in basically the same cpu usage on obs' part),
- clocking my system differently through the wattman it came installed with,
- and many restarts and lots of research into other potential causes of encoding overloads, including messing with custom mixer settings and looking into dealing with an igpu.
my pc has not had any major software or hardware changes that i am aware of in the time between obs' last successfully exported recording and the first recording that i had problems on, although it has a habit of updating with no notifications or anything whatsoever telling me that it did. i also obviously did not update obs itself in this time, so the only possibility i can really think of is a windows update potentially causing a problem between my hardware and the program.
i have a log of a recording i did for ~3 minutes attached as well as my system specs, more than half of the latter document likely being unnecessary to this post, and i am ok with attaching the resulting recording and screenshots of my obs settings if i need to. i will not be surprised if the cause is something hiding in complete plain sight.
i don't know the complete ins and outs of how the program works, or if by any chance i need to do something from the bios or command line, but i can follow detailed instructions.
thank you for your time!
Last edited:
