Hmm yea I'm kind of at a loss here...
Your log shows the tyFlow sim completing without issue, prior to render completion. And the error says it's related to an ExecuteMAXScriptScript exception - but the only time tyFlow calls that function of the API in your scene is before simulation starts, and every time tyFlow calls that function it also specifies a conditional argument telling max to ignore any exceptions which may occur....so it shouldn't even be possible for tyFlow to generate an exception related to that function call.
Are you sure you don't have another script or plugin which is generating the error? I can render the scenes you've sent from the command line without issue, and nobody else has reported any similar issues.....the error doesn't seem related to tyFlow at this point...I could be wrong of course, but I can't figure out how or where tyFlow could be causing this issue.
The only other thing I can think of, is that tyFlow generates some macroscripts when Max starts to expose certain tyFlow properties to MAXScript...it's possible that those macroscripts are being evaluated after the simulation completes (therefore the log doesn't show the exception occurring) and that your machine is configured in a way that results in an error when they evaluate....but that macroscript-generating function has been unchanged within tyFlow for at least a year, and you mentioned only recent versions of tyFlow have the crashing issue, so I don't think that can be it.
Maybe some other script or plugin you have installed is conflicting with new tyFlow classes introduced in recent versions, and so when the other script/plugin evaluates, the naming conflict generates an error. That's my best guess but I honestly have no idea.
One thing I could do is see about writing a dummy plugin that hooks Max's ExecuteMAXScriptScript function and prints a log of anything sent to it...running that on your machine would tell us exactly which script is the troublemaker. Let me know if you're up for trying that.
Your log shows the tyFlow sim completing without issue, prior to render completion. And the error says it's related to an ExecuteMAXScriptScript exception - but the only time tyFlow calls that function of the API in your scene is before simulation starts, and every time tyFlow calls that function it also specifies a conditional argument telling max to ignore any exceptions which may occur....so it shouldn't even be possible for tyFlow to generate an exception related to that function call.
Are you sure you don't have another script or plugin which is generating the error? I can render the scenes you've sent from the command line without issue, and nobody else has reported any similar issues.....the error doesn't seem related to tyFlow at this point...I could be wrong of course, but I can't figure out how or where tyFlow could be causing this issue.
The only other thing I can think of, is that tyFlow generates some macroscripts when Max starts to expose certain tyFlow properties to MAXScript...it's possible that those macroscripts are being evaluated after the simulation completes (therefore the log doesn't show the exception occurring) and that your machine is configured in a way that results in an error when they evaluate....but that macroscript-generating function has been unchanged within tyFlow for at least a year, and you mentioned only recent versions of tyFlow have the crashing issue, so I don't think that can be it.
Maybe some other script or plugin you have installed is conflicting with new tyFlow classes introduced in recent versions, and so when the other script/plugin evaluates, the naming conflict generates an error. That's my best guess but I honestly have no idea.
One thing I could do is see about writing a dummy plugin that hooks Max's ExecuteMAXScriptScript function and prints a log of anything sent to it...running that on your machine would tell us exactly which script is the troublemaker. Let me know if you're up for trying that.