Question / Help Whats causing my OBS to crash?

T

ToejaM

Member
This happened three/four times today and these are the only logs I have where the crashlog generated to go alongside the obs log.

Stream Rig Spec:
  • CASE: BitFenix Neos ATX Tower Black/Red Window
  • CPU: AMD Ryzen 1700 (8Core/16thread) @ 3.7Ghz
  • CPU Cooler: Wraith Spire (AMD Stock)
  • RAM: Corsair LPX Vengeance 8GB 3000Mhz
  • MOBO: MSI PC MATE B350
  • GPU: GTX 460
  • PSU: Corsair CX 430
  • SSD: Integral V 120GB SSD
  • Storage: Assorted sizes
  • Capture Card: Elgato HD60 Pro

Crashlog: https://pastebin.com/ycisQWmx

OBS Log: https://pastebin.com/CRbvZmWM

Any ideas on whats causing it?

CPU temps are fine, as are GPU temps.

Just want to point out that I'm aware I'm not using the latest OBS, the latest OBS 20.0.0.1 was causing crashes to be more frequent, by downgrading it appears it has made them less frequent. I also thought it was due to the slow preset but it happens on any preset so far as I can tell.

It also appears quite random, once my stream is running. Aside from Ankhbot running and Streamlabels, there isnt much else going on and I rarely use the stream rig after pressing start stream. The crash doesn't appear to have a consistent time to crash, sometimes it can be hours into a stream and sometimes its less than 10minutes.
 
Last edited:
S

SamTDS

New Member
Are you running obs as administrator? the exception code indicates an access violation that most of the time is fixed by running the program as an adminstrator. Please can you also include the Event Viewer log for the crash which would give us a better idea of the module the error is caught in. I have recently had a problem where none of my web browsers were working with the same exception code caused by ntdll.dll
 
T

ToejaM

Member
Interesting, I didn't think about the event viewer log. Looks like there are lots of potential candidates for what it could be and I'm not entirely sure which one is the exact one related to the crash, if not all of them, let me post these as a timeline:

12:17:59 - ERROR event https://pastebin.com/uHUQXZFj

12:18:11 - This is the (i) information event following that crash which says the following: https://pastebin.com/1GL8qbX1

Then this is the report.wer that it alludes to in the above information in the folder it says "maybe there": https://pastebin.com/Ts0LsU9X

12:19:03: - Another "ERROR" event https://pastebin.com/Ms6Ad6Lc

12:19:03: - information event https://pastebin.com/fzMg1Caj

Another report.wer from the above information event: https://pastebin.com/UhgSHkmf

To me that looks as if the Elgato icuin57.dll is starting the crash as that's the first thing that comes up, however, there is a libcef.dll causing another issue. I want to add here that I've had issues with bits freezing certain browser sources, namely, the streamlabs alerts window and usually when bits less than 100 are used, so the grey ones. A couple of times subs have frozen the alert also but it's never outright crashed OBS.

I want to point out that the crash above and others today from OBS have been random, no bits have been tipped to cause it to crash as I had no bits during this stream.

As for Boom, its hard to see if thats the cause - I dont see anything in any of the logs to suggest it and I know quite a few people who use boom that have no crash issues - happy to try without it but boom wasnt even used today either, of course its still active!

I'm also tempted to try obs 32bit - I know that boom says it requires 64bit but it works under both.
 
S

SamTDS

New Member
The first error shows a buffer overflow which could be related to a memory leak. The seccond shows a normal exception error probably caused by the other process of obs crashing
 
R

R1CH

Forum Admin
Developer
Random crashes in unrelated modules suggests hardware issues like faulty RAM or Ryzen microcode bugs. Turn off any overclocking and make sure your BIOS is up to date. Try a memtest too.
 
T

ToejaM

Member
The annoying thing is, my memory is actually underclocked - its on 2667mhz as the motherboard refuses to post if its set to 2997mhz even if I set the timings manually (as close as I can get to the rated 3000mhz)

I'll run a memtest when I go to bed, thats a fair shout.

Ryzen microcode bugs would also be quite possible. I'm not sure if I can run 6000kbs, 720p @ slow preset on the default overclock but I can tinker with it, perhaps even underclocking by 100mhz may make things more stable. I guess there are a few things I can try here though.

I also had to send off my Elgato HD60 Pro to have another sent back that was compatible with Ryzen as older firmwares on the capture card make the card undetectable by Ryzen motherboards. All props to Elgato for that turn around speed though.

Some days my stream has been on for 8-12hours straight and no crash, which is what makes testing this so difficult.
 
You must log in or register to reply here.
Top