OBS Studio crashes on launch

[coolepicgaymer]

My OBS crashes on launch and has since I installed it again recently.

My windows 10 is completely up to date, and so are all of my CPU and graphics drivers.

I've also tried reinstalling it several times, clearing old app data and such, none of which has done anything.

Spoiler: Crash log

Unhandled exception: e06d7363
Date/Time: 2021-11-26, 20:19:20
Fault address: 7FFEA3B64F69 (c:\windows\system32\kernelbase.dll)
libobs version: 27.1.3 (64-bit)
Windows version: 10.0 build 19044 (release: 2009; revision: 1387; 64-bit)
CPU: Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz


Thread 10AC: (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
00000095084ECD90 00007FFEA3B64F69 FFFFFFFFFFFFFFFE 00000095084ECF60 0000022BC4B291C0 00007FFE2A64EE01 kernelbase.dll!0x7ffea3b64f69
00000095084ECE70 00007FFE2A95115E 00007FFE2A400000 0000022BC4E68D10 00007FFE2B30CBF8 00000095084F0E38 libmfxhw64.dll!0x7ffe2a95115e
00000095084ECEF0 00007FFE2A665760 FFFFFFFFFFFFFFFF 00000095084F0CB8 00007FFE2B304818 0000000000000001 libmfxhw64.dll!0x7ffe2a665760
00000095084ECFD0 00007FFE2A683A96 0000000000000000 00000095084FCFA0 FF00363149786600 0000000000000000 libmfxhw64.dll!0x7ffe2a683a96
00000095084ED050 00007FFE2A667305 0000022BC01FA730 0000000000000005 0000000000000300 00007FFEA5E747B1 libmfxhw64.dll!0x7ffe2a667305
00000095084FCDC0 00007FFE2A66359B 00000095084FE549 0000000000000000 0000000000000000 00007FFE2A66389E libmfxhw64.dll!0x7ffe2a66359b
00000095084FCDF0 00007FFE2A648FD2 0000000000000001 0000022BC4BCCA28 0000022BC4BCCA28 00007FFE7A1096D0 libmfxhw64.dll!0x7ffe2a648fd2
00000095084FCF60 00007FFE7A0FABED 0000022BC4980C40 0000022BC4E791B8 0000022BC4E6CB80 0000022BC4B5B360 obs-qsv11.dll!0x7ffe7a0fabed
00000095084FE3F0 00007FFE7A0F9977 0000000000000000 0000000000000000 0000000000000000 0000022BC0114100 obs-qsv11.dll!0x7ffe7a0f9977
00000095084FE470 00007FFE7A0F8FD0 0000022B00010000 0000000000000000 0000022BC4E2F180 00000000000000E0 obs-qsv11.dll!0x7ffe7a0f8fd0
00000095084FE4A0 00007FFE7EC72E01 0000000000000000 0000022BC4E6CB80 00000095084FE549 00000095084FE549 obs.dll!obs_init_module+0x51
00000095084FE4D0 00007FFE7EC72C4B 00007FFE7EC72420 0000000000000000 0000022BC4A4DC00 0000022BC03B4420 obs.dll!obs_find_modules+0x39b
00000095084FE5B0 00007FFE7EC72E5E 0000022BBDA0A720 00007FF65E6BE038 0000022BBB714C80 0000000000000001 obs.dll!obs_load_all_modules+0x1e
00000095084FE5E0 00007FF65E516684 0000022BBD7CA7D0 0000022BBD7CA7D0 FFFFFFFFFFFFFFFF 00000095084FFA80 obs64.exe!OBSBasic::OBSInit+0x454
00000095084FF4E0 00007FF65E4F0A22 00000095084FF8D0 00007FF65E795ED0 00000095084FFBE0 0000022BBB652480 obs64.exe!OBSApp::OBSInit+0x342
00000095084FF830 00007FF65E4F6F53 0000000000000000 0000022BBB648F90 0000022B00000000 0000022BBB645B10 obs64.exe!run_program+0x703
00000095084FFBA0 00007FF65E4F9290 0000000000000000 0000000000000000 0000000000000000 FFFFFFFFFFFFFFFF obs64.exe!main+0x6c0
00000095084FFD70 00007FF65E68E3D7 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!WinMain+0x157
00000095084FFE00 00007FF65E68DC96 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!__scrt_common_main_seh+0x106
00000095084FFE40 00007FFEA4037034 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7ffea4037034
00000095084FFE70 00007FFEA5EA2651 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffea5ea2651

Full log file is attached below.

 

[Harold]

Your intel igpu drivers are not actually up to date.

 

[coolepicgaymer]

Your intel igpu drivers are not actually up to date.

Well, checking for updates in the driver assistant leads me to a page saying that there are "No supported driver or software updates are available for your system.". The icon for the assistant suggests that it is up to date as well, since it's got a green dot.

I've also tried just downloading a driver directly from the Intel website, but when launching that I am met with the installer saying "Your system has a driver that is locked to manufacturer specifications. Please try downloading the latest driver from the manufacturer's website." which I'm not sure what that is supposed to mean considering it is indeed manufactured by Intel.

Do you have any suggestions? Is there something that I am missing?

 

[Want To Learn]

I have the same issue. I posted from a shortcut. I hope it works! Thanks.

 

[Harold]

Well, checking for updates in the driver assistant leads me to a page saying that there are "No supported driver or software updates are available for your system.". The icon for the assistant suggests that it is up to date as well, since it's got a green dot.

I've also tried just downloading a driver directly from the Intel website, but when launching that I am met with the installer saying "Your system has a driver that is locked to manufacturer specifications. Please try downloading the latest driver from the manufacturer's website." which I'm not sure what that is supposed to mean considering it is indeed manufactured by Intel.

Do you have any suggestions? Is there something that I am missing?

Graphics Driver Installation Error: "Your system has a...

Solution for how to install Intel Graphics Driver 26.20.100.8141 or newer when receiving Original Equipment Manufacturer (OEM) installation errors.

www.intel.co.uk

 

[Want To Learn]

Fixed my crash or freeze startup issue. I watched youtube video that showed me how to move the .json (I think they are the scene information) files for a backup. I moved them to another place and I tried to startup OBS so it crashed! After Win 10 loaded in I thought why not quickly click on settings to see if I can quickly disable the parameters that might be requiring too much power. It seemed that I would get as far as the sound meters would be active for a few seconds before the crash, but this time I had all the time I needed to change the settings if that was the problem. I would think I did too much with my scenes. I need to mention I am using Win 10 on a Virtual Machine. I do realize I can only do some things on it before it should freeze, but I am enjoying it so why not? LOL. Thanks!

 

[Want To Learn]

Fixed my crash or freeze startup issue. I watched youtube video that showed me how to move the .json (I think they are the scene information) files for a backup. I moved them to another place and I tried to startup OBS so it crashed! After Win 10 loaded in I thought why not quickly click on settings to see if I can quickly disable the parameters that might be requiring too much power. It seemed that I would get as far as the sound meters would be active for a few seconds before the crash, but this time I had all the time I needed to change the settings if that was the problem. I would think I did too much with my scenes. I need to mention I am using Win 10 on a Virtual Machine. I do realize I can only do some things on it before it should freeze, but I am enjoying it so why not? LOL. Thanks!

Update: It could be the sound settings within the VBox settings. When I was troubleshooting I turned them off. When I turned them back on The meters were red and in the trouble zone. I plan to investigate more on it. Hopefully my posts will benefit someone. Thanks to ALL!

 

[Want To Learn]

Fixed my crash or freeze startup issue. I watched youtube video that showed me how to move the .json (I think they are the scene information) files for a backup. I moved them to another place and I tried to startup OBS so it crashed! After Win 10 loaded in I thought why not quickly click on settings to see if I can quickly disable the parameters that might be requiring too much power. It seemed that I would get as far as the sound meters would be active for a few seconds before the crash, but this time I had all the time I needed to change the settings if that was the problem. I would think I did too much with my scenes. I need to mention I am using Win 10 on a Virtual Machine. I do realize I can only do some things on it before it should freeze, but I am enjoying it so why not? LOL. Thanks!

Update: The crash has nothing to do with OBS it has to do with the VM that I'm using. It turns out that if I check "audio in" before Win 10 loads any audio application crashes after a short period of time. Voice recorder crashed, so it must be that setting or maybe it's in a Win 10. setting?