For me, the most reliable way to get it working is to load the autosave where you've just landed on the beach (for me its Autosave 4) and then load your latest save.
This suggests something isn't being loaded into memory correctly on a fresh start of the game. Potentially due to the location of the save, since anything before the grove seems to work, none of my blighted village saves work until I load my beach save.
As an experiment, I fast travelled back to the over grown ruins, saved the game. restarted the game and tried to load the save and it worked. so now every time I load the over grown ruins save before I load any other save.
Ok in other words:
To workaround a loading crash when loading a savegame you do the following.
You save a game on a location where you allways can load the savegame. Tried and tested it and know it allways works out.
So you then load allways that specific Savegame bevore you load (other actual savegame)into the other environment/location of your current progress Savegame.
Wow, thats some thinking around the corner.
Still to figure out what part of the loading process does make the game crash.
Is it the number of NPCs or is it the number of Polygons/Gameenvironment with a lot of Items etc.
Something is going wrong when loading a lot more instances into memory.
Might be a way to discover the bug.
I have Win 10 Pro
16GB of DDR3
I5-4670k OC@4,1GHz
Nvidia RTX 2060 6GB
4 TB Samsung EVO850 SSD
