Unfortunately without the minidump
we cannot identify the problem, because the error is too generic (just an exception was triggered).
This is the documentation from Deadline:Trapped SEH Exception in CurRendererRenderFrame(): Access Violation
An Access Violation means that when rendering the frame, Max either ran out of memory, or memory became corrupted. The stack trace in the error message usually shows which plugin the error occurred in. If that doesn’t help track down the issue, try stripping down the max file by deleting objects and seeing if the error still occurs.
If the last line of your job log report showed INFO: Lightning: Overriding save file option to 0 as the message, it may be related to one or more of your render output paths, including Render Element file paths being > 255 characters in length (Windows OS limitation). To resolve, simply reduce the overall length of the file path you are saving your renders to. Bear in mind, if using V-Ray’s VFB “Separate render channels” option, the overall file path may be longer than you can currently visualize inside of 3ds Max prior to network render submission. If enabled, there are SMTD Sanity Check’s to test for this situation during submission.
What render engine do you use ?
I would suggest to try a render using Backburner, to see if there is any difference, or at least Max generates the minidump and we can get more information.