Question / Help Obs has crashed twice now Please help

R

rodez

New Member
Obs crashed twice now, first time it crashed a couple of days ago I restarted obs then it wouldn't start streaming then my streaming pc got a blue screen (I have a dual pc setup). The second time, today, the recording stopped (I record with nvenc while streaming with x264), then, about half an hour or so later, so did the stream. when the stream stopped It was just a black screen on both of my monitors on my streaming pc, I could still hear the music from spotify on the streaming pc, but couldn't do anything. I clone a dell s2716dg 1440p 144hz monitor to an elgato 4k60pro that sends the gameplay from the gaming pc to the streaming pc. I will include all logs from the days obs has crashed. Please help, thank you.
Logs:
https://obsproject.com/logs/nmpTW7-4jp3JuYmF
 

Attachments

  • 2018-10-25 17-21-04.txt
    13.3 KB · Views: 9
  • 2018-10-25 17-24-31.txt
    12.9 KB · Views: 3
  • 2018-10-27 16-13-30.txt
    20.1 KB · Views: 3
  • 2018-10-27 19-52-56.txt
    8.9 KB · Views: 3
  • 2018-10-29 21-58-57.txt
    13.1 KB · Views: 3
  • Crash 2018-10-25 00-34-40.txt
    117.7 KB · Views: 6
koala

koala

Active Member
A bluescreen is a hardware failure or a driver failure and must not occur. It is a symptom of faulty hardware or faulty driver installation and a sign of an unstable PC. In Windows event log, you can find the details of the bluescreen. Would help finding the cause of the bluescreen.

Your OBS crash seems to happen during memory allocation for video frames for the delay filter you use in your elgato source. This could happen due to an out of memory condition, or due to memory corruption due to faulty memory hardware, or due to a bug in OBS.

Connected with the bluescreen, it may point to faulty memory hardware. To check that, run Windows Memory Diagnostic on your PC. It's a Windows application you find by searching the start menu.
As workaround, see what happens if you remove the delay filter for your elgato source. If the crash doesn't happen any more, you know at least I didn't write complete rubbish.

If your memory diagnostic found no faulty memory, it would be good if you can get more crash logs (the ones that begin with Crash in the file name). If there is a bug in OBS connected with the delay filter, they will look all the same and show OBS crashing at the same code. Would be interesting to see, if this is the case.
 
R

rodez

New Member
Thank you, uninstalled all drivers and programs I use and reinstalled them, will see what happens today and tomorrow when I stream.
 
You must log in or register to reply here.
Top