OTOY Forums

Hi everyone,

I have an issue for several days and don't succed to fix it!

I just changed my old gtx 780 for a 1080 ti (msi gaming x 11g ), and since then, Octane ( and redshift ) on cinema 4D, doesn't want to render at all.
To stick to octane, i am getting a message error ( CUDA error 700 on device 0: an illegal memory access was encountered ) when i press play on the ipr, even if there is nothing on my scene!

For more informations:

- working on win10
- C4D r 19 ( i tried as well on the R20 to see if i had more luck, but no )
- octane v.4

Everything is update.

I installed the last version of the drivers for the card, no luck.
Tried with another old version of the driver, not working.

When i am doing benchmark to test my card, everything looks like it's working and i have a decent score ( even if the video test is lagging...strange right? )

The card is reconized by windows, c4d, octane, redshift, gpu-z...

I tried to uncheck "out-of-core" from octane preferences, i saw a post telling it could be it, no.

Do you thing that the problem can come from the bios? or an hardware problem?

Here some screenshot of the error and some gpu informations to have a deeper look.








Thanks a lot for your help!

It's hard to be stuck on a hardware issue and not be able to work!
Jeremy

same here. Cuda 700 with rtx 2080ti cards and 417.11 drivers. Another PC with 1080s and 380.33 driver works fine. So it is driver or octane messing up

Some help would be much appreciated

You ar not alone, I have encountered the same problem on R19. Exactly as descripted.
This occur today, in my case only on Live Viewer, sometime as i try to render region on "Lock resolution" view. I think is due to the new driver 417.71, but also the previous driver gave several other crash problems, but which could not be identified because C4D freeze. The crash problem start from the beginning of January, so I have installed the latest drivers some days ago. For now the error is CUDA error 700 on device 0: an illegal memory access
I have tried also on R20 the problem is the same and occur as I have described above.

A. Win 10 Pro
B. Graphics Cards GTX 1080 8GB + 4 GTX1080TI 11GB
C. RAM 64 GB
D. Nvidia driver version 417.71
E. OctaneRender Standalone 4.02
F. OctaneRender plugin version 4.01.1 - R2
G. Host application C4D R19

On R20 the situation is even worst. It crashed also during modeling or setting material. The messege is always the same "The Plugin octane.dll has crashed". I have sent several bug reports to Maxon that confirmed that Octane is the problem.

augdalmo wrote:You ar not alone, I have encountered the same problem on R19. Exactly as descripted.
This occur today, in my case only on Live Viewer, sometime as i try to render region on "Lock resolution" view. I think is due to the new driver 417.71, but also the previous driver gave several other crash problems, but which could not be identified because C4D freeze. The crash problem start from the beginning of January, so I have installed the latest drivers some days ago. For now the error is CUDA error 700 on device 0: an illegal memory access
I have tried also on R20 the problem is the same and occur as I have described above.

A. Win 10 Pro
B. Graphics Cards GTX 1080 8GB + 4 GTX1080TI 11GB
C. RAM 64 GB
D. Nvidia driver version 417.71
E. OctaneRender Standalone 4.02
F. OctaneRender plugin version 4.01.1 - R2
G. Host application C4D R19

On R20 the situation is even worst. It crashed also during modeling or setting material. The messege is always the same "The Plugin octane.dll has crashed". I have sent several bug reports to Maxon that confirmed that Octane is the problem.

are you using any 8k or 16k textures?

A little more than 8K see attached file of textures in the scene. The problem of CUDA error occurr as i try to select a render region on Live Viewer some time at first try or after some different selection (always on Loked resolution (6000x3375)
I have installed now 4.02 release of C4D plugin in R19 an try it but doesn't solve the problem but there are more information now on the error.
this scene has never given me problems before, I think it's a problem with the new releases of the program and plugins

I have run some further test on the same scene with 3.08.5 NOT PROBLEM AT ALL and also on 2018.1-RC3 that crash immediately as I select a region on Locked resolution on LV. Same Cuda 700 error illegal memory access.
I am even more convinced there is a compatibility problem between the program / plugin and new video dirver.
I have observed that as I select "lock resolution" on LV on 3.08.5 the image change almost immediately, instead on 4.02 or 2018.1-RC1 is letagic it needs al least 6-10 seconds, then it may crash immediately or after one or two different region selection.

I'm bumping this thread, because I'm having CUDA error 700 issues quite frequently as well. Anybody found a solution yet?

Hi,
in general, CUDA error 700 is drivers or timeout related.
Please, use DDU to completely remove the installed drivers:
http://www.guru3d.com/files-details/dis ... nload.html
Then perform a clean installation of 417.22 drivers for your Win version.

To change the timeout, either run the Standalone installer or manually set the TdrDelay key to something like 10s or so. See here:

https://msdn.microsoft.com/en-us/librar ... s.85).aspx

In the Standalone installer we set these values:

WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrLevel 3
WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrDelay 10jh

Some Win 10 users have set the TdrDelay at 60, to solve their stability issues with CUDA.

ciao Beppe

bepeg4d wrote:Hi,
in general, CUDA error 700 is drivers or timeout related.
ciao Beppe

Thank you Beppe for your help, I appreciate it! I will test it.