OctaneRender™ 2019.2 XB2 [latest 2019.2.x]

[glimpse]

I get crashes all the time with this XB2, as in PC Freezes and goes to that Blue Win 10 DPC Watchdog screen.
It seems to happen with random things, like moving a slider, loading a texture, copying and then pasting a texture.

I've seen this instability in many test versions before, but just wondering if anyone else sees this here too.
Don't know if it's my rig setup, where memory and GPU gives my CPU a heart attack suddenly.

of You are on PLX equipped mobo, it's not the issue with OctaneRender but moore with NVIDIA drivers. Do MSI fix for each of Your cards and this will go away. It's know driver issue (same that effects X99E WS), that hasn't been solved properly.

[Notiusweb]

I get crashes all the time with this XB2, as in PC Freezes and goes to that Blue Win 10 DPC Watchdog screen.
It seems to happen with random things, like moving a slider, loading a texture, copying and then pasting a texture.

I've seen this instability in many test versions before, but just wondering if anyone else sees this here too.
Don't know if it's my rig setup, where memory and GPU gives my CPU a heart attack suddenly.

of You are on PLX equipped mobo, it's not the issue with OctaneRender but moore with NVIDIA drivers. Do MSI fix for each of Your cards and this will go away. It's know driver issue (same that effects X99E WS), that hasn't been solved properly.

Hey Tom, what's up!
I suspect as much , that it is my rig and not Octane. What always is odd, though, is that some iterations of Octane (ie 2019.1 official) do not have this issue on my rig.

But, anyway what is the MSI-fix that you speak of? I am not familiar with this yet

On the side, do you know if the X99E-WS has many issues with Octane? That was always the mobo I would pick to replace my current!

And more than anything, thank you!!!

[J.C]

This build stopped working with Game ready drivers 440.97

Code: Select all

CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to bind device to current thread
device 1: failed to initialize context
device 1: failed to initialize render thread 00000265C7408CC0

[jobigoud]

This build stopped working with Game ready drivers 440.97

Code: Select all

CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to bind device to current thread
device 1: failed to initialize context
device 1: failed to initialize render thread 00000265C7408CC0

Is this scene-specific? I'm not reproducing the issue here with Game ready drivers 440.97 or 441.41. Any other specific context?

[J.C]

This happens after enabling RTX in devices preferences in one of the test scenes I use. Without RTX the scene render fine. There is 4GB free memory.

Code: Select all

CUDA error 2 on device 0: out of memory
  -> error mapping external memory
CUDA error 2 on device 1: out of memory
  -> error mapping external memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to wait for event
device 0: path tracing kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to wait for event
device 1: path tracing kernel failed

Before enabling RTX Octane works fine. After enabling it Octane generates errors and I need to restart the app to make it work again.

[rajib]

I get crashes all the time with this XB2, as in PC Freezes and goes to that Blue Win 10 DPC Watchdog screen.
On the side, do you know if the X99E-WS has many issues with Octane? That was always the mobo I would pick to replace my current!

I was on ASUS X99E-WS and currently on the ASUS X299-Sage WS. I did and currently do get BSOD with the watch dog error. Though it was a lot more frequent on the X99-WS (almost everyday multiple times). On my current X299 SAGE WS it only occurs now and then. Sometimes I can go a few weeks before I get it. One thing I had noticed and I did post it here was that out of my 128GB RAM if I allocated more than 14GB of RAM for OOC memory, Octane render become very unstable. So currently I do not allocate more than 14GB for OOC memory and things more or less run okay. But yes there are scenes I am unable to do because it needs more than 14GB of OOC memory. Maybe with the new nVidia Studio Drivers I should give this a try again. Hopefully it will be stable.