OTOY Forums

Hi!

Ițm using 3x 980TI and 1x780 TI. After I installed Octane 3.0 I get very often this error " CUDA error 700 on device 0: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed" with various simple scenes.
I have also disabled the 780TI because it has less RAM, but I still get the same error using 6gb.

This is insane......I cannot work this way. Please help.

Here is the log for a very simple scene: https://dl.dropboxusercontent.com/u/254 ... 180752.log

Here is a render from scene: https://dl.dropboxusercontent.com/u/254 ... na0008.jpg

I have been getting the same error, I don't know how to fix it either.
I don't get it that often, but often enough.

Log file and render out is not enough to know the reason. Maybe a driver related problem or about renderer.
Please try to give more information. So we can talk with team and help to solve it. Also put your scenes and write steps to reproduce the problem.

I have this same problem with scenes too. usually displacement related but I'm in full production with something right now and i can't figure out why it's giving me this error. My windows notifications show this:

Never got this error on this scene before, and the only way to get rid of it is to go back to a scene that was days ago(losing days of work.).

I've attached log file if that helps :S

jeffbriant wrote:I have this same problem with scenes too. usually displacement related but I'm in full production with something right now and i can't figure out why it's giving me this error. My windows notifications show this:

Never got this error on this scene before, and the only way to get rid of it is to go back to a scene that was days ago(losing days of work.).

I've attached log file if that helps :S

Different for Octane on displacements, it doesn't use pre-triangulation for the effect and recalculate the displacement as voxels in run-time. So it looks like the renderer is stressing too much and being unresponsive due displacement on object. Have you set TDR values to high enough to avoid this errors?

Having the same problem with the same windows notification. Closing C4D and restart scene works only for a few minutes. Had the impression too, that it is somehow displacement-related. Will send logfile next time. This time just for report.

Chriz wrote:Having the same problem with the same windows notification. Closing C4D and restart scene works only for a few minutes. Had the impression too, that it is somehow displacement-related. Will send logfile next time. This time just for report.

Can you make an orbx scene and try in Standalone? If you can reproduce in Standalone then we can report it to Otoy. Because these are not plugin issues.

I'm back again after some tests. I reinstalled windows 10 and 8.1 and fresh drivers. Tested also with latest driver and also old ones.
The problem sounds like this.
I haven't changed any hardware since Octane V2 and used the same scenes in V2 and V3. In V2 everything works, but in V3 I get those errors posted above from time to time (quite often).
I don't know if it's necessary to send a scene because it happens on all scenes and the errors are random....it can work 2 days with no error and then I get 10 errors/day.
Tested with single gpu and multiple gpus. There are more threads pointing to this problem on the forum, but no solution to this.
I do't think it's a harware or driver issue since it works sometimes and also works with V2 with no error.
I know this may not be a plugin issue, but I don't know what to do.

See more threads: viewtopic.php?f=81&t=55562
viewtopic.php?f=81&t=55529&p=284307&hil ... or#p284307
viewtopic.php?f=30&t=54446&p=281502&hil ... or#p281502

Hi Yan,
what about GPUs overclocking/overheating?
V2 and V3 are working in different ways, so maybe your particular set up is suffering about this
ciao beppe

Hi, i haven´t had this problem again since i posted last time, without changing anything in my system.

It makes me feel uncomfortable, reading ,that the mistake returns sometimes....

But i can give the advice, that it not only happens in V2 -> i am working with V3.