Question / Help OBS Crash / "possibly" causing BSOD

Ryanx0r

New Member
About a month or so, I've been experiencing very strange issues with the PC that's running OBS (latest version).
It has been randomly BSOD'ing. At first I thought it was Hardware, but in the course of this month, I have tested everything and have also RMAed everything (Memory, Motherboard, PSU, Graphics Card, ...)
So, Basically, everything I have tested under high load and normal load (this is aside from OBS) - this also includes heavy stress testing and so forth.

My OBS setup was having a Spotify stream playing, adding some graphics and sending it off to YouTube Live stream. It worked really well for a 24/7 stream for at least a whole month of so, then suddenly it stopped with all the problems mentioned above. Basically random "obs64.exe" crashes (no logs) and BSOD's which may or may not be linked to OBS.
The reason, I think it's related is the following.

I can open OBS and just "dummy" stream everything - so basically the stream is just running locally and not being sent off to a streaming service. I just test everything in the preview window and let it run for a few days. Nothing really out of the ordinary.
However, it seems as though once I start letting it connect to a streaming service it can either run for 24 hours, or it can crash within a minute. Very very randomly.
I have tried this with a new PSU
Removing the Nvidia graphics card and using the onboard graphics card
Running OBS along side a high stress test
running OBS under little to no load
Running OBS with just some random YouTube videos playing along side in a browser.

Doesn't matter which one, there will always be a random OBS crash and/or a BSOD. Actually, it sometimes seems that the computer runs a lot better when a high stress test is running (for instance Prime95).

I have absolutely no idea what is going on.
I have also tried formatting and tried running an older version of OBS (18 instead of 19)... nothing helps.

Oh and it seems to be worse when I add an MP4 (playing in loop) as a media source. It never had any issues, and there's nothing special about the loop - just just more of a background loop. But it seems to cause most of the BSODS a lot faster.

Logs can be found here: https://www.dropbox.com/sh/sac8apx7u0ls3n3/AABqjurixrpgUUJrGYZxj6bEa?dl=0
 

Attachments

  • 2017-08-10 01-08-34.txt
    5.6 KB · Views: 8
  • 2017-08-10 11-31-30.txt
    5.4 KB · Views: 5

R1CH

Forum Admin
Developer
Please include one of your .dmp files from the BSOD (%WINDIR%/minidump). It's most likely hardware or driver issues exasperated by OBS' CPU and GPU usage patterns.
 

Ryanx0r

New Member
Ok, will do so later tonight.
But as far as BlueScreenViewer is telling me - most of the BSODS are related to 'ntoskrnl' (which is too global an error afaik). But I'll send them through nonetheless.
 

R1CH

Forum Admin
Developer
Your minidump seems to indicate memory corruption. Try an overnight run of memtest86+.
 

Ryanx0r

New Member
Thanks R1CH - I've been running Memtest for 15 hours now and not a single error at the moment. Memory corruption is not linked to software or maybe the page file?

Also - I have pretty much the same system for personal use on which I have the same software - nothing abnormal there - FYI.
 

Ryanx0r

New Member
UPDATE: After 2 months of Hardware troubleshooting (Memtest (on both RAM sticks together and separately), new motherboard, different PSU, with or without GFX card, new install of Windows, ...)
It turns out it was the CPU. Got a new CPU (out of warranty) and has been doing well during the 24/7 stream I have running since end of last week.

So, where the BSODs were talking about memory corruption and the BSODs were very random (stress tests never crashed the CPU, but live streaming to Youtube using OBS did) - it was actually very difficult to conclude that the CPU was the issue. So if anyone has any issues, it may well be the CPU.
It's an i7-7700k with boxed cooler.
The Hardware store that helped me out was baffled, seeing the load on the CPU is minimal, but he said it's about the 3rd CPU issue he's had in a relatively short period of time (something they never used to see) - so could just be an issue with bad cooling (boxed cooler) or some manufacturing issue with the latest CPUs.

In any case, case is closed and 'luckily' doesn't have anything to do with OBS ;)
 
Top