Page MenuHome

Crash Rendering (Cycles/Cuda)
Closed, ResolvedPublic

Description

System Information
Window 7 64-bit and Nvidia GeForce GTX 760

Blender Version
Broken: 2.74

Short description of error

A simple nodes setup shown on the top part of the image, with GPU rendering in both F12 or viewport render, it happen to be crash as shown at the bottom part of the image.
Tested with CPU render in viewport render mode, when adjusting/draging the ColorRamp node gradient bar, it having some stall/freeze situation for more or less of a second.

Event Timeline

B-Lee (toki46) claimed this task.
B-Lee (toki46) raised the priority of this task from to Needs Triage by Developer.
B-Lee (toki46) updated the task description. (Show Details)
B-Lee (toki46) added a project: BF Blender.
B-Lee (toki46) set Type to Bug.
B-Lee (toki46) added a subscriber: B-Lee (toki46).

We need a bit more information from you so let me give you some homework:

  • Information about what kind of operating system and graphics card you use might be helpful
  • Try the latest build from our buildbot.(Not Gooseberry)
  • Ensure both your OS and drivers are fully up-to-date
  • For Windows 7, at least Service Pack 1 is mandatory, please ensure it is installed on your machine.
  • Ensure you have installed MSVC2013 redistributable package.
  • Try to disable any running antivirus.
  • Ensure you have no python executable available in your %path% envvar.
  • Try to re-download and re-install Blender.
  • Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
  • If you are using Win7, Try to place this dll next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not).

(and again, more or less copied & pasted from Bastien)

Think that's enough for now... ;)

(Copied from Julian :)

Aaron Carlisle (Blendify) removed B-Lee (toki46) as the assignee of this task.Apr 1 2015, 9:34 PM
Aaron Carlisle (Blendify) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.
Krzysztof Rećko (chrisr) raised the priority of this task from Needs Information from User to Confirmed, Medium.Apr 1 2015, 10:33 PM

Hey, I can confirm this bug.

  • I have Win7 64, SP1, Nvidia GTX 560Ti, driver 347.88 (17 March).
  • Latest buildbot, and my own build from latest master both have this.
  • Check!
  • Check!
  • Check!
  • Check!
  • Check!
  • Check!
  • Check!
  • Check!

Here is a file I ended up creating:

. To reproduce the bug: Set device to CUDA, F12 to render -> exact same error as @B-Lee (toki46) had and complete blender crash.
Listing from console after the bug:

CUDA error: Unknown error in cuCtxSynchronize()

Refer to the Cycles GPU rendering documentation for possible solutions:
http://www.blender.org/manual/render/cycles/gpu_rendering.html

CUDA error: Unknown error in cuMemcpyDtoH((uchar*)mem.data_pointer + offset, (CUdeviceptr)(mem.device_pointer + offset), size)
CUDA error: Unknown error in cuMemcpyDtoH((uchar*)mem.data_pointer + offset, (CUdeviceptr)(mem.device_pointer + offset), size)
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
(...) - around 264 of these
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
(...) - around 18 of these
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
AL lib: (EE) alc_cleanup: 1 device not closed

I seem to require a large quantity of memory.

  • Windows 7 64bit SP1, Nvidia GeForce GTX 760 (driver ver: 347.88) latest driver release date: 3/17/2015
  • Windows 64 bit Official blender-2.74-4b84759-win64.zip
  • Check
  • Check
  • Check
  • Check
  • Check
  • Check
  • Check
  • Check

After doing all above, new test with latest buildbot is still the same, only difference is blender still operate instead of totally crash.
Here are both viewport render and F12 render test.

@Aaron Carlisle (Blendify), this is only to be copied in certain bugs that look like OpenGL failures or crashes that cannot be reproduced by others. It's good that you want to help, but the best way users can help is by confirming that a bug occurs for them. Generally merging tasks and such replies should be done by developers (who can evaluate if something really is a bug in our code or not, in which case we check for crappy drivers etc).

And finally, summoning @Thomas Dinges (dingto) or @Sergey Sharybin (sergey) here to take a look.

At reporter: A blend file is -always- better than a picture and means we are on the same page - which is often not the issue if we try to recreate the file here.

Well since the picture shows a crashing driver it was probably a good idea

Campbell Barton (campbellbarton) renamed this task from Blender Crash to Crash Rendering (Cycles/Cuda).Apr 6 2015, 5:35 AM

Pointiness is a surface attribute, can't really be used for volume. But crash should not happen as well. Will have a look into this.