OBS updated and now crashes (won't start)

Can you also attach regular log-file not only crash report? There should be one with similar time and date.

OBS log files can be found in the folder: %APPDATA%\obs-studio\logs
OBS crash reports can be found in the folder: %APPDATA%\obs-studio\crashes
 
if you rename
Code: 
%appdata%\obs-studio\basic\profiles
to
Code: 
profiles-backup
you should at least be able to start OBS, although your settings will be reset.
 
Suslik V said:
Can you also attach regular log-file not only crash report? There should be one with similar time and date.

OBS log files can be found in the folder: %APPDATA%\obs-studio\logs
OBS crash reports can be found in the folder: %APPDATA%\obs-studio\crashes
Click to expand...
I'm putting both here - looking back it looks like I somehow put the wrong crash log.
 

Attachments

prgmitchell said:
if you rename
Code: 
%appdata%\obs-studio\basic\profiles
to
Code: 
profiles-backup
you should at least be able to start OBS, although your settings will be reset.
Click to expand...
Thanks - there was a weird (corrupted probably) profile in that directory. I dropped our primary back in there and we are running on an older version.
 
Code: 
Unhandled exception: e06d7363
Date/Time: 2026-08-30, 10:53:51
Fault address: 7FF96B1B187A (c:\windows\system32\kernelbase.dll)
libobs version: 32.2.2 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 9168; 64-bit)
CPU: Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz


Thread 5104: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000125CD9E7F0 00007FF96B1B187A 000002082D8932A0 00007FF6D4D0C12D 000002082BD49EE0 00007FF6D4DB8A65 kernelbase.dll!0x7ff96b1b187a
000000125CD9E8F0 00007FF967425277 000000125CD9EA09 00007FF8C0F30E44 000002082D8932A0 00007FF8C0F7D0F8 vcruntime140.dll!0x7ff967425277
000000125CD9E950 00007FF6D4F1C830 000002082D9564E0 0000000000000000 0000000000000003 000000125CD9EB70 obs64.exe!OBSBasic::GetCurrentProfile+0x1c0
000000125CD9EA10 00007FF6D4FB5D4E 000002089055BB40 0000020800000000 000002082EE0A620 000000006B0A9BD1 obs64.exe!OBSStudioAPI::obs_frontend_get_current_profile_path+0x1e
000000125CD9EA70 00007FF8C0E7059D 000002084AF8F940 00000594F02057C7 000002082DE53C40 0000000000000000 obs-websocket.dll!0x7ff8c0e7059d
000000125CD9EC20 00007FF8DD35B9CD 000002084AF8F940 000000125CD9ED08 0000000000000000 000002082F5C8520 obs.dll!obs_init_module+0x5d
000000125CD9EC50 00007FF8DD35C61F 000002084AF8F940 000002084AA57200 0000000000000012 00007FF8DD411ABE obs.dll!load_all_callback+0x12f
000000125CD9ECA0 00007FF8DD35DAD2 00007FF8DD35C4F0 000000125CD9ED90 000000125CD9EE00 000002082DE53C40 obs.dll!obs_find_modules2+0xd32
000000125CD9ED70 00007FF8DD35C7D0 000000125CD9EF00 00007FF6D516E270 7FFFFFFFFFFFFFFC 0000000039667B94 obs.dll!obs_load_all_modules2+0x40
000000125CD9EDF0 00007FF6D4EF58C9 000002082BD49EE0 000000125CD9F2D0 000002082D6FAF40 00007FF6D4EC9C60 obs64.exe!OBSBasic::OBSInit+0x14b9
000000125CD9F1D0 00007FF6D4FC09E1 0000000000000002 0000000000000000 000002082DD53E20 000002082BCE1670 obs64.exe!OBSApp::OBSInit+0x331
000000125CD9F4D0 00007FF6D4FB31C1 000000125CD9F950 0000001200000001 0000000000000001 00007FF96D8C0000 obs64.exe!run_program+0xa51
000000125CD9F910 00007FF6D4FB4201 0000000000000000 000000125CD9FB20 000000000000000A 0000020829A8824E obs64.exe!main+0xa91
000000125CD9FAF0 00007FF6D502C070 0000000000000001 0000000000000000 0000000000000000 0000000000000000 obs64.exe!qtEntryPoint+0x30
000000125CD9FB80 00007FF6D502B699 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!__scrt_common_main_seh+0x109
000000125CD9FBC0 00007FF96B7BCCB7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ff96b7bccb7
000000125CD9FBF0 00007FF96D96AD6C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff96d96ad6c
...
It is crash caused by the "websoket" load procedure (probably the file path handling, UTF-8, Unicode symbols in the path to the file or inside the file etc; at least, the problem started after the corresponding part of OBS was changed). Very similar to this old thread (v31.1.0): https://obsproject.com/forum/threads/crashing-upon-startup-after-newest-update.186845/

According to the timestamps your OBS crashed right after the:
Code: 
10:53:46.083: Current Date/Time: 2026-08-30, 10:53:46
...
10:53:46.259: OBS 32.2.2 (64-bit, windows)
...
10:53:50.332: [obs-websocket] [obs_module_load] you can haz websockets (Version: 5.7.4 | RPC Version: 1)
10:53:50.332: [obs-websocket] [obs_module_load] Qt version (compile-time): 6.11.1 | Qt version (run-time): 6.11.1
10:53:50.332: [obs-websocket] [obs_module_load] Linked ASIO Version: 103200
<--- here it crashed
...
and then few messages were added from few remaining program threads.

Previously, developers asked ( here: https://github.com/obsproject/obs-websocket/pull/1282#issuecomment-2721796951 ) for the logs to understand what is happening. Now you have it. So, you may try to fill out new issue on GitHub (if the problem still exist, and reproducible): https://github.com/obsproject/obs-studio/issues
 
Suslik V said:
Code: 
Unhandled exception: e06d7363
Date/Time: 2026-08-30, 10:53:51
Fault address: 7FF96B1B187A (c:\windows\system32\kernelbase.dll)
libobs version: 32.2.2 (64-bit)
Windows version: 10.0 build 26200 (release: 25H2; revision: 9168; 64-bit)
CPU: Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz


Thread 5104: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
000000125CD9E7F0 00007FF96B1B187A 000002082D8932A0 00007FF6D4D0C12D 000002082BD49EE0 00007FF6D4DB8A65 kernelbase.dll!0x7ff96b1b187a
000000125CD9E8F0 00007FF967425277 000000125CD9EA09 00007FF8C0F30E44 000002082D8932A0 00007FF8C0F7D0F8 vcruntime140.dll!0x7ff967425277
000000125CD9E950 00007FF6D4F1C830 000002082D9564E0 0000000000000000 0000000000000003 000000125CD9EB70 obs64.exe!OBSBasic::GetCurrentProfile+0x1c0
000000125CD9EA10 00007FF6D4FB5D4E 000002089055BB40 0000020800000000 000002082EE0A620 000000006B0A9BD1 obs64.exe!OBSStudioAPI::obs_frontend_get_current_profile_path+0x1e
000000125CD9EA70 00007FF8C0E7059D 000002084AF8F940 00000594F02057C7 000002082DE53C40 0000000000000000 obs-websocket.dll!0x7ff8c0e7059d
000000125CD9EC20 00007FF8DD35B9CD 000002084AF8F940 000000125CD9ED08 0000000000000000 000002082F5C8520 obs.dll!obs_init_module+0x5d
000000125CD9EC50 00007FF8DD35C61F 000002084AF8F940 000002084AA57200 0000000000000012 00007FF8DD411ABE obs.dll!load_all_callback+0x12f
000000125CD9ECA0 00007FF8DD35DAD2 00007FF8DD35C4F0 000000125CD9ED90 000000125CD9EE00 000002082DE53C40 obs.dll!obs_find_modules2+0xd32
000000125CD9ED70 00007FF8DD35C7D0 000000125CD9EF00 00007FF6D516E270 7FFFFFFFFFFFFFFC 0000000039667B94 obs.dll!obs_load_all_modules2+0x40
000000125CD9EDF0 00007FF6D4EF58C9 000002082BD49EE0 000000125CD9F2D0 000002082D6FAF40 00007FF6D4EC9C60 obs64.exe!OBSBasic::OBSInit+0x14b9
000000125CD9F1D0 00007FF6D4FC09E1 0000000000000002 0000000000000000 000002082DD53E20 000002082BCE1670 obs64.exe!OBSApp::OBSInit+0x331
000000125CD9F4D0 00007FF6D4FB31C1 000000125CD9F950 0000001200000001 0000000000000001 00007FF96D8C0000 obs64.exe!run_program+0xa51
000000125CD9F910 00007FF6D4FB4201 0000000000000000 000000125CD9FB20 000000000000000A 0000020829A8824E obs64.exe!main+0xa91
000000125CD9FAF0 00007FF6D502C070 0000000000000001 0000000000000000 0000000000000000 0000000000000000 obs64.exe!qtEntryPoint+0x30
000000125CD9FB80 00007FF6D502B699 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs64.exe!__scrt_common_main_seh+0x109
000000125CD9FBC0 00007FF96B7BCCB7 0000000000000000 0000000000000000 000004F0FFFFFB30 000004D0FFFFFB30 kernel32.dll!0x7ff96b7bccb7
000000125CD9FBF0 00007FF96D96AD6C 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x7ff96d96ad6c
...
It is crash caused by the "websoket" load procedure (probably the file path handling, UTF-8, Unicode symbols in the path to the file or inside the file etc; at least, the problem started after the corresponding part of OBS was changed). Very similar to this old thread (v31.1.0): https://obsproject.com/forum/threads/crashing-upon-startup-after-newest-update.186845/

According to the timestamps your OBS crashed right after the:
Code: 
10:53:46.083: Current Date/Time: 2026-08-30, 10:53:46
...
10:53:46.259: OBS 32.2.2 (64-bit, windows)
...
10:53:50.332: [obs-websocket] [obs_module_load] you can haz websockets (Version: 5.7.4 | RPC Version: 1)
10:53:50.332: [obs-websocket] [obs_module_load] Qt version (compile-time): 6.11.1 | Qt version (run-time): 6.11.1
10:53:50.332: [obs-websocket] [obs_module_load] Linked ASIO Version: 103200
<--- here it crashed
...
and then few messages were added from few remaining program threads.

Previously, developers asked ( here: https://github.com/obsproject/obs-websocket/pull/1282#issuecomment-2721796951 ) for the logs to understand what is happening. Now you have it. So, you may try to fill out new issue on GitHub (if the problem still exist, and reproducible): https://github.com/obsproject/obs-studio/issues
Click to expand...
Thank you! I believe the update corrupted the directory where profiles are stored. Current working on an older version and will retry the upgrade.
 
You must log in or register to reply here.
Back
Top