Help please, crash obs after n-number of minutes of recording or stream.

PROGRAMMIST116

New Member
Greetings. Help please, crash obs after n-number of minutes of recording or stream. I tried to use another streaming program, it works great 3 hours streaming no problems. But as soon as I use obs after 5-10-15 minutes of crash or stream recording ... Windows 10 20h2 reinstalled several times there is no use.

System configuration:
Windows 10 20h2

Antivirus:
Eset nod32 internet security

Video card:
MSI Radeon RX 580 Gaming X (no overclocking)

CPU:
AMD Ryzen 5 3600 (no overclocking)

Memory:
Crucial 4 x 4 3200 (overclocking frequency)

All drivers have been updated and drivers for the chipset have been updated. No viruses, neat user.

Directx has been updated.
I don't even know what to do. I provide crash logs and logs below.
 

Attachments

Last edited:
03:13:48.227: Game DVR: On
disable it > i disabled Game DVR
1610029977660.png

1610029989793.png

1610029997022.png


set your display to 60 hz -> i set 60 hz
1610030045408.png


libobs version: 25.0.7-997
update to To newes version -> i updated obs to v 26.1.1
1610030646032.png


here you have more than one OBS running -> yes? i'am run one OBS
 
my tips
ESET Deinstall Defender make the same JOB thiry party vscanner makes more problems than it helps

03:13:48.227: Game DVR: On
disable it

03:13:48.282: output 0: pos={0, 0}, size={1920, 1080}, attached=true, refresh=66, name=2260W
set your display to 60 hz

libobs version: 25.0.7-997
update to To newes version

03:13:48.227: ================================
03:13:48.227: Warning: OBS is already running!
03:13:48.227: ================================
03:13:48.227: User is now running multiple instances of OBS!

here you have more than one OBS running

look that all runtimes up2date and okay


How to update p2date??
 
x264 crashes usually mean hardware issues - update your BIOS, turn off overclocks, test your RAM with Prime95.
 
Yeah, let it run for a few hours. If it stops by itself then it found a memory error, if you aren't overclocking then one of your RAM modules is likely faulty.
 
Yeah, let it run for a few hours. If it stops by itself then it found a memory error, if you aren't overclocking then one of your RAM modules is likely faulty.

Again, as you can see on the screenshot, everything is running and 2 windows are written not running, what does this mean?

And I also have 16 GB of RAM when loading only 11 GB the program uses ..


Снимок.PNG
1610036629764.png
 
the worker endet seen in the text fatal error rouinding was ....
that means that your system makes to mutch errors on working
that is mostly a case if system to mutch overlocked or timings to hard (memory to high mhz)
or cpu/memory broken

default its only a to high oc of CPU/RAM (downgrade your XMP profile)
try with all OC disable (No Auto) and without XMP
sometimes if you find out that the fastest xmp not works then you can try to little increase the power of memory sometimes this can help
but mostly its required to reduce the speed below a working level
 
the worker endet seen in the text fatal error rouinding was ....
that means that your system makes to mutch errors on working
that is mostly a case if system to mutch overlocked or timings to hard (memory to high mhz)
or cpu/memory broken

default its only a to high oc of CPU/RAM (downgrade your XMP profile)
try with all OC disable (No Auto) and without XMP
sometimes if you find out that the fastest xmp not works then you can try to little increase the power of memory sometimes this can help
but mostly its required to reduce the speed below a working level
I only overclocked the RAM because the frequency is important for ryzen, and I was able to disperse it through bios. Is there a problem with RAM? Thank you very much, I'll try to play XMP profile for RAM. As the results are, I'll write off here.
 
Last edited:
prime makes High grade calculations thinks that needs a high precission
default a pc makes errors like on this number if you make a calc where the result is like
0.394726345687253287462387652387468763254725692347688239856239462387947
then its recommend that the result is
0.394726345687253287462387652387468763254725692347688239856239462387947
your system by issue related to a missconfiguration
is
0.394726345687253287462387652387468763254725692347688239856239462387944
that is for the most thinks the pc do not a visual problem
it is only then a problem if the result is required
like in x264 encoding every calculation is the base for the next
so this small issue increase over time and then result in a crash
 
The worker endet observed in the text fatal error rouinding was.... This signifies that your system is making too many mistakes while working, which is usually the case if the system is overclocked, timings are too tight (memory is running at too high a mhz), or the cpu/memory is broken. More information can be found here.

It's only a to high oc of CPU/RAM by default (downgrade your XMP profile)
If you discover that the fastest xmp isn't functioning, try disabling all OC (No Auto) and turning off XMP. If that doesn't work, you can try increasing the memory power a little to see if that helps, but most of the time it's necessary to drop the speed below a usable level.
 
The worker endet observed in the text fatal error rouinding was.... This signifies that your system is making too many mistakes while working, which is usually the case if the system is overclocked, timings are too tight (memory is running at too high a mhz), or the cpu/memory is broken. More information can be found here.

It's only a to high oc of CPU/RAM by default (downgrade your XMP profile)
If you discover that the fastest xmp isn't functioning, try disabling all OC (No Auto) and turning off XMP. If that doesn't work, you can try increasing the memory power a little to see if that helps, but most of the time it's necessary to drop the speed below a usable level.
The fatal error rouinding that the worker endet noticed in the text was.... This indicates that your system is making too many errors while functioning, which is common if the system is overclocked, timings are too tight (memory is running at too high a mhz), or the cpu/memory is broken. Here's where you can learn more.

By default, it's set to a too high oc of CPU/RAM (downgrade your XMP profile)
If you find that the fastest xmp isn't working, try turning off XMP and disabling all OC (No Auto). If it doesn't work, try raising the memory power a little to see if that helps, but most of the time, slowing down to a usable level is required.
 
Back
Top