Cuda Error 700

[Krischl]

Hi guys and happy new year.
Im Pretty new to Octane, i started working with a Titan x (Maxwell) and i was impressed.
So i bought two GTX 1070 Pascal additionally to speed up even more the work process.
And here starts the problem named:
"CUDA error 700 on device : an illegal memory access was encountered
-> could not get memory info"

This error occurs only with the GTX 1070 Pascal cards. if i render with the Titan x (Maxwell) only, the Cuda error dont show up and everything is fine. This happens with diffrent Project files.
But it seems to be really random. once i was able to render the full frame range of a project(project file attached) but this happend really only once, the other times i get the cuda error(also with the same project).
In the Picture Viewer it happens like everey time. In the Live Viewer it happens also but not that constant like in the Picturer Viewer.

Currently im working with the Cinema 4D Plugin Version 3.05.1, but i tried also 3.04.5R2 without success. I reinstalled an tried different Display driver versions but it dosent solved the problem.

I tried the Octane Bench 3.034 and it runs fine. i get 407 Points with all 3 cards enabled.

here are my specs:
Mainboard: Asrock x99 Extreme4
CPU: Intel Core i7 5820K
RAM: 32GB DDR4
GPU: 1x TITAN X 12GB (Maxwell), 2x GTX 1070 8GB (Pascal)
Cinema 4D R17.053
Octane C4D Plugin Version 3.05.1
Octane Standalone: 3.05.1
Nvidia Driver Version: 376.33
Windows 10


Sorry for the bad english, im not a native speaker .
thanks for any answers!
Greez
Christian

Project file and error log:

[aoktar]

I don't have exact idea about your CUDA errors. But DO NOT build materials like this. Use octane shaders or images not LAYER texture.

First this is horrible way to slow down you. It takes lot of cpu time to pre-render to images on opengl/material previews + on sending to renderer.
Second, this LAYER textures are causing crashes on render outputs.

[Krischl]

Hi aoktar.

Thanks for this hint.
i bought a Material pack from pixel lab and tihs one was part of it.
Good to know the right way anyway.

Could you be more specific about the Cuda error please?
is this a thing with a lot of possible reasons? or can we specfic localize the problem ? can i support you with something?

it would be nice to use the whole power of the hardware

[aoktar]

There is not much things to say from me for these kind of errors. I'm not a core developer, Octane guys may have much more info about it.

[smicha]

First of all - always run "clean install option" of nvidia driver when inserting any additional gpu. Have you done it?

[smicha]

And please check if you updated bios to 3.60
http://www.asrock.com/mb/Intel/X99%20Ex ... ad&os=BIOS

[Krischl]

Hey smicha.
thanks for your advise!

i checked my bios version and did the update from 1.6 to 3.60.
to be safe, i used the program "Display Driver Uninstaller" to get rid of all the display driver files, after that i installed the display driver wiht the clean install option.

but no succses


Gradually, I think it has to be the hardware. but the two GTX 1070 Cards are brand new. and the the Octane Bench was completely fine. maybe the mainboard? i dont know. just thinking.

Do you have any other ideas?

[mikeadamwood]

I did the same thing as you bought a eGPU to run Octane and loved it, so went ahead and bought a new watercooled 1080 rig. Thought I'd be flying high now but quite the opposite.

It crashes all the time, if I render to picture viewer it freezes.

All pascal cards are broken apparently.

[abstrax]

I rendered the 101 frames of the Mercedes scene without problems on my GTX 1080 using the latest C4D plugin release 3.05.1 on Windows 7.

One thing I always do is run MSI Afterburner to make sure that the GPU is cooled properly. Personally I find the default fan settings a bit too hot, which is why I'm setting the curve to 30% at 30deg and 100% at 70deg:

Worth a try but I'm not sure if that would help you in your particular case.

Could you also check whether disable post-processing makes any difference? Thanks.

[Krischl]

Hi abstrax,
i tried the fan settings and to render without post-procesing.
but it doesnt help.

Luckly i was able to find the issue, at least for my case.
The thing is i tried this before without sucsess.
but at the first time i didnt had the current version of the Bios for my Mainboard.

I did a little overclocking with MSI After Burner . and as i said before, i did a reset to the default settings but the cuda 700 error was still there.

but yesterday i saw in the Event Display from windows that the nvidia driver was crashed.

so i did a reset on the MSI After Burner to default settings.
and it works.

i was able to render the whole mercdess scene without problem.
i tried also a bit of a long term test, im currently working on a really havy scene and i was able to render this scene for 13 hours without any error.

so i think , in my case the problem was a combonation from an old bios version and overclocking.

im happy!

Greez
Chrisitan