If I reset Blender to factory settings, turn on CUDA + Cycles, delete everything in the scene but the camera, and hit F12 to render, I get an Out of Memory error:

CUDA error: Out of memory in cuLaunchKernel(cuPathTrace, xblocks, yblocks, 1, xthreads, ythreads, 1, 0, 0, args, 0)

CUDA error: Out of memory in cuLaunchKernel(cuPathTrace, xblocks, yblocks, 1, xthreads, ythreads, 1, 0, 0, args, 0)

I've already made sure of the following things:

  • My GPU [512MB NVIDIA GeForce GT 640M] supports CUDA and has a 3.0 compute capability (more than the minimum of 2.0 required by Blender).

  • My CUDA PrefPane states that I'm on the latest possible version of CUDA [7.0.52]

  • Blender is aware of my GPU and does not have experimental features enabled:

My 640m GPU is very weak, and should certainly render slowly. However, it fails to render anything, even the just default cube, even just the default sky with nothing else in the scene. I don't understand why this is the case.

After getting the same error a few dozen times, one instance "succeeded"–that is, it didn't throw an out of memory error!

Instead, Blender displayed this:

...and gradually brought my computer to a standstill until it rebooted itself.

Any advice or suggestions for things to try will be greatly appreciated. CPU rendering gets very tedious very quickly, especially for complex scenes.


I'm not sure how to precisely measure VRAM usage, but iStat menus shows a rough estimate. This is what it looks like before and after turning on Blender (without rendering anything): about 20% about 80%

If 90% of my VRAM is being used by Blender window rendering + system stuff, that leaves 51.2MB free. A fresh-from-reset scene has a memory footprint of about 10MB (according to information panel). If I take the error to be accurate, that means the memory footprint of the scene in VRAM is about 5x the normal scene memory footprint, which sounds crazy, but certainly possible.

  • 6
    512 MB is not a lot, is it possible most is being used by windows and other programs with basically none left over for cycles? – gandalf3 Jul 21 '15 at 6:57
  • 1
    Rendering an empty scene takes 750MB of VRAM, thats what I measured with GPU-Z. Also lowering output resolution or other things doesn't change a thing. Don't expect Blender to be efficient, it's opensource after all. – Jaroslav Jerryno Novotny Jul 21 '15 at 9:02
  • 1
    GPUs in laptops (the M versions of Nvidia cards) are not very powerful to begin with. With so little vRAM I'm afraid your system is not going to work for GPU rendering, or it's going to be extremely limited. Stick to CPU rendering. – cegaton Jul 21 '15 at 15:30
  • 1
    In the Performance control try using a smaller tile size. – cegaton Jul 22 '15 at 5:29
  • 1
    An empty render takes 480MB here on my computer. (GTX770, Windows 7 64bit, 1080p screen) So it it very possible you are simply running out of memory. – Mike Pan Jul 27 '15 at 21:05

retaking this now. I am using a NVIDIA GeForce GT 640M 512 MB (not the best, I know) in an iMac (21.5-inch, Late 2012) running OSX 10.11.5 (15F34) El Capitan. With CUDA version 7.5.27 and Blender 2.77a. I was struggling to render an empty image using GPU and CUDA. When I saw @cegaton suggestion: Reduce tile size. It made an empty image render with GPU. Maybe is the most we can do with it, but at least, we can get something. I was using X:64 and Y:64 tile size, and moved to X:32 and Y:32. If I find anything interesting, will post back. But maybe this is the limit. Hope it helps.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.