Page MenuHome

CUDA error
Open, Needs Information from UserPublic


System Information
Operating system and graphics card

Windows 7
2x GTX 1060 6GB

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)

Broken: 2.79b
Worked: 2.79a, 2.79 daily (10/04/2018)

Short description of error

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

Rendering on GPU often results in a CUDA error now, since I installed 2.79b and more precisely after I started using the new daily (not sure if it's connected). I don't know how to replicate the problem, it kind of just happens sometimes and after that it doesn't really render and it's best to restart Blender. There is an error message up the top in the progress bar I hope you can read it, something to do with CUDA memory and an illegal operation. I've been using the daily now and I haven't seen it yet.



Event Timeline

I've had something similar happen to me, actually with two AMD GPUs, on a laptop; one the onboard of the APU and another external one. One card rendered normal squares and the other semi-transparent one, until the crash happened and all the rest were rendered transparent, is that how it happens?

I think blender still has to improve quite a bit in multiple GPU support. I've recently had crashes also with another mixed couple, RX56 + RX480, both 8GB, scene went max. to 4.7, so all fine in theory, both cards render flawlessly separately but rendering with both just shuts down the application... My suspicion is that somehow blender/the driver, somehow reserves the occupied ram of a card on the other, even if GPUZ doesnt show it; you can try lowering sample sizes (which also reduces a bit the RAM used), worked in a few cases for me, but performance degraded so much below 256x256 that the vega @320x320 was faster than both cards in combo.

Sebastian Parborg (zeddb) triaged this task as Needs Information from User priority.Mon, Feb 11, 11:27 AM

Is this still an issue with the latest build from ?