Is Streamlabs causing BSOD?

[Dylswerb]

Recently, Streamlabs OBS has been causing my PC to crash during a livestream. This has never happened to me until last week, when I was streaming Subnautica, and the game froze, and the upper half of the screen was BSOD and the lower half was still Subnautica. Then just tonight, I was streaming modded Guitar Hero, and the same thing happened. I have played both of these games extensively off-stream, and neither game has caused any issues with the rest of the PC like this. My PC is a 12700k, 3070ti, 32gb DDR4, and an 850w PSU, running Windows 10. 

[Dylswerb]

This is what happened last week

[WereCat]

I doubt it. It's more likely that your RAM is causing issues if you have XMP enabled and the motherboard autoconfigured some timings wrong... especialy if you have 4 sticks.

 

Anyway, you can always switch to OBS Studio and try if that will solve it, there is no point in using Streamlabs anyways as they just blatlantly steal OBS in both name and code.

 

Temps are ok?

 

maybe also worth a try to check your WIndows... maybe something got corrupted after an update...

 

Open CMD and type in

 

sfc /scannow

[Kisai]

11 minutes ago, Dylswerb said:

Recently, Streamlabs OBS has been causing my PC to crash during a livestream. This has never happened to me until last week, when I was streaming Subnautica, and the game froze, and the upper half of the screen was BSOD and the lower half was still Subnautica. Then just tonight, I was streaming modded Guitar Hero, and the same thing happened. I have played both of these games extensively off-stream, and neither game has caused any issues with the rest of the PC like this. My PC is a 12700k, 3070ti, 32gb DDR4, and an 850w PSU, running Windows 10. 

Update Streamlabs, or use real OBS with Streamelements instead.

 

That said, your setup is nearly the same as mine. (I have a 11700k instead) and have not had any issues with OBS. 

 

My guess would be one of three:

a) You're using the GPU encoder too close to the GPU being maxed out, this applies to all GPU's, but generally there are parts of the video encoder/decoder that rely on the gpgpu part of the GPU and the video ram for the necessary GOP buffer. When you are playing a game vs streaming, the streaming requires roughly 15frames x capture resolution + 1 for rescaling + 1 for every additional scene layer of video memory. Normally this is a non-issue except for vtubers who have a 2d/3d model running.

b) You need to clean the GPU cooling, similar to A, but instead the problem is a hot spot somewhere on the GPU.

c) functionality problem in "Streamlabs" that isn't present in OBS.

 

I'd first suggest just setting up basic OBS, not streamlabs, and see if it causes the same problem under the same conditions. If it does, then try the CPU encoder only and see if it also happens under that. If the CPU encoder "fixes" it, then the problem lies somewhere in the GPU or the drivers. You can also just try the CPU encoder first on Streamlabs. But again, if that "fixes it" then there is a problem that needs to be solved with the GPU settings or drivers.

 

If you are streaming, you should also make sure any overclocking features are turned off, eg set the GPU mode to "full power, maximum cooling" rather than defaults which favor ramping the fans up and down. Overclocking features should only be turned on under conditions that you know are stable, and are generally not worth the headache, as they also tend to be the reason for GPU's to fail when a new game drops. The last thing you need is for the stream to become a slide show, or crash because the GPU decided it's a good time to save itself by power throttling.

 

Additional things to try:

- Frame limit the game to 60fps, this is a problem I find streamers do not understand. If you are streaming, the maximum frame rate is 60. There is no way for someone watching in 60fps to see a 120fps stream, and the underlying capture mechanic knows this, and will not capture a game at anything but a constant 60fps. Yet, when G-sync or Freesync are enabled, the variable frame rate seems to throw the capture mechanic out, and thus you occasionally see artifacts on the stream that aren't visible to the streamer, or vice-versa. (for example, when I stream with freesync/gsync, my game I swear is running at 40fps, when the stream preview shows a smoother 60fps)

- This "half screen" effect is basically the BSOD not having access to a locked part of the screen buffer, which again points to a hardware/driver problem