You have attached the "crash report". It is different from the session log. The session log has info of what was attempted to load and sometimes may give a hint of what is caused the issue.
Because the crash report:
Code:
Unhandled exception: c0000005
...
Thread 4F78: (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
00000034798FE420 00007FFD30CDBEB8 00007FFD728C3EE0 0000016EF518C060 0000000000000007 0000016EF524BE10 qt6core.dll!0x7ffd30cdbeb8
00000034798FE4E0 00007FFD30CDBB8B 0000000000000002 0000016EF51CDD40 0000000000000000 0000000000000002 qt6core.dll!0x7ffd30cdbb8b
00000034798FE5A0 00007FFDBB088A28 00007FFD72702FF0 0000016EF4C59D20 0000016EF04432C0 0000016EF51CDF80 frontend-tools.dll!0x7ffdbb088a28
00000034798FE600 00007FFDBB061089 0000016EF04432C0 000000031B1E2656 00000034798FE7E0 000000000000001B frontend-tools.dll!0x7ffdbb061089
00000034798FE630 00007FFDC0736AD2 0000000000000000 00000034798FE7E0 0000016EEE150580 0000000000000A10 obs.dll!obs_init_module+0x52
00000034798FE660 00007FFDC07373BA 0000016EF04432C0 0000000000000001 0000016EF5194BA0 000000000000002B obs.dll!load_all_callback+0x11a
00000034798FE690 00007FFDC07387DB 0000016EF5008B00 0000000000000080 0000000000000010 00007FFDC07372A0 obs.dll!process_found_module+0x36b
00000034798FE750 00007FFDC0738B38 0000016EF524E720 00007FFDC07372A0 00000034798FE7E0 0000000000000000 obs.dll!find_modules_in_path+0x2a8
00000034798FE7C0 00007FFDC0737598 0000016EEDD9D4A0 0000016EEDD9D4A0 00000034798FE920 0000016EEDFA8EA0 obs.dll!obs_load_all_modules2+0x68
00000034798FE820 00007FF71EC4FB59 0000016EEDD9D4A0 0000016EEDD9D4A0 00007FFD30FA5360 00000034798FF890 obs64.exe!OBSBasic::OBSInit+0x1809
00000034798FF210 00007FF71EDB95A2 0000016EEAF82D01 0000000000000000 00000034798FFAD0 00000034798FFA20 obs64.exe!`QtPrivate::QMetaTypeForType<AuthListener>::getDefaultCtr'::`5'::<lambda_1>::<lambda_invoker_cdecl>+0x2
00000034798FF2E0 00007FF71EDC1CE9 0000000000000000 00000034798FFAD0 0000016EEAFE3BD0 0000000000000001 obs64.exe!ParseVarName+0xc9
00000034798FF9D0 00007FF71EDC4167 0000000000000000 0000000000000000 0000000000000000 0000016EEAFE3BD0 obs64.exe!OBSApp::FindThemes+0x987
00000034798FFBA0 00007FF71EDEF3CD 0000000000000001 0000000000000000 0000016EEAFC3B10 0000016EEAFC73E0 obs64.exe!MultitrackVideoOutput::HandleIncompatibleSettings+0x51d
00000034798FFC30 00007FF71EDEEC6E 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!GoLiveApi::Config::operator=+0x11e
00000034798FFC70 00007FFDEB3CE8D7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ffdeb3ce8d7
00000034798FFCA0 00007FFDECD314FC 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ffdecd314fc
...
only shows that there was problem during load of the "frontend-tools.dll" module that is part of OBS. It can be fault at loading of the
Scripts or something else, so some details are needed.
If you don't want to troubleshoot the issue and need instant solution - you can try OBS portable mode in different folder. For portable mode, please read only after the words "if it was not clear":
https://obsproject.com/forum/thread...»-when-opening-app-settings.82157/post-346499 or in the Help:
https://obsproject.com/kb/portable-mode
It should start fine.