Cycles crashes on GPU render using OpenCL - Dual AMD WX 7100 GPUs #67954

Closed
opened 2019-07-30 21:46:50 +02:00 by Brandon Hix · 20 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.13558 Core Profile Context FireGL 26.20.11015.5009

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449

Short description of error
When I open Blender and try to render the default scene using Cycles and GPU compute I get an immediate crash.

Under Preferences > System > Cycles Render Devices > OpenCL, I have four identical lines that say, "AMD Radeon Pro WX 7100 Graphics".
If the top two are checked off then I can render without Blender crashing.
But with all four checked off or even just the bottom two checked off Blender always crashes.

Exact steps for others to reproduce the error

  1. Launch the official Blender 2.8 Windows 10 build from today, July 30, 2019
  2. In Edit > Preferences > Cycles Render Devices > OpenCL, check off all four instances of 'AMD Radeon Pro WX 7100 Graphics'.
    B-28-Prefs-System-Graphics.jpg
  3. Under render properties, select Cycles engine.
  4. Set device to GPU compute
  5. Use F12 or Render menu to render a single image
**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.13558 Core Profile Context FireGL 26.20.11015.5009 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` **Short description of error** When I open Blender and try to render the default scene using Cycles and GPU compute I get an immediate crash. Under Preferences > System > Cycles Render Devices > OpenCL, I have four identical lines that say, "AMD Radeon Pro WX 7100 Graphics". If the top two are checked off then I can render without Blender crashing. But with all four checked off or even just the bottom two checked off Blender always crashes. **Exact steps for others to reproduce the error** 1. Launch the official Blender 2.8 Windows 10 build from today, July 30, 2019 2. In Edit > Preferences > Cycles Render Devices > OpenCL, check off all four instances of 'AMD Radeon Pro WX 7100 Graphics'. ![B-28-Prefs-System-Graphics.jpg](https://archive.blender.org/developer/F7638071/B-28-Prefs-System-Graphics.jpg) 3. Under render properties, select Cycles engine. 4. Set device to GPU compute 5. Use F12 or Render menu to render a single image
Author

Added subscriber: @Acolyte

Added subscriber: @Acolyte

Added subscriber: @GavinScott

Added subscriber: @GavinScott

Do you have Crossfire enabled for the two cards? It seems like it's double-enumerating them somehow. I believe generally things will work better for rendering if Crossfire is disabled, similar to SLI on Nvidia cards. But I'm not an AMD user so I'm not as familiar with the setup there.

Do you have Crossfire enabled for the two cards? It seems like it's double-enumerating them somehow. I believe generally things will work better for rendering if Crossfire is disabled, similar to SLI on Nvidia cards. But I'm not an AMD user so I'm not as familiar with the setup there.
Author

In #67954#739935, @GavinScott wrote:
Do you have Crossfire enabled for the two cards? It seems like it's double-enumerating them somehow. I believe generally things will work better for rendering if Crossfire is disabled, similar to SLI on Nvidia cards. But I'm not an AMD user so I'm not as familiar with the setup there.

Crossfire isn't enabled, and I've attempted to update Windows 10 and the graphics driver to the latest version, and I'm still getting the same crash as long as the bottom two options are selected.
For now, I'm disabling them to continue working and rendering with my GPU, but I'm not able to compare to see if I'm getting a performance drop without the other two cards checked in the list.

For now, I'll leave them unchecked, but I think, either way, it's a bug.

It seems like I've had all these enabled since the 2.8 alpha releases and it rendered without any issues, only with the release candidates have I been seeing this problem.

> In #67954#739935, @GavinScott wrote: > Do you have Crossfire enabled for the two cards? It seems like it's double-enumerating them somehow. I believe generally things will work better for rendering if Crossfire is disabled, similar to SLI on Nvidia cards. But I'm not an AMD user so I'm not as familiar with the setup there. Crossfire isn't enabled, and I've attempted to update Windows 10 and the graphics driver to the latest version, and I'm still getting the same crash as long as the bottom two options are selected. For now, I'm disabling them to continue working and rendering with my GPU, but I'm not able to compare to see if I'm getting a performance drop without the other two cards checked in the list. For now, I'll leave them unchecked, but I think, either way, it's a bug. It seems like I've had all these enabled since the 2.8 alpha releases and it rendered without any issues, only with the release candidates have I been seeing this problem.

Does the speed of rendering approximately double between choosing only the first card and choosing the first two on the list?

Does the speed of rendering approximately double between choosing only the first card and choosing the first two on the list?
Author

Yes, so the first two in the list are behaving correctly. This gives me a workaround, but I'm still not sure why the double-enumeration is occurring.
At my earliest possible convenience, I'm switching to an NVidia card. AMD has been nothing but headaches since I first got these cards.
Real-time performance in Eevee is a breeze, but GPU rendering in Cycles always seems to have less stability and support by the BF.

@GavinScott Thanks for your help in diagnosing the problem.

Hope the double listing bug gets fixed as it definitely bricks Blender when they're all checked.

Yes, so the first two in the list are behaving correctly. This gives me a workaround, but I'm still not sure why the double-enumeration is occurring. At my earliest possible convenience, I'm switching to an NVidia card. AMD has been nothing but headaches since I first got these cards. Real-time performance in Eevee is a breeze, but GPU rendering in Cycles always seems to have less stability and support by the BF. @GavinScott Thanks for your help in diagnosing the problem. Hope the double listing bug gets fixed as it definitely bricks Blender when they're all checked.

I searched around but could not find other examples of this sort of issue either with Blender or with OpenCL apps in general, so I don't think it's really likely to be a Blender bug but some obscure issue in your particular system. As long as it's otherwise working I'm not sure I would spend too much time messing with it, but you could try completely removing all AMD/ATI video related drivers and stuff and re-installing the latest. I will keep my eyes out for anyone else seeing the same issue though.

I searched around but could not find other examples of this sort of issue either with Blender or with OpenCL apps in general, so I don't think it's really likely to be a Blender bug but some obscure issue in your particular system. As long as it's otherwise working I'm not sure I would spend too much time messing with it, but you could try completely removing all AMD/ATI video related drivers and stuff and re-installing the latest. I will keep my eyes out for anyone else seeing the same issue though.
Member

Added subscriber: @jesterking

Added subscriber: @jesterking
Member

IIRC the double enumeration occurs because of two different OpenCL platforms being available - one from AMD, one from Intel. I have found the Intel platform for OpenCL to be quite unreliable - I think I've blacklisted it for Cycles in Rhino so that one can not select it.

FWIW I run on a machine that has one WX 9100 in it (and a GTX 1060 and a GTX 760, but that is besides the point ;) )

FWIW2: I see only one WX 9100 in the OpenCL section.

IIRC the double enumeration occurs because of two different OpenCL platforms being available - one from AMD, one from Intel. I have found the Intel platform for OpenCL to be quite unreliable - I think I've blacklisted it for Cycles in Rhino so that one can not select it. FWIW I run on a machine that has one WX 9100 in it (and a GTX 1060 and a GTX 760, but that is besides the point ;) ) FWIW2: I see only one WX 9100 in the OpenCL section.
Member

@Acolyte did you by any chance ever set any of the Cycles environment variables. Maybe double-check your user and system environment variables, and remove any that says CYCLES in it...

@Acolyte did you by any chance ever set any of the Cycles environment variables. Maybe double-check your user and system environment variables, and remove any that says CYCLES in it...
Author

In #67954#741768, @jesterking wrote:
IIRC the double enumeration occurs because of two different OpenCL platforms being available - one from AMD, one from Intel. I have found the Intel platform for OpenCL to be quite unreliable - I think I've blacklisted it for Cycles in Rhino so that one can not select it.

FWIW I run on a machine that has one WX 9100 in it (and a GTX 1060 and a GTX 760, but that is besides the point ;) )

FWIW2: I see only one WX 9100 in the OpenCL section.

Hey Nathan, thanks for the explanation, this helps me understand a bit more about what's going on behind the scenes. The WX 7100s haven't been bad cards, but I think I'll have less overall issues if I just get a card that has CUDA, so that's where I'm headed next I think.

In #67954#741775, @jesterking wrote:
@Acolyte did you by any chance ever set any of the Cycles environment variables. Maybe double-check your user and system environment variables, and remove any that says CYCLES in it...

There are no environment variables related to Blender or Cycles listed in my system, but I appreciate the suggestion.
For now, I'll just proceed with the top two checked in the list.

@jesterking Is there any chance this is still a bug and can be fixed so that it doesn't cause an instant crash when rendering with Cycles? Just thinking for other OpenCL users who might run into this issue in the future.

> In #67954#741768, @jesterking wrote: > IIRC the double enumeration occurs because of two different OpenCL platforms being available - one from AMD, one from Intel. I have found the Intel platform for OpenCL to be quite unreliable - I think I've blacklisted it for Cycles in Rhino so that one can not select it. > > FWIW I run on a machine that has one WX 9100 in it (and a GTX 1060 and a GTX 760, but that is besides the point ;) ) > > FWIW2: I see only one WX 9100 in the OpenCL section. Hey Nathan, thanks for the explanation, this helps me understand a bit more about what's going on behind the scenes. The WX 7100s haven't been bad cards, but I think I'll have less overall issues if I just get a card that has CUDA, so that's where I'm headed next I think. > In #67954#741775, @jesterking wrote: > @Acolyte did you by any chance ever set any of the Cycles environment variables. Maybe double-check your user and system environment variables, and remove any that says CYCLES in it... There are no environment variables related to Blender or Cycles listed in my system, but I appreciate the suggestion. For now, I'll just proceed with the top two checked in the list. @jesterking Is there any chance this is still a bug and can be fixed so that it doesn't cause an instant crash when rendering with Cycles? Just thinking for other OpenCL users who might run into this issue in the future.
Member

@Acolyte it could be a bug still yes. We'd need to be able to repro this though.

With the one WX9100 in I don't see problems. Running Cycles on it works just fine in the 2.80 official release.

I'll dig a bit more into this on the code side. Maybe I can get sometime this month access to a machine with two AMD GPUs.

@Acolyte it could be a bug still yes. We'd need to be able to repro this though. With the one WX9100 in I don't see problems. Running Cycles on it works just fine in the 2.80 official release. I'll dig a bit more into this on the code side. Maybe I can get sometime this month access to a machine with two AMD GPUs.
Nathan Letwory self-assigned this 2019-08-02 00:25:56 +02:00
Nathan Letwory removed their assignment 2019-09-12 17:09:50 +02:00
Jeroen Bakker was assigned by Nathan Letwory 2019-09-12 17:09:50 +02:00
Member

@Jeroen-Bakker I remembered having dealt with something like this when I had the Intel CPU OpenCL driver installed as well - it has been a few years since I tested that, and opted to remove that driver, since it caused a whole lot of instabilities on my machine. Perhaps something to keep in mind while investigating.

@Jeroen-Bakker I remembered having dealt with something like this when I had the Intel CPU OpenCL driver installed as well - it has been a few years since I tested that, and opted to remove that driver, since it caused a whole lot of instabilities on my machine. Perhaps something to keep in mind while investigating.
Jeroen Bakker removed their assignment 2019-12-04 07:59:06 +01:00
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker

Added subscriber: @rjg

Added subscriber: @rjg

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

@Acolyte In case this is still an issue on your system with current graphics drivers, please download the most recent daily build of Blender 2.92 and extract the achive. Open the directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

2019_12_04_upload_icon_developer_blender_org.png

Have you check if the Intel CPU OpenCL driver may be causing issues as @jesterking has suggested?

@Acolyte In case this is still an issue on your system with current graphics drivers, please download the most recent daily build of [Blender 2.92 ](https://builder.blender.org/download/) and extract the achive. Open the directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer). ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png) Have you check if the Intel CPU OpenCL driver may be causing issues as @jesterking has suggested?

@Acolyte I know this ticket has been inactive for quite a while, but could you please check and provide the requested information?

@Acolyte I know this ticket has been inactive for quite a while, but could you please check and provide the requested information?

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#67954
No description provided.