Not on your end. You could switch to NVENC if you have a Nvidia GPU and recent model. This, to avoid using x264 and its DLL.
There's not enough information in the call stack and no symbolic information to help know what exact function was called to generate the exception. Unless this problem is easily reproducible, I wouldn't expect a fix anytime soon. Given that the call structure hasn't been reported from other users since 26.1.1 has been released.
If this happens all the time on your system and you been an OBS users from the past, another suggestion is to rollback to an earlier version.
OBS Studio - Free and open source software for live streaming and screen recording - obsproject/obs-studio
github.com
Search for a version and then click on the Assets link. Try starting off with 26.0.2 and download the Windows full installer to see if the problem goes away. Then, report back what version works.
I'm not sure what the Windows full installer is - is that a fresh installation of windows? I rolled back to 26.0.2 and I recieved this report. Is this the same as the previous?
The crash is happening in the same x264 DLL. But it is not the same calling signature. In your second log, the DLL is not triggering an exception due to an address instruction pointer of 0 (like the first one did).
The first log you posted was using a different x264 DLL version of
libx264-161.dll
The second log you posted was using version
libx264-157.dll
This seems like a deeper problem in your system configuration.
Are you running your motherboard's current BIOS version? I would go update it.
Check your RAM with MemTest as well.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.