Hi Team,
Few months ago I posted a question on assertion failures in sql 2016, for more info please check below link.
Here Am posting this again as , I could find resolution for this kind of errors in SQL 2016:
1. By changing the recovery Model to full and to execute the script/SP/ or your query,, and you can change back the recovery model to simple, then you couldn't see this error again
2. By enabling the trace flag 692 globally/ session, also will fix the issue.