Page 1 of 3

error with demo and cinema 4d plugin

Posted: Thu Sep 05, 2013 9:46 am
by anschelk
hi all

i'm just started with playing arround with octane. i have a gtx 680. i've got this error message in cinema 4d

"CUDA error 700 in device 0:
An exception occurred on the device while executing a kernel."

please can help me someone, i have now idea what this mean.

thanks
diego

Re: error with demo and cinema 4d plugin

Posted: Fri Sep 06, 2013 12:20 am
by FooZe
Hi Diego,

Do you have the latest NVIDIA drivers?

Thanks
Chris.

Re: error with demo and cinema 4d plugin

Posted: Fri Sep 06, 2013 7:40 am
by anschelk
hi chris

thanks for the quick reply. Now i have a full license. i'm not sure about my grafikcard.

so my question is, does the gtx 680 mac edition run on octane render?? i'll check and install now
the latest nvidia driver.

thanks
diego

Re: error with demo and cinema 4d plugin

Posted: Fri Sep 06, 2013 12:00 pm
by bepeg4d
hi, which version of osx?
what happen if you open the octane standalone?
you can put you hw and sw configuration in your signature in the control panel, in this way is more easy to try to help ;)
ciao beppe

Re: error with demo and cinema 4d plugin

Posted: Fri Sep 06, 2013 12:39 pm
by anschelk
okay i have also problem with the full version.

it works fine to load the model and it starts to render, but after a while i have the error message and it stop to render. Do i have the wronge grafikcard?

hope someone can help me, i'd like to start working with octane :D

i got this error message after a while:

OctaneRender version 1.20 (1200001)

CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Kernel execution failed (pt)
CUDA device 0: Path tracing failed

My System:

Processor 2 x 2.93 GHz 6-Core Intel Xeon
Memory 64 GB 1333 MHz DDR3 ECC
Graphics NVIDIA GeForce GTX 680 2048 MB
OS X 10.8.4 (12E55)
CUDA Driver Version: 5.5.24

Re: error with demo and cinema 4d plugin

Posted: Fri Sep 06, 2013 1:56 pm
by bepeg4d
i'm still on 10.7 but i never seen this kind of error.
your card is a special mac version, maybe is a driver issue
you could try with this graphic driver version from the nvidia site:
http://www.nvidia.com/object/macosx-313 ... river.html
i hope that works
ciao beppe

Re: error with demo and cinema 4d plugin

Posted: Tue Sep 10, 2013 9:03 am
by anschelk
hmm again an error

i have installed this driver: 313.01.02f01

i thought this is the solution, but error again.

LOG:
OctaneRender version 1.20 (1200001)

CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Kernel execution failed (pt)
CUDA device 0: Path tracing failed
CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Failed to load symbol data to the device (camera data)

do i need a stronger grafikcard? file to big? why does it start to render an stop after a while?

any solution?

thanks
Diego

Image

Re: error with demo and cinema 4d plugin

Posted: Tue Sep 10, 2013 2:16 pm
by aoktar
can you check total gpu memory with another program?
I think you are using one card for opengl and rendering. If so system and octane will use same memory space and capacity. If you working while render, you can consume more memory then start time

Re: error with demo and cinema 4d plugin

Posted: Tue Sep 10, 2013 2:51 pm
by anschelk
looks like its not so easy, can i disable the opengl for the system and just use it for octane?

Re: error with demo and cinema 4d plugin

Posted: Tue Sep 10, 2013 10:01 pm
by FooZe
You should be able to test if you are running out of VRAM by trying a simple scene.
If a plain cube renders ok then this is probably the problem.

Another thing you can try is if you have another GPU around (doesn't need to be strong) to use for display only, this may help. It means that your 680 can be used purely for octane rendering, nothing else will be using it's VRAM.

Thanks
Chris.