I have been having the problem of Mental Ray crashing after a distributed render - that is, MR does the translation, distributes photon processing, does multiple final gather passes, renders, and finally crashes after all the buckets are put back together in the buffer. To salvage my precious rendering, I have to move the error message aside and screen capture the window.

I breathlessly installed both SP1 and the hotfix on all boxes. Now, after it crashes just the same, it at least gives me the error reporting window. Tiny consolation.

I’ve tried all combinations of turning certain servers on and off. It doesn’t happen during a single-box render, but of course that negates the purpose of building my server cluster.

I’m having a hard time describing how frustrating this is, waiting through a render for a crash that happens at the very end. I’m losing billable hours trying to work around this, and I’m wishing there were a way to save out my file in a previous version so I could at least try doing this in Max 2009.

We’ve encountered this problem here at work.  We have several dedicated render boxes that we use for DBR and Backburner jobs.  Occasionally, we’ll get errors like Slave 1 Died, or the end of render crash like you’ve described. 

Sometimes it’s caused by more than one person using DBR with the same boxes.  Or a job running in Backburner while trying to DBR.  We’ve found that this can sometimes cause multiple instances of the raysat service running.  Check to make sure it’s only running once.

We’ve also had to do rebuilds of the boxes, full reinstall of OS and software. 

Does it give you a specific mental ray error, or just the generic “error has occurred and Max will now close” error message?

3DS Max Design 2011 64-bit - Advantage Pack
Dell Precision T5500, Dual Six Core Xeon X5650 @ 2.67GHz, nVidia Quadro 5000, 24 GB RAM, Win 7 Enterprise 64-bit
Minneapolis, MN, USA

I had this happen to me last week.
After waiting 14hrs for a dbr render and it crashes is enough to drive a man crazy.
One thing I found was hiding geometry, doing a render test and seeing if any geometry or material was the culprit . I found a Plasma screen I was using was causing problems.
I deleted that and It worked.
I also found using BSP2 caused a lot of crashes, if I canceled during a dbr render it would crash.
So I went back to BSP1, its more robust.

cheers

AKA Bullseye, Spacelord

I just can’t win - This time I was reproducing the crash condition, and the crash shut down Firefox where I was trying to document it!

Here’s what I did - simplified the render conditions so that it worked, then worked my way back until it crashed. In my interior architecture scene:
1. Turned off GI, left FG on, turned on Material Override with a flat grey Arch & Design Mat. DBR worked.
2. Turned on GI, all else same. Worked.
3. Turned off Material Override - broke.

I’d say it’s something to do with materials or raytracing, but why would it fully render and then crash?

Error Codes:
DB 4.n fatal 041500: interrupted by exception code 0x0000005 (access code violation)

Followed by perpetual C++ runtime errors:
R6025 Pure Virtual Function Call

yeah i had the same problem once .

same error 2010
db render

DB 5.n fatal 041500: interrupted by exception code 0x0000005 (access code violation)

Okay, a little progress - per a friend’s suggestion, I tried installing the extensions (Not just the patches), and I’m having better luck. I successfully did three distributed renders, and it actually seemed to get the buckets out and back faster than before!

Then I changed one particular Arch & Design material from flat to shiny and it broke. I made it less shiny and it worked. I’m afraid I’m at a loss to figure out the problem in any sort of logical way.

I just moved over to 2010 and I’m having this same problem right now.  What’s the deal?  Anybody find a solution? . . .

Thanks,
Cory

I’m having the same problem using 3ds MAX 2010 Design.

I HATE this!!!

All my renderfarm is uselless because of this error!!!

And this happens using BSP and BSP2.

Autodesk should work the solution out instead of offering another new versions of 3ds MAX to get more of our money.

I’m looking forward for the fix.

Greetings,

kcpr

kcpr raffaEl

http://www.wizualizacje-3d.eu/en/portfolio