00000007F7AFEA38 00007FFB81047B20 000001674E0F6490 0000000000000000 000001674E04B210 FFFFFFFFFFFFFFFF win-decklink.dll!DeckLinkDeviceMode::GetHeight+0x0
00000007F7AFEA40 00007FFB81043293 000001675309A0E0 000001675309A0E0 000000000000001A 0000016746EDC5E0 win-decklink.dll!decklink_output_start+0x133
00000007F7AFEAB0 00007FFB7EBC9221 000001675309A0E0 0000000000000000 0000000000000020 0000016746EDC5E0 obs.dll!obs_output_actual_start+0x51
00000007F7AFEAE0 00007FFB7EBCB427 0000000000000002 0000000000000002 000001675305DFC0 0000000000000000 obs.dll!obs_output_start+0x87
00000007F7AFEB10 00007FFB8AE0EB23 000001675305DFC0 0000000000000002 0000000000000020 000001674E04B210 decklink-ouput-ui.dll!output_start+0x43
00000007F7AFEB40 00007FFB8AE0E786 0000000000000006 0000016746EDC5E0 0000000000000070 000001675305D420 decklink-ouput-ui.dll!OBSEvent+0x36
Well, according to that crashlog it's definitely the Decklink dll causing the crash. :/
Unfortunately there is no 'last known good-start' configuration saved by OBS to easily recover.
It IS possible to edit the Scene Collection JSON to remove the Decklink source from your scenes... by hand. Which can similarly break things if it isn't done just right.
Unfortunately there is no way to easily recover, unless you backed up your 'basic' directory.
For a quick 'get it running again ASAP', you can go to %appdata%\obs-studio\basic and rename the 'scenes' directory to something else. They'll be blank when you start OBS again, but it SHOULD start up at least. You can then (with OBS not running!) move the .json files from the renamed directory to the new 'scenes' directory one by one until you find the scene collection that's causing the problem.
There ARE .bak files in there, but as it sounds like you've tried to start OBS a few times, the .bak would likely have been overwritten by the bad-values .json by now.
This is why I save a backup of my 'basic' directory every month, and before doing any significant config changes. It's bitten me before, though not with a Decklink.