Question / Help OBS Crashing: Unhandled exception: 80000003

[Cormiester3241]

Hello everyone,

I am opening this thread because I have been experiencing OBS Studio, 64-bit crashes since October. I started streaming in April of 2015 and it has never happened until October of 2018. Now, I did research and found out that the issue was related to OBS.22.1.0 or a version similar and was recommended to install the older version of OBS Studio, 21.1.2, which I did. Everything was great for a few weeks until a few nights ago, as well as tonight. Open opening OBS to begin streaming, it crashed. The Crash Report has been attached. Any recommendations? Again, I have been streaming since April of 2015 with no issues. Nothing was changed and now it continues to crash. Thanks in advance.

 

[koala]

I would only use the most recent version of any software. In the crashlog traces of this software can be found:

- Windows 10 17134 (1803)
- AVG Antivirus
- Elgato software
- Nvidia Video driver
- Nvidia 3d Vision driver
- CoreAudio driver

Make sure that every one of these, including OBS, is the most recent version available. Update OBS to the current version and update Windows to the current version (you still have the previous 1803) and update every other software mentioned above. Remove Nvidia 3d Vision, if you don't use any of the 3D features of this driver. If your AVG Antivirus is old, remove it and rely on the default Microsoft Defender Antivirus - recent tests say Defender is on par with the best virus scanners since about a year, so there is no reason to not use Defender.

 

[Cormiester3241]

Thank you for your input, koala.

Last night I uninstalled all Elgato software I had, uninstalled AVG, updated my NVIDIA drivers while uninstalling the 3D drivers, completely uninstalled Apple as that is where the CoreAudio came from, uninstalled OBS and did a restart. I then went back through the process of reinstalling everything and their latest versions.

I even downloaded 7Zip to installed the CoreAudio AAC stuff from iTunes. It all worked perfectly yesterday. But, like I said, it’s absolutely random when it happens.

With that said, when/if it happens again, I’ll be back with an update.

Thanks!