Radeon RX5xx: Computer freezes/crashes when user performs actions in Viewport during rendering in Blender 2.90 #80519

Closed
opened 2020-09-06 13:57:23 +02:00 by Bernd Konnerth · 16 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29
Worked: 2.8x (did not have this issue wit versions < 2.9)

Short description of error
When rendering with Cycles and doing actions in parallel like changing Viewport Shading from "Material Preview" to "Rendered" (while using Cycles), or even only moving around the rendering window, Blender either freezes completely (but stoppable via Taskmanager) or crashes the whole machine. Symptoms are different. Sometimes screen flips between full black and full white. Sometimes it is possible to still access the Taskmanager, but in some cases also mouse freezes and only pressing the power button can bring the system up again.

Exact steps for others to reproduce the error

  • Set Viewport Shading to "Material preview"
  • Press F12 to start rendering
  • Set Viewport Shading to "Rendered"
  • Move around the render window with the mouse

Normally the issue is reproducible a after a view seconds. Sometimes its even enough just to press F12 and move the window. It looks like the issue does not happen that offen when I remove some of the textures (also attach in the zip), but it doesn't look like a specific texture causes the issue.

Even when I'm able to stop the hanging/crashed Blender process it looks like something with the display driver is broken permanently after restarting Blender the issue is back immediately. When I then reboot the machine, it takes a little bit longer until I can reproduce it.

I also saw the attached image of the menu (with a lot of green little dots). Minimizing/maximizing the Blender Window did not help in this case to restore the menus.

My machine 0,5 years old thus a very new system with a Radeon RX570. I can't reproduce the issue with a simple cube (incl. a material). It also doesn't matter when changing the number of threads in use to a fixed number (lower than 12, which is the maximum of my CPU). In case I set it to a very low number e.g. 1-3 it even seems to get worse. The issue than appears nearly immediately.

If you need additional information, let me know. I really love version 2.9 and the new features. Would be really great if you could find and fix this annoying issue or even let me know if there is a good workaround.

Thanks & Regards,
Bernd

Crash Example.zip
blender_debug_output.txt

blender_system_info.txt
2020-09-08 10-34-46.mkv

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29` Worked: 2.8x (did not have this issue wit versions < 2.9) **Short description of error** When rendering with Cycles and doing actions in parallel like changing Viewport Shading from "Material Preview" to "Rendered" (while using Cycles), or even only moving around the rendering window, Blender either freezes completely (but stoppable via Taskmanager) or crashes the whole machine. Symptoms are different. Sometimes screen flips between full black and full white. Sometimes it is possible to still access the Taskmanager, but in some cases also mouse freezes and only pressing the power button can bring the system up again. **Exact steps for others to reproduce the error** - Set Viewport Shading to "Material preview" - Press F12 to start rendering - Set Viewport Shading to "Rendered" - Move around the render window with the mouse Normally the issue is reproducible a after a view seconds. Sometimes its even enough just to press F12 and move the window. It looks like the issue does not happen that offen when I remove some of the textures (also attach in the zip), but it doesn't look like a specific texture causes the issue. Even when I'm able to stop the hanging/crashed Blender process it looks like something with the display driver is broken permanently after restarting Blender the issue is back immediately. When I then reboot the machine, it takes a little bit longer until I can reproduce it. I also saw the attached image of the menu (with a lot of green little dots). Minimizing/maximizing the Blender Window did not help in this case to restore the menus. My machine 0,5 years old thus a very new system with a Radeon RX570. I can't reproduce the issue with a simple cube (incl. a material). It also doesn't matter when changing the number of threads in use to a fixed number (lower than 12, which is the maximum of my CPU). In case I set it to a very low number e.g. 1-3 it even seems to get worse. The issue than appears nearly immediately. If you need additional information, let me know. I really love version 2.9 and the new features. Would be really great if you could find and fix this annoying issue or even let me know if there is a good workaround. Thanks & Regards, Bernd [Crash Example.zip](https://archive.blender.org/developer/F8847210/Crash_Example.zip) [blender_debug_output.txt](https://archive.blender.org/developer/F8851693/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8851694/blender_system_info.txt) [2020-09-08 10-34-46.mkv](https://archive.blender.org/developer/F8853610/2020-09-08_10-34-46.mkv)
Author

Added subscriber: @berkon

Added subscriber: @berkon

#80059 was marked as duplicate of this issue

#80059 was marked as duplicate of this issue
Author

Blender menus broken.png
For some reason the screenshot which I mentioned in my description above was not uploaded. Here it is ...

![Blender menus broken.png](https://archive.blender.org/developer/F8847293/Blender_menus_broken.png) For some reason the screenshot which I mentioned in my description above was not uploaded. Here it is ...
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

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

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Start Blender with blender_debug_log.cmd script and use it normally. when Blender crashes, you'll find debug log, system info and crash.txt file.
please upload them.
I could render the file you gave on e56ff76db5 intel hd 6000, Darwin 18.x

Start Blender with `blender_debug_log.cmd` script and use it normally. when Blender crashes, you'll find debug log, system info and crash.txt file. please upload them. I could render the file you gave on e56ff76db5 intel hd 6000, Darwin 18.x
Author

Attached you can find the requested files. It doesn't really crash. I guess that is the reason why there is no crash file, but the whole machine became completely unusable, with the whole screen blinking black and white once. Before the screen became black/white, I saw the menus optically distorted again. After lets say 15sec I saw the border of the Blender main window and the render window again. I was able to click the red close cross. After a few seconds later Windows asked me if I want to stop the process, and I acknowledged. After that I copied the traces.

blender_debug_output.txt

blender_system_info.txt

Attached you can find the requested files. It doesn't really crash. I guess that is the reason why there is no crash file, but the whole machine became completely unusable, with the whole screen blinking black and white once. Before the screen became black/white, I saw the menus optically distorted again. After lets say 15sec I saw the border of the Blender main window and the render window again. I was able to click the red close cross. After a few seconds later Windows asked me if I want to stop the process, and I acknowledged. After that I copied the traces. [blender_debug_output.txt](https://archive.blender.org/developer/F8851693/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8851694/blender_system_info.txt)
Member

Please retry after a GPU driver update
this should be the correct file, or use their detector tool
https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-570
https://www.amd.com/en/support/

Please retry after a GPU driver update this should be the correct file, or use their detector tool https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-570 https://www.amd.com/en/support/
Author

Ok, I've updated from version 19.12.2 to 20.8.3. Unfortunately the issue is still there. I was able to capture the issue with screen recording. See attached: 2020-09-08 10-34-46.mkv

After the screen turns black ... just keep watching the video ... after a while the bare frames of the Blender windows become visible again. But as said this is not always the case. Sometimes the machine is completely forzen and I have to power it off.

Ok, I've updated from version 19.12.2 to 20.8.3. Unfortunately the issue is still there. I was able to capture the issue with screen recording. See attached: [2020-09-08 10-34-46.mkv](https://archive.blender.org/developer/F8853610/2020-09-08_10-34-46.mkv) After the screen turns black ... just keep watching the video ... after a while the bare frames of the Blender windows become visible again. But as said this is not always the case. Sometimes the machine is completely forzen and I have to power it off.
Ankit Meel changed title from Blender 2.9 freezes/crashes when user performs actions in Viewport during rendering to Computer freezes/crashes when user performs actions in Viewport during rendering in Blender 2.90 2020-09-08 10:59:14 +02:00
Member

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

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Ankit Meel changed title from Computer freezes/crashes when user performs actions in Viewport during rendering in Blender 2.90 to Radeon RX5xx: Computer freezes/crashes when user performs actions in Viewport during rendering in Blender 2.90 2020-09-08 10:59:52 +02:00
Member

Added subscribers: @AMEXif, @rjg

Added subscribers: @AMEXif, @rjg

Added subscriber: @iss

Added subscriber: @iss

No problems on
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001

#80453 is another report

No problems on Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001 #80453 is another report
Author

Just updated to Radeon Version 20.9.1. Now the crash caused by moving the render window is gone. So I think we can close this issue. Nevertheless I still have severe issues (Blender 2.90.1). E.g. when simply switching off the screen and turning it on again. Sometimes Blender freezes. Sometimes even the whole system freezes in such case. Then its even not possible to open the Taskmanager anymore ... only hard power off. Very annoying. :-( I'cant recommend the use Radeon RX 570 with Blender at all.

Just updated to Radeon Version 20.9.1. Now the crash caused by moving the render window is gone. So I think we can close this issue. Nevertheless I still have severe issues (Blender 2.90.1). E.g. when simply switching off the screen and turning it on again. Sometimes Blender freezes. Sometimes even the whole system freezes in such case. Then its even not possible to open the Taskmanager anymore ... only hard power off. Very annoying. :-( I'cant recommend the use Radeon RX 570 with Blender at all.

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Changed status from 'Needs Developer To Reproduce' to: 'Archived'
Richard Antalik self-assigned this 2020-10-27 05:06:20 +01:00

Thank you for update. The issues you are describing are not bugs in Blender itself, so we can't really do anything about them.
Since the issue is gone, I will close this report.

Thank you for update. The issues you are describing are not bugs in Blender itself, so we can't really do anything about them. Since the issue is gone, I will close this report.
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
4 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#80519
No description provided.