Cycles crash on CPU denoise with old gpu driver #117112

New Issue

Thomas Dinges · 2024-01-14T16:26:14+01:00

Thomas Dinges commented

2024-01-14 16:26:14 +01:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: Radeon RX 5500 XT ATI Technologies Inc. 4.6.0 Core Profile Context 22.20.27.09.230330

Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2024-01-14 13:03, hash: 665cfbe564b9

Short description of error
Cycles rendering crashes on the denoising step

Exact steps for others to reproduce the error

Open Blender, set Cycles as render engine
Start a F12 render and wait until the render is done (or set the samples to something lower for faster render)
Alternatively enable Denoising for the viewport and start a viewport render
Blender closes

Tested with CPU rendering.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: Radeon RX 5500 XT ATI Technologies Inc. 4.6.0 Core Profile Context 22.20.27.09.230330 **Blender Version** Broken: version: 4.1.0 Alpha, branch: main, commit date: 2024-01-14 13:03, hash: `665cfbe564b9` **Short description of error** Cycles rendering crashes on the denoising step **Exact steps for others to reproduce the error** * Open Blender, set Cycles as render engine * Start a F12 render and wait until the render is done (or set the samples to something lower for faster render) * Alternatively enable Denoising for the viewport and start a viewport render * Blender closes Tested with CPU rendering.

Thomas Dinges added the

labels 2024-01-14 16:26:36 +01:00

Iliya Katushenock commented

2024-01-14 16:36:32 +01:00

Can not confirm.

Thomas Dinges commented

2024-01-14 17:12:59 +01:00

After further investigation, this was a general crash on HIP init with the old driver I had. After installing driver 23.12.1.231124 the issue is gone.

I still wonder, why HIP is initialized in denoise when rendering on the CPU. Can this be avoided?

After further investigation, this was a general crash on HIP init with the old driver I had. After installing driver `23.12.1.231124` the issue is gone. I still wonder, why HIP is initialized in denoise when rendering on the CPU. Can this be avoided?

Thomas Dinges added

and removed

labels 2024-01-14 17:13:19 +01:00

Thomas Dinges changed title from ~~Cycles crash on denoise~~ to Cycles crash on CPU denoise with old gpu driver

2024-01-14 17:13:52 +01:00

Brecht Van Lommel commented

2024-01-15 11:18:55 +01:00

@Stefan_Werner @BrianSavery @salipour, I think the way this was meant now is that GPU denoising for F12 renders is only used with GPU rendering. So if it's initializing the GPU here that indeed seems wrong.

A general crash in HIP init even if the drivers are old also does not sound good, though it's hard to say what is going on without more information like a backtrace.

@Stefan_Werner @BrianSavery @salipour, I think the way this was meant now is that GPU denoising for F12 renders is only used with GPU rendering. So if it's initializing the GPU here that indeed seems wrong. A general crash in HIP init even if the drivers are old also does not sound good, though it's hard to say what is going on without more information like a backtrace.

Thomas Dinges commented

2024-01-15 11:54:07 +01:00

I unfortunately don't have more infos, I did not get a crash.txt file, Blender just closed.
With crash on init (to be more precise), I meant selecting HIP in the user preferences.

I unfortunately don't have more infos, I did not get a crash.txt file, Blender just closed. With crash on init (to be more precise), I meant selecting `HIP` in the user preferences.

Sahar A. Kashi commented

2024-01-15 22:10:07 +01:00

If either the driver is old or non-existent, loading the driver fails (gracefully, without crashing the app) and the HIP option in the user interface will not be available.
What @ThomasDinges describes indicates that the driver is already loaded. If the mere act of selecting HIP in the user preferences causes the crash, then it is not likely related to the driver. If the crash happens when rendering starts, that could be a driver issue. However, the app still handles this case; unless the driver crashes itself and doesn't return any error to the app.
Hard to know without a repro case.

If either the driver is old or non-existent, loading the driver fails (gracefully, without crashing the app) and the HIP option in the user interface will not be available. What @ThomasDinges describes indicates that the driver is already loaded. If the mere act of selecting HIP in the user preferences causes the crash, then it is not likely related to the driver. If the crash happens when rendering starts, that could be a driver issue. However, the app still handles this case; unless the driver crashes itself and doesn't return any error to the app. Hard to know without a repro case.

Germano Cavalcante referenced this issue

2024-01-18 13:55:57 +01:00

Crashes when rendering Cycles #117229

Thomas Dinges commented

2024-01-19 11:43:42 +01:00

You could try yourself with an old driver (I had 22.20.27.09.230330). Other than that feel free to close this, since it's solved with the new driver. :)

You could try yourself with an old driver (I had `22.20.27.09.230330`). Other than that feel free to close this, since it's solved with the new driver. :)

Germano Cavalcante referenced this issue

2024-04-02 17:29:52 +02:00

Cycles: GPU Denoising breaks the UI and doesn't abort #120167

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 crash on CPU denoise with old gpu driver #117112