Red/Green artifacts display on screen and then Blender 2.8 crashes #68748

Closed
opened 2019-08-16 21:42:33 +02:00 by Eli Johnsrud · 11 comments

System Information
Operating system: Windows 10 10.0.18362 Build 18362
Graphics card: Radeon RX 570 Series Have tried Driver Versions Adrenalin 2019 19.2.3 as well as Adrenalin 19.5.2

Blender Version
Broken: Blender 2.8
Worked: Blender 2.79

Short description of error
When working in Blender 2.8 (manipulating a point on the default cube or anything else) the screen freezes with red artifacts on the screen. Shortly after Blender crashes and a notification that Radeon Wattman crashed pops up. I have to close Blender through the task manager and then reload all Radeon software. I cannot recreate this error in Blender 2.79. I even attempted to force the issue by running a FurMark GPU stress test while rendering a .blend file in Blender 2.79 with no issues.

Exact steps for others to reproduce the error
Doing anything in Blender 2.8 causes the error

**System Information** Operating system: Windows 10 10.0.18362 Build 18362 Graphics card: Radeon RX 570 Series Have tried Driver Versions **Adrenalin 2019 19.2.3 as well as Adrenalin 19.5.2** **Blender Version** Broken: Blender 2.8 Worked: Blender 2.79 **Short description of error** When working in Blender 2.8 (manipulating a point on the default cube or anything else) the screen freezes with red artifacts on the screen. Shortly after Blender crashes and a notification that Radeon Wattman crashed pops up. I have to close Blender through the task manager and then reload all Radeon software. I cannot recreate this error in Blender 2.79. I even attempted to force the issue by running a FurMark GPU stress test while rendering a .blend file in Blender 2.79 with no issues. **Exact steps for others to reproduce the error** Doing anything in Blender 2.8 causes the error
Author

Added subscriber: @Kortike

Added subscriber: @Kortike
Author

Installed and tested Blender 2.8 on an identical build (sorry for the mental lapse I ignored the fact that we just built two of these), and was unable to replicate the issue. The only differences between the computers is the software that is installed. I am going to do a full wipe of my PC and install Blender 2.8 from a clean slate. I'll test it out and if there are no issues I will install the software/python dependencies/Visual Studio etc... one by one and see what I can find. Otherwise it may be a hardware issue with the GPU, but I would think that FurMark and Blender 2.79 running at the same time would crash it as well.

Installed and tested Blender 2.8 on an identical build (sorry for the mental lapse I ignored the fact that we just built two of these), and was unable to replicate the issue. The only differences between the computers is the software that is installed. I am going to do a full wipe of my PC and install Blender 2.8 from a clean slate. I'll test it out and if there are no issues I will install the software/python dependencies/Visual Studio etc... one by one and see what I can find. Otherwise it may be a hardware issue with the GPU, but I would think that FurMark and Blender 2.79 running at the same time would crash it as well.

Added subscriber: @rjg

Added subscriber: @rjg

Unless you have already wiped the affected machine, you could run Blender in debug mode to get a stack trace. This would already help to narrow down the issue.

In the install directory of Blender you can find a blender_debug_log.cmd. Double-click on it to start Blender in debug mode and try to make it crash again. Once Blender has been terminated it will open up the Windows Explorer to the created log file.

Thank you for putting in effort and investigating this yourself.

Unless you have already wiped the affected machine, you could run Blender in debug mode to get a stack trace. This would already help to narrow down the issue. In the install directory of Blender you can find a `blender_debug_log.cmd`. Double-click on it to start Blender in debug mode and try to make it crash again. Once Blender has been terminated it will open up the Windows Explorer to the created log file. Thank you for putting in effort and investigating this yourself.

Added subscriber: @merlinstail

Added subscriber: @merlinstail

New drivers have been published on the 12th August. Try the detect and install utility available from AMD here

New drivers have been published on the 12th August. Try the detect and install utility [available from AMD here](https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-570)
Member

Added subscriber: @EAW

Added subscriber: @EAW
Member

Radeon™ Software Adrenalin 2019 Edition 19.7.5 Release Notes

Known Issues

  • Some system configurations may experience green color corruption after install of Radeon Software when running Windows® 10 May 2019 update.

Radeon™ Software Adrenalin 2019 Edition 19.8.1 Release Notes

Fixed Issues

  • Some system configurations may experience color corruption after install of Radeon Software when running Windows® 10 May 2019 update. Issue is resolved in the latest Windows® Update 18362.267 (KB4505903)

It might be the Windows 10 May update according to AMD.

I was trying to help another user who has had a similar issue, but [[
https://developer.blender.org/T68519 | they report that updating both Windows 10 and their AMD graphic drivers has not fixed the issue.]]

All I could find in that Windows 10 update's notes regarding color is

  • Addresses an issue that may display colors incorrectly when viewing an image on 10-bit display panels.
  • Addresses an issue that may prevent you from changing the display brightness when using certain graphics drivers after resuming from Sleep or Hibernation.
> **[Radeon™ Software Adrenalin 2019 Edition 19.7.5 Release Notes ](https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-7-5)** > > **Known Issues** > > - Some system configurations may experience green color corruption after install of Radeon Software when running Windows® 10 May 2019 update. --- > **[Radeon™ Software Adrenalin 2019 Edition 19.8.1 Release Notes ](https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-8-1)** > > **Fixed Issues** > > - Some system configurations may experience color corruption after install of Radeon Software when running Windows® 10 May 2019 update. Issue is resolved in the latest [Windows® Update 18362.267 (KB4505903) ](https://support.microsoft.com/en-ca/help/4505903/windows-10-update-kb4505903) > > It might be the Windows 10 May update according to AMD. I was trying to help another user who has had a similar issue, but [[ https://developer.blender.org/T68519 | they report that updating both Windows 10 and their AMD graphic drivers has not fixed the issue.]] All I could find in that Windows 10 update's notes regarding color is > - Addresses an issue that may display colors incorrectly when viewing an image on 10-bit display panels. > - Addresses an issue that may prevent you from changing the display brightness when using certain graphics drivers after resuming from Sleep or Hibernation.

@EAW That explains the issue.

@Kortike Does installing KB4505903 solve the issue for you?

@EAW That explains the issue. @Kortike Does installing KB4505903 solve the issue for you?
Author

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Eli Johnsrud self-assigned this 2019-08-21 12:57:20 +02:00
Author

The PC sat powered down for 4 days, I just booted it up this morning and within 30 seconds of loading Windows the red artifacts displayed on the screen and then the display/gpu reset multiple times before correcting itself. First time I was able to get the error without having Blender open. Looks like the card needs to be RMAed. Thanks for your help guys.

The PC sat powered down for 4 days, I just booted it up this morning and within 30 seconds of loading Windows the red artifacts displayed on the screen and then the display/gpu reset multiple times before correcting itself. First time I was able to get the error without having Blender open. Looks like the card needs to be RMAed. Thanks for your help guys.
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#68748
No description provided.