Failed to destroy texture objects
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
-
chrisbrearley
- Posts: 23
- Joined: Mon Jul 11, 2016 11:09 am
Anyone seen this one before and/or know how to fix it? Happens when when we use our machine as a slave, seems ok when rendering from an ORBX with standalone. Tried a few driver versions including latest 442.19 but no change.
Hi,
please, upgrade both Master and Slaves to v2019.1.5, thanks.
Have you installed Standalone on the Slave, at least once? Not the zipped version, but the proper installer.
It changes the TdrDaelay registry in Windows.
If yes, then probably it is not enough and you need to increase it. See here:
https://msdn.microsoft.com/en-us/librar ... s.85).aspx
The Standalone installer sets these values:
WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrLevel 3
WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrDelay 10jh
Some Win 10 users have set the TdrDelay at 60, to solve their stability issues with CUDA.
ciao Beppe
please, upgrade both Master and Slaves to v2019.1.5, thanks.
Have you installed Standalone on the Slave, at least once? Not the zipped version, but the proper installer.
It changes the TdrDaelay registry in Windows.
If yes, then probably it is not enough and you need to increase it. See here:
https://msdn.microsoft.com/en-us/librar ... s.85).aspx
The Standalone installer sets these values:
WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrLevel 3
WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrDelay 10jh
Some Win 10 users have set the TdrDelay at 60, to solve their stability issues with CUDA.
ciao Beppe