Sometimes it will render a few frames and then vanish crash. Other times it says blender stopped working, and other times it vanish crashes before it makes it through as single
frame.
tried it just cuda without optics, still crashes.
It was working fine for weeks.
Just added a sphere and a light to a blank file. Still crashes.
Post it here if you find it, otherwise try to restore factory settings. You can delete Blender’s user data manually (in Windows path is something like C:\Users.…\AppData\Roaming\Blender Foundation, just delete the Blender Foundation folder, but note you will lose your addons and they must be reinstalled).
You should delete all logs then run Blender again and render something until it crashes then get the latest log. If you upload the wrong log it won’t be of much help.
And if you know how to do it, you can also run Blender from a command line with the “–factory-startup --debug-all” arguments to get more info.
I saw there was new one, but I didn’t install it yet. I was thinking about installing it to see if it fixed it. also, I am not having render problems in 2.91.
Looks like the renderer can’t write the image file. Check if the output path has enough space. What video card do you have btw? I see some CUDA stuff listed in the log. Beware that CUDA is useless if you have an AMD GPU, it may also mess up existing AMD drivers.
If you are using an HDRI go to your world properties/settings/surface/sampling and change it from Auto to Manual. Map resolution should be 1024 and Max Bounces should be 1024. Try rendering after you have changed the Sampling to Manual. Worked for me a while back.
How do I know if it’s an out-of-core render? I haven’t heard that term before.
I tried just loading up an hdri for the background and lighting, a UV sphere, and one area light. It’s still crashed. Yet for weeks everything was working fine even with scenes had a lot going on in it.
For mine, i am trying out the adaptive subdivision. I am addicted to crazy displacement map for the last few weeks and did a lot of experiment with it
adjusting dicing rate (adaptive sub-d) in 2.92beta too low will break the render and crash to desktop.
While in 2.91, i will see my gpu shared memory filled up and my system RAM grew to 30GB± and in worst case, system become unresponsive instead of crash, which is expected.
for the out of core, i did it in a crude way,
fire up my task manager, take note at ‘shared GPU memory’ stats just right after the render started.
for my scene, cycles crash when my ‘shared GPU memory’ started going up, in other words, the VRAM onboard is not enough and the scene started to load to system RAM.
I have the same problem. It crashes whenever you use Eevee render viewport, the UV Editor, or just try to render in cycles. Even crashes with a new file with only the default cube in it. Not sure if it’s my computer or the program. Either way, rendering or using a UV is currently impossible for me.