Page MenuHome

Win10 64-bit - Cycles - Various CUDA errors in cuCtxSynchronize()
Closed, ArchivedPublic

Description

System Information
Windows 10 64-bit; NVIDIA GeForce GT 750M 2GB

Blender Version
Broken: 2.75a c27589e (current stable release), 2.75 c86a519 (latest Windows 64-bit release from buildbot)
Worked: neither

Short description of error
Every time I try to render all 2141 frames of this Cycles animation, it gives me one of two CUDA errors.

CUDA error: ILLEGAL_ADDRESS in cuCtxSynchronize()
CUDA error: ILLEGAL_INSTRUCTION in cuCtxSynchronize()

I have no control over which one pops up. It either happens within 100 frames of rendering, or it happens as quickly as 2.
Because of this, I have to make one bug report instead of two.

I have only been using the stable release (2.75a c27589e) up to this point.

My OS and GPU drivers are all up to date. I have no add-ons enabled.

I tried rendering with the latest build from the buildbot (2.75 c86a519), but I still get the errors after 20 frames or so. I do have these, though:

system-info.txt: http://pastebin.com/cPZ0QGk7
Console Window: http://pastebin.com/HhazJ4nb

Then I tried again with the stable release, and I couldn't even render ONE frame:

system-info.txt: http://pastebin.com/JJ9j1K5y
Console Window: http://pastebin.com/BarW2iwM

Exact steps for others to reproduce the error
Render the animation of the attached .blend using Windows 10 64-bit and NVIDIA GeForce Windows 10 Driver 355.82.

Event Timeline

Blender uses CUDA 6.5, but it does not support win10 officially.
CUDA Toolkit 6.5
win10 should be supported by CUDA7.5RC.
nVidia Developer Zone

It does not think it's strange even if an error occurs in my opinion.

It is not necessary to mind my opinion because I am not a developer.

Sergey Sharybin (sergey) changed the task status from Unknown Status to Unknown Status.Sep 3 2015, 11:25 AM
Sergey Sharybin (sergey) claimed this task.

Woops, mentioned wrong report in the commit..

As for this particular report -- windows 10 has much higher GPU use which isn't under blender's control and which will make GPU to run out of memory sooner than later.

Also CUDA Toolkit is only used for building kernel and not needed at runtime -- it is all up to driver to run compiled kernel.

So thanks for the report, but we can't really control anything from our side, it is all up to driver and operation system, not up to blender itself.

Is there anything I can do to override the extra CUDA control of the OS/GPU drivers so I can render properly?

Not really. You can try looking around how to limit GPU usage by the OS itself. Or try using dedicated card for compute.

You could also try and minimize blender and or close all other apps, lower the screen resolution, disable (aero / whatever windows calls fancy desktop effects now )

Use and older blender version ( older versions have a smaller fixed startup cost)

Use a smaller tile-size.

None of those suggestions worked, unfortunately.

The fact that other people with Windows 10 don't get frequent CUDA errors tells me that this indeed is a problem with NVIDIA drivers.

Thanks for the suggestions anyway, Martijn.