Unable to use GPU to render any more. "Cuda illegal address in cuCtxSynchronize(), line 1372" #53072

New Issue

Simon Pollard · 2017-10-15T10:51:19+02:00

Simon Pollard commented

2017-10-15 10:51:19 +02:00

System Information
Windows 10 Home
10.0.14393 Build 14393

nVidia GeForce GTX 1080
Driver: 387.92 (latest version)

Blender Version
Broken: 2.79 2017-09-11 10:43 Hash: 5bd8ac9
Worked: 2.78c

Since upgrading to 2.79 I am now no longer able to use the GPU to render. I get the error "Cuda illegal address in cuCtxSynchronize(), line 1372" as soon as it tries to render.

The previous version (2.78c) worked absolutely fine. Need to move to 2.79 for the Principled BSDF shader workflow.

Exact steps for others to reproduce the error
N/A

**System Information** Windows 10 Home 10.0.14393 Build 14393 nVidia GeForce GTX 1080 Driver: 387.92 (latest version) **Blender Version** Broken: 2.79 2017-09-11 10:43 Hash: 5bd8ac9 Worked: 2.78c Since upgrading to 2.79 I am now no longer able to use the GPU to render. I get the error "Cuda illegal address in cuCtxSynchronize(), line 1372" as soon as it tries to render. The previous version (2.78c) worked absolutely fine. Need to move to 2.79 for the Principled BSDF shader workflow. **Exact steps for others to reproduce the error** N/A

Simon Pollard commented

2017-10-15 10:51:19 +02:00

Changed status to: 'Open'

Simon Pollard commented

2017-10-15 10:51:19 +02:00

Added subscriber: @polly2carpets

Brecht Van Lommel commented

2017-10-15 11:43:16 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2017-10-15 11:43:16 +02:00

Does it happen with the default startup cube scene? If not, please attach a .blend to reproduce the problem.
Did you verify it's the Blender version and not the Nvidia driver version that makes the difference, by running Blender 2.78c with the latest driver?
You could test the latest build from https://builder.blender.org/download/.
Running a slightly older Nvidia driver version may work around the problem.

* Does it happen with the default startup cube scene? If not, please attach a .blend to reproduce the problem. * Did you verify it's the Blender version and not the Nvidia driver version that makes the difference, by running Blender 2.78c with the latest driver? * You could test the latest build from https://builder.blender.org/download/. * Running a slightly older Nvidia driver version may work around the problem.

Simon Pollard commented

2017-10-15 12:25:22 +02:00

Thanks for such a prompt reply, Brecht

Does it happen with the default startup cube scene? If not, please attach a .blend to reproduce the problem.

Yes. It occurs even with reset to factory default and no addons installed.

Did you verify it's the Blender version and not the Nvidia driver version that makes the difference, by running Blender 2.78c with the latest driver?

I've just tried 2.78c and I get CUDA error: Illegal address in cuCtxSynchronise().

You could test the latest build from https://builder.blender.org/download/.

Tried the latest build of 2.79.1 and get "CUDA error: Illegal address in ctuCtxSynchronise(), line 1348"

Running a slightly older Nvidia driver version may work around the problem.

I've regressed my nVidia driver as far back as I can go from what's available at http://www.nvidia.com/Download/Find.aspx?lang=en-gb (to version 375.95) and I still get "Cuda illegal address in cuCtxSynchronize(), line 1372".

~ Simon

Thanks for such a prompt reply, Brecht > Does it happen with the default startup cube scene? If not, please attach a .blend to reproduce the problem. Yes. It occurs even with reset to factory default and no addons installed. > Did you verify it's the Blender version and not the Nvidia driver version that makes the difference, by running Blender 2.78c with the latest driver? I've just tried 2.78c and I get CUDA error: Illegal address in cuCtxSynchronise(). > You could test the latest build from https://builder.blender.org/download/. Tried the latest build of 2.79.1 and get "CUDA error: Illegal address in ctuCtxSynchronise(), line 1348" > Running a slightly older Nvidia driver version may work around the problem. I've regressed my nVidia driver as far back as I can go from what's available at http://www.nvidia.com/Download/Find.aspx?lang=en-gb (to version 375.95) and I still get "Cuda illegal address in cuCtxSynchronize(), line 1372". ~ Simon

Ivan Santic commented

2017-10-16 12:48:36 +02:00

Added subscriber: @moth3r

Ivan Santic commented

2017-10-16 12:48:36 +02:00

I believe, I was getting the same message on ASUSstrix 980Ti with all Blender builds (2.78 - 2.79c). I don't know what's the exact cause but I suspect card comes with a bit of factory overclock. On example, If I set it to work with GPU Tweak II on the 'silent mode' which lowers the default clock and not "oc" or "gaming" I was not getting that error. On top of the same message like Simon I was also experiencing visual glitches or random artifacts while over-viewing the 3d models. From the moment I started to see glitches BSOD were prone to happen.

Funny enough, card was and still is rock steady in the games like BF1 and it was running cool without overheating whatsoever. Only had these issue with Blender so far. More lately I am not using CYCLES for rendering so I am not sure is it still present. I only replied to this thread cause that's the first time I saw someone with the same problems I have experienced a couple of months ago.
It could be Blender but card could be also be faulty. If it's not Blender I'll have to do RMA myself.

System Information
Windows 10 Pro, Version 1703
15063.674 Build

nVidia GeForce GTX 980 TI ( ASUSstrix 980Ti)
AMD Ryzen 7 1800x 3.6ghz

I believe, I was getting the same message on ASUSstrix 980Ti with all Blender builds (2.78 - 2.79c). I don't know what's the exact cause but I suspect card comes with a bit of factory overclock. On example, If I set it to work with GPU Tweak II on the 'silent mode' which lowers the default clock and not "oc" or "gaming" I was not getting that error. On top of the same message like Simon I was also experiencing visual glitches or random artifacts while over-viewing the 3d models. From the moment I started to see glitches BSOD were prone to happen. Funny enough, card was and still is rock steady in the games like BF1 and it was running cool without overheating whatsoever. Only had these issue with Blender so far. More lately I am not using CYCLES for rendering so I am not sure is it still present. I only replied to this thread cause that's the first time I saw someone with the same problems I have experienced a couple of months ago. It could be Blender but card could be also be faulty. If it's not Blender I'll have to do RMA myself. System Information Windows 10 Pro, Version 1703 15063.674 Build nVidia GeForce GTX 980 TI ( ASUSstrix 980Ti) AMD Ryzen 7 1800x 3.6ghz

Brecht Van Lommel commented

2017-10-16 13:08:41 +02:00

We have a couple of similar reports, but currently none of the developers have been able to reproduce this issue. I've tried different scenes, different driver versions, different Windows 10 versions, reinstalling Windows, etc. Still it's unclear why there is a problem for some users, while most users seem to have no problem (as evidenced by threads like these ).

There's a few possible causes:

Bug in Cycles that causes it to access invalid memory, either in the kernel itself or in preparing data for the kernel. So far I have found nothing inspecting the code and running tools like valgrind and cuda-memcheck.
Different Nvidia graphics settings. Checking the "clean install" option when installing Nvidia drivers may help.
Corrupted Nvidia graphics installation. We've seen a few cases where Blender and any other application using CUDA crashes due to this, but not this type of error.
Differences in Windows versions or hardware. So far no pattern is visible here.

For now, all I can suggest is to do a totally clean driver install:

Uninstall any NVidia, AMD or Intel graphics drivers
Download latest driver from nvidia.com
Install, with clean install option checked
Reboot computer

Perhaps upgrading to Windows 10 Creators Update (or Fall Creators Update) may indirectly help as well.

We have a couple of similar reports, but currently none of the developers have been able to reproduce this issue. I've tried different scenes, different driver versions, different Windows 10 versions, reinstalling Windows, etc. Still it's unclear why there is a problem for some users, while most users seem to have no problem (as evidenced by [threads like these ](https://blenderartists.org/forum/showthread.php?439394-The-new-Cycles-GPU-2-79-Benchmark)). There's a few possible causes: * Bug in Cycles that causes it to access invalid memory, either in the kernel itself or in preparing data for the kernel. So far I have found nothing inspecting the code and running tools like valgrind and cuda-memcheck. * Different Nvidia graphics settings. Checking the "clean install" option when installing Nvidia drivers may help. * Corrupted Nvidia graphics installation. We've seen a few cases where Blender and any other application using CUDA crashes due to this, but not this type of error. * Differences in Windows versions or hardware. So far no pattern is visible here. For now, all I can suggest is to do a totally clean driver install: * Uninstall any NVidia, AMD or Intel graphics drivers * Download latest driver from nvidia.com * Install, with clean install option checked * Reboot computer Perhaps upgrading to Windows 10 Creators Update (or Fall Creators Update) may indirectly help as well.

Brecht Van Lommel commented

2017-10-17 12:19:41 +02:00

Closed as duplicate of #52572

Brecht Van Lommel closed this issue

2017-10-17 12:19:41 +02:00

Simon Pollard commented

2017-10-22 13:27:04 +02:00

Thanks again for your reply.

For now, all I can suggest is to do a totally clean driver install:

Uninstall any NVidia, AMD or Intel graphics drivers
Download latest driver from nvidia.com
Install, with clean install option checked
Reboot computer

I did all those things prior to posting. So frustrating. I came to use Blender today and it worked fine for a while in GPU rendered view and then stopped! Nothing else has changed!!

Thanks again for your reply. > For now, all I can suggest is to do a totally clean driver install: > Uninstall any NVidia, AMD or Intel graphics drivers > Download latest driver from nvidia.com > Install, with clean install option checked > Reboot computer I did all those things prior to posting. So frustrating. I came to use Blender today and it worked fine for a while in GPU rendered view and then stopped! Nothing else has changed!!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Unable to use GPU to render any more. "Cuda illegal address in cuCtxSynchronize(), line 1372" #53072