Constant crashing

[oMeGa]

Hi! Any solution for this problem? The SLI, the bridge? I'm in the same situation...

Me too man! I can't regular use octane and cinema 4d, it keep crashing after some time, render stops, all i can do every **** single time is to save (if i can) > close cinema > reopen cinema > back to work
If i work with simple things like a prop etc, it's fine, but if i try to render an interior or a heavy scene after some work it stop rendering unless i restart cinema 4d.

I'm equipped with dual gtx 1080, but this thing about SLI bridge connected is new to me, ill check it out! if the SLI Bridge (the physical bridge) is the cause of this issue, can be a very pain switch from app who require SLI and Octane.

Anyway just my 2 cents. Cheers

What's crashes here? Render failures(cuda error) or plugin crashes?

With previous stable 3.05.3 i have render failures after some work, for example i start a render in live-viewer, then stop render and continue my work (i can't work with live-preview active is a lot laggy, like modeling, move camera and so on...), then start another render to see the changes, after some times i do this procedure all i got is a render failures, with cuda errors 719 or 700.

With this new version 3.06.1 when i use the same workflow/procedure it just stop rendering, in log it don't throw any error, for log is all fine, no failure, no errors, it only just stop render, then i save the project, restart cinema, then i can render again for some time.

I have all updated nvidia/system drivers, cinema 4d, i have format my o.s. a couple of times, nothing works. The only thing i don't have try is to physical remove the sli bridge and see if i have the same error.
I think i don't have an hardware failure because all other apps works fine, games who use both gpu's and so on...

for what i have understand in these forums is a common issue for some people with gtx 1080 or same architecture, and is not plugin related, it's core related, so i don't want blame you about your hard work, but i'm very angry for these issues... ( i speak like that because with my old single gpu build, equipped with a gtx 970, i never had any issue with octane, but we talk about a 1 year ago).

[aoktar]

With previous stable 3.05.3 i have render failures after some work, for example i start a render in live-viewer, then stop render and continue my work (i can't work with live-preview active is a lot laggy, like modeling, move camera and so on...), then start another render to see the changes, after some times i do this procedure all i got is a render failures, with cuda errors 719 or 700.

With this new version 3.06.1 when i use the same workflow/procedure it just stop rendering, in log it don't throw any error, for log is all fine, no failure, no errors, it only just stop render, then i save the project, restart cinema, then i can render again for some time.

I have all updated nvidia/system drivers, cinema 4d, i have format my o.s. a couple of times, nothing works. The only thing i don't have try is to physical remove the sli bridge and see if i have the same error.
I think i don't have an hardware failure because all other apps works fine, games who use both gpu's and so on...

for what i have understand in these forums is a common issue for some people with gtx 1080 or same architecture, and is not plugin related, it's core related, so i don't want blame you about your hard work, but i'm very angry for these issues... ( i speak like that because with my old single gpu build, equipped with a gtx 970, i never had any issue with octane, but we talk about a 1 year ago).

Interesting! PM for a remote connect if you wish.

[Giz]

Hi I keep having this issue as well, maybe it's an issue with the card? I'm using a single 1080
viewtopic.php?f=30&t=60347&p=309252&hil ... +0#p309252

[bepeg4d]

Hi Giz,
according to your log, you are still with 3.06, that does not have the fix for Pascal GPUs, that has been introduced with 3.06.1.
Please update to 3.06.2 and try again:
viewtopic.php?f=85&t=60816
ciao beppe

[Giz]

Hi Beppe,
I've installed 3.06.2 and the same issue. this is happening with a default cube in a scene. I've a Geforce gtx 1080 driver version 382.33. Does anyone know how i might be able to check whether it's the card that is failing or Octane?

Thanks,
giz

[bepeg4d]

Hi giz,
sorry to hear that you have so many issues.
What happen if you start the Standalone?
Are you able to render without CUDA error?
Just right click in the node graph, create a matetial node, right click on it and choose Render.
What are the exact specs of your machine?
Have you tried to make a clean installation of the Nvidia drivers?
Could you also share a bugreport.txt file?
ciao beppe

[Giz]

Hi Beppe,
I have the same issue with the stand alone, could be driver issue. I'm running windows 10, i7 - 6950x, 64Gb Ram, Geforce gtx 1080, - again i suspect that this might be the card, think i'm going to try blender and cycles set to gpu rendering and see if i have any issues.

Thanks,
Gizmo

[bepeg4d]

Hi Gizmo,
the CUDA error also in Standalone is not a good sign.
Firstly try with a clean installation of stable Nvidia drivers.
Sometimes some piece of old drivers stay in the system bringing instability.
Looking forward for your feedback,
ciao beppe

[proundkontra]

I've got the same issue. But i use 3x980ti cards.

[maxuser2]

Same 700 errors on 3 x 1070 and another system 1080 + Titan in standalone. Titan was absolutely stable before 1080 installation and upgrading 3.02 => 3.06, looks like driver or pascal fix issue.

Code: Select all

OctaneRender 3.06.2 (3060200)
CUDA error 700 on device 0: an illegal memory access was encountered
  -> kernel execution failed(report)
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to launch kernel(ptBrdf2)
device 0: path tracing kernel failed
CUDA error 700 on device 2: an illegal memory access was encountered
  -> kernel execution failed(report)
CUDA error 700 on device 2: an illegal memory access was encountered
  -> failed to copy memory from device.
device 2: path tracing kernel failed

Same issue on 3.06.4

Code: Select all

OctaneRender 3.06.4 (3060400)

CUDA error 700 on device 0: an illegal memory access was encountered
  -> kernel execution failed(report)
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to copy memory from device.
device 0: path tracing kernel failed
CUDA error 700 on device 2: an illegal memory access was encountered
  -> kernel execution failed(report)
CUDA error 700 on device 2: an illegal memory access was encountered
  -> failed to launch kernel(ptBrdf2)
device 2: path tracing kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
  -> kernel execution failed(report)
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to launch kernel(ptBrdf2)
device 1: path tracing kernel failed

So now I have a scene with fastest way to crash driver on both systems (attach vdb), driver clean install doen't help. And even after octane restart Pascal GPUs remain disappeared in this case one by one!

Code: Select all

Display driver stopped responding and has recovered