OTOY Forums

A: Windows 64bit Pro (10.0.17134)
B: GTX 1080 Ti 11Gb
C: 64MB
D: 23.21.13.9135
E: 3.08
F: 3.08
G: C4D R19.053
H:
I am repeatedly getting the 700 and 719 CUDA errors which results in Octane crashing and having to restart Cinema 4D. It got to a point where it was crashing every 10-30 minutes and also not being able to complete renders. I have struggled to find exactly a specific things to recreate it, but if I have the Live Viewer on and I move the camera around a lot and adjust/create new materials (I'm mostly using specular materials with transmission colour and an absorption medium, if that counts for anything?). I am also getting corrupted material previews.

After reading through what seemed like a similar issue on this forum, I followed the advice and did a clean uninstall with DDU and then installed the recommended drivers. I'm relatively new to the world of C4D and Octane, so forgive me if there is a glaring mistake that I've not picked up. I've attached a few log files, an example scene file and a screen shot of the material preview glitch.

Any help on this would be massively appreciated as it is making an already tight deadline a bit more scary.

Many Thanks,
Jamie

Your scene looks like doesn't have anything wrong. You may be in suffering by gpu/driver problems.
1-Did you tried to use 3.08.1?
2-Did you checked gpu temperatures in rendering?
3-Did you tried different drivers by clean installs?

Hi aoktar, thanks for your response.

1. Do you mean v3.08.1 Standalone or Cinema 4D plugin? I can only see the following latest version from the download section: (3.08 Standalone) & (3.05.3 R1 Cinema 4D plugin)
2. I just manged to get it to crash whilst looking at the GPU temp with CPUID HWMonitor. The GPU went up to a maximum of 66C but was at around 56C when it crashed.
3. First of all I tried a clean install with the latest drivers. I then read on here that latest drivers might be an issue, so I read around and saw this thread:
viewtopic.php?f=30&t=68024#p341070
So I followed those instructions. Booted in Safe Mode, uninstalled both AMD and NVidia drivers, and then did a clean install with the Nvidia v391.35 drivers.

I've attached a larger scene project where the crashes are happening more frequently for me, just in case that helps shed any light onto the problem?

Thanks again,
Jamie.

It's still persistently crashing here. I'd say anywhere between 5 and 15 minutes of working on before it does. Occasionally the screen goes black for a few seconds and then comes back into Windows desktop view and Cinema 4D has closed down. and I don't even get a chance to see the crash log.

I have an older GTX 1080 (Not Ti and currently not installed). Is it worth me just trying to run that on it's own to identify if it's an issue with the Ti card?

Thanks,
Jamie

Latest builds are always here And 3.08.1-R4 here: viewtopic.php?f=85&t=66885

Thanks again for replying aoktar.

I did eventually find that post. Sorry I'm still pretty new to Octane and this forum.

So I installed v3.08.1 R1 through to R4. And whilst R4 seemed a little more stable it still crashes.

I've attached a zip file that has a scene file that crashes my render when I do a Render to Picture Viewer, along with it's .log file.

Do you think trying my older 1080 card would be a good idea? The 1080 Ti is new.

Thanks,
Jamie

I don't have XP4 to test your scene. Could you test it without vdbmesher? What happens on Live Viewer? May you have a lot of triangles in your scene?

It still crashes in renders where I have none of the X-Particles turned on.

Unfortunately I've got to focus on getting this project to a point so I can send it to a render farm, so I can't spend too much time trying to fix the problem. I'm finding a more stable work around for now... if I keep my pathtracing Max Samples low to something like 16, then it works a lot better.

I'm happy to collate my .log files on here though as and when it does crash. The one I've attached to this post I just had a very simple scene. Most of the assets where turned off and I was rendering at 128 Max Samples.

Thanks,
Jamie