Hi Marcus,
I've got the same problem:["the device driver gets "killed" by windows"] and the render fails again and again and stops eventually.
My scene is quite heavy but my hardware should do the job easily. The problem still occurs after removing octane proxys and displacement.
So I've changed the "TdrDelay" to 30 and even 60 but nothing changed.
Honestly, this is a very important problem.
I'm thinking of reversing to another rendering program for this scene. It depresses me to do that but I don't see any other way. Do you?
PS: error log attached
1 GTX TITAN X and 2 GTX TITAN Black
Octane Version 2.21.1
GeForce Driver Version 347.88
Sincerely,
Julien
abstrax wrote:Hi Coilbook,
The last problem is a limitation: You are very likely using a lot of displacement mapping, which can be really slow (especially since 2.13 - we are working on it). That means that a kernel call may take longer than the times specified in the TdrDelay settings of the registry. The Standalone installer sets this value to 10 (seconds). If the kernel takes longer, the device driver gets "killed" by Windows. The reason why it does that is because a kernel call on a display GPU that never finishes, will cause the whole system to hang.
Unfortunately, when Octane launches a kernel and it takes too long, there is no way to stop it. In other words, we can't do anything about the timeout it. But you can manually change it to a higher timeout via the registry editor:
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
- The key "TdrLevel" should be set to 3.
- The key "TdrDelay" is the delay in seconds. Maybe set it to 20 or 30.
If that is still not solving the problem and you are using displacement mapping in the scene, you may have stumbled over a displacement bug, that Andrey fixed a few days ago (causing the kernel to hang in an infinite loop).
I hope that helps,
Marcus