Serious errors when using Octane C4D

[lideborg]

First of all I'd like to thank you for a great product. I've been using it for almost two years now and with the updates and support it became my go to renderer.

But a few weeks ago when rendering or using the live viewer my computer started to act up strange. I was not sure about what it was but i kept on getting some serious graphical card glitches. The computer would just lock up. Sometime it would start up just fine again and sometimes it would be hours of rebooting before even getting in to windows again. In the beginning it was almost just once a week so it didnt bother me that much but now it gets to a point where if i just open up the live viewer or render a scene it will happen. I took some pictures of how it looks which can be viewed here http://d.pr/i/njgk

Let's start off saying I'm currently on this rig http://pcpartpicker.com/list/rN6wxr but with MSI Titans instead of Asus.

I actually got so worried what it was, thinking it could be something wrong with the hardware so I sent it in to a shop, which went through it all and got it back saying that there was nothing wrong with it. Although when I got it back I actually reinstalled Windows and tried Octane (3.04.4 and 3.04) both with Cinema R16 v16.050 and R17 v17.055. But still, on both i get this issue when everything freezes. I tried to see when it happens to understand what it could be, but its total random. Tried changing samples, different pathtracing/direct/pmc, changing priority on the cards, which one it should use, basically it feels like I tried everything. I rendered via Physical, Standard, even tried out old vray and when I use that it's always fine. So it has to be only when using Octane. I know it has been talked on temperature on the cards as well but they usually run around 60-70 degrees so that should not be a problem right?

Never get the chance to get a errorfile as it just crashes but if it matters here is one of the scenes that I try to render. http://d.pr/f/ECHe

Would love to get this resolved so I can go back using the renderer that i love, and also to get those Titans not just being used for playing Diablo

If you would need anything, let me know and I'll try grab screenshots or data!

Thank you
/Hampus

[lideborg]

I looked through the forum and seems like at least one other have a similar problem. viewtopic.php?f=30&t=57106

I did as they said in the thread and uninstalled all GPU drivers and is now using the one said 362.00 on both my titans. Although I still get the same error. Please, can someone take a look at this, or at least guide me towards some kind of solution where I might find the problem?

[bepeg4d]

Hi Hampus,
from your link, seems that you are working with two Titan X with two 27" monitors, without a dedicated GPU for them.
What happen if you have the two monitors connected to only one Titan and the other one is used for Octane only?
ciao beppe

[lideborg]

Thank you for the reply! Yes that is correct, currently on 2, 27" monitors. I guess then the setup would be something like this?

http://d.pr/i/WwkQ

[bepeg4d]

Hi Hampus,,
it should be correct, anyway, if not , you can try in the opposite way in c4dOctane to see the difference. Sometimes the GPU are not listed in the order that you expected.
ciao beppe

[SLIMESUNDAY]

My computer hit a brick wall a couple weeks ago. Render crashes, unable to boot the computer up, it was a disaster. I thought there was some serious hardware issues but in fact it was completely related to the Windows 10 anniversary update. I would give microsoft a call and see if they can trouble shoot the issue for you. I had to completely reinstall windows to get my computer back to a functional state again.

[lideborg]

Hello again,
Unfortunately I'm back with the same issues. I tried for a while to unplug one of the monitors I used and use octane on the other. I even tried with one GPU only dedicated to the screen and the other only for rendering but after a little while same thing happened again. I tried using all the different connections (HDMI/DVI/DisplayPort) but same here getting the glitch problems again. I even re-installed Windows both with 8 and then with 10. Everything works great until I open the LiveViewer and start rendering. It's sometimes when I'm fiddling around in the LiveViewer but mostly after i played around a bit, then closed it down. Recorded me sitting at the screen just so I could show what happens. The GPUs are both never getting higher then 80 degrees so I don't think it's a overheating problem? You can see it occur around 6 seconds into the clip, mostly in the lower right corner but the glitches fill the screen. Here I have been working with a scene and then started a new, then it crashed. Not sure if vimeo-linking works so link underneath as well.

https://vimeo.com/197373393

https://vimeo.com/197373393

Is there anyone that has the same problem? Would love to get this resolved as I'm using C4D daily and going back to Vray/Standard is just a no-no. As stated earlier the computer is now fully re-installed with Windows 10, NVidia v. 376.33 (used different versions) running Cinema R18 with Octane 3.04.5-R2 but had the same problem when tried other versions as well.

[bepeg4d]

Hi Hampus,
sorry, but I have this error if I try to see your vimeo video:

have you tried to use GPU-Z to monitoring the cards while rendeting?
Have you disabled SLI in the nvidia control panel?
ciao beppe

[lideborg]

Hmm, seems like the privacy was wrong. Here is a private link, should work!

https://vimeo.com/197373393/7d38a8de51

And yes, SLI is disabled!

I'll try GPU-Z now, it's this one right? http://filehippo.com/download_gpuz/

[bepeg4d]

hi,
unfortunately the video does not give to much info
try with this link:
https://www.techpowerup.com/gpuz/
ciao beppe