CUDA error when using displacement on the GPU.

Question

question

Ewan Laidlaw asked · Sep 22, 2020 at 10:26 AM

CUDA error when using displacement on the GPU.

I get this error on some scenes when using a Maya displacement shader on the GPU:

// Error: [gpu] an error happened during rendering : Unknown error (Details: Function "_rtContextLaunch2D" caught exception: Encountered a CUDA error: cudaDriver().CuEventSynchronize( m_event ) returned (700): Illegal address, file: <internal>, line: 0) //

I am using a RTX 2070 Super.

The error occurs on a scene basis, it will begin happening randomly as far as I can tell and doesnt occur all the time even with the exact same shader setup in a different.

The same scene on the CPU renders with no issue.

Ignoring displacement in the diagnostics doesn't stop the error. The image texture and/or displacement shader has to be disconnected in the node editor. The scene will render with the same shader network if the displacment is disconnected (Maya restart is required). Using Arnold subdivision works fine, its only displacement.

I have tried up and down grading the MtoA version as well as installing different Nvidia drivers (both game and studio editions).

I do get a fatal GPU error occasionally when updating a scene in the render view, maybe its related.

Cheers.

gpu shader displacement

4

10 |600 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Piers Cowburn · Sep 27, 2020 at 06:30 PM

I get the same error. I managed to track it down to specifically using cell noise to drive displacement. Regular noise works fine, but as soon as any path including cell noise gets used for displacement, I get this error and am unable to render.

I'm using an RTX 2080, with Houdini and Arnold 6.0.4.0 on Ubuntu 18.04.5.

0 ·

Declan Russell Piers Cowburn · Sep 28, 2020 at 01:53 PM

Hi Piers,

I tried to repro your crash. I just had a simple polygon sphere and used a cell noise as the displacement but did not experience the crash. Is there something extra I need to do to reproduce the crash, or better yet do you have a simple .ass file that I can use to repro?

Cheers,

Dec

0 ·

Piers Cowburn Declan Russell · Sep 28, 2020 at 07:11 PM

I experimented a bit more and found that there were a few more things in my material that were required in order for it to crash. I've attached a .hiplc that contains a minimal example. If any of the six nodes in the material are removed, the crash no longer occurs – this is true even though the two multiply nodes simply multiply the input by 1.

error.hiplc.zip

0 ·

errorhiplc.zip (113.9 KiB)

Show more comments

Answer 1 · 2021-04-25T23:47:10Z

Yang Liu answered · Apr 25 at 11:47 PM

I have also hit this problem when using Maya 2020 + Arnold 4.2.2. Arnold outputs a similar error message when my GPU memory is still clearly sufficient.

I don't know why Arnold don't like the height map I used. Would be great if anyone can give any workarounds. Arnold also needs to output a better error message.

10 |600 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Answer 2 · 2020-12-19T03:08:21Z

Andrew Neilson answered · Dec 19, 2020 at 03:08 AM

Having exact same issue with 3DS Max and RTX 3080.

Arnold: 4.2.2.20

NVIDIA: 360.89

[Arnold]: 00:04:14 7372MB ERROR | [gpu] an error happened during rendering : Unknown error (Details: Function "_rtContextLaunch2D" caught exception: Encountered a CUDA error: cudaDriver().CuEventSynchronize( m_event ) returned (700): Illegal address, file: <internal>, line: 0)

1

10 |600 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Thiago Ize · Jan 04 at 06:53 PM

This is unfortunately a generic error message that could be triggered in many ways. Is this happening because of displacement, which should now be fixed? If it's a new problem, please post a new arnold answers question so we can make sure it gets the attention it deserves.

0 ·

Answer 3 · 2020-11-16T13:42:50Z

Declan Russell answered · Nov 16, 2020 at 01:42 PM

An update on this. We have a workaround to stop the crash that will be coming in the next bug fix release. The workaround essentially means that we disable autobump when this case pops up. This is far from ideal I know, but its better than a crash. A real fix will come when we move to OptiX 7.

10 |600 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

Answer 4 · 2020-11-14T17:36:17Z

Lucas Tebib answered · Nov 14, 2020 at 05:36 PM

Hi, the same happens to me on a scene that was perfectly working less than 24hours ago. If I ignore displacement, it's working, otherwise same error.

I tried both latest Game Ready and Studio driver, doesn't change anything.

10 |600 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 2.0 MiB each and 9.8 MiB total.

question