Black Screen / Windows Freeze when open OBS with offline GoPro?

[Vilandino]

Hi, I have a very strange case of an error in OBS. In one of the scenes I use a GoPro camera via the GoPro webcam driver. However, most often this camera is turned off and I use other scene to record the screen itself (without camera). Despite everything, with this configuration, every time OBS is launched, after a while Windows displays an error that it was not possible to connect to the GoPro camera (because it is turned off). I have noticed that this moment of displaying this message in 90% of cases causes the entire computer to go black and freeze. Sometimes a hard restart is needed, sometimes the image returns by itself after about 30-60 seconds. Previously, despite this error, nothing would freeze and I could record. Everything changed when I updated the NVIDIA drivers to the latest ones (they have a very bad reputation and many people complain about black screens). It is also strange that the black screen also appeared when updating these drivers (re-update), so it seems that it is not only an OBS problem, but it is caused exceptionally often in OBS. I just used DDU and installed the latest STUDIO driver and the exact same problem. (I should note that when I disable GoPro in the image source settings the problem goes away.) Any advice? Because I'm thinking of going back to the old NVIDIA driver, but then I can't use the latest DaVinci Resolve. So that's not a solution for me. Is it more of an NVIDIA issue, a lot of people are having problems now, an OBS issue, or maybe a physical damage to the video card?

Any suggestions on what else I can test?

 

[Vilandino]

Technical information:
GPU: RTX 4070 Ti

Logged error info by Windows:
Caused By Driver: ntoskrnl.exe (Bluescreen)

Windows Log: LiveKernelEvent, Code: 141

Many errors with:
Source: nvlddmkm, ID: 153, \Device\Video3, Error occured on GPUID: 100

 

[prgmitchell]

You'd want to reach out to GoPro, OBS is just loading the device but OBS itself is not capable of what you're describing....that would be the driver.

 

[Vilandino]

You'd want to reach out to GoPro, OBS is just loading the device but OBS itself is not capable of what you're describing....that would be the driver.

But when I start special app for GoPro (with drivers installed) error doesn't occur. Only when open OBS and after few seconds Windows show prompt about Camera Offline, and instant Black Screen. I added that It's started occur after update Nvidia Drivers :/ Many people have started notice black screen after Update. This driver are mess probably. (Nvidia, not GoPro).
Any one would try for yourself. You don't need GoPro camera, only download drivers from GoPro page, and add source in OBS, and Activate it. If you will try share your results. Please.

 

[prgmitchell]

But when I start special app for GoPro (with drivers installed) error doesn't occur. Only when open OBS and after few seconds Windows show prompt about Camera Offline, and instant Black Screen. I added that It's started occur after update Nvidia Drivers :/ Many people have started notice black screen after Update. This driver are mess probably. (Nvidia, not GoPro).
Any one would try for yourself. You don't need GoPro camera, only download drivers from GoPro page, and add source in OBS, and Activate it. If you will try share your results. Please.

Once again, no issue with OBS but with either the GoPro or NVIDIA driver....you'd want to reach out to either of them for this. I did what you said, got the connection error from Windows, but no black screen. Downgrade you NVIDIA drivers if you think that is the issue.

 

[Vilandino]

Finally, with the help of a guide on YouTube, I solved the problem. I'm sharing it because it might be useful to someone.
All I had to do was disable the setting in the advanced graphics settings in Windows settings: "Scheduling hardware-accelerated GPU processor". That's it. There's no more black screen, even when I use an unconnected GoPro camera and Windows displays an error message, nothing hangs.

Despite everything, the problem started after updating Nvidia drivers, so it's probably still more a problem of failed Nvidia drivers than Windows.

Best regards :)