Anyone seen this message in the log file before?
00:00:14 (0014.44) * OCTANE API MSG: CUDA error 999 on device 3: unknown error
00:00:14 (0014.44) * OCTANE API MSG: -> failed to bind device to current thread
00:00:14 (0014.44) * OCTANE API MSG: device 3: failed to initialize resources
00:00:14 (0014.44) |
00:00:14 (0014.44) | ++++++++++++++++++++++++++
00:00:14 (0014.44) | +++ IPR RENDER FAILURE +++ processing the failure callback
00:00:14 (0014.44) | ++++++++++++++++++++++++++
00:00:14 (0014.44) |
00:00:14 (0014.70) | ... second update
00:00:14 (0014.70) | ... isRenderingPaused
00:00:14 (0014.70) | Render setup Ok.
It just started happening. I was playing with the hardware to try to get things cooler (using a PCIe extender) and now when I load this particular LW scene (it has TFD in it) it gives me this error and won't render.
CUDA Error
Moderator: juanjgon
Hi,
Hmm, this crash sounds to me like a problem with these extenders. One thing that you can try if you are using GPU extenders of external boxes is to disable the tone mapping for all these GPUs, leaving this option enabled only for the GPUs attached directly to the main board. The "use for tone map" option is available in the same panel used to configure the GPUs.
Thanks,
-Juanjo
Hmm, this crash sounds to me like a problem with these extenders. One thing that you can try if you are using GPU extenders of external boxes is to disable the tone mapping for all these GPUs, leaving this option enabled only for the GPUs attached directly to the main board. The "use for tone map" option is available in the same panel used to configure the GPUs.
Thanks,
-Juanjo
You could try increasing your drivers timeout...
Open the registry and go to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers"
Edit the key "TdrDelay". I think it's default value is 10, try setting it higher to something like 60 or 90.
Basically this will give your graphics drivers 60 or 90 seconds to recover rather than 10. I believe heavy scenes take a long time to transfer in and out of vram and 10 seconds simply isnt enough time for the process to happen, so your computer assumes it has crashed and will restart your drivers.
Open the registry and go to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers"
Edit the key "TdrDelay". I think it's default value is 10, try setting it higher to something like 60 or 90.
Basically this will give your graphics drivers 60 or 90 seconds to recover rather than 10. I believe heavy scenes take a long time to transfer in and out of vram and 10 seconds simply isnt enough time for the process to happen, so your computer assumes it has crashed and will restart your drivers.
Awesome, thank you both. I'll try both suggestions. I haven't had any previous problems with any scenes (I should have left well enough alone) but the cards were getting too hot (and throttling) and was hoping to create some relief. I have removed the extender and put all the cards back direct and still have the issue. One card will drop without any response (with drivers crash) and I have to reboot the machine or re-install drivers to get it back. I removed that card and it happened to a second one in a different slot. With that revelation, I'm hopeful it's not a hardware issue.
Strange thing here. When I load the VDB version of the TFD solve, there is no such error when rendering...It doesn't show up in IPR, but the IPR window works and renders as normal. I just don't know how to get VDB's to render yet 
I'm wondering if there is a memory issue (is 6GB's enough for this TFD calculation?)...
I'm wondering if there is a memory issue (is 6GB's enough for this TFD calculation?)...