Few weeks ago, I've reported it as a bug for Max 2018. Issue still exists, but happens on a file which contains imported models from several sources. (Sketchup, Autocad etc.) The reason is likely a bad object, destroying the session's integrity.
After the view turns to Ortho, if you try to orbit the view, Object center gizmos move to viewport center like a visual glitch. Actually objects seem to be moved to infinity. If you render the scene like that, Mental Ray message window gives clues to what is going on. There are several invalid normal errors:
MSG 0.0 186 MB warn : expected structure "E" missing from "m" shader declaration
MSG 0.0 609 MB error: Invalid normal found on object "balta" on face 7827, replacing with a dummy normal
LIB 0.0 10 MB warn 292006: cannot invert a transformation matrix
SCEN 0.4 922 MB error 071011: world-to-camera transformation is singular, abort RC 0.4 922 MB error 081008: scene preprocessing failed
Final is the crash message. Max hangs and you have to terminate the program. But interestingly, it doesn't happen right now, although nothing has changed. I think Autocam plugin has nothing to do with it. May be sparing a few bytes of memory and just delay the issue.
Figuring out the reason of such problems is sheer "mission impossible" when those rendered pixels are the composition of such infinitely many components. Even Windows 10's memory management shoud be examined.