crash during stream c0000005 libx264-164.dll

koala

Active Member
This kind of error might be caused by hardware malfunction near the CPU such as overclocking, overheating, bad voltage.
 

ZaRaki

New Member
no, i dont have overclocking, overheating, bad voltage.
And i checked google and forum, this is a known problem.
 

ZaRaki

New Member
I think it's not the hardware that's the problem. Because I use Photoshop, vegas pro, 3d max
browsers firefox, MS edge, opera, chrome.
VLC mplayer, smplayer, steam, mumble, discord, telegram.
Games: skyrim, dota 2, lineage 2 (3 different clients), cyberpunk 2077, Witcher 3, New World, Lost Ark, Battlefield 5-4
Over the past 3 years, none of the listed programs have had any errors. None.
OBS is the only program that has such problems, and from the very beginning of its installation.
constantly crash periodically.
The best period for a week is 1-2 crashes. But it also happens 10 times in 1 stream.
Even in heavy programs like 3d max or vegas pro, there are no errors during rendering.
And you want to say that it is for OBS that something needs to be done. This is at least strange.
Usually, on the contrary, the minimum requirements for the program are set. And then the program is updated in such a way that further errors in the program with compatibility are eliminated.
Besides, the BIOS of 2021 is definitely not old.
To be honest, I have heard a lot of different problems from my friends and colleagues. But this is the first time I hear that it is the BIOS that needs to be updated.
 

bcoyle

Member
im still running obs 27, but this probably applies to 28-29. My impression is that obs accumilates errors and saves these errors. brower sourses that aren't connected anymore have caused me problems. So when i start obs, i like to start from a clean start. So i use the command line arg to start clean. I use the following:
Z:\Video\OBS\obs-studio\bin\64bit\obs64.exe --multi, -m --collection "CASTER" --profile "CASTER".
I reset the collection and the profile everytime on start up.. the "multi -m" arg lets me run multiple copies of obs without an error message. I also have a collection called "reset" that is really a "new" collection with nothing in it. I have had situations where obs will just not start. so i use the reset collection shortcut to start obs, then exit to save a "clean" configuration and then restart it with the normal shortcut. Does it get rid of all crashs? no but a hell of a lot fewer ones. Hope that this helps.
 

bcoyle

Member
oh - i also use rammap to automatically reset the windows free-cached memory. it's set in the schedule manager to free up the memory once and hour or so. Seem that vlc uses that memory when playing and when filled, has to page which sometime causes problems. rammap is free
 

bcoyle

Member
1685904193935.png

i think there is a way to do this in windows using the newer windows os, but not sure
 

bcoyle

Member
hmmm, it really can be. I'll try your way
really, all i can say is this worked for me. Your case might be entirely different. My last round of obs streaming ran for 264 hours without crashing. even then, i stopped it on purpose

here is my currently streaming channel if interested

 

Suslik V

Active Member
I think it's not the hardware that's the problem...
If all crash reports is the same then you need specific x264 stress test.

If you unable to find any, you may try FFmpeg "empty" encoding (it runs infinitely until you close the CMD window or until RAM for the process ended):
Code:
ffmpeg -f lavfi -i nullsrc=s=1920x1080:r=60 -filter_complex "geq=random(1)*255:random(1)*255:random(1)*255" -c:v libx264 -preset placebo -f null -
There is "-" in the end of the command line string (see above).
 
Top