Crash when i try to stream and record at the same time

[fran_kingpancho]

When i try to record and stream at the same time obs crash and the probes it says is
Unhandled exception: c0000005
Date/Time: 2021-02-23, 20:10:55
Fault address: 7FFB21D726BA (c:\program files\obs-studio\bin\64bit\libx264-157.dll)
libobs version: 26.0.2 (64-bit)
Windows version: 10.0 build 19042 (release: 2009; revision: 804; 64-bit)
CPU: AMD Ryzen 9 3900X 12-Core Processor


Thread 208C (Crashed)

i dont know to resolve that or know how to fix it

 

[fran_kingpancho]

yesterday what I did was let the processor do the stream and the GPU record on the disk, what happens is that I do not want to leave all the load on the GPU, no matter how powerful it is, the idea is to distribute the load and what The whole pc is put to good use, in this way if it worked without problems, today I will do more tests, but the problem is that my processor is quite good and due to problems with the codec it does not support loading the stream and recording at the same time

 

[Lawrence_SoCal]

understand that NVENC is a separate section of the GPU, typically not in use unless doing other video encoding at same time??

 

[fran_kingpancho]

understand that NVENC is a separate section of the GPU, typically not in use unless doing other video encoding at same time??

Well you're right, I should use nvec instead of x264, but it doesn't remove the fact that there are problems with the x264 codec in obs. in the same way that I can record and stream at the same time with the nvec codec, I should be able to do it with the x264 codec with a processor like mine

 

[Lawrence_SoCal]

I should be able to do it with the x264 codec with a processor like mine

maybe, maybe not ..... it depends
having a monster CPU helps, but if PC is busy doing other things, and you add the super demanding task of real-time video encoding to it... most people don't have a clue how their PC actually works, how to monitor it, etc. and just whine when something used to work, and now doesn't, and you have a situation of PEBKAC [not saying that is the case with you... I don't know enough one way or the other]

Sorry, you aren't posting enough info (and OBS logs are only a small part of the picture) to identify/ troubleshoot... and OBS is free software... so if codec has an issue have you
1. confirmed the bug, and is there a tracked bug report?
2. offered to pay someone to address it for you?
If you want codec addressed, and confirmed it is a real issue, not something specific to your system, there are helpful, collaborative ways of going about it. the above... not so much