Enabling papyrus logging was very interesting.

There are so many script errors. Mainly dealing with startup and the adventurers and travelers mod (which may only be state change errors).
The game kept playing w/o hickups.
I also have a lot of errors on barricade activators that I use for my fortifications. ( I will want to see if I can switch them for static barricades).

But the kicker, right before the repeatable CTD is:
There is a critter spawn right there in/next to the -2,2 cell. where the CTD occurs

Does that look like the kind of error that would cause a CTD?


(edited for typo's)

These critter script errors are Bethesda-made and very common, and not indicative of your CTD. I would go as far as to say that Papyrus logs sometimes aren't the best place to look when diagnosing a CTD because generally the cause of the crash isn't script subsystem related. They sandboxed Papyrus away from the main game pretty well.

I hear what you are saying, but the spawn scripts have been a common feature with observed ctd's.
my vram and processor are nominal at that point and I have a fairly beefy rig. I am not saying the spawn is the proximate cause of the crashes , but I am not ruling it out as a precipitous cause, either. It may be part of an a+b+c=ctd . I will do more testing and report .