Page 1 of 1

CUDA error 702

Posted: Tue May 22, 2018 5:08 pm
by DDC
I've been constantly plagued by the CUDA 702 error - Had it constantly in 3.07, then reverted my drivers back to 382.33 which worked for a bit.

When 3.08 was released, I figured those bugs would be solved, so upgraded, then realized had to update drivers, so did that as well - CUDA 702 returns.

Reverted back to 3.07, reverted drivers back, worked for a week, then getting errors again. Like most people, it doesn't trigger if I set to use only ONE of my graphics cards, but that is not an acceptable solution.

Help computer.

A. Windows 10 x64
B. 3 x Nvidia GTX 1080 Ti
C. 128 GB
D. 382.33
E. 3.08
F. 3.07-R2
G. Cinema 4D R19.053
H. Rendering anything remotely beyond simple will bring up the error in octane (latest project for this to happen attached)
I. CUDA error 702 on device 0: the launch timed out and was terminated

Re: CUDA error 702

Posted: Wed May 23, 2018 7:24 am
by bepeg4d
Hi unfortunately CUDA error 702 is drivers related, there are other Win 10 users reporting the same issue.
Remove the automatic update option in Win 10, use DDU, then perform a clean installation of 387.92 drivers:
http://www.nvidia.com/download/driverRe ... px/125586/
ciao Beppe

Re: CUDA error 702

Posted: Wed May 23, 2018 9:26 pm
by DDC
Thanks. I did all of that, and am still getting errors, Attaching error log and project file. please help, thanks

Re: CUDA error 702

Posted: Wed May 23, 2018 10:47 pm
by roeland
That can happen if the GPU code takes too long to complete. To work around this, you have to increase the timeout for the TDR recovery system (the default is 2 seconds, you may increase it to 10 seconds or so if you often render heavy scenes). The Octane standalone installer will do that for you when installing.

If you want to do this manually, you can use regedit and add following DWORD values.
(as usual with regedit, mistakes may render your system unstable or otherwise maimed, so be careful)
HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\TdrLevel = 3
HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\TdrDelay = 10

Re: CUDA error 702

Posted: Wed May 30, 2018 3:46 pm
by DDC
So does that mean I can upgrade to 3.08? I'm not sure why this is happening to my computer while other people do not.

Some explanation behind why some PC's have this error and others do not would be appreciated - especially for people like me who spent THOUSANDS to build a rig to run octane specifically and now doesn't work.

Re: CUDA error 702

Posted: Wed May 30, 2018 4:09 pm
by bepeg4d
Hi,
unfortunately a lot of Win 10 users are reporting issues with the latest Nvidia driver, especially with X99 motherboards.
Please, follow my suggestions and downgrade to an older but more stable version like 387.92, or 388.13 using DDU and a clean installation.
ciao Beppe

Re: CUDA error 702

Posted: Thu May 31, 2018 7:39 pm
by DDC
I have used DDU to clear out old drivers then installed 387.92.

I have also incresed the timeout for the TDR recovery as instructed (this did NOT happen automatically when I installed the standalone version fyi)

I am still getting the CUDA errors

Re: CUDA error 702

Posted: Thu May 31, 2018 8:58 pm
by DDC
Here's a super simplistic scene that caused the latest crash, along with crash log if that helps at all