3.6 RT GPU: Render crashes

[kosso_olli]

Hey,
I seem to have severe problems with anything GPU related: The lens effects and the GPU rendering itself. When rendering, the display driver crashes, I get a little warning from windows that the display driver was restored. Also, this error appears in the message window.

So, two problems:
- Lens effects crashing Max to desktop while generating glare and bloom with GPU accel.
- Render crashes display driver, render doesn't finish

Hardware specs:

- Xeon E5-2687W 3.1Ghz
- 128gb Ram
- GTX Titan 6gb
- driver version: 382.53 (on Blagos recommendation), also tried 368.22, same problem
- Max 2016 SP3
- V-Ray 3.60.01
- Windows 7 Pro SP1

This happens on two identical workstations with the same drivers, OS, etc.
Only GPU selected, I didn't try Hybrid yet.
I have to restart Max in order to render again, until the next crash occurs...

[savage309]

Please try with driver as closest as possible to 376.

Best,
Blago.

[kosso_olli]

Just did a clean install of 376.09: Problem is still occuring with GPU alone.
However, when I restart Max and select my CPU as CUDA device as well, the scene renders fine. No crash of the display driver at all. With GPU alone, the render crashs at a noise threshold of around 0.07, with CPU+GPU it renders on. Very strange, this...

[savage309]

The CPU as CUDA device does not rely on the NVIDIA drivers. Apparently there is some issue with your GPU and the newest V-Ray GPU code. I will ask the support guys to try to reproduce that here.

Best,
Blago.

[kosso_olli]

Well, maybe my last post was a little misleading: Both CPU and GPU are rendering. GPU-Z is showing me that the GPU has 100% load all the time until the render finishes. Why it doesn't render on it's own is a mystery to my, though.
What I can say is that I get a significant speed boost in hybrid mode. The render reaches the noise threshold of 0.07 (as far as the GPU can render on its own before crashing) nearly twice as fast.

[savage309]

I have misunderstood that. We will still try to reproduce that here. Thanks for the update!

Best,
Blago.

[Zdravko.Keremidchiev]

We tested the issue with the same card, drivers and V-Ray build but everything is working fine on our side. Could you please try to delete the content in %APPDATA%/NVIDIA and if the issue still persist send us the scene so we could investigate further.

[kosso_olli]

Deleting the content in the temp folder didn't help, either. Will send the scene to support and post the ticket number here.

[kosso_olli]

Ticket number is: [#638960]

Thanks guys!

[mitchell_architecural]

Is this happening even with new scenes?

Yesterday I installed 3.6 and started testing RT with my GPUs (980Ti & 1080). Was getting Error 719 every time as well. Crashing my driver. This was on existing scenes that had rendered with RT in 3.5 just fine. I had tried updating the NVIDIA driver and restarting. But, IIRC, it wasn't until I started a new scene with a simple test setup that I was able to use the GPUs successfully, and then reopened the previous existing scenes and they rendered fine. No errors. Weird.

[Zdravko.Keremidchiev]

Ticket number is: [#638960]

Thank you for sending us the file, we manage to reproduce the crash error. The developers are investigating the issue.

[Zdravko.Keremidchiev]

This is a compiler bug which is due to a missing material in the base blend material of the material "floor_wood". If you set a shader there it won't crash.

[kosso_olli]

Zdravko, thanks for the pointer. Is it something that can be fixed on the V-Ray side, meaning it won't crash if there is a blend material with no base?