GPU Compute in Cycles is broken on AMD stable drivers and Blender stable release #48028

New Issue

Adrian · 2016-04-01T12:45:13+02:00

Adrian commented

2016-04-01 12:45:13 +02:00

System Information
Windows 10 x64 Pro
Radeon R9 380 4G

Blender Version
Broken: 2.76b
Worked: On AMD drivers from last year

I have already reported this bug in the past, but it was ignored because AMd drivers were not stable then.
Now it happens on certified stable driver release, and on blender stable release.
The problem is: If you use GPU compute on AMD GPU with Cycles, the sampling is broken and results in visible horizonral artifacts instead of normal noise.

Exact steps for others to reproduce the error
I attach the simplified project here, just hit F12 to render again with AMD:
bug.blend

Here is also the errornous render result:

Please don't say again that you don't care, apparently a lot of people use their AMDs to render things and WONT want to downgrade drivers.

Thank you.

**System Information** Windows 10 x64 Pro Radeon R9 380 4G **Blender Version** Broken: 2.76b Worked: On AMD drivers from last year I have already reported this bug in the past, but it was ignored because AMd drivers were not stable then. Now it happens on certified stable driver release, and on blender stable release. The problem is: If you use GPU compute on AMD GPU with Cycles, the sampling is broken and results in visible horizonral artifacts instead of normal noise. **Exact steps for others to reproduce the error** I attach the simplified project here, just hit F12 to render again with AMD: [bug.blend](https://archive.blender.org/developer/F300079/bug.blend) Here is also the errornous render result: ![bugblender.png](https://archive.blender.org/developer/F300080/bugblender.png) Please don't say again that you don't care, apparently a lot of people use their AMDs to render things and WONT want to downgrade drivers. Thank you.

Adrian commented

2016-04-01 12:45:13 +02:00

Changed status to: 'Open'

Adrian commented

2016-04-01 12:45:13 +02:00

Added subscriber: @afl_ext

blender-admin commented

2016-04-01 12:45:13 +02:00

#48031 was marked as duplicate of this issue

Mischa Alff commented

2016-04-01 14:33:32 +02:00

Added subscriber: @MrAster

Mischa Alff commented

2016-04-01 14:33:32 +02:00

I get the same issue on Windows 8.1 x86-64, AMD Radeon R7 200 series with latest AMD drivers, and Blender 2.76b.

Adrian commented

2016-04-01 14:43:56 +02:00

I also tested 2.77 f185eff build version and it's still the same

I also tested 2.77 f185eff build version and it's still the same

Thomas Dinges commented

2016-04-01 20:25:07 +02:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2016-04-01 20:25:07 +02:00

Can you both confirm, that 2.76 is broken too?

Because in that case, I doubt it is Cycles fault. Blender 2.76b is several months old, and we did not get such reports back then. Which means, the issue is in the driver, and yes we cannot fix that.

Can you both confirm, that 2.76 is broken too? Because in that case, I doubt it is Cycles fault. Blender 2.76b is several months old, and we did not get such reports back then. Which means, the issue is in the driver, and yes we cannot fix that.

Thomas Dinges commented

2016-04-01 20:25:34 +02:00

Added subscriber: @StefanW

Stefan Wojtyna commented

2016-04-01 21:12:24 +02:00

I tested it on version 2.76 and 2.76b
So probably there's something with the latest AMD Driver :/

I tested it on version 2.76 and 2.76b So probably there's something with the latest AMD Driver :/ ![Screenshot_1 (2).png](https://archive.blender.org/developer/F300382/Screenshot_1__2_.png) ![Screenshot_2.png](https://archive.blender.org/developer/F300383/Screenshot_2.png)

Adrian commented

2016-04-01 21:18:31 +02:00

Please consider that AMD won't give a damn about such issue. Maybe there is easy workaround? It looks like compute work group X dimension is read incorrectly. I'm not familiar with Cycles code to test solutions.

Thomas Dinges commented

2016-04-01 21:27:29 +02:00

Maybe there is a workaround, but such Driver issues are very difficult and time consuming to find. Time we should spend on other things. If AMD cannot get their act together, that is unfortunate for both developers and users, but that is simply not fixable from our side.

For now, I suggest to downgrade the driver and test an older one.

Maybe there is a workaround, but such Driver issues are very difficult and time consuming to find. Time we should spend on other things. If AMD cannot get their act together, that is unfortunate for both developers and users, but that is simply not fixable from our side. For now, I suggest to downgrade the driver and test an older one.

Vuk Gardašević commented

2016-04-01 21:27:44 +02:00

Added subscriber: @VukGardasevic

Vuk Gardašević commented

2016-04-01 21:27:45 +02:00

Tested the same file on Linux and Windows. Same machine, dual boot.
R7 360, X3 455 8 gig ram

Linux:
Xubuntu 15.10 Driver Packaging Version 15.201.1151-150908a-188977E
Blender Build 2683dd8

Windows 7 64-bit
Driver Packaging Version - 16.15-160307a-300321E
Blender Build 29bb10e

Windows has installed the non-WHQL 16.3 driver from 09.03. The horizontal lines are very noticable in the render preview/render on lower samples; after a while they clean up, but still can be noticed. First image is after 5 samples, the second one after 144.

Linux (Older) Driver, on the other hand, doesn't have that problem. Even on lower samples.

Tested the same file on Linux and Windows. Same machine, dual boot. R7 360, X3 455 8 gig ram Linux: Xubuntu 15.10 Driver Packaging Version 15.201.1151-150908a-188977E Blender Build 2683dd8 Windows 7 64-bit Driver Packaging Version - 16.15-160307a-300321E Blender Build 29bb10e Windows has installed the non-WHQL 16.3 driver from 09.03. The horizontal lines are very noticable in the render preview/render on lower samples; after a while they clean up, but still can be noticed. First image is after 5 samples, the second one after 144. ![bug_after_5_samples.jpg](https://archive.blender.org/developer/F300389/bug_after_5_samples.jpg) ![bug_after_144_samples.jpg](https://archive.blender.org/developer/F300391/bug_after_144_samples.jpg) Linux (Older) Driver, on the other hand, doesn't have that problem. Even on lower samples. ![test_linux.jpg](https://archive.blender.org/developer/F300393/test_linux.jpg)

Adrian commented

2016-04-01 21:42:50 +02:00

I fired a ticket to AMD support but well, I can only expect that if stars constellation is fortunate I will see the fix in next year :)

Jeffrey Engelstad commented

2016-04-02 03:55:34 +02:00

Added subscriber: @JeffreyEngelstad

Jeffrey Engelstad commented

2016-04-02 03:55:34 +02:00

Just tested on
blender-2.77-f185eff-win64
Windows 10
AMD 7970 6gb
AMD Driver 16.3.2

GPU Render no settings changed.
No artifacts in the render other then normal noise.

Just tested on blender-2.77-f185eff-win64 Windows 10 AMD 7970 6gb AMD Driver 16.3.2 GPU Render no settings changed. No artifacts in the render other then normal noise.

Adrian commented

2016-04-02 11:17:32 +02:00

In #48028#367886, @JeffreyEngelstad wrote:
Just tested on
blender-2.77-f185eff-win64
Windows 10
AMD 7970 6gb
AMD Driver 16.3.2

GPU Render no settings changed.
No artifacts in the render other then normal noise.

Are you completely sure you have GPU compute enabled? I tested exactly this driver version, on the same os and the same Blender version, and got the bug.

> In #48028#367886, @JeffreyEngelstad wrote: > Just tested on > blender-2.77-f185eff-win64 > Windows 10 > AMD 7970 6gb > AMD Driver 16.3.2 > > GPU Render no settings changed. > No artifacts in the render other then normal noise. Are you completely sure you have GPU compute enabled? I tested exactly this driver version, on the same os and the same Blender version, and got the bug.

Mauro Castaldi commented

2016-04-02 22:05:15 +02:00

Added subscriber: @MauroCastaldi

Mauro Castaldi commented

2016-04-02 22:05:15 +02:00

Same issue on

Blender 2.76b build f337fea
Blender 2.77 build 22a2853

AMD R9 390 NITRO 8 mb,
AMD Crimson driver version 16.3.2
Driver Packaging Version 16.15.2211-160321a-300865C

O/S Windows 10 64 bit

Does anyone know the latest working AMD drivers version ?

Same issue on Blender 2.76b build f337fea Blender 2.77 build 22a2853 AMD R9 390 NITRO 8 mb, AMD Crimson driver version 16.3.2 Driver Packaging Version 16.15.2211-160321a-300865C O/S Windows 10 64 bit Does anyone know the latest working AMD drivers version ?

Adrian commented

2016-04-02 22:46:02 +02:00

In #48028#367934, @MauroCastaldi wrote:
Same issue on

Blender 2.76b build f337fea
Blender 2.77 build 22a2853

AMD R9 390 NITRO 8 mb,
AMD Crimson driver version 16.3.2
Driver Packaging Version 16.15.2211-160321a-300865C

O/S Windows 10 64 bit

Does anyone know the latest working AMD drivers version ?

http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-Software-Crimson-Edition-16.1-Hotfix-Release-Notes.aspx
This is the latest version working, I use it now and it works.
Keep in mind that cleaning up after Crimson drver is PITA, be sure to uninstall it via control panel and then switch the driver in device manager to something older, so installer won't spot new driver already in place.

> In #48028#367934, @MauroCastaldi wrote: > Same issue on > > Blender 2.76b build f337fea > Blender 2.77 build 22a2853 > > AMD R9 390 NITRO 8 mb, > AMD Crimson driver version 16.3.2 > Driver Packaging Version 16.15.2211-160321a-300865C > > O/S Windows 10 64 bit > > Does anyone know the latest working AMD drivers version ? http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-Software-Crimson-Edition-16.1-Hotfix-Release-Notes.aspx This is the latest version working, I use it now and it works. Keep in mind that cleaning up after Crimson drver is PITA, be sure to uninstall it via control panel and then switch the driver in device manager to something older, so installer won't spot new driver already in place.

Jeffrey Engelstad commented

2016-04-03 00:46:21 +02:00

Adrian.

Yes I am positive I am Using GPU Render on my system.
User preferences OpenCL Device is set to (Tahiti)
and your default settings in the file you submitted has the Render settings of supported and GPU Compute.
Works fine on my system. it may be a Problem with the new AMD GPU's as I see you have the R9.

Adrian. Yes I am positive I am Using GPU Render on my system. User preferences OpenCL Device is set to (Tahiti) and your default settings in the file you submitted has the Render settings of supported and GPU Compute. Works fine on my system. it may be a Problem with the new AMD GPU's as I see you have the R9.

Mauro Castaldi commented

2016-04-03 10:47:29 +02:00

Adrian thank you, 16.1 Crimson drivers work like a charm.

Thomas Dinges commented

2016-04-03 10:54:03 +02:00

Changed status from 'Open' to: 'Archived'

Thomas Dinges closed this issue

2016-04-03 10:54:03 +02:00

Thomas Dinges self-assigned this 2016-04-03 10:54:03 +02:00

Thomas Dinges commented

2016-04-03 10:54:03 +02:00

Closing this then, as it is a driver issue, and that is simply not fixable by us.

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

GPU Compute in Cycles is broken on AMD stable drivers and Blender stable release #48028