When a computer is acting up, render to a still sequence. When it crashes, see what the last frame rendered was, and start the next render after that. Also, since each frame is its own finished still, there’s no “wrapping up” of the movie at the end, which may cause the crash. I don’t know about that “wrapping up” — I could be way off base.
But that’s a workaround, and general good practise with a flakey computer. But as for a solution, we need to see what happens at the crash:
– Watch your RAM usage (Task Manager or Activity Monitor) to see if it gets to 100%. That could cause a crash. Secret settings should fix that, but you might have already done that. But if it always crashes when RAM usage reaches a specific amount, then yes, you probably have bad RAM. If that’s the case, can you run lean, with no other apps going, purging every frame to try to keep RAM usage low?
– See if it crashes at the exact same frame each time. Maybe a layer with a troublesome plugin starts there?
– Maybe queue up multiple renders, each rendering a portion of the length of the comp as a workaround.
– are you rendering a huge file to a FAT32 drive, which can’t take over 4GB? I don’t hink so, but I had to ask.
Let us know …