I am a 16 year old. I am new to this community as well as blender. When I was rendering today, I encountered a strange problem. When I try to render the below given scene using GPU COMPUTE it crashes, but GPU COMPUTE works absolutely fine in rendered mode. When I render using CPU, its all right. When I check my gpu stats in MSI AFTERBURNER,everything is fine. No temp throttling, No memory Bottleneck(only 2gb of vram was used out of 4gb). My Computer Specifications are :-

  1. CPU :- AMD RYZEN 1600
  2. RAM :- Corsair 16gb ddr4 3000mhz
  3. GPU :- RX 480 4gb(Crimson 17.7.2)
  4. HDD :- Two 7200rpm drives
  5. MOBO :- Gigabyte GA-AB350 Gaming 3(BIOS :- F7a)

    MY Problem is clearly shown in this video

And also, I Found that the GPU COMPUTE works fine in very simple renders (like the startup file render)

Any help from this community will be deeply appreciated.

  • Maybe it is a bug with the GPU you are using. AMD graphics cards support on Blender cycles still quite new. It has been introduced a few versions back. – Hendriks3D Aug 15 '17 at 13:51

The viewport render is designed to give you an approximation of the scene taking some shortcuts, usually renders using lower samples and using less subdivisions (depending on how the modifiers are set) and ignoring some other features that are only available on the final render. The idea behind this is to give you a more responsive interface.

More on this topic on this link

When you render using F12 you are using a lot more resources. If your scene's complexity exceeds the capabilities of your GPU, the render will fail is that simple.

Memory usage in afterburner might not reflect the real vRAM usage for the scene.

Your options are to simplify your scene (or break in smaller, renderable pieces to be composited together later) or to render using CPU.

I've got the exact same issue with same symptoms but with a AMD R9 290, and YES there is something strange here.

Blender was crashing because some of my materials were using the NORMAL MAP node. I had to delete the normal map nodes from my materials so it wasn't crashing anymore. Detaching them didn't help. Also, even if the material was not assigned to any object, it was still crashing.

BTW, I'm using 2.78, before looking for the origin of my issue, I tried to render using Blender 2.79rc2 and the bleeding edge 2.80, it was still crashing (maybe for other reasons uh ? but still crashing)

So, if some of your materials use the normal map node, try to delete these nodes.

Someone have the same issue here in this post from blenderartists.org, it seems like other nodes make cycle crash when using openCL with AMD cards.

  • Why is my answer getting downvoted to death ? Please guys, if you downvote, leave a comment telling why. – CPP_Meister Sep 1 '17 at 8:34

protected by Community Jan 23 at 7:56

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

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