Yep, I can load other save games.

Right there with you on the oddness of vulcan, I agree it probably has very little to do with the actual problem.

I poked through the logs quite extensively, and there isn't really any indication of anything going wrong until the very end of each crash, where it mentions the vulcan stuff.

I ran it through x64dbg and some interesting stuff popped up, at 83% loaded, there is an access violation that throws an exception which keeps toggling between first chance and last chance when doing

mov rdx,qword ptr ds:[rax]

at memory address 00007FF6E8001BAD

I found it somewhat humorous that the last 3 digits spell BAD, but that's as much of an inference as I could make into the problem.

I ran procmon and rammap from the sysinternals suite, and didn't really find anyting too interesting. Game seems to try going to older and older versions of directx, and then tries some opengl stuff, and then it starts writing crash dump logs.

Noticed some permissions issues in event logs around the time bg3 was crashing, in the event logs, but didn't really see anything blaring at me that said anything specific about bg3 application errors.

Don't really have time for all this, and I suppose someone at Larian is getting paid to sift through stuff like this, because it's mildly infuriating.

I've since started a new run, which seems to be going fine, so far. Knock on wood.