OBS Bricking My Computer

[paulknakk]

Hey everyone, I've tried everything and can't seem to get OBS to work. I had been using OBS for years without any issues and now if I open OBS it'll brick my computer and send it into repair mode after I hard restart it.

Even without streaming...just having the program open it will average 7 FPS and have 83% of frames missed due to rendering lag.

MOTHERBOARD: ASUS ROG Maximus VIII Extreme
CPU: i7-6700K @ 4.00GHz
RAM: 32gb
GPU: NVIDIA GeForce GTX 1080
Windows x64

LOG FILE: https://obsproject.com/tools/analyzer?log_url=https://obsproject.com/logs/c6NSa-7_W0Yt2mVy


Any help would be incredible. I can't figure it out for the life of me and have stopped streaming because of it.

Thank you!

 

[FerretBomb]

Your logfile looks fine at a slow glance, aside from using Display Capture (which should be avoided at all costs, as it is the least-performant capture method, and can conflict BADLY with Game or Window Captures placed into the same scene).

You can try going into %appdata%\obs-studio and rename the 'basic' directory to something else. This is where your Profiles and Scene Collections are stored, so if it's named something else, OBS will start 'fresh', just to see if it's something in your scenes that might be causing the crash (a corrupt video file, stinger, who knows?).
You can also rename global.ini while you're there, before trying to start OBS. Nothing in there should change, but it stores some global config data, so renaming it (and having OBS re-create it on start) is covering-all-bases.
You'll be able to get everything back by deleting the new ones and changing the original ones' names back.
If it works and OBS starts fine? Something's messed up. At that point you can either re-create your scenes by hand, or try to figure out what the problem is and edit the existing. I'd recommend re-creating. Gives a chance to do stuff better than before.

OBS really wouldn't cause a crash and return to Repair Mode though. Normally something like that happens due to system instability, OS file corruption, a bad overclock, or dying hardware component. If the system still crashes, it's not going to be an OBS thing.

Generalized, try running "sfc /scannow" from an elevated command prompt. After that, run a Scandisk.
Are you monitoring your system temperatures, and GPU temp/voltage draw?
Might be a good idea to run Memtest86+ for a while, to make sure your RAM isn't getting notchy, and snag CrystalDiskInfo to check your hard drive's SMART diagnostics.

 

[Deleted member 121471]

To add to Ferret's already info rich reply, another maintenance command that is useful to run in an elevated command prompt is "Dism /Online /Cleanup-Image /RestoreHealth".

 

[paulknakk]

Your logfile looks fine at a slow glance, aside from using Display Capture (which should be avoided at all costs, as it is the least-performant capture method, and can conflict BADLY with Game or Window Captures placed into the same scene).

You can try going into %appdata%\obs-studio and rename the 'basic' directory to something else. This is where your Profiles and Scene Collections are stored, so if it's named something else, OBS will start 'fresh', just to see if it's something in your scenes that might be causing the crash (a corrupt video file, stinger, who knows?).
You can also rename global.ini while you're there, before trying to start OBS. Nothing in there should change, but it stores some global config data, so renaming it (and having OBS re-create it on start) is covering-all-bases.
You'll be able to get everything back by deleting the new ones and changing the original ones' names back.
If it works and OBS starts fine? Something's messed up. At that point you can either re-create your scenes by hand, or try to figure out what the problem is and edit the existing. I'd recommend re-creating. Gives a chance to do stuff better than before.

OBS really wouldn't cause a crash and return to Repair Mode though. Normally something like that happens due to system instability, OS file corruption, a bad overclock, or dying hardware component. If the system still crashes, it's not going to be an OBS thing.

Generalized, try running "sfc /scannow" from an elevated command prompt. After that, run a Scandisk.
Are you monitoring your system temperatures, and GPU temp/voltage draw?
Might be a good idea to run Memtest86+ for a while, to make sure your RAM isn't getting notchy, and snag CrystalDiskInfo to check your hard drive's SMART diagnostics.

Amazing, thank you so much. I'm going to try this stuff. Literally the second I open OBS my entire computer goes into snail mode. It makes no sense...this doesn't happen with any other program I use whether it's a video game, DAW, Premiere, etc. I tried to open OBS and then open snipping tool to get you a screen shot of the stats and it almost bricked my computer.

 

[paulknakk]

Your logfile looks fine at a slow glance, aside from using Display Capture (which should be avoided at all costs, as it is the least-performant capture method, and can conflict BADLY with Game or Window Captures placed into the same scene).

You can try going into %appdata%\obs-studio and rename the 'basic' directory to something else. This is where your Profiles and Scene Collections are stored, so if it's named something else, OBS will start 'fresh', just to see if it's something in your scenes that might be causing the crash (a corrupt video file, stinger, who knows?).
You can also rename global.ini while you're there, before trying to start OBS. Nothing in there should change, but it stores some global config data, so renaming it (and having OBS re-create it on start) is covering-all-bases.
You'll be able to get everything back by deleting the new ones and changing the original ones' names back.
If it works and OBS starts fine? Something's messed up. At that point you can either re-create your scenes by hand, or try to figure out what the problem is and edit the existing. I'd recommend re-creating. Gives a chance to do stuff better than before.

OBS really wouldn't cause a crash and return to Repair Mode though. Normally something like that happens due to system instability, OS file corruption, a bad overclock, or dying hardware component. If the system still crashes, it's not going to be an OBS thing.

Generalized, try running "sfc /scannow" from an elevated command prompt. After that, run a Scandisk.
Are you monitoring your system temperatures, and GPU temp/voltage draw?
Might be a good idea to run Memtest86+ for a while, to make sure your RAM isn't getting notchy, and snag CrystalDiskInfo to check your hard drive's SMART diagnostics.

100% something in the scenes. I uninstalled this and streamlabs obs just in case. Did a fresh install and 0 dropped frames, 60FPS. I've uninstalled / reinstalled previously but I probably just dropped all of my old stingers into the scenes without paying attention. Such an easy fix..I feel dumb for asking. Thank you for the help guys. Followed you on twitch!

 

[FerretBomb]

100% something in the scenes. I uninstalled this and streamlabs obs just in case. Did a fresh install and 0 dropped frames, 60FPS. I've uninstalled / reinstalled previously but I probably just dropped all of my old stingers into the scenes without paying attention. Such an easy fix..I feel dumb for asking. Thank you for the help guys. Followed you on twitch!

No worries man, I had something similar in the past crop up myself. One reason it's my first troubleshooting step... if OBS can be opened, new Scene Collection. If it can't, rename/move the config files out to force it to square-zero. Even if it's just a scene misbehaving or doing something weird.

Also why it pays to make regular backups of the "basic" folder. If you get into complex setups, stuff can break pretty easy and waste *days* of work. If a source/video/etc goes bad on the drive somehow (write error, bit rot, whatever) it won't help, but at least you can try rolling back to a known-working state and go from there (and if it still crashes, know you get to start churning through all your files for the busted one).

Coolcool, catch you there sometime, then! :D

 

[paulknakk]

No worries man, I had something similar in the past crop up myself. One reason it's my first troubleshooting step... if OBS can be opened, new Scene Collection. If it can't, rename/move the config files out to force it to square-zero. Even if it's just a scene misbehaving or doing something weird.

Also why it pays to make regular backups of the "basic" folder. If you get into complex setups, stuff can break pretty easy and waste *days* of work. If a source/video/etc goes bad on the drive somehow (write error, bit rot, whatever) it won't help, but at least you can try rolling back to a known-working state and go from there (and if it still crashes, know you get to start churning through all your files for the busted one).

Coolcool, catch you there sometime, then! :D

Completely makes sense. After I replied last, I had the issue again...completely bricked. It happened as soon as I added my camera to OBS via the elgato camlink. I noticed I had the cam link plugged into a USB 3.1 instead of a 3.0 on the back of my computer. Not sure if that would be enough to make it bug out as much as it did...but it seems to be running fine now.