Crash during cycles GPU rendering in viewport
#75319
Closed
opened 3 years ago by sebsoto
·
268 comments
No Branch/Tag Specified
main
temp-sculpt-dyntopo
refactor-mesh-face-generic
blender-v3.3-release
refactor-mesh-corners-generic
refactor-mesh-sharp-face-generic
gpencil-new-data-proposal
overlay-next
temp-sculpt-roll-mapping
sculpt-dev
tmp-volume-matrix-api-update
tmp-eevee-shadow-commit-mp
universal-scene-description
cycles_path_guiding
temp-vulkan-descriptor-sets
tmp-eevee-shadow-commit
temp-angavrilov
asset-shelf
brush-assets-project
tmp-workbench-rewrite2
temp-T101739-fix-seam-bleeding-non-manifold
tmp-mak-012623
temp-bundled-assets
asset-lite-greasepencil
temp-pbvh-split
temp-pbvh-texpaint-automasking
microfacet_hair
tmp-worbench-rewrite2-optimizations
temp-offset-array-ref
blender-v2.93-release
blender-projects-basics
temp-pbvh-seam-texturing-tweaks
temp-nodes-group-declarations
refactor-mesh-sharp-edge-generic
temp-asset-library-all
refactor-mesh-uv-map-generic
refactor-mesh-position-generic
temp-T102440
temp-rbf-pose-blender
geometry-nodes-tetrahedralization
nodes-matrix-types
temp-xr-painting
blender-v3.4-release
geometry-nodes-simulation
bli-matrix-template
temp-linux-35x-libs
refactor-mesh-corner-normals-lazy
temp-py-gpubatch-draw-advanced
xr-dev
temp-vulkan-shader
bevelv2
soc-2022-soft-bodies
arcpatch-D16436
tmp-dynamic-usd
temp-image-engine
tmp-vfx-platform-2023
soc-2022-many-lights-sampling
tracking_tools
nla-scale-fix
principled-v2
temp-ui-cpp
temp-ghost-vulkan
tmp-libs-2.93-lts
temp-T97352-3d-texturing-seam-bleeding-b2
temp-xr-virtual-camera-experiment
temp-vse-retiming-tool
gpencil-next
temp-sculpt-brush-channel
asset-browser-grid-view
temp-asset-representation
temp-gpencil-automask
tmp_libs_34
temp-T101905-gpu-backend-argument
node-add-asset-menu
temp-collection-objects-link-multiple
temp-texture-painting-gpu
tmp-workbench-perf-experiment
tmp_usd_import_unbound_mtls
tmp-drw-split-matrix
temp-sculpt-normals-masking
temp-sculpt-cavity-mask
temp-pbvh-vbos
tmp-usd-alab-v2-T100452
refactor-mesh-selection-generic
temp-T96708-brush-texture-refactoring
temp-chunk-list
feature-imformat
temp-geometry-nodes-evaluator-refactor
refactor-mesh-bevel-weight-generic
temp-chunked-list
temp-outliner-new-element-storage
refactor-mesh-remove-pointers
soc-2022-text-usability
refactor-mesh-material-index-generic
drw-manager-next
refactor-mesh-hide-generic
blender-v3.2-release
sculpt_curve_collisions
temp-anim-editors-redo-panel-D14960-D14977
retopo_transform
temp-libepoxy
temp-T99046-platform-reference-images
geometry-nodes-rigid-body-integration
file-browser-grid-view
temp-legacy-mesh-format-option
arcpatch-D14645
soc-2022-waveform-drawing
temp-T95933-object-mode-curve-selection
temp-deform-curves-on-surface
cycles_oneapi
temp-viewport-compositor-merge
temp-texpaint-automasking
temp-deform-curves-with-surface
asset-greasepencil
temp-T99046-render-test-increase-fail-threshold
temp-T98708-gpu-conservative-depth
lineart-shadow
temp-lineart-contained
cleanup-id-override-const
temp-T98375-share-gpu-textures
wintab
temp-T97352-3d-texturing-seam-bleeding
temp-T97905-compositor-meta-data
lineart-cas-2
temp-T97272
temp-T97907-compositor-meta-data
temp-T96952
tmp-usd-mak-c87f6242
temp-outliner-library-override-hierarchy
lineart-object-load
tmp-eevee-next-merge
draw-deferred-compilation-experiment
soc-2021-porting-modifiers-to-nodes-remesh-voxel
blender-v2.83-release
tmp_lib_update_32
temp-mesh-cpp
temp-viewport-compositor-compiler
temp-T96710-pbvh-pixels
tmp-new-gpu-codegen
devirtualizer
temp-T96709-painting-target
temp-collection-assets
temp-lineart-embree
temp-multi-function-eval-varray
temp-sculpt-colors
soc-2021-curves
blender-v3.1-release
temp-vertex-paint
temp-vse-channels-edge-panning
eevee-rewrite
temp-library-overrides-outliner
cycles_hydra
temp-3d-texturing-brush-b
temp-abc-features
tmp-transform-navigate
temp-image-buffer-rasterizer
soc-2021-porting-modifiers-to-nodes-remesh-blocks
temp-3d-texture-brush-prototype
temp-fix-normals-custom-data
viewport-compositor
bli-math-basic-types
soc-2021-simulation-display
greasepencil-object
temp-license-header-spdx
KTX_support
gsoc-2021-porting-modifiers-to-nodes-solidify
2d
gltf_vtree
soc-2021-porting-modifiers-to-nodes-decimate
temp-T95279-remap-referenced-data
temp-gpu-image-engine
tmp-eevee-rewrite-compilation-error
draw-viewport-data
temp-T94900-b
temp-T94900-gpu-viewport-default-layers
temp-T94185-id-remapper-ui
tmp-workbench-shader-create-infos
blender-v3.0-release
temp-geometry-nodes-extrude-mesh
tmp-T95052
tmp-gpu-polyline-shaders
tmp-gpu-shader-descriptor-2
temp-usd-prev-export2
tmp-core-id-remap-test-cases
temp-vert-normals-cleanup
temp-move-geometry-to-cpp
tmp-vector-template
drw-gpu-wrapper
temp-geometry-nodes-extrude-and-scale
temp-scale-elements-node-test
temp-usd-udim-import
temp-copy-on-write
temp-T94185-id_remapping-experiment-a
temp-llvm-testing
nurbs-opencascade
temp-usd-preview-surf-export
soc-2021-uv-edge-select-support
T93558
temp-gpu-texture-partial-updates
gpu-shader-descriptor
temp-geometry-nodes-text
tmp-vulkan
temp-T90535-usd-alab-material-import
node-tree-update-refactor
temp-sample-sound-node
temp-interface-region-search-cpp
temp-enum-socket
temp-link-portals
temp-unity-build-test
geometry-nodes-level-set-nodes
temp-virtual-array-value-type
soc-2020-io-performance
studio-sprite-fright
temp-cycles-source-reorganize
asset-browser-snap-dragging
temp-python-zstandard
soc-2021-porting-modifiers-to-nodes-merge-by-distance
temp-compositor-cleanups
temp-eevee-gpencil-rewrite
temp-vse-handles
temp-ui-tweaks
xr-controller-support
temp-node-common-cpp
temp-varray-get-set-multiple
soc-2021-uv-editor-improvements
temp-geometry-nodes-output-attributes
soc-2021-knife-tools
temp_test_sc_keymap
cycles-x
temp-field-visualization
soc-2021-curve-fillet
temp_bmesh_multires
temp-cocoa-scroll-acceleration-fix
temp-socket-decl-refactor
fluid-mantaflow-gpu
soc-2021-vse-strip-thumbnails
temp-noise-nodes-cpp
temp-compositor-canvas
T90952
temp-parallel-multi-function
temp-geometry-nodes-fields
grab_walk_fix
soc-2021-adaptive-cloth
temp-geometry-nodes-fields--fields-jacques
temp-cpp-ghc-filesystem
temp-geometry-nodes-fields--fields
temp-geometry-nodes-fields--anonymous-attributes
refactor-idprop-ui-data
compositor-full-frame
temp-runtime-node-def
temp-geometry-nodes-fields-prototype-visualization
temp-geometry-nodes-fields-prototype
temp-multi-function-procedure
soc-2021-porting-modifiers-to-nodes_all
cycles_texture_cache
experimental-build
cycles_procedural_api
soc-2021-porting-modifiers-to-nodes-extrude-and-move
soc-2021-porting-modifiers-to-nodes-extrude
temp-geometry-nodes-expandable-geometry-socket-prototype
fluid-mantaflow-2d
windows_make_docpy
usd-importer-T81257-merge
nodes-update-readonly-tag
geometry-nodes-closest-points
tmp-buildbot-gcc-10
soc-2021-geometry-nodes-regression-test
node-group-single-socket-nodes
curve-nodes-modifier
temp-geometry-nodes-curve-sample
geometry-nodes-unnamed-attributes
temp-nodes-intersect-alt-key
tmp_arcpath-D11868
refactor-vertex-group-names
temp-gpencil-bezier-stroke-type
temp-gpu-uniform-builtin-structs
wintab_fallback_walknav
temp-socket-inspection
temp-long-link-dimming
fixed_width_integers
lineart-bvh
temp-gpencil-camera-reproject
temp-gpu-push-constants
temp-attribute-processor
temp-cpp-type-cleanup
temp-geometry-nodes-curve-deform-node
wintab-logging
fix-tablet-walk
geometry-nodes-raycast
temp-spreadsheet-row-filter
lineart-fn-cached
temp-compact-node-prototype
asset-browser
geometry-nodes-curve-to-points-node
node-editor-edge-pan
eevee-gpencil
asset-system-filelist
temp-geometry-nodes-viewer-node
lineart-fn-thread-loading
tmp-buildbot-cleanup
temp-gpencil-masking
temp-ffmpeg-4.4
temp-attributes-panel
profiler-editor
FixT87160_DSE_Channel_Selection
temp-interface-cpp
geometry-nodes-curve-support
info-editor-cpp
temp-attribute-transfer-node
virtual-array-attributes
temp-pose-slide-D9054
spreadsheet-active-node
ui-asset-view-template
temp-node-tree-pages-prototype
override-outliner-view
temp-geometry-nodes-processor-prototype
temp-any-instead-of-variant
temp-unreachable-abort
temp-spreadsheet-instances
temp-geometry-nodes-instances-api-v2
temp-geometry-nodes-instances-attributes
geometry-nodes-mesh-primitives
temp-asset-tools-prototype
temp-geometry-nodes-mesh-primitive-line
lanpr-under-gp
temp_D10504-2_nla_keyframe_remap_upper_strips
blender-v2.92-release
usd-importer-T81257
temp-spreadsheet-editor-python-prototyping
temp-spreadsheet-editor
override-refactor-tmp-2
temp-derived-node-tree-refactor
T85799
tracking_scopes
temp-icons-fixes
temp_D10504_nla_keyframe_remap_upper_strips
temp-weight_mirror
temp_T76472_graph_editor_fcurve_extrapolation
eevee-closure-lib-cleanup
eevee-dof-refactor
eevee-probe-roughness-fix
eevee-ggx-lut-fix
df0bce3f7d0
temp-geometry-nodes-instances-api
tmp-ocio-v2
temp-nodes-redesign
tracking_proportional_editing_v2
blender-v2.91-release
temp-uv-face-select-no-thresh-when-inside
temp-D10103-nla_support_strip_overlap_during_transform
fracture_modifier
temp-point-distribution-refactor-experiment
temp-experimental-cpp-math-refactor
vfx-clip-ui-update
tmp-T82230-nla_remove_hold_reset_behavior
temp-D8687-directly_select_fcurves
geometry-nodes
soc-2020-testing-frameworks
geometry-nodes-point-separate-node
temp-nla-strip-alignment
temp-atomics-int16
geometry-nodes-deduplicate-float-math
asset-metadata
geometry-nodes-active-modifier-drawing
attribute-accessor
geometry-nodes-attribute-nodes
temp-T82588-box-select-invisible-keys
greasepencil-edit-curve
codesign_error_tracker
outliner-cpp-refactor
temp-fix-headerless-panels-switch-windows
temp-gpencil-fading-modifier
temp-D8915-copy-rotation-remove-sheer
geometry-nodes-boolean-node
temp-T81874-box-select-active-keyframe
geometry-nodes-transform-node
temp-trimesh-sculpt
geometry-tree-evaluation
fcurve-modifier-panels
temp-fcurve-key-insert-follow-curve
temp-fcurve-active-keyframe-D7737
mesh-to-volume-modifier
blender-v2.90-release
soc-2020-fluid-tools
property-search-ui-v2
tmp-T80603
soc-2020-greasepencil-curve
tmp-gldebuglayer
tmp-gltexture
soc-2020-custom-menus
active-fcurve-keyframe
soc-2020-soft-body
newboolean
fail-on-memleak
soc-2020-outliner
soc-2020-production-ready-light-tree-2
soc-2020-info-editor
property-search-ui
temp-ui-button-type-refactor
soc-2020-production-ready-light-tree
particle-solver-dev
tmp-gpu-context-isolation
soc-2020-xr-input
temp-remesh-octree
mac_arm64
tmp-eevee-glsl-cleanup
tmp-pointcloud-render
buildbot-lts
asset-engine--archived
asset-uuid--archived
eevee-motionblur-object
modifier-panels-ui
temp-cycles-tbb
wm-drag-drop-rewrite
temp-lanpr-review
gsoc-2018-many-light-sampling
tmp-eevee-material-refactor
tmp-widget-opti
tmp-texture-sampler
xr-world-navigation
blender-v2.82-release
node-tree-ref
simulation-access-modifier
blenloader-decentralization
temp-test-point-cloud-simulation-depsgraph-integration
functions
builtin-simulation-nodes
performance-test
obj-import-experiments
soc-2019-openxr
vr_scene_inspection
blenloader-api
tmp-workbench-rewrite
id-ensure-unique-memory-address
simulation-tree
greasepencil-refactor
draw-colormanagement
temp-gizmo-decoupled-redraws
fluid-mantaflow
blender-v2.81-release
tmp-overlay-engine
soc-2019-bevel-profiles
temp-npr-gpencil-modifiers
soc-2019-npr
temp-gpencil-drw-engine
soc-2019-embree-gpu
temp-npr-smooth-contour
temp-lanpr-staging
filebrowser_redesign
tmp-eevee-shadowmap-refactor
vamr-openxr-module
sculpt-mode-features
soc-2019-adaptive-cloth
tmp-drw-callbatching
soc-2019-outliner
soc-2019-cycles-procedural
temp-D5423-update
temp-vr-draw-thread
blender-v2.80-release
tmp-batch-cache-cleanup
soc-2019-fast-io
temp-toolsystem-multiwindow
blender2.7
collada
soc-2018-npr
temp-keymap-industry-compat
temp-fracture-modifier-2.8
temp-dna-rename
userpref_redesign
hair_object
motion_curve_fix
collada2.8
cycles_embree
interactive_physics
temp-ui-layout-2.8
cloth-improvements
soc-2018-cycles-volumes
hair_guides_grooming
hair_guides
benchmark
soc-2018-bevel
soc-2018-hair-shader-fixes
temp-udim-images
soc-2018-hair-shader
temp-volume-object
cycles_cryptomatte
temp-eeveelightcache
temp-tab_drag_drop
temp-keymap-save
temp-dynamic-overrides
fracture_modifier-master
ui_layout_gridflow
temp-keymap-changes
tmp-CollectionsAnim
tmp-b28-motionpath-drawing
uv_unwrapping_slim_algorithm
blender-v2.79b-release
tmp-COW_InsertKeyframe_Fix
temp-unified-collections
temp-modifier-rm-cddm
tmp-TimelineHeaderButtonsStretching
blender2.8-workbench
soc-2017-normal-tools
cycles_bvh8
blender-v2.79a-release
temp-scene-obedit-remove
temp-workspace-object-mode-removal
blender-v2.79-release
soc-2017-sculpting_brush
split-kernel-faster-building
id_override_static
openvdb
custom-manipulators
soc-2016-uv_tools
soc-2016-pbvh-painting
soc-2017-vertex_paint
soc-2017-sculpting_improvements
soc-2017-package_manager
strand_editmode
smooth-fcurves
id_copy_refactor
gsoc2016-improved_extrusion
temp-ssr
temp-cycles-opencl-staging
temp-cycles-denoising
ge_2df_textures
HMD_viewport
soc-2016-multiview
transform-manipulators
datablock_idprops
cycles_disney_brdf
temp_cycles_split_kernel
cycles_split_kernel
unlock_task_scheduler
uv_unwrapping_slim_and_ceres
surface-deform-modifier
cycles-tiles-rework
soc-2016-cycles_denoising
temp-layers-ui-table
uiTable
render-layers
clay-engine
multi_previews_id
cycles_disney_bsdf_transmittance
layers
pbr-viewport
temp_display_optimization
viewport_bvh_select
temp-cycles-microdisplacement
soc-2016-cycles_images
strand_nodes
object_nodes
asset-experiments
soc-2016-sculpt_tools
temp_viewport_fx_merge
custom-normals-bmesh
temp-decklink
compositor-2016
decklink
BendyBones
cycles_panorama_experiments
temp_remove_pointcache
temp_remove_particles
temp_depsgraph_split_ubereval
temp_textedit_comment_toggling
GPencil_Editing_Stage3
temp_bge_moto
UI-experiments
UI-graphical-redesign
missing-libs
free-refcount-ids
cycles_camera_nodes
epic-navigation
temp-ui-widget-refactor
gooseberry_farm
gooseberry
temp-ghash-experiments
temp-ghash-setops
temp_motionpaths
fcurves-simplify
soc-2014-fluid
GPU_data_request
depsgraph_refactor
multiview
vertex_paint_pbvh
alembic_pointcache
cycles-ptex-49
viewport_experiments
soc-2014-bge
texture_nodes_refactor
input_method_editor
GPencil_EditStrokes
soc-2014-shapekey
terrible_consequencer
GPencil_FillStrokes
libmv_prediction
blender2.4
dyntopo_holes
soc-2014-viewport_context
gtest-staging
blender-tiles
soc-2014-viewport_fx
soc-2014-remesh
soc-2014-nurbs
pie-menus
soc-2014-cycles
soc-2013-paint
particles_refactor
soc-2013-viewport_fx
tiles-scheduler
bake-cycles
soc-2013-cycles_volume
overscan
soc-2013-depsgraph_mt
soc-2013-dingto
soc-2013-sketch_mesh
soc-2013-rigid_body_sim
soc-2011-tomato
soc-2013-bge
soc-2013-motion_track
soc-2013-ui_replay
soc-2012-sushi
ge_dev
soc-2013-depsgraph_eval
soc-2008-mxcurioni
soc-2012-bratwurst
soc-2012-swiss_cheese
soc-2012-fried_chicken
meshdata_transfer
smoke2
tile
soc-2011-cucumber
bmesh
soc-2011-carrot
cycles
soc-2011-garlic
soc-2011-radish
soc-2010-nicks
vgroup_modifiers
soc-2011-pepper
soc-2010-jwilkins
merwin-spacenav
bge_components
soc-2010-merwin
render25
soc-2010-nicolasbishop
soc-2009-chingachgook
soc-2010-nexyon
soc-2010-aligorith
ge_eigen2
sculpt25
soc-2009-jaguarandi
soc-2009-imbusy
soc-2009-kazanbas
blender2.5
volume25
soundsystem
soc-2009-aligorith
sim_physics
ge_dome
etch-a-ton
soc-2008-nicholasbishop
animsys2
projection-paint
harmonic-skeleton
soc-2008-jaguarandi
fluidcontrol
apricot
soc-2008-quorn
cloth
ndof
orange
v2.93.14
v3.3.3
v2.93.13
v2.93.12
v3.4.1
v3.3.2
v3.4.0
v3.3.1
v2.93.11
v3.3.0
v3.2.2
v2.93.10
v3.2.1
v3.2.0
v2.83.20
v2.93.9
v3.1.2
v3.1.1
v3.1.0
v2.83.19
v2.93.8
v3.0.1
v2.93.7
v3.0.0
v2.93.6
v2.93.5
v2.83.18
v2.93.4
v2.93.3
v2.83.17
v2.93.2
v2.93.1
v2.83.16
v2.93.0
v2.83.15
v2.83.14
v2.83.13
v2.92.0
v2.83.12
v2.91.2
v2.83.10
v2.91.0
v2.83.9
v2.83.8
v2.83.7
v2.90.1
v2.83.6.1
v2.83.6
v2.90.0
v2.83.5
v2.83.4
v2.83.3
v2.83.2
v2.83.1
v2.83
v2.82a
v2.82
v2.81a
v2.81
v2.80
v2.80-rc3
v2.80-rc2
v2.80-rc1
v2.79b
v2.79a
v2.79
v2.79-rc2
v2.79-rc1
v2.78c
v2.78b
v2.78a
v2.78
v2.78-rc2
v2.78-rc1
v2.77a
v2.77
v2.77-rc2
v2.77-rc1
v2.76b
v2.76a
v2.76
v2.76-rc3
v2.76-rc2
v2.76-rc1
v2.75a
v2.75
v2.75-rc2
v2.75-rc1
v2.74
v2.74-rc4
v2.74-rc3
v2.74-rc2
v2.74-rc1
v2.73a
v2.73
v2.73-rc1
v2.72b
2.72b
v2.72a
v2.72
v2.72-rc1
v2.71
v2.71-rc2
v2.71-rc1
v2.70a
v2.70
v2.70-rc2
v2.70-rc
v2.66
v2.63
v2.60
v2.59
v2.58a
v2.58
v2.57b
v2.57a
v2.56a
v2.55
v2.45
softbody-stable-v1
softbody-stable-v2
softbody-stable-v3
v2.25
v2.26
v2.27
v2.28
v2.28a
v2.28c
v2.30
v2.31
v2.31a
v2.32
v2.33
v2.33a
v2.34
v2.35
v2.35a
v2.36
v2.37
v2.37a
v2.40
v2.41
v2.42
v2.42a
v2.43
v2.44
v2.46
v2.47
v2.48
v2.48a
v2.49
v2.49a
v2.49b
v2.50
v2.51
v2.52
v2.53
v2.54
v2.56
v2.57
v2.60a
v2.61
v2.63a
v2.64
v2.64a
v2.65
v2.65a
v2.66a
v2.67
v2.67a
v2.67b
v2.68
v2.68a
v2.69
Labels
Apply labels
Clear labels
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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 Label
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Set Project
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
52 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#75319
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.3.1 26.20.15029.15007
Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash:
375c7dc4caWorked: (optional)
Short description of error
Blender crashes when using my GPU to render with cycles. This does not occur when using CPU. This does not occur when using F12 to render, only when in viewport.
This occurs when rendering anything, including a basic cube.
Blender displays "Loading render kernels" for a period of time before closing with no error message.
Running it via the console shows an LLVM error.
I have tested it on blender 2.81 as well and it does not work there.
Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]
bug.blend
2.82 debug logs.txt
2.81 logs.txt
Added subscriber: @sebsoto
#79669 was marked as duplicate of this issue
#82802 was marked as duplicate of this issue
#82780 was marked as duplicate of this issue
#82716 was marked as duplicate of this issue
#82528 was marked as duplicate of this issue
#82272 was marked as duplicate of this issue
#81683 was marked as duplicate of this issue
#81517 was marked as duplicate of this issue
#80781 was marked as duplicate of this issue
#80172 was marked as duplicate of this issue
#80264 was marked as duplicate of this issue
#79829 was marked as duplicate of this issue
#79628 was marked as duplicate of this issue
#77674 was marked as duplicate of this issue
Here is another round of logs using the
blender_debug_log.cmdtool.blender_system_info.txt
blender_debug_output.txt
Back again with another update. I built the current master:
version: 2.83 (sub 11), branch: master, commit date: 2020-04-03 16:25, hash: 63922c5056d1,and tried again. Same issue.blender_system_info.txt
blender_debug_output.txt
Added subscriber: @iss
Can not reproduce on
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
Are you aware, that you have uploaded default cube file? (steps to reproduce are not applicable, so I will rather ask)
I am.
If you look at the debug logs you will see:
I suspect this is hardware specific as this is a fresh Windows 10 install, with the latest drivers for my GPU. AMD released a new set of drivers this month, which I have also tried with the same results.
Added subscriber: @mano-wii
I also cannot reproduce the problem.
Everything fine in:
Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.50.01.05 26.20.15001.5006
I notice that your installed driver is newer.
Perhaps the problem is related.
Changed status from 'Needs Triage' to: 'Needs User Info'
I have updated my driver, and still no crash.
Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013
@sebsoto I haven't noticed rprblender addon first time, can you check if crash happens if you click on File > Defaults > Load Factory Settings?
I removed the addon like asked. Same issue.
blender_system_info.txt
blender_debug_output.txt
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscribers: @Hrodemx, @Insertcoin.tv
Hello guys, we did some tests instead of jobs... jesus..
so..
AMD Radeon(TM) Pro Duo (monitor)+ AMD Radeon RX 5700 XT (discrete)
Blender 2.82 in render, scene time 20sec per frame, with 2 youtube session 2k in play and game GuildWars2 opened, no problem, no crash.
Same thing with 2.83, render much faster like 14sec per frame, really unstable, random crash while render. If we open some youtube, or some other app that use graphics card, Blender stop render, and after about 15/20 sec, black screen driver reset, and then pc stalled, must restart physically.
If we open Guild Wars2 game, blender stop render asap, and crash 100%.
We tried with AMD Radeon(TM) Pro Duo (monitor) + AMD rx580 and same story.
Also viewport in 2.83 is much more responsive, but often crash all the system.
system-info.txt
Changed the TDR values of the Registry and set to 60.
Better, sometimes computer didn't crash, no more black screen and drivers reset, but blender sadly freeze completely so render stopped.
difference in render on my scene, 20 sec 2.82, 13:35 sec 2.83 LTS (newly downloaded and clean install without any external plugin)
Here the scene we use. But with 2.82a no problem.
Spaceship_TEST_CRASH_.7z
Added subscriber: @brecht
@brecht , Let me know if we can help in any others way.
Ciao!
Hello again,
just for info, we also tested 2.90 (blender-2.90.0-52b125a790e3) with Junk shop rtx.
After some previews, orbit around, ctrl+b etc etc, entire pc freeze. Need reboot.
Like before no problem at all with 2.82 (much more slow, but no crash).
Added subscriber: @Pastean_Narcis_Dan
blender_system_info.txt
blender_debug_output.txt
Slight;;y the same issue here also. After windows 20.04 update it started to happen to me also, no matter if i use 2.83.1 or 2.90 on a small default cube scene viewport i get an OpenCL error and on bigger scenes the whole GPU driver crashes
tried different versions of AMD drivers but with no change, also some versions caused blender to freeze or BSOD on my system while rendering second of third tile usualy.
Since i`m dual booting Windows and Kubuntu, i have no issues with linux blender using the latest amd drivers. Maybe it has something to do with the GPU scheduler the latest update introduced.
Hi all, i'm testing new enterprise drivers, and they seems to work... ye some crash on old scene but not always..
https:*drivers.amd.com/drivers/prographics/win10-radeon-pro-software-enterprise-20.q2.1-june24.exe
@Dan_P. try it.
Added subscriber: @Kryztoval
I have been recently getting this error, here is what I have found so far:
I am running:
Steam Blender 2.83.2
Windows 10 v2004
2x Duke GTX1080 SLI Bridged with SLI Disabled
64GB ram
i7 6700k
My system has been running for a while with and without OC, so I know the OC is not the problem. Also, nothing else crashes, only Blender
What I noticed is that if I go to the default file with the cube, set cycles as render, select only the GPU that has a display connected, and I enable Cycles in the viewport it definitively doesn't crash
What makes it crash is when i select the other GPU that has no displays connected to it, it will just freeze blender until it gets killed or terminated by windows. It doesn't matter if I chose the main gpu or not, as long as the secondary gpu is selected and used in the viewport render it will halt. This (as a pure guess) seems to be a context switching error that only happens when using a secondary gpu core.
I was able to reproduce this in another computer running a GTX1070 and a GTX1080ti, but in that case the GPU that won't load the context was the one with the display
This is the error I keep getting, and this is the behaviour i keep seeing
It seems to reason that, if this is the case, any GPU that has multiple contexts or that requires the set up of multiple contexts in order to render will also make blender crash in viewport cycles rendering.
Please someone test if connecting a display to the secondary GPU solves the issue. Upgrading drivers did not fix this.
I will do a few more tests on my own, as most people reported, CPU cycles rendering did not crash.
Now if you are gonna tell me this is an error with drivers, hardware, etc. Then can you explain to me why this happens disregarding if the GPU is AMD or nVidia? it is not like AMD has a cuda context.
Added subscriber: @verrafa
Hard to find a solution for that in the net.
I have a rtx 2070 super and a 980ti with an ryzen 9, and everything worked fine in Cycles with both GPUs until the last windows 2004 update.
Now i am only able to see the rendered viewport on my 2070, which has also the display connected.
When i try to view the viewport in render mode on my 980 it crashes after 1 sec. also tried the tdiDelay and tdiDdiDelay (60). https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html
But didnt it work.
Cpu mode doesn't crash.
I also tested your suggestion and plugged the monitor to the secondary graphics card (980 ti) but it crashes. When i try to render it runs fine and uses both graphicscards.
Does any body know whats going on? I can pretty much say it was the damn windows update. Because before the update it bought also a new mainboard and it ran also fine with both graphics cards. Even with big files it was flawlesly stable.
But now the viewport render view is broken for me.
Please help.
Added subscriber: @guidobruzadin
just added a comment with my solution to this issue maybe it is also related to this one:
https://developer.blender.org/T74883
Also in the comments:
https://devblogs.microsoft.com/directx/hardware-accelerated-gpu-scheduling/#comment-194
It seems this feature requres an onboard hardware scheduler. So my 980 ti does not support it. Thats the reason why:
See:
https://www.reddit.com/r/nvidia/comments/grwe8y/will_900_series_support_hardwareaccelerated_gpu/
So i dont think it is a bug in blender, maybe the error message should be better in this case
Let's stick to AMD issues only this bug report, any issues with NVIDIA are almost certainly a different problem.
Added subscriber: @Mickaa
Experiencing the same issue with Gigabyte RX 5700 XT
system-info.txt
Added subscriber: @jshlxx
Same Issue with Gigabyte 5700 non-XT
with 2.83.4 and 2.90
Every Driver after 20.4.2 locks up my system completely, but everything works fine with 20.4.2.
Still the same issue on latest Adrenalin 2020 Edition 20.8.1 for Gigabyte RX 5700 XT and blender version 2.83.4.
system-info.txt
Removed subscriber: @verrafa
The problem is with the Adrenalin drivers. If you uninstall them and install the "Radeon Pro Software for Enterprise Driver" the viewport render will work.
This is the more stable driver of the two and is especially designed for content creators. There is a minor difference between performance with gaming but its negligible. These will have to do until the Adrenalin drivers are stable.
Added subscriber: @Wolfeius
Exact same issue, with blender 2.83.4 from Steam and AMD 5600XT, Radeon software V20.8.1.
Crashes and exits to windows while compilling render kernels either in viewport or in the render screen. With the CPU works fine, games work fine.
Just open a new project and click on the Shadded viewport OR F12, and it crashes while compilling render kernels.
Not really blender, but perhaps helpfull, GPU global lighting bakes also fail in Unity 3D 2020.1
Added subscribers: @Sajunara, @ChristopherAnderssarian, @kingsushi001, @REYNEP
Hi,
Topic https://developer.blender.org/T79628 was moved here, so:
I installed: win10-radeon-software-adrenalin-2020-edition-20.4.2-may25 - still crash in kernels
on win10-radeon-pro-software-enterprise-20.q2.1-june24 i have a luck but render looks like this (but no blender crash):
but i was writing this post and render change into that :):):):):):)
- so its progress FINALLY
And Finnaly with no blender crash
win10-radeon-software-adrenalin-2020-edition-20.4.2-may25 - CRASH
win10-radeon-pro-software-enterprise-20.q2.1-june24 - WORKING on RX5700 XT - YAY !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Here are my results on 20.8.1, steps to reproduce are the same
blender_system_info.txt
blender_debug_output.txt
Last working drivers are 20.4.2 but with artifacts in large scenes. Will test enterprise Drivers now and report back.
Sadly Pro Drivers only work when a simple Default Cube is rendered, as soon as i render a larger scene my viewport is black as seen here

It will get stuck on Sample 32 and crash after about 30 Seconds
blender_debug_output.txt
blender_system_info.txt
version: 2.90.0 Beta, branch: master, commit date: 2020-08-09 12:07, hash:
00162e6b7b, type: ReleaseEDIT
Found the culprit why the render is black, Volumes don't seem to work with the enterprise driver it will still crash after compiling render kernels, every other scene without volume bsdf works fine!
Seems like the enterprise drivers should be recommended, and i thing brecht updated the wiki for it already.
Should i put a seperate bug report for the Volumes not working with the enterprise driver?
i had the same as Josh Luchs (jshgdmn), but it was only at the first time. It looks there is a problem with loading shaders or something. I reply render 1-2 times and was fine. Im not sure why, stil testing - but it was a small headphones scene.
I put bigger scene and there u go:
wireframe view



and CRASH (shit!!!!), repeat again and ????? Crash
solid view
viewport render
material prewiev
f12 render
There is no problem with ram:

DEBUG:
blender_system_info.txt
blender_debug_output.txt
i was trying with headphones and its still working :)

BMW demo scene - looks fine - no crash :)

Material Preview
f12 -
Any1 ? :):):):):):):)
Enterprise driver works better, less crash, but when you work on blender 12/24, crash occurs anyway :(
In a while we throw out of the window all ours AMD gpu... (radeon pro duo 32gb, 2x 5700xt, 4x 580, and so on...
and switched on Cuda, so no problem :(
Even Davinci Resolve go faster.. no way.. I love AMD, but we need to work no stop... and their drivers are ****
Good luck with Amd.
so we wait - f****k :(:((:(
Removed subscriber: @Insertcoin.tv
Guys dont forget to send a bugreport to AMD aswell, maybe they can help solve the issue AMD Bug Report
Done already, now we can wait for better times and updates :) its good that GW2 isn't crashing. XDXDXD. See you in Tyria :)
Added subscriber: @miro32
Downloaded bender 2.83.5 and the new Adrenalin 2020 Edition Adrenalin drivers 20.8.2 for 5700XT and seems to be fixed. I can now change view-port to rendered with Cycles renderer and not crash. Blender release notes and AMD driver notes does not say anything about a "blender fix" but they are both working in harmony once again.
EDIT: Forgot to enable GPU compute. When I did it crashed again...Oh well back to enterprise drivers then.
Actually i tested blender 2.83.5 and the new adrenaline with factory reset on my RX580 and no crashes yet, works great on my scene. 14 min render time on 20.4.2 drivers and 5 min render time on 20.8.2, its an improvement in terms of stability. However in Linux the same scene renders in 43 seconds so ...... yea AMD card wont get love anymore, maybe one everything transisions to Vulkan
Did you use GPU Compute? Asking because just like Michael (mneivandt), mine crashes as well with the same GPU and Adrenalin drivers 20.8.2.
EDIT: Did anyone notice that when you switch over to GPU in the viewport that there's no lighting?
Yes, for a regular exterior archviz scene, the above mentioned works, however after a while and further adding complexity to the scene in terms of effects like a different ligning envoirment and more artifical lights, the driver crashes.
For me its an improvemnt but not stable. Thank god i started using Linux a few month ago other wise now there was no way for me the gpu render any scene.
lol, you're lucky... I tried Blender's default scene and it crashes.
Same here. Blender 2.83.5 and AMD 20.8.2 and crashes with GPU Compute on both the viewport and render "/
Should we return the cards instead?
This comment was removed by @Mickaa
Here are some more Reports #80108 and #80092
Both are running the latest 20.8.2 Drivers.
It seems to be affecting the whole GCN1 and RDNA1 Generation. It has to be a Driver Problem right?
Added subscriber: @SirKadachi
Same problem is occurring for me on my non XT RX 5700 when trying to render in cycles. As far as I known it seems to be an AMD driver issue as the issue persists on any version higher than 20.5.1. The current driver I'm using is the 20.8.2 with Blender 2.83.5. Seems to be an issue that occurs during the compiling render kernels stage, which results in a crash of the entire application.


Added subscribers: @Monkey_D.Efrain, @GoodGuyJack
Added subscriber: @EddoWagt
I want to add to this topic.
)
I've tried my RX 480 and RX 5700(XT bios), both are not working.
On Radeon settings 20.7.1 and 20.8.3 neither are working, sometimes it get just white like this{F8846987} (For reference, this is what it is supposed to look like
while other times Blender just crashes after a while.
On Radeon settings 20.5.1 HWS from Guru3D the viewport rendering works, but F12 is still broken for me.
I haven't tried, but I'm going to assume older drivers work just fine, also, the Radeon ProRenderer works perfectly on any driver version.
The issue is obviously driver related, but it's still weird...
Edit: I forgot to add that I also have the same issue with my Manjaro Linux, I guess AMD really messed up, or there's something wrong with my computer
Added subscriber: @Diogo_Valadares
Added subscriber: @geralt-of-trivia
I have a RX580 and I also have this problem. While using Cycles with OpenCL on the GPU, my PC BOSDs.
Added subscribers: @Mulock_666, @rjg
Added subscriber: @HILLARIOUS
Is anyone actually looking at this problem? Because this piece of fuck trash AMD calls a GPU is going back. Going back to NVidia
Removed subscriber: @Kryztoval
I agree! He's not worth his money! -35-40% of the cost! I would like to return the money, and the 2nd graphics card! Nobody cares as we can see ... Nobody cares about AMD driver developers. Everyone is busy with new products ...
Added subscriber: @Hendrik.D
Hi Guys,
very similar Problem for me too, I've got some random crashes with cycles seem like, for me the sample count is important with 128s@1080p that's fine, but with 1024s@1080p it's just a matter of time till blender crashes, sometimes the AMD driver only, sometimes the complete system.
It's very annoying and not matter which blender version, it's the same for me...
Somebody can confirm the sample count dependency? Any News or Workaround at least?
System:
Win10 (v2004),
FX-8320E,
16GB RAM,
RX 480 (v20.8.2),
If anyone is having problems like these the only solution for now is to try to revert the drivers to the last stable ones(20.4.2)
Thanks for the answer, but this driver is producing the following error...
https://developer.blender.org/T77095
I will give 20.5.1 a try
maybe this "fix" only include AMD video cards from this generation then.
Probably, for me atm Blender 2.9 is working with driver version 20.5.1 .
But soo much slower than v2.8 or 2.9beta, that's kinda strange.
BWM Benchmark:
v2.8 #4.01.68
v2.9beta T03.10.81
v2.9 #5.46.43
Did anyone try the 20.9.1 driver?
Yes, I did. Don't waste your time. It's still not working.
Can confirm 20.9.1 not working on RX5700
RX 5700 XT - Crash blender 2.9 on 20.9.1 drivers......................
Added subscriber: @Doidero
Added subscriber: @dstiglitz
RX 5700 XT - Blender 2.82a and 2.9 on 20.9.2, both still fucked
It's incredible.. That thing is cutting out tons of AMD customers.. Someone must do something, urgently
At this point I kind of feel like AMD's attitude is "We have their money, fuck them"
I agree! I have been using only AMD for 15 years, but when I reach the top segment and feel "Indifference", this is not something that is not pleasant ... This, gkh! ... If nothing is decided by the end of 2020, then it was AMD's last support...
@kingsushi001 @Mulock_666 Please keep it civil and on-topic, this is the official bug tracker, not a forum to discuss shortcomings of different GPU vendors.
at this point im no longer amd fan, 3 months and useless gfx gard. Cant do anything in blender. Maybe they dont want to fix that because we need to use ProRender engine with different nodes system. Now for the same money we can buy nvidia 3060 series with optix or cuda,
Added subscriber: @harryheck1
Added subscriber: @Peeeynk
Added subscriber: @elliotgascoigne
Sorry for the duplicate bug report, I thought mine was a little different as mine closes in the final render (f12). I could add some info on the matter. When pressing render and waiting for it to reach compiling render kernals if I press esc to manually close the render then re render - it renders with no issue as if the kernals where already compiled and doesnt close blender
@elliotgascoigne I see, based on the description I thought this was the same issue.
Added subscriber: @verrafa
Okay everyone that has a 5700XT I found a work around that results in no hang/closing of blender and instant renders using GPU. Firstly I installed the AMD enterprise driver here: https://www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q3-1
(This shouldn't effect gaming performance)
This next bit I only advise if you have worked with registry keys before as they can mess up your windows so please don't proceed if you are unsure.
You need to follow Verrafa's guide on disabling GPU scheduling (thank you @verrafa) , but for me the option wasn't there so see below for how I fixed it.
For me I had to create my own registry key which I did by following this guide: https://www.windowslatest.com/2020/07/07/enable-windows-10-hardware-accelerated-gpu-scheduling/#:~:text=Open%20Start%20Menu%20and%20tap,%2Daccelerated%20GPU%20scheduling%E2%80%9D%20option.
You have to actually create a DWORD registry if it doesn't show up in the place specified (Decimal mode with exactly the same name) set it to 1 and restart your machine.
I say again please don't do this if you are unsure with registry keys as I don't want to be responsible for breaking your windows! But this solution worked for me and I can switch to GPU rendering in cycles and it begins right away without stalling and ultimately crashing on compiling render kernels!
I hope it helps!
EDIT: On more complex scenes the render kernels take a minute or so to compute but it doesn't crash blender. I'm not sure how necessary the GPU scheduling step is in this case, you may be okay with just the enterprise driver
Thanks for this. Before I go and test this, does this fix the viewport rendering as well? You know, when switching from Solid to Rendered.
EDIT: Never mind, this didn't work at all for me. Not in Blender 2.82a or in 2.90. Couldn't switch viewport rendering or render the default cube scene. Crashes every time.
Scenes with no volume are well managed by enterprise drivers. If you instead use a Principle Volume node in any mesh, then Blender freezes also with enterprise drivers. I really wonder how it's possible.
You're lucky... Nothing I have tried have worked. At all. No specific set of drivers or registry edits. Nothing has worked. Blender ALWAYS freezes.
У меня есть вопрос, проблемы только с видеокартами в стоке, или в разгоне? У меня бывали проблемы с Ryzen и Rx460 после небольших разгонов. Как себя ведет в Blender видеокарта RX5700 , которая не разогнанная ?
I have a question, are there only problems with video cards in stock, or overclocking? I've had problems with Ryzen and Rx460 after minor overclocks. How does an RX5700 video card that is not overclocked behave in Blender?
My RX5700XT is not overclocked, blender is only working with drivers that are v20.4.2 and below, unless its a scene that contains volume, tho I think in this case this may not be a driver problem, its probably a blender problem since 2.83(?) as you can see in this task https://developer.blender.org/T78027
Added subscriber: @SilentMrDave
Forgot to indicate the versions RX5700XT and RX5700, is there an error on both cards? The theme was created using RX5700XT, the question with tests during overclocking remains in test mode for both video cards.
Added subscriber: @(Deleted)
Not exactly the same issue (AMD RX 460 2GB, drivers 20.9.2):
If the scene is extremely simple, like the default cube, after waiting for "loading render kernels" (if I do anything* during this message Blender crashes) the scene does render. It's slower than just the CPU, but it renders, and I can move the camera without causing a crash.
If the scene is more complex than a default cube, Blender (after some waiting) manages to get to the first sample, but it won't go any further. Again, doing anything* crashes Blender.
*Actually not anything: only actions that cause another rendering, like moving the camera, will crash Blender. For the second example, if I change render device to CPU, Blender will switch successfully without crashing.
Removed subscriber: @verrafa
I hope AMD fixes this, I'm new to 3D and I bought the RX 5700 months ago in hopes of learning. Now its just a useless brick :(
Did everyone here send AMD a bug report as well?
I'm not a newbie, but I bought it with the hope of responsiveness and fixes, we really look forward to positive responses ... But I won't even think of advising AMD to anyone else. We are all waiting for a miracle. Sorry for the flood!
Added subscriber: @AlphaCloud
I have an rx 5700 with amd drivers 20.9.2 and blender version 2.90.1 and blender just doesn't want to render with the gpu, so I'm stuck with cpu rendering, hopefully amd does something about this
Added subscriber: @Zodijac
Added subscriber: @Reenuip
Added subscriber: @MihaiPlesa
I also have the same problem, on the rx 5700 XT with the latest drivers installed. I made a report at AMD, I hope everyone here did. Let's hope it gets fixed as soon as possible.
I hope they are fixing this and performance will be good in render times. Many of us is tired about this situation but still with hope that somebody in AMD and Blender is reading posts here :) Best of LUCK for all users of AMD products :)
All this damn time, I personally lost money for the purchase, and I lose for every not made render, like most of the guys gathered here ... There is one question, why was AMD suddenly forgotten here? Can someone send them a link to the topic? Are there any facts that they are browsing the forum? How it works?
As far as I can tell, this is an AMD problem, not a Blender issue
Added subscriber: @Alejandro-Nevarez-Lucio
I've got the same problem since the release of the AMD new drivers, i've been just reading this thread, i've tried everything, and i have something weird besides the crash.
Sometimes (it is just random) when i hit render view with OpenCL the whole scene turns white materials, everything, the HDRI, textures, materials, it all goes white (even with factory reset default cube thing or complex scene) for a minute or two, then it crashes. This just happens from time to time, it usually just crashes when loading kernels finish.
It now happens with every latest blender version, even 2.83 LTS from windows store giving me always same problem.
I think it has something to do with Radeon Drivers, this same thing happened to me back in April, and the problem just went away with new AMD Drivers, now same thing i guess we'll have to wait for new AMD drivers and hope Blender works fine with them.
Just wanted to say i sometimes get a white scene (yes, white scene with shadows and everything, not white screen) something different from what i've read.
AMD Rx 5600 XT
Ryzen 5 3600
32GB ddr4 3000Mhz ram
750W Corsair 80+ Bronze power supply
and running on SSD m2
I actually had the same issue before quite a few times! I thought it was just a bug, mine didn't crash, I just went back into material preview mode and back into rendered mode and that seemed to fix it. Sometimes I had to restart blender though. But what's even weirder is that even rolling back to a driver version that I'm sure worked fine now doesn't work even if I factory reset the drivers
I have tried EVERY workaround posted here and everywhere else. None of the drivers work for me. Not the adrenaline ones or the pro drivers of any version.
I am seriously starting to think that AMD really just don't care. I've submitted numerous bug reports to AMD as well, they never get back to you or fix the issue. I've been having problems for about 2-3 months and I'm sure there's people here who has been waiting even longer. This was my 1st AMD card, sure as hell my last.
Today while making some 3D stuff got a flash on blender then it crashed, now i tried once again to render after this weird flash and i'm getting this error "OpenCL error (-52): CL_INVALID_KERNEL ARGS in clEnqueueNDRangeKernel" After a few seconds when this shows up, blender crashes.
Something new and different from the old problem.
For people who want to render now there is a solution. Pro Render. Im to lazy to make a new nodes that is why im waiting for cycles working, but still. https://www.amd.com/en/technologies/radeon-prorender-blender - Its working, rendering but own node system or old one, before principled bsdf nodes
Its just another render engine.
Example: https://www.youtube.com/watch?v=355sBBql6Rk
Hope i helped.... may the force be with you
Render Engines for Blener: https://www.blendernation.com/2020/08/03/overview-of-free-blender-renderers/#prettyPhoto
VFX explained: https://youtu.be/dE4g7sdNbi4
Renderman from PIXAR: https://renderman.pixar.com/product
https://www.youtube.com/watch?v=E3vPJybuG9s
https://www.youtube.com/watch?v=aKh2taqONg8
Regards, Saju
Anyone try the 20.10.1 drivers yet? Doubt it'll work, but probably worth a shot.
I just updated to give it a try. Unfortunately the problem is still there.
I've tried the pro drivers Radeon™ Pro Software for Enterprise Revision Number 20.Q3.1 on my rx 5700 XT and cycles are working fine.
Also, when I've installed the new driver I did a factory reset of the card.
I have not tested the drivers to see if it affects gaming performance.
Link: https://www.amd.com/en/support/graphics/amd-radeon-5700-series/amd-radeon-rx-5700-series/amd-radeon-rx-5700-xt
I hope this helps some of you.
It's true. But if you try to add any type of volume mesh/shader and then open render viewport or try to render, then it will crash. Nothing changed and, probably, nothing will change in the future because of amd's policy.
Personally, and i'm sorry about it, i already bought a nvidia card. People need to work and that's not a correct way to do marketing from amd.
Tested now and you are correct, it's crashing after adding new mesh/volume.
I'll definitely switch to nVidia after the launch of the 3070.
Which AMD policy?
As someone said previously in this topic, amd replied that for working we should use the radeon pro series gpus and not the "normal" RX Vega/Navi gpus, that are supposed to be for gaming
Wow.... Just wow. Again, I will not be supporting them again. Ever. That's a very nice middle finger to their customers. I hope nVidia crushes them
Added subscriber: @hauser
Can confirm that this problem happens to me as well, using RX 5600 XT. I opened up an issue over at https://gitlab.freedesktop.org/drm/amd/-/issues/1343.
Hi!
i just deinstalled the adrenalin driver, so i only have installed the newest chipset drivers and gp rendering with cycles and my 5700 XT works now!!!
Where can I find the chipset drivers @Zodijac ?
Nice, can you explain a bit more how you did everything? I'm a noob when it comes to this.
Added subscriber: @EmperadorFELES
Hello someone have solutions for the RX 5600 XT? @Zodijac could you help, please? And remove the drivers will be bad for games?
Added subscriber: @jin.veiss
This is all I want for Christmas...
Anyone who has encountered a problem is asked to send a bug report to AMD using the built-in function in the driver with the image of a bug in the upper right corner of the program
There is one more note, I came across a topic on the net where it was said that the "Game" mode in Win10 cuts performance in some video cards very much, and there is an RX 5xxx version there.
Someone came across, maybe it got better? In addition to all this, since there was a question about an error in Win10, how about our problem on Linux ?? Are there mistakes too?
Есть еще одно замечание, наткнулся в сети на тему, где говорилось, что "Игровой" режим в Win10 очень сильно режет производительность в некоторых видеокартах, и там есть RX 5xxx версии.
Кто то сталкивался, может стало лучше? Ко всему этому , раз образовался вопрос о ошибке в Win10 , то как с нашей проблемой на Linux ?? Тоже есть ошибки ?
On version 2.9.01 there are no changes, at the moment you can somehow see the picture and even try in a perverse way to work with ProRender, but there ...=(
Today I found a solution to the issue of speeding up the processor, installed the driver and decided to look at the Rx5700xt tab, and there I found the stock Pro driver! I cannot check at the moment.
Сегодня нашел решение вопроса по ускорению процессора, устанавливал драйвер и решил заглянуть на вкладку по Rx5700xt , а там я обнаружил стоковый Pro драйвер ! На данный момент проверить не могу.
No dice, however I didn't do the factory reset option on the card. Kernels just load forever until Blender crashes.
Added subscriber: @PoorManFury
I tried to install Pro driver, everything changed places! ProRender hangs, and Cycles renders only a standard scene, I will not leave it in this state, other programs require a normal driver. Try you.
Hooray! there are some results! And so, I have an Asrock AB350 Pro4 motherboard, in some of the articles I came across a solution to problems by correcting the BIOS of the motherboard, I decided to go in and look at the BIOS updates, they added as many as 5 versions there, installed the latest firmware version 6.4. Pro driver did not give results, I decided to install Adrenaline 20.1.2 (1 \ 13 \ 2020)! ProRender refused to work, and Cycles gave 3 minutes, Eve 2 seconds. but this is already progress, though I don't know what helped, driver rollback or BIOS update. tomorrow I will continue installing the drivers in turn. The driver for the RX5700xt was taken from here
Ура! есть какие-то результаты! И так, у меня материнская плата Asrock AB350 Pro4 , в какой то из статей наткнулся на решение проблем исправлением BIOS материнской платы, решил зайти и посмотреть на обновления BIOS, там добавили целых 5 версий, установил последнюю прошивку 6.4 версии. Pro драйвер не давал результатов, решил установить Адреналин 20.1.2 (1\13\2020) ! ProRender отказался работать, а Cycles дал результат в 3 минуты, Eve 2 секунды. но это уже прогресс, правда не знаю что помогло, откат драйвера либо обновление BIOS. завтра продолжу установку драйверов по очереди. Драйвер для RX5700xt брал отсюда https://www.amd.com/ru/support/previous-drivers/graphics/amd-radeon-5700-series/amd-radeon-rx-5700-series/amd-radeon-rx-5700-xt
Awesome, so atleast you can now get a functional card. Please do tell if later drivers work with the bios. I do remember updating my bios a while ago, but am not sure whether or not that was around the same time cycles started to crash
Version 20.1.4 (Working) Long responsive to switching render in the viewport
(Body Color standart)
Версия 20.1.4 (Работает) Долго реагирует на переключение рендера во вьюпорте
BMW: 128 semple
Cycles 0/12/19

ProRender 0/17/76
Version 20.1.3 Recommended WHQL ( ViewPort Nice)
BMW: 128 sample
Cycles 0.13.38 ViewPort Nice (Render body BLACK)

ProRender 0.47.23 ViewPort Nice

And when using the Principled Volume node? Does it work then?
Version 20.2.1 ( Work )
BMW: 128 sample
Cycles 0.13.60 ( ViewPort Nice ) (Render body BLACK)
ProRender 0.14.93 ( ViewPort Nice )
Today I will conduct tests on all available versions (installation on top of the previous one), later we will try to dance ... True, the black body confuses me)))
Driver 20.4.2 was the latest that blender worked for me. Driver 20.5.1 and later seem to have the same problem in blender.
Edit: I have RX 5700XT, Ryzen 3700X on a X570 motherboard running 3200mhz RAM.
yea, blender is working fine with driver version 20.4.2., at least on my RX5700XT
this one I don't think its AMD's blame, it's has been in blender since 2.83 as far as I'm aware of https://developer.blender.org/T78027, but I can also render scenes with volume fine as in blender 2.90.1, with random crashes if I change the nodes while rendering.
How does one rollback a GPU driver? I have a RX5700XT and I'm experiencing crashes.
You could just uninstall like other program or use DDU to uninstall if want to be sure. Then install the driver 20.4.2 from AMD site.
Added subscriber: @isaac.47
Hello everyone. I also had the same problem with my RX Radeon 5600XT card, the blender only caught me in the radeon 20.4.2 software version, currently I use blender 2.90.1.
I currently have Radeon software version 20.10.1.
with blender 2.90.1 and when using the blender GPU, it took a long time to load and closed.
a person recommended me something.
So I didn't lose anything by trying, I did it and they think the GPU of blender 2.90.1 with software version 20.10.1 takes me perfectly.
Я решил не выкладывать перечень по всем драйверам, и решил остановится на самом адекватно работающем драйвере, ниже моя система и некоторая информация теста. Cycles работает хорошо! ProRender Хорошо! В обоих движках рендер во вьюпорте работает хорошо и быстро реагирует! Черная краска BMW в предыдущих комментариях это выход на Displace , сразу этого не проверял было мало времени.
Вывод:
.......................................................................................................................
I decided not to post a list of all the drivers, and decided to stop at the most adequately working driver, below is my system and some test information. Cycles works well! ProRender Good! In both engines, the render in the viewport works well and is responsive! Black BMW paint in the previous comments is an exit on Displace, I didn't check it right away for a little time.
Conclusion:
In Blender 2.9.1
Asrock AB350 Pro4
Ryzen5 3600
16Gb DDR4
Asrock Rx5700xt Phantom Gaming
..............................................................................................
Version Driver : Adrenalin 2020 Edition 20.4.2 Recommended (WHQL) NICE WORK! FAST !
the solution that they advised me is this.
2 download the current drivers for the chipset and graphics card you have, but do not install it yet.
3 uninstall the drivers that you have installed for both the chipsets and the graphics card, I recommend a deep uninstallation, so that you do not have folders.
4 once everything is downloaded and uninstalled, disconnect from the internet, and there if you install chiptsets first and then graphics card.
5 once everything has been updated both computer and drivers, this part is crucial so pay attention "we crush" windows + r "so that we open the" run ". We put"% appdata% "once a window opens we look for" \ AppData \ Roaming \ Blender \ 2.90 \ cache \ kermels "and we eliminate. And voila you should take the GPU component of blender.
I uninstalled the latest drivers and installed "Adrenalin 2020 Edition 20.4.2 Recommended (WHQL)". I had to reload the scene a couple of times in order for everything to render but it works.
Added subscriber: @prxllx
I'm pretty sure that those problems are caused by the driver, I've tried 20.9.1 then rollback to 20.4.2 and yep 20.4.2 woks perfectly fine with volume nodes in Blender 2.90
My rig:
AsRock A320M-HDV
Ryzen5 2400G
RX 5500 XT
16GB DDR4
I have got respornse from AMD:
Thank you for the information and the links that you provided.
Our engineering team is aware of the issue and they are working on a fix which will be implemented in a future driver.
Please review our release notes once a new driver to see if your issue has been fixed
In order to update this service request, please respond without deleting or modifying the service request reference number in the email subject or in the email correspondence below.
Please Note: This service request will automatically close if we do not receive a response within 10 days and cannot be reopened.
If it is not feasible to respond within 10 days, feel free to open a new service request and reference this ticket for continued support.
Best regards,
AMD Global Customer Care
This email is a direct result of your contact with AMD Global Customer Care and not part of a campaign. There is no need to unsubscribe to this email as you will only be contacted again if you directly request another service from AMD Global Customer Care.
The contents of this message are provided for informational purposes only. AMD makes no representation or warranties with respect to the accuracy of the contents of the information provided, and reserves the right to change such information at any time, with or without notice.
Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
I contacted the manufacturer of my 5600 XT (XFX) and they told me to return the card for a full refund. So i bought a new RTX 2060 from nVidia. All my problems were solved, and now the performance is extremely, extremely fast. Like 100x faster than what i was experiencing with the 5600XT, even on those brief moments when it actually worked. Error codes in Substance Painter also disspeared and I think some artifacts that were very common before no longer appear or do so much less often (still testing this bit). But overall is better, faster, even denoised is waaaay faster than the 5600 XT.
I had to reduce the viewport passes to 16, because 32 was just too slow with the 5600XT, with the nVidia RTX 2060 AND the viewport denoiser active (something VERY slow with the 5600 XT) is SO fast i can't even see the numbers as they go up to 32. The improvement should be at least 100 times faster.
Upgrading to the RTX 2060 was an absolute GAME-CHANGER, in terms of speed, quality, and features (like denoising or OptiX), albeit for about 40£ extra. Like other users have said before, don't waste any more time with the Radeon cards, AMD certainly isn't, as this has been going on for a year now. I can recommend the cheapest 2060 you can get, as it changed entirely my workflow. Its like Blender paradise.
why did you close this thread? it hasn't been resolved for those who still use amd
Changed status from 'Resolved' to: 'Needs Developer To Reproduce'
@Wolfeius Please don't close tickets that are not your own, especially when many users have confirmed the issue. Based on @Sajunara 's comment, AMD is working on a patch for their graphics driver.
This is exactly what I did as well. Contacted XFX last week, got a full refund from the online shop I bought the 5700XT from and bought a RTX2060s. I should receive it by Monday or Tuesday.
If somebody are switching to nvidia consider 3070 Nvidia Card.
https://versus.com/en/galax-geforce-rtx-2060-super-vs-palit-geforce-rtx-3070-gamingpro
There is twice more CUDA and Optix will work like crazy. HOPE.
im waiting for driver update, i heard that amd is working on feature where cpu share resources with gpu and backwards, - will be shared resources. only thing is that you have both amd - cpu and gpu. info not confirmed but interesting.
Regards, Saju
Unfortunately that's not an option here in South Africa. Cheapest 3070 is like 1.5 times more than the 2060s
In that case is good option. i were choseing betwen 5700 xt and 2060 Super.
Это будет работать только на Ryzen5000+ с новыми видеокартами Radeon 6xxx. О других совместимостях я не слышал. В ProRender Есть такая функция обработки CPU+GPU но она на данный момент даёт сбой, кажется что AMD готовится взорвать производительностью КОМПЛЕКСОМ своей системы, что очень разумный маркетинговый шаг на данном этапе событий. В целом мне жалко продавать Rx5700xt, но всё так резко изменилось, я уже год работаю в другой сфере деятельности из-за ошибок, но всё равно это сложно...Я всю жизнь использовал AMD комплектующие...
This will only work on Ryzen5000 + with newer Radeon 6xxx graphics cards. I have not heard about other compatibility. In ProRender there is such a function of processing CPU + GPU but it is currently malfunctioning, it seems that AMD is preparing to explode the performance of its system with a COMPLEX, which is a very reasonable marketing step at this stage of events. In general, I am sorry to sell the Rx5700xt, but everything has changed so dramatically, I have been working in another field of activity for a year due to errors, but still it's difficult ... I have used AMD components all my life ...
So it was possible ?! I don't think that this is possible in the Republic of Belarus = (But, I would like to return her to the store
so RX 5700 XT was a bad choice.... feel so unlucky..........
Added subscriber: @Yonatan-Avhar
just delete this folder: \ AppData \ Roaming \ Blender \ 2.90 \ cache \ kermels.
right click on the blender icon.
troubleshoot compatibility issues.
Are you sure you are using your GPU for rendering? Because the "device" section is grayed out.
well, this was one of the first things I tried when I got this bug, It didnt work back then neither it did now, I get the following error
crashing some seconds later
my computer specs are a ryzen 3600 and an rx5700xt
make sure you are not rendering with cpu
New drivers, folder: \ AppData \ Roaming \ Blender \ 2.90 \ cache \ kermels - deleted, and still no renders. Hahahahahahahahahahahahahahaha, just great.
👍👍👍👍👍👍👍👍👍👍
I am also experiencing this issue with an AMD Radeon RX 5600 XT.
AMD Driver version: 20.11.1
CPU: Intel Core i5 8400
Windows 10 2004
Here are the logs from Blender 2.90:blender_system_info.txt
blender_debug_output.txt
Отправьте пожалуйста багрепорт, с помощью меню драйвера в AMD corp
Added subscriber: @VlaDexa
Added subscriber: @Tedzem
I have a RX 5700 XT and have the same problem. I got into blender only a couple of days ago so this is a little menacing.
Its sad that you have start like that, Bender is awesome software so be patient or switch to nvidia if you can.
you can also just revert the drivers to 20.4.2, render with only the cpu or use eevee/luxcore
Added subscriber: @Booler
Added subscriber: @en
Added subscribers: @silverstar48-3, @Hector-Castillo
UPDATE
Just updated to the new 20.11.2 Drivers and now all my renders on the GPU (RX 5700) work!
Even the principled Volume works without crashing!
Note the loading of the render kernels the first time after updating the driver took about 4 Minutes, after that everything was instantly loaded.
system-info.txt
Have the same, i couldnt believe it XD
20.11.2 - drivers. Blender working no crash so far, so we colse, plz check in your specs ? Good Job AMD. 👍👍👍👍👍👍👍👍❤❤❤❤❤❤❤❤😍😍😍😍😍😍😍😍😍👏👏👏👏👏👏👏👏👏
I can to confirm the new drivers work, just with a really long compiling of render kernals. I am still converting to team green. I haven't been able to work efficiently for months now because of this so can't risk it happening again which is a HUGE possibility as their drivers seem to break things all the time.
Yep, I can confirm it has been fixed, as josh said, it takes a while loading and even gave me a kernel error, but if you go to solid mode and go back to render it works fine.
My graphics card is an RX5700xt, it would be good if someone with an older gen card also test it to see if it has been fully fixed
RX 5700 XT - Working.
It still feels quite iffy in some scenes to get it working, but yeah I can get it to render aswell on my 5700(XT)
Confirmed, 20.11.2 version AMD driver works fine. Although loading for the kernels takes up to 3 minutes
https://www.youtube.com/watch?v=nQdd57NZBrg 😜😜😜😜
Removed subscriber: @Yonatan-Avhar
Well, the crash is fixed! When doing actions that cause a new render, it will do a new render, just as it should.
Unfortunately it still doesn't go past the first sample. Or maybe it eventually will, but too much time passed, CPU rendering would have already finished. I don't know if the little VRAM I have is the cause.
Also unrelated, but I tried to render (not via viewport) and it caused a driver hang, forcing me to kill Blender via task manager.
Я был очень рад прочитать позитивные отзывы о 20.11.2 , но у меня в рендере окна

И очень медленно реагирует на переключения, включения рендеров. ОЧЕНЬ медленно реагирует, во время выхода из рендера окна даже подумал что Blender завис! Но всё же отошел через некоторое время...
Обычный рендер F12 действительно загружается очень долго
Но! Это уже что, то! С нетерпением жду полного устранения проблемы! Очень нужно работать, я уже забыл хоткеи и отстаю от нововведений на столько что заново придется учить программу ((
I was very happy to read the positive feedback on 11/20/2, but I have
in my window render
And very slowly responds to switching, turning on renders. VERY slow to react, when exiting the render window I even thought that Blender was frozen! But still, he left after a while ...
Normal F12 render takes a really long time to load
But! This is something! I look forward to completely fixing the problem! I really need to work, I have already forgotten the hotkeys and am lagging behind innovations to re-learn the program ((
Radeon ProRender (very Slow reaction in renders)
to be fair, openCL always took a long time to start rendering, even before the bug
Ubuntu 20.04
Video card: Nvidia 780Ti
Compute card: rx 5700 xt
Command: sudo ./amdgpu-pro-install --opencl=pal --headless
Compute GPU not in Blender 2.90.1 OpenCL list
Command: sudo apt install ocl-icd-dev ocl-icd-libopencl1-amdgpu-pro-dev -y
Compute GPU appeared in Blender.
Testing: viewport rendering... same behavior as previous drivers, takes about 3 mins to compile.
Testing: rendering monkey with default material and default settings
Testing BAKE!...... Fail.
Aborted
This is not a fresh install but it should have worked anyway.
I'll try in a fresh install later this week, no luck for me so far.
20.4.2 Ok speed reaction , for my system.
Added subscriber: @Luciddream
I did some tests with latest 5700xt drivers on Linux (20.45) - I downloaded Nishita Sky Demo from Cycles, then tried to Render a single image.
ProRender completes in 55 seconds for 100% image size, and gives this result: https://i.imgur.com/Qqp2IFm.jpg
Cycles completes in 3,5 minutes for 52% image size, and gives this result: https://i.imgur.com/5jR3Szu.jpg
Is this expected or I'm doing something wrong? I have no experience with Blender I'm just trying to figure out if the drivers are working properly, and exploring new features :)
Looks like ProRender is not set up correctly, as it looks notably worse and there's even missing textures
Thanks, I realize now I need to configure ProRender to get better quality which also makes it slower. I will make more tests - but I guess both OpenCL and ProRender are working for these drivers. Sometimes after I click Render Image, the UI will stop responding and I will have to kill blender from terminal, so it's kinda relevant to the issue.
hi All,
I tested Blender with new drivers couple of times, and its stable. First render is preparing kernels and it was about 2-4 min. after that all next renders in viewport or F12 was working fast. Before testing i cleared kernel cache. For me its ok, working smooth with no crash.
Thanks all for help and involve with problem together somehow. i wish you all the best renders ever made, 😘😘😘
Bake Project still has no luck.
Added subscriber: @voyager3
I had the same issues with my 5600xt with Adrenaline 20.9.1 (which came as recommended) and 20.11.1.
I now changed it to 20.4.2 and rendering works Einwandfrei ! :)
If you are new to this, you need to uninstall your old drivers first using DDU (https://www.guru3d.com/files-details/display-driver-uninstaller-download.html). If you do not do this, then you will have compatibility issues with your drivers and software.
Step 1: Install DDU
Step 2: Run the DDÚ application. Choose to uninstall 'GPU'-> AMD.
Step 3: Restart
Step 4: Install 20.4.2 adrenaline from here : https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-4-2
Step 5: Restart
Added subscriber: @voyagercgi
@voyager3 try 20.11.2 not 20.11.1
@Diogo_Valadares Tried it. The cycles rendering doesn't work and Blender crashes.
No issues with 20.4.2. I shall continue using it until AMD fixes this, hopefully in their next release.
Has anybody tried the drivers(20.11.2) with blender 2.91? I tried messing around with the new "mesh to volume modifier" and it seems to not like it. The volume has no material but its colored red, I don't know why.
Added subscriber: @lichtwerk
#82856 (After updating the video card drivers to 20.11.2, interface artifacts appeared.)
My advice to you, do not suffer, but exchange for RTX2070S, RTX3070, I sold my RX5700xt ... Until AMD comes up with a replacement for CUDA \ Optix, there is no sense in working in Blender with Radeon. This is the segment of mining and video games. Blender Positioned on Nvidia and Linux.
Added subscribers: @DoctorGlimmerity, @franMarz, @Th3ho0d, @Jeroen-Bakker, @fclem, @ankitm
Added subscriber: @Alirion-2
Yeah, thats why we re stuck with a NOT STABLE Blender version sicne 2.83 on the AMD side. This does NOT fix the Problem.
I just installed the driver version 20.11.2 for 5700xt. It works fine with blender version 2.90.1
However it shows an error with cycles enabled in blender version 2.91
Yes, I already said, at this point in time I sell PRO versions from AMD will not give results, in terms of technology-performance-price-quality of the scene (work). AMD + Blender - makes it possible to use Blender, but they are not suitable for permanent work in the program, only in a separate segment such as video editing.
this only happens once, if you go to solid then go to rendered mode again it works fine
for some reason when you go to solid mode it finishes the kernels compilation, so for a second blender will look like it hanged, but if you look at the console it will show what its doing:
it fails here, and then going to solid mode I get:
Seems like all the GCN 4 and RDNA 1 Cards are Having this OpenCL+Kernel Related Bug. (BUT NO GCN 5 CARD)
Added subscriber: @skittlituted_scorpion
Does anybody have any updates or fixes to this? 20.11.2 crashes for me when I use 2.90 or 2.91
Working in the new Blender 2.91.1 Alpha
Sapphire Nitro+ RX5700 XT
Ryzen 7 3700X 32GB Ram
Latest AMD Drivers
It does seem to still struggle a bit to compile kernels and what not prerendering in the image editor and especially with large scenes. Testing with the BMW GPU scene the viewport starts rendering right away. Seemingly not quite there yet, maybe the ball's in AMD's court for further optimization, or maybe I just don't know what to expect as this is the first GPU rendering I've been able to do on this machine, but it is at least useable now!
Please test and report back results. Specifically curious how better processors will fare with the 5700XT.
Works for me in blender 2.91.0
I have an Amd rx 5700, Amd ryzen 7 2700 and 32gb of ram with the latest amd drivers(20.11.3).
Takes a while for it to load the kernels and stuff for the render but when actually doing the rendering there are no issues.
20.12.1 are the latest drivers, but 20.11.3 didn't work for me then either in any previous version of Blender so that's interesting.
Starting GPU rendering in the viewport is almost instant now. The only Kernel loading I have is in the image editor rendering. Try 2.91.1 and see how it goes. There's specific updates in the release notes regarding AMD GPUs. I can't seem to pull up the release notes for it now though...
Added subscriber: @MeDo4k
This comment was removed by @MeDo4k
Hi, today the new update "Adrenalin 2020 Edition 21.2.1 Optional" came out for my GPU rx 5700xt and it solved the problems with volume shaders, in the past I couldn't render any volume shader at all I tried all the different versions of the GPU drivers and Blender versions too.
Today I upgraded the GPU driver to "Adrenalin 2020 Edition 21.2.1 Optional" and it solved the problems for me, I use Windows 10 with rx 5700xt GPU and Blender 2.91.0 I hope it works for you guys as well.
Note;
Before this update I couldn't render at all in "Radeon Software" drivers so I had to install "Radeon™ Pro Software for Enterprise" drivers, then I couldn't play games properly with it, till I found out if you change "Feature set" to 'Experimental' you can actually render using "Radeon Software" drivers. Even though they all had issues with volume shaders.
Nice but what is the difference between "Adrenalin 2020 Edition 21.2.1 Optional" and Adrenalin 2020 Edition 20.11.2 Recommended (WHQL)?
the WHQL stands for "Windows Hardware Quality Labs" it basically means that Microsoft tested this driver and it met the standards of Microsoft, and it is compatible with their operating systems.
so they recommended the WHQL driver instead of the latest driver. since it is tested, certified, compatible with the operating system, etc..
Removed subscriber: @Booler
Thanks for the clarification, do I have to uninstall my current driver(Adrenalin 2020 Edition 20.11.2) before installing non-WHQL version?
welcome, no you don't have to. If you want to you can completely remove the current driver using amd cleanup utility and install the new one.
Actually this is the first time I install a driver without restarting my PC, the screen did go black longer than usual so I think the GPU restarted or something I don't really know.
So far it kind of works, but after some testing I found a couple of issues. Attaching a noise to the density gives you errors.
and detaching the principled volume while in render view freezes blender.
It works fine with me, even if I detach the principled volume in render view mode
I reported this issue some time ago in #78027
also related:
#77858
Added subscriber: @ThomasDinges
Changed status from 'Needs Developer To Reproduce' to: 'Archived'
OpenCL rendering support was removed in Blender 3.0.
The combination of the limited Cycles kernel implementation, driver bugs, and stalled OpenCL standard
has made maintenance too difficult. Thanks for all your reports, but it's unlikely that there will be further fixes for OpenCL.
For AMD GPUs, there is a new backend based on the HIP platform.
In Blender 3.0, this is supported on Windows with RDNA and RDNA2 generation discrete graphics cards.
It includes Radeon RX 5000 and RX 6000 series GPUs. Driver version Radeon Pro 21.Q4 or newer is required.
https://wiki.blender.org/wiki/Reference/Release_Notes/3.0/Cycles
https://code.blender.org/2021/11/next-level-support-for-amd-gpus/