All of the sudden today (first time using v.2.31) I have exactly the same errors as OP using both TexGen64 and DynDOLOD64, Skyrim SSE and MO2 v.2.0.83.
I do know for sure that my load order (and my mod list), although very heavy, is rock solid.
It loads perfectly fine with xEdit (latest version posted in AFK)
So I started doing tests...basically the majority of what you have advised in this post. What I have discovered:
1. Rolling back to v.2.26 of both TexGen64 and DynDOLOD64 gave me exactly the same errors as 2.31 (!!!); the ones like OP.
2. I made a separate profile to MO2 and loaded only the DLCs+USSEP+Vanilla Billboards. All loaded fine. No Errors. Both versions of TexGen and DynDOLOD.
3. I started enabling 10-10 plugins at a time. TexGen64 (2.31) was loading fine until it reached plugin order 180 (Mod Index B2). Then crashed. Exactly same errors like before, like OP. Of course there is nothing wrong with the plugins after order 180...no matter what plugin I was placing after 180 and enabling it, TexGen64 and DynDOLOD64 would immediately throw an exemption when reach at this index when loading.
4. As a last step I run my entire load order (enabled everything) using TexGen32 and DynDOLOD32 through MO2...and what do u know!!! They worked just fine!!!??? No errors, no exemptions, no crashes, no "Your Load Order is messed up" messages.
Taking into account that not much had changed in my mod list ever since I was running successfully 2.27; I hardly think that this is a DynDOLOD64 problem.
But then why 32-bit version to work out well when I have never ever used it in the past?
A windows update screwing up things? Don't know...running out of ideas.
My Win 10 version is 1703 (OS Build 15063.540).
Edited by Astakos, 01 September 2017 - 01:32 PM.