Page MenuHome

Cuda error(s) illegal adress in rendering GTX 780 Ti
Closed, ArchivedPublic

Description

System Information
Win 10 64-bit
RAM 16 Gb
GTX 780 Ti - driver 386.51

Blender Version
2.78

Short description of error
One object in a project (cube), rendering mode Cycles - render mode GPU leads following errors.
Cycles rendering error :

  • 1st time - Cuda error : illegal address in cuCtxSynchronize()
  • 2nd (and afterwords) : illegal address in cuCtxCreate

In Blender render mode rendering works fine, but quite slow.

Event Timeline

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to 30.Apr 30 2017, 3:01 AM

Which exact Blender version are you using, have you tried 2.78c or the latest from https://builder.blender.org/download/ ?

You mention NVidia driver version 386.51, but are you sure that's correct? I can't find any information about the existence of that version. Have you tried other driver versions?

Can you attach a .blend file to reproduce the error, or does this happen with the default scene?

Blender has been downloaded 2-3 weeks ago, so the version might be 2.78c.
Driver version just updated a week ago from Nvidia, that is version 386.51, Windows shows version 22.21.13.8165, the date march 23th 2017.
This happens in default screen, rendering a cube and nothing else.
This device is enabled using CUDA.

Ok, it's probably version 381.65.

All I can suggest is to try uninstall the driver and reinstall the latest from nvidia.com, something might be broken in the driver installation. The drivers auto installed by Windows are known to have issues.

Well, this issue occured before reinstalling these drivers - that's why I reinstalled them. New Nvidia drivers were installed about a week ago - Nvidia drivers, not Windows.

Ok, regardless, there have been some bugs in recent NVidia drivers that have been fixed in newer versions, and there can be issues where some installation is incomplete. There is not much we can do about such bugs on the Blender side besides waiting for NVidia to fix them. If we get more reports from users saying that things don't work at all for them with any of the recent drivers, that's something we can investigate, but so far this does not look like a Blender issue.

So all I can suggest is to completely uninstall whatever version you have now and try newer versions like 381.89 or 382.05.

Thanks Brecht,
I have to do it, hope it will help - upgrade those new drivers as well!

Aaron Carlisle (Blendify) changed the task status from Unknown Status to Unknown Status.May 16 2017, 9:19 PM
Aaron Carlisle (Blendify) claimed this task.

Marking as archived until a dev can reproduce.