Issue while rendering with Geforce 780 Ti #51696

New Issue

Tapani Korhonen · 2017-06-01T17:48:23+02:00

Tapani Korhonen commented

2017-06-01 17:48:23 +02:00

System Information
Windows 10, GPU Nvidia Geforce GTX 780 Ti

Blender Version
2.78c

Short description of error
Cyclic rendering using GPU does not work. Plain scene - cube+camera+lamp.

first rendering : Cuda error : illegal address in cuCtxSynchronize() (image - error 1)
second time rendering : Cuda error : illegal address in cuCtxCreate (image - error 2)
there are settings of User Preferences (image - settings)

I've been upgraded GPU drivers totally, the issue remains as it has been a while.

**System Information** Windows 10, GPU Nvidia Geforce GTX 780 Ti **Blender Version** 2.78c **Short description of error** Cyclic rendering using GPU does not work. Plain scene - cube+camera+lamp. - first rendering : Cuda error : illegal address in cuCtxSynchronize() (image - error 1) ![kuva.png](https://archive.blender.org/developer/F615362/kuva.png) - second time rendering : Cuda error : illegal address in cuCtxCreate (image - error 2) ![kuva.png](https://archive.blender.org/developer/F615364/kuva.png) - there are settings of User Preferences (image - settings) ![kuva.png](https://archive.blender.org/developer/F615366/kuva.png) I've been upgraded GPU drivers totally, the issue remains as it has been a while.

Tapani Korhonen commented

2017-06-01 17:48:23 +02:00

Changed status to: 'Open'

Tapani Korhonen commented

2017-06-01 17:48:23 +02:00

Added subscriber: @Tapu-3

Fable Fox commented

2017-06-02 03:18:39 +02:00

Added subscriber: @fablefox

Fable Fox commented

2017-06-02 03:18:39 +02:00

Can you run Blender with --debug-cycles command line argument to make prints much more verbose to see where exactly things stuck. The resulting messages might help developers.

Tapani Korhonen commented

2017-06-02 08:30:20 +02:00

Ok, started blender in --debug-cycles mode : image

Rendering started in cycles : image

After couple seconds render : image

Hope this will help!

Ok, started blender in --debug-cycles mode : image ![kuva.png](https://archive.blender.org/developer/F615734/kuva.png) Rendering started in cycles : image ![kuva.png](https://archive.blender.org/developer/F615736/kuva.png) After couple seconds render : image ![kuva.png](https://archive.blender.org/developer/F615738/kuva.png) Hope this will help!

Sergey Sharybin commented

2017-06-02 11:28:05 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2017-06-02 11:28:05 +02:00

Please attach logs as text files, not as screenshots. Attached screenshots are lacking most crucial details since those are scrolled away.

So run blender with --debug-cycles command line argument,. make it to fail, copy-paste console logs to a file and attach file here (do not copy-paste logs directly to the comment box).

Additionally, test whether any previous Blender version works for you and whether latest builds from builder.blender.org works.

Please attach logs as text files, not as screenshots. Attached screenshots are lacking most crucial details since those are scrolled away. So run blender with --debug-cycles command line argument,. make it to fail, copy-paste console logs to a file and attach file here (do not copy-paste logs directly to the comment box). Additionally, test whether any previous Blender version works for you and whether latest builds from builder.blender.org works.

Tapani Korhonen commented

2017-06-02 12:29:30 +02:00

Here's the file attached. There's only the Blender 2.78c which I've been using.

Here's the file attached. There's only the Blender 2.78c which I've been using.![GPU issue Nvidia Geforce 780 Ti.png](https://archive.blender.org/developer/F615874/GPU_issue_Nvidia_Geforce_780_Ti.png)

Sergey Sharybin commented

2017-06-02 12:33:18 +02:00

Please do full textfile log of everything printed by Blender to the console.
Also test if it ever worked in previous Blender version and whether it works with latest builds from buildbot.

Please do **full** textfile log of **everything** printed by Blender to the console. Also test if it ever worked in previous Blender version and whether it works with latest builds from buildbot.

Tapani Korhonen commented

2017-06-02 12:42:04 +02:00

This file is all what I got... there was only same "CUDA error : illegal cuda address in cuMemAlloc(&device_pointer, size)" repeating over and over again...
I do not have previous versions of Blender, as I told.

This file is all what I got... there was only same "CUDA error : illegal cuda address in cuMemAlloc(&device_pointer, size)" repeating over and over again... I do not have previous versions of Blender, as I told.

Sergey Sharybin commented

2017-06-02 12:48:39 +02:00

Those are inducted errors, we need to know exact first CUDA error and know what cycles was doing right prior that error occurred.

If you don't have previous blender version, get a newer one from builder.blender.org. The issue might have been already solved.

And one more thing. Windows 10 tempts to re-install video driver with their tweaked version via Windows Update. This was giving issues in the past already. So try getting drivers from nvidia.com and re-install them (even if they report same version, the content might be different).

Those are inducted errors, we need to know exact first CUDA error and know what cycles was doing right prior that error occurred. If you don't have previous blender version, get a newer one from builder.blender.org. The issue might have been already solved. And one more thing. Windows 10 tempts to re-install video driver with their tweaked version via Windows Update. This was giving issues in the past already. So try getting drivers from nvidia.com and re-install them (even if they report same version, the content might be different).

Tapani Korhonen commented

2017-06-02 13:07:49 +02:00

Those are inducted errors, we need to know exact first CUDA error and know what cycles was doing right prior that error occurred.

This is the very first error when Cyclic rendering starts : "Cuda error : illegal address in cuCtxSynchronize()". I will be able to give more specific info, if you let me know how to do it.

If you don't have previous blender version, get a newer one from builder.blender.org. The issue might have been already solved.

This version (2.78c) has been installed in the mid of april 2017. Is there a new upgrade?

And one more thing. Windows 10 tempts to re-install video driver with their tweaked version via Windows Update. This was giving issues in the past already. So try getting drivers from nvidia.com and re-install them (even if they report same version, the content might be different).

Drivers has been reinstalled several times in this week. Downloaded from Nvidia (version 382.33).

> Those are inducted errors, we need to know exact first CUDA error and know what cycles was doing right prior that error occurred. This is the very first error when Cyclic rendering starts : "Cuda error : illegal address in cuCtxSynchronize()". I will be able to give more specific info, if you let me know how to do it. > If you don't have previous blender version, get a newer one from builder.blender.org. The issue might have been already solved. > This version (2.78c) has been installed in the mid of april 2017. Is there a new upgrade? > And one more thing. Windows 10 tempts to re-install video driver with their tweaked version via Windows Update. This was giving issues in the past already. So try getting drivers from nvidia.com and re-install them (even if they report same version, the content might be different). Drivers has been reinstalled several times in this week. Downloaded from Nvidia (version 382.33).

Bastien Montagne commented

2017-06-16 16:05:35 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2017-06-16 16:05:35 +02:00

@Tapu-3 Please always try the latest build from our buildbot.

@Tapu-3 Please always try the latest build from [our buildbot](https://builder.blender.org/download).

Tapani Korhonen commented

2017-06-19 14:08:13 +02:00

The Blender version is 2.78c and it's installed in the mid of april 2017. Please inform if there is a new version to be installed.

The Blender version is **2.78c** and it's installed in the **mid of april 2017**. Please inform if there is a new version to be installed.

Bastien Montagne commented

2017-06-19 14:17:26 +02:00

@Tapu-3 there is nothing more to inform, as said just download latest build from given link and test with it, this is basic task to do before reporting a bug (those daily builds reflect current master code, not as stable as official release, but will contain all fixes done since last release).

Tapani Korhonen commented

2017-06-19 15:17:08 +02:00

Ok, this is the version what I'm using at the moment. It has been released in january 2017, I installed this version in april - it's the official version.

Bastien Montagne commented

2017-06-19 15:34:27 +02:00

In #51696#440786, @mont29 wrote:
@Tapu-3 Please always try the latest build from our buildbot.

What is not clear in this simple phrase? 2.78c release IS NOT CURRENT MASTER CODE!

Please download THE LATEST BUILD FROM OUR BUILDBOT, which IS NOT 2.78c but current master code, and try to reproduce your issue with that build.

> In #51696#440786, @mont29 wrote: > @Tapu-3 Please always try the latest build from [our buildbot](https://builder.blender.org/download). What is not clear in this simple phrase? 2.78c release **IS NOT CURRENT MASTER CODE**! Please download **THE LATEST BUILD FROM [OUR BUILDBOT](https://builder.blender.org/download),** which **IS NOT 2.78c** but current master code, and try to reproduce your issue with that build.

Tapani Korhonen commented

2017-06-19 16:01:21 +02:00

Ok, latest version 2.78 downloaded - results :

Blender default scene
Cyclic rendering
GPU mode
- render -> CUDA error : illegal address in cuCtxSynchronize(), line 1371 (render stops)

Ok, latest version 2.78 downloaded - results : - Blender default scene - Cyclic rendering - GPU mode - > render -> CUDA error : illegal address in cuCtxSynchronize(), line 1371 (render stops)

Bastien Montagne commented

2017-06-19 16:21:47 +02:00

Thanks, now we know issue is still in current code.

Now, please run Blender (the latest one you downloaded from buildbot) with --debug-cycles option, and attach here as a text file (do not paste it directly in comment!) the full log. See e.g. this stackexchange topic for how to get proper full textual log from console.

Thanks, now we know issue is still in current code. Now, please run Blender (the latest one you downloaded from buildbot) with `--debug-cycles` option, and attach here as a text file (do not paste it directly in comment!) the full log. See e.g. [this stackexchange topic](https://blender.stackexchange.com/questions/6921/how-to-write-the-output-of-blender-console-out-to-a-file) for how to get proper full textual log from console.

Steffen Dünner commented

2017-06-19 16:31:41 +02:00

Added subscriber: @SteffenD

Tapani Korhonen commented

2017-06-19 17:17:21 +02:00

Here's the blender.log, I assume there's only the last part of the action (quit)... blender.log

CMD :

blender --debug-cycles>blender.log

Here's the blender.log, I assume there's only the last part of the action (quit)... [blender.log](https://archive.blender.org/developer/F635775/blender.log) CMD : - blender --debug-cycles>blender.log

Ray molenkamp commented

2017-06-19 17:35:05 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2017-06-19 17:35:05 +02:00

Can you check your windows event log for any reports of event ID 4101 around the time that blender crashes?

Can you check your windows event log for any reports of event [ID 4101 ](https://technet.microsoft.com/en-ca/library/dd349439(v=ws.10).aspx) around the time that blender crashes?

Tapani Korhonen commented

2017-06-19 18:13:38 +02:00

There was no crash reports at that time for id 4101, but this is what was found during the error "illegal address" :

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvlddmkm" /> 
<EventID Qualifiers="49322">13</EventID> 
<Level>2</Level> 
<Task>0</Task> 
<Keywords>0x80000000000000</Keywords> 
<TimeCreated SystemTime="2017-06-19T14:33:07.194255300Z" /> 
<EventRecordID>14416943</EventRecordID> 
<Channel>System</Channel> 
<Computer>Computer_i7</Computer> 
<Security /> 
</System>

<Data>\Device\UVMLiteProcess4</Data> 
<Data>Graphics Exception: ESR 0x524e48=0x1000e 0x524e50=0x4 0x524e44=0x13eff2 0x524e4c=0x7f</Data> 
<Binary>0000000002003000000000000D00AAC0000000000000000000000000000000000000000000000000</Binary> 
</EventData>
</Event>

There was no crash reports at that time for id 4101, but this is what was found during the error "illegal address" : ``` <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="nvlddmkm" /> <EventID Qualifiers="49322">13</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-06-19T14:33:07.194255300Z" /> <EventRecordID>14416943</EventRecordID> <Channel>System</Channel> <Computer>Computer_i7</Computer> <Security /> </System> ``` - <EventData> ``` <Data>\Device\UVMLiteProcess4</Data> <Data>Graphics Exception: ESR 0x524e48=0x1000e 0x524e50=0x4 0x524e44=0x13eff2 0x524e4c=0x7f</Data> <Binary>0000000002003000000000000D00AAC0000000000000000000000000000000000000000000000000</Binary> </EventData> </Event>

Ray molenkamp commented

2017-06-19 18:18:55 +02:00

Reduce your tile size in the render settings, should fix the issue.

Bastien Montagne commented

2017-06-28 10:38:26 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2017-06-28 10:38:26 +02:00

Bastien Montagne self-assigned this 2017-06-28 10:38:26 +02:00

Bastien Montagne commented

2017-06-28 10:38:26 +02:00

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

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

Issue while rendering with Geforce 780 Ti #51696