Cycles viewport rendering stuck at Path Tracing Sample 1/32 with high GPU usage #79090

New Issue

Francisco Medina · 2020-07-19T21:47:16+02:00

Francisco Medina commented

2020-07-19 21:47:16 +02:00

System Information
Operating system: Ubuntu Mate 18.04.4 LTS and Windows 10 (1909) x64
Graphics card: AMD Radeon RX 570 4GB

Blender Version
Broken: 2.82a, 2.83.2 LTS, 2.83.3 LTS, 2.90.0-b8601b64c7cb, 2.91.0-a51048a5d335, 2.90.0 Stable

Short description of error
Viewport GPU rendering on Cycles stuck at Path tracing sample 1/32 with high GPU usage when applying Volume Absorption properties in a Material over any Object

Newer Blender versions (2.90+) or versions previous to 2.83 throws an error "Split kernel error: failed to load kernel_path_init"

Exact steps for others to reproduce the error

Load attached .blend file in 2.83.2 LTS, 2.90.0 or the latest beta
cube_with_water.blend
If not set, set the rendering engine to Cycles and select GPU Compute
Select the "Cube_Content" object
Go to materials tab, and in Volume section, select "Volume Absorption"
Change to Viewport rendering

Additional Notes

This is only happening on Viewport rendering only, in the final render (when hitting F12) it works fine
CPU Rendering in viewport works fine
Viewport shading works fine
Seems like every other Volume type is affected by this (Volume Scattering, Velvet BSDF, Emission, etc)
Trying to apply any BSDF Volume, freezes the computer
Some versions like 2.82a and latest alpha at this edition date makes high CPU and RAM usage freezing the computer.
2.90.0 causes high CPU usage only.

My system-info.txt in Linux (2.83.2 LTS):
system-info.txt

My system-info.txt in Windows (2.83.3 LTS):
system-info-win.txt

**System Information** Operating system: Ubuntu Mate 18.04.4 LTS and Windows 10 (1909) x64 Graphics card: AMD Radeon RX 570 4GB **Blender Version** Broken: 2.82a, 2.83.2 LTS, 2.83.3 LTS, 2.90.0-b8601b64c7cb, 2.91.0-a51048a5d335, 2.90.0 Stable **Short description of error** Viewport GPU rendering on Cycles stuck at Path tracing sample 1/32 with high GPU usage when applying Volume Absorption properties in a Material over any Object Newer Blender versions (2.90+) or versions previous to 2.83 throws an error "Split kernel error: failed to load kernel_path_init" **Exact steps for others to reproduce the error** 1) Load attached .blend file in 2.83.2 LTS, 2.90.0 or the latest beta [cube_with_water.blend](https://archive.blender.org/developer/F8707215/cube_with_water.blend) 2) If not set, set the rendering engine to Cycles and select GPU Compute 3) Select the "Cube_Content" object 4) Go to materials tab, and in Volume section, select "Volume Absorption" 5) Change to Viewport rendering **Additional Notes** - This is only happening on Viewport rendering only, in the final render (when hitting F12) it works fine - CPU Rendering in viewport works fine - Viewport shading works fine - Seems like every other Volume type is affected by this (Volume Scattering, Velvet BSDF, Emission, etc) - Trying to apply any BSDF Volume, freezes the computer - Some versions like 2.82a and latest alpha at this edition date makes high CPU and RAM usage freezing the computer. - 2.90.0 causes high CPU usage only. My system-info.txt in Linux (2.83.2 LTS): [system-info.txt](https://archive.blender.org/developer/F8707268/system-info.txt) My system-info.txt in Windows (2.83.3 LTS): [system-info-win.txt](https://archive.blender.org/developer/F8715121/system-info-win.txt)

Francisco Medina commented

2020-07-19 21:47:16 +02:00

Added subscriber: @PANCHO7532

blender-admin commented

2020-07-19 21:47:16 +02:00

#81725 was marked as duplicate of this issue

blender-admin commented

2020-07-19 21:47:16 +02:00

#81175 was marked as duplicate of this issue

blender-admin commented

2020-07-19 21:47:16 +02:00

#79798 was marked as duplicate of this issue

Richard Antalik commented

2020-07-23 06:03:26 +02:00

Added subscriber: @iss

Richard Antalik commented

2020-07-23 06:03:26 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Richard Antalik commented

2020-07-23 06:03:26 +02:00

I can confirm this with
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61

Viewport render actually starts rendering afrer a few minutes but it quickly breaks my system requiring reboot.

I can confirm this with Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61 Viewport render actually starts rendering afrer a few minutes but it quickly breaks my system requiring reboot.

Richard Antalik commented

2020-07-23 06:09:18 +02:00

I have no problems with Blender 2.82a. @PANCHO7532 can you test this version?

Francisco Medina commented

2020-07-23 08:06:17 +02:00

@iss

2.82a is still broken, it froze my computer due to high CPU and RAM usage. Both in Windows and Linux, GPU doesn't seems to be affected on this one.

Also i tried the new LTS release (2.83.3 LTS) on both Windows and Linux and is still broken.

Just tried the new alpha (2.91.0-a51048a5d335) in Windows and throws the following:

I haven't tried yet the alpha version in Linux, i'm gonna test it there in the following hours and update with results

@iss 2.82a is still broken, it froze my computer due to high CPU and RAM usage. Both in Windows and Linux, GPU doesn't seems to be affected on this one. Also i tried the new LTS release (2.83.3 LTS) on both Windows and Linux and is still broken. Just tried the new alpha (2.91.0-a51048a5d335) in Windows and throws the following: ![Captura.PNG](https://archive.blender.org/developer/F8715107/Captura.PNG) I haven't tried yet the alpha version in Linux, i'm gonna test it there in the following hours and update with results

Richard Antalik commented

2020-07-23 08:36:17 +02:00

I have updated driver on windows to Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.7.2 27.20.2001.9003
PC doesn't crash anymore, but rendering is now stuck on sample 1.

I have updated driver on windows to `Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.7.2 27.20.2001.9003` PC doesn't crash anymore, but rendering is now stuck on sample 1.

Raman Monorath commented

2020-08-13 20:40:18 +02:00

Added subscriber: @ramanamono

Raman Monorath commented

2020-08-13 20:40:18 +02:00

I'm on windows 10 Pro version 2004, Ryzen 5 1600 (Original AE version), XFX RX 580 4GB radeon 20.71 driver
I have this issue too with Blender 2.83.4 - LTS
In 2.82 it render a clay, but if you click on anything else it freezes blender.

I'm on windows 10 Pro version 2004, Ryzen 5 1600 (Original AE version), XFX RX 580 4GB radeon 20.71 driver I have this issue too with Blender 2.83.4 - LTS In 2.82 it render a clay, but if you click on anything else it freezes blender.

Richard Antalik commented

2020-08-18 03:59:43 +02:00

Added subscriber: @iamcapmurica

Richard Antalik commented

2020-09-02 00:13:49 +02:00

Can you try new GPU drivers? today I updated to 2.8.3 version, and I don't have this problem anymore. Also other crashy issues are gone.

Francisco Medina commented

2020-09-02 23:31:40 +02:00

In #79090#1006991, @iss wrote:
Can you try new GPU drivers? today I updated to 2.8.3 version, and I don't have this problem anymore. Also other crashy issues are gone.

Just updated my drivers from 20.20 to 20.30 in Linux, it's still the same, both 2.83 and 2.90, the split kernel error is gone, but it's still stuck at path tracing 1/xx with high GPU usage

Haven't tried updating on Windows yet, as at the moment i have limited data connection, so probably tomorrow i will give it a try and i'll update this

> In #79090#1006991, @iss wrote: > Can you try new GPU drivers? today I updated to 2.8.3 version, and I don't have this problem anymore. Also other crashy issues are gone. Just updated my drivers from 20.20 to 20.30 in Linux, it's still the same, both 2.83 and 2.90, the split kernel error is gone, but it's still stuck at path tracing 1/xx with high GPU usage Haven't tried updating on Windows yet, as at the moment i have limited data connection, so probably tomorrow i will give it a try and i'll update this

Francisco Medina commented

2020-09-06 09:49:21 +02:00

Ok, so, i updated my drivers to latest available (20.8.3) in Windows, both in Blender 2.83 and 2.90 and it's still the same

2.90 test with split kernel error

2.83 test with an "cancel" status while eating an really big amount of RAM

Ok, so, i updated my drivers to latest available (20.8.3) in Windows, both in Blender 2.83 and 2.90 and it's still the same 2.90 test with split kernel error ![1.png](https://archive.blender.org/developer/F8846822/1.png) 2.83 test with an "cancel" status while eating an really big amount of RAM ![2.png](https://archive.blender.org/developer/F8846824/2.png)

Richard Antalik commented

2020-10-15 23:39:14 +02:00

Added subscriber: @EnderProtix

Richard Antalik commented

2020-10-15 23:39:24 +02:00

Added subscriber: @RTamaasP

Tamás Péter Radványi commented

2020-10-16 07:05:54 +02:00

So yeah, I have same problem with making the guru's dounut tutorial, at the point where we have to add volume to my coffee. Render stops at 1/32 samples with MSI Armor RX580 8G OC Edition graphics card, so I've tried to fix that in many-many-many different versions of drivers and blenders.

With Blender 2.82, 2.83, 2.90.1 I have sucessfully made a wiewport render with driver 20.4.2 and 20.5.2 but with these combinations, more hundred weird pixels appeared in the wiewport, so it became more and more noisy while was rendered in higher and higher samples. Withever, then weird stripes appeared too in 2 or 3 groups in the wiewport window's left bottom to the screen's mid. And this affected the final render too, causing the same problems in it. But in the final render, these stripes appear in the whole picture and the denoising makes horribly wrong job. example (final render) picture for this is _D.png.

But these happened without enabling the volumed object too, wich means that the rx580 gpu with these drivers, simply uncompatible with any Blender.

So yeah, I have same problem with making the guru's dounut tutorial, at the point where we have to add volume to my coffee. Render stops at 1/32 samples with MSI Armor RX580 8G OC Edition graphics card, so I've tried to fix that in many-many-many different versions of drivers and blenders. # With Blender 2.82, 2.83, 2.90.1 I have sucessfully made a wiewport render with driver 20.4.2 and 20.5.2 but with these combinations, more hundred weird pixels appeared in the wiewport, so it became more and more noisy while was rendered in higher and higher samples. Withever, then weird stripes appeared too in 2 or 3 groups in the wiewport window's left bottom to the screen's mid. And this affected the final render too, causing the same problems in it. But in the final render, these stripes appear in the whole picture and the denoising makes horribly wrong job. example (final render) picture for this is _D.png.![_D.png](https://archive.blender.org/developer/F8997755/_D.png) But these happened without enabling the volumed object too, wich means that the rx580 gpu with these drivers, simply uncompatible with any Blender.

Tamás Péter Radványi commented

2020-10-16 07:14:50 +02:00

I've tried with all compatible drivers above these versions, like
20.7.1
20.7.2
20.8.1
20.8.2
20.9.1
20.9.2
No more weird, wrong noisy pictures without volumed object too, BUT then I had arrived back to the above mentioned problem, where I had started from: wiewport render with a volumed object stopped at 1/32, no matter wich of these drivers I used, neither wich blender from 2.82, 2.83 or 2.90.1

I've tried with all compatible drivers above these versions, like 20.7.1 20.7.2 20.8.1 20.8.2 20.9.1 20.9.2 No more weird, wrong noisy pictures without volumed object too, BUT then I had arrived back to the above mentioned problem, where I had started from: wiewport render with a volumed object stopped at 1/32, no matter wich of these drivers I used, neither wich blender from 2.82, 2.83 or 2.90.1

Brill Jasper Rayel commented

2020-11-16 11:10:58 +01:00

Added subscriber: @BlenderMacUser

Brill Jasper Rayel commented

2020-11-16 11:10:58 +01:00

I am doing the same. Froze rendering at 1/32 Path Tracing Sample. Graphics is 570RX

I tried prorender but i dont know how to make my glass water into coffee.

In #79090#1035417, @RTamaasP wrote:
So yeah, I have same problem with making the guru's dounut tutorial, at the point where we have to add volume to my coffee. Render stops at 1/32 samples with MSI Armor RX580 8G OC Edition graphics card, so I've tried to fix that in many-many-many different versions of drivers and blenders.

With Blender 2.82, 2.83, 2.90.1 I have sucessfully made a wiewport render with driver 20.4.2 and 20.5.2 but with these combinations, more hundred weird pixels appeared in the wiewport, so it became more and more noisy while was rendered in higher and higher samples. Withever, then weird stripes appeared too in 2 or 3 groups in the wiewport window's left bottom to the screen's mid. And this affected the final render too, causing the same problems in it. But in the final render, these stripes appear in the whole picture and the denoising makes horribly wrong job. example (final render) picture for this is _D.png.

But these happened without enabling the volumed object too, wich means that the rx580 gpu with these drivers, simply uncompatible with any Blender.

I am doing the same. Froze rendering at 1/32 Path Tracing Sample. Graphics is 570RX I tried prorender but i dont know how to make my glass water into coffee. > In #79090#1035417, @RTamaasP wrote: > So yeah, I have same problem with making the guru's dounut tutorial, at the point where we have to add volume to my coffee. Render stops at 1/32 samples with MSI Armor RX580 8G OC Edition graphics card, so I've tried to fix that in many-many-many different versions of drivers and blenders. > > > # With Blender 2.82, 2.83, 2.90.1 I have sucessfully made a wiewport render with driver 20.4.2 and 20.5.2 but with these combinations, more hundred weird pixels appeared in the wiewport, so it became more and more noisy while was rendered in higher and higher samples. Withever, then weird stripes appeared too in 2 or 3 groups in the wiewport window's left bottom to the screen's mid. And this affected the final render too, causing the same problems in it. But in the final render, these stripes appear in the whole picture and the denoising makes horribly wrong job. example (final render) picture for this is _D.png.![_D.png](https://archive.blender.org/developer/F8997755/_D.png) > But these happened without enabling the volumed object too, wich means that the rx580 gpu with these drivers, simply uncompatible with any Blender.

Richard Antalik commented

2020-11-25 18:10:39 +01:00

I am going over old reports and found duplicate that is older so I will merge this.

Richard Antalik commented

2020-11-25 18:11:06 +01:00

Closed as duplicate of #71258

Richard Antalik closed this issue

2020-11-25 18:11:06 +01:00

R Singer commented

2021-01-05 21:31:22 +01:00

Added subscriber: @eclay104

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

Cycles viewport rendering stuck at Path Tracing Sample 1/32 with high GPU usage #79090