Hi Guys. Please help me to sort out this annoying problems. Keep getting this errors (sometimes in the viewport render and sometimes after f12) even after upgrading nvidia driver and cuda 8 and adding more threads in TdrDelay file. Interesting thing that computer can render one scene for example the car… But then if i go to render more detailed scene with smoke for example its get that error…then another menu pops up which says:
“Blender Application has been blocked from accessing graphics hardware”
and once that pops up i cant render nothing at all even that car blend file, so i have to update driver nvidia and cuda again and everything starts again, another same circle of the hell once i decide to render something complicated.
Maybe tell me at least how to tell my Windows 10 or antivirus (i dont know who or what ) not to block Blender from accessing hardware when problem with cuda arise
Hm. Interesting thing that i can render my car scene again without error. So i think the problem is maybe in file where the smoke scene is. Because once i go to that blend scene with smoke and try to render it…i have CUDA error + “Blender Application has been blocked from accessing graphics hardware” . And after this i cannot render anything until i close Blender. If i close blender and go to render car scene for example it will render again…, So i need to stay clear of that blend file with smoke probably
Tdr delay to set it to 0? Nope. In my case I put value 100 decimal. If I set it to 0, I almost always have another cuda error which says something like cuda exceeded time out limit, smth like that. And same thing I had on my old laptop.
BTW, thanks for the tip to make a bug report. I think, I will, I just not sure if it’s bug or not
You are not using Branched Path Tracing then if you do not know where it is. I thought that this could cause the problem.
It is under Sampling settings in Render tab.
Hehe, no, not TdrDelay I wrote TdrLevel but 100 is really high anyway.
Btw., the CUDA error : Launch failed in cuCtxSynchronize()” and “cuCtxCreate: is a Blender error and has nothing to do with Driver timeout.
If it is not to heavy you can upload the smoke file, we can test it.
This is for anyone that happens to stumble upon this thread. I had a similar issue with cycles, and had ample amounts of VRAM for rendering certain scenes and benchmark test files.
I discovered rebooting your system helps because there may be an issue with the Nvidia drivers, and your system may simply need to be rebooted. Another way to fix this issue is switching to a previous driver, and then switching back to the most recent driver. By doing it this way, you also have to reboot your system.
This is just a theory, but trying one or both of these methods may help reset and fix some code linking issues between your OS, the Nvidia drivers, and Blender.
If this doesn’t help, there could be other issues.
So far, things seem to be operating as before. I’ll give it some time, and hopefully this issue doesn’t come up again.
