The “solution” for this is more of a workaround. I used an online tool to generate a sequence of commands to render each frame separately, like so:
"C:\Program Files\Blender Foundation\Blender\blender" -b "C:\Path\To\Blender\File.blend" -f 1 "C:\Program Files\Blender Foundation\Blender\blender" -b "C:\Path\To\Blender\File.blend" -f 2 ... "C:\Program Files\Blender Foundation\Blender\blender" -b "C:\Path\To\Blender\File.blend" -f 100
I’m trying to render a sequence of RGBA 16-bit PNG frames at 1920X1080 with my GPU. Unfortunately, after rendering a few frames, the render fails.
When rendering with the Blender GUI open, Blender will suddenly stop rendering and I’ll get a Windows error message saying that “Blender has stopped working”, and the frame it fails on won’t save.
When rendering from a command line, rendering will just continue, but the frame it fails on will only be partially done when it saves, and every frame after that is entirely transparent.
At first I thought it might be running out of RAM, but task manager shows that almost no RAM is in use when it’s rendering. CPU usage hovers below 20% and GPU around 100%.
OS: Windows 10
Motherboard: AsRock Extreme4 Z97
CPU: Intel i5-4590
GPU: Evga GTX 650Ti
Hard Drive: Western Digital WD Green 1TB
SSD: Samsung 850 Evo 250GB
RAM: Ballistix Sport 1600Mhz 9-9-9 2x8Gb
PSU: Corsair VS 450W