Cycles Render Crash Windows/AMD RX Vega #65924
Labels
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
26 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#65924
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.7006
Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-18 23:46, hash:
e73647bf5bWorked: (optional)
system crash to black screen wile attempting to render a scene. Radeon driver is reset to default settings (even if it was on the default settings)
The crash is random,not crashing every time and not always at the same tile.
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)]
Added subscriber: @AssafNegev
#76983 was marked as duplicate of this issue
#73444 was marked as duplicate of this issue
#70137 was marked as duplicate of this issue
#72770 was marked as duplicate of this issue
#69271 was marked as duplicate of this issue
#67897 was marked as duplicate of this issue
#67371 was marked as duplicate of this issue
Added subscriber: @WhitecloudFX
Same issue here on my Radeon VII, Cycles crashes after a short rendertime and the screen turns black. Sometimes it turns on again after a short time with blender being turned into a white window, sometimes it totally crashes the whole system. However, rendering on additional graphics cards (3x Radeon VII) that aren't connected to the display seems to work quite well.
EDIT: The file I've added crashes reproduceably all the time when being rendered on the GPU connected to the display.SaturnVPacked.blend
Added subscribers: @Jeroen-Bakker, @ZedDB
@Jeroen-Bakker I'm guessing we need to beg AMD for some cards :P
@WhitecloudFX @AssafNegev which catalyst version are you guys using?
Adrenalin 2019- 19.5.2
Does updating to 19.6.2 help?
No, that makes ist even worse for some scenes.
No, I'm on 19.6.2 and the issue persists.
I did a clean install of the drivers and reset blender to defaults, didn't help.
U know what I just found out? When rendering in the image editor (not in a new window but in the user interface) things work out just fine. Just change that in the Header in the Render > Display Settings menu. I'll still continue testing with some other files but so far it seems to work.
using the image editor or other render display mode doesn't work for me.
it looks like it only happens withe files started on 2.79 and opened in 2.80.
don't know if it's related but i do get strange artifacts from time to time, only on display not saved to the final image.
looks like disabling particle/hair resolves the issue
new Radeon Drivers 19.7.1, recent blender 2.8 build, same issue.
Render with hair crashes.
@Jeroen-Bakker can you reproduce this on a Vega card?
2.8 RC1, not a crash, a full system freeze.
Not able to reproduce on linux/Vega64/AMDPro drivers. My system gets unresponsive, but that is hardware related, after the scene is rendered it gets responsive again. (I used the SaturnVPacked.blend). No crashes or blank screens.
I will setup windows on my machine and see if I can reproduce it on Windows.
Can anyone test if it renders ok when run from the command prompt? (blender.exe -b -f)
My gut feeling is a OS/driver related issue on heavy loads of the system, not something we can do about. What would help is a log/stacktrace when the crash happens.
Unable to reproduce with
65168825e0Note: that the OS is freshly installed.
Additional note. After retesting several times I received a
Split kernel error: invalid ray state. what makes blender halt due to data corruption. It is unclear that if driver resets the GFX card and thereby creating invalid buffers or that the driver writes corrupt data and therefore resets the GFX card. Will check.In the Event Viewer I see that the driver failed, but not the reason for it
When I disable the motion blur pass it seems to be work fine.
This is the mimimum blend file based on default cube. Only changed the samples to 1024 and enabled motion blur. You can also test with 32 samples and a larger tile size here it also crashes for me.
T65924_minimal.blend
Will check tomorrow if there is a recent change that introduces/enhanced this.
Also check https://community.amd.com/thread/229164 where similar issues was solved by:
The TDR did not work for me. It does not restart the driver when it fails, making the system halt. Note that this demonstrates that the blank screen is the OS trying to fix the state of the driver, by restarting it.
For now my idea is that the following happens:
Blender will stall as the state machine is in an invalid state.
@brecht, @ZedDB to test if this is really power supply related can we test on one of your machines if we can reproduce the issue.
Added subscriber: @brecht
i have done a few tests and I don't think it is the driver or the PSU fault.
I created a file like "t65924_minimal.blend" for version 2.79. T65924_minimal-2.79.blend
First I rendered in 2.79b (official) and it was OK. than I rendered it in 2.80RC1 and it didn't crash.
so i disabled the motion blur and rendered again in 2.80RC1 and it didn't crash. i enabled motion blur and rendered again it it froze the system.
i did it several times and every time i render first in 2.79b (official) and then render in 2.80RC1 it renders fine.
if disable motion blur > render > enable motion blur > render (in 2.80RC1 after rendering in 2.79b), the system freezes.
if i restart/shut down and render first in 2.80RC1 the system freezes.
the same behavior is happening with 2.79 master (downloaded a few days ago).
to me it seems like the issue is with changes made to cycles between 2.79b (official) and the development branches.
@AssafNegev It is a more complex than just saying it crashes due to changes in Blender so it is should be Blenders fault :-)
I was also able to reproduce the issue with the AMD Pro Drivers. I haven't been able to reproduce it on Polaris. Polaris uses a different OpenCL implementation in the AMD drivers, but the blender side is identical. We have contacted AMD for their insight.
i didn't think so :-)
I should work on my powers of deduction (just finished a 'Sherlock' binge) :D
@Jeroen-Bakker Thank you for your help & time.
i'll be happy to run any tests if needed.
new AMD driver 19.7.2 still freezes.
Added subscriber: @Aaron-Guo
Added subscriber: @idkartist3d
I'm having the same issue to a slightly worse degree;
I recently built a new computer and threw two Vega 56 cards in it with a 750w PSU.
I did some tests in Blender, and ran into this problem. I updated my drivers, tried lowering the card's power draw, tested Blender again, and it completely fried one of my GPUs - massive artifacting everywhere
So I drop another boatload of money on a 1000w PSU and another Vega 56, lower their power draw (both at -20% power limit, state 6 and 7 set to 1000mV in WattMan), and while going through tests, it black screens/crashes again.
No blender crash logs as far as I can find, and I just get the same "Display driver amdkmdap stopped responding and has successfully recovered." message in event viewer.
I don't want to keep throwing money at it when I truly don't know if getting yet another PSU upgrade will actually fix it, and I'm almost afraid to use blender now for fear that it's gonna fry another one of my cards.
Slightly off-topic but related enough, the reason I upgraded my computer in the first place is because a very similar issue (black screen, crashing) started happening on my old system with a GTX 970 while rendering in blender. I don't know if the cause is the same, but it's wildly frustrating when I can't even escape it with new hardware.
@idkartist3d
At this point I think that it is not hardware related. I tried different 2 motherboards 2 different CPUs, 3 different PSU (2x 750W + 1200W), 3 different GPU's 2 different drivers and 2 different OS's. My gut feeling is that it is an OS/driver related software error. The crash ain't consistent (not always when doing the same actions). We are still checking with AMD what could be the issue.
@Jeroen-Bakker Dang, thank you for your extensive testing! Guess my PSU upgrade was a bit unneeded, but luckily now I know I don't need to upgrade again!
Hope the folks at AMD can figure it out soon, and again I appreciate your dedication to the issue - support like this is why I love blender :)
I can confirm the motion blur/hair issue on my machine as well. The SaturnVpacked.blend renders just fine with motion blur and Hair disabled and the system freezes reproduceably after a short time when either one of these functions is on.
I'm currently rendering on CPU+GPU
Threadripper 2990WX
4x Radeon VII, running the Adrenaline 19.7.3 driver
Added subscriber: @blenderscuba
Added subscriber: @Magusbear
AMD has confirmed that it is an issue inside the driver. They have solved the issue, but don't know which driver it will be available in.
For now I will keep this task open for other people to find.
Added subscribers: @brunocb, @lichtwerk
Added subscriber: @ndru
Changed status from 'Open' to: 'Resolved'
Closing Issue, driver has been released. users need latest driver for correct result.
Added subscriber: @MarinMyftiu
Dont think new drivers have solved anything though. On my side:
Vega rx56 on one systen, triple rx56 on the other, latest adrenalin 19.11.3 driver & blender 2.81: still experiencing whiteouts and driver resets during various video renders. Other details:
Added subscriber: @nah
omg I finally found a thread about the same issue as I have! I've been looking around for ages but all the problems I found weren't exactly the same as mine, I'm gonna try the new drivers and see if it works, but I'm very excited to find others with the same problem :)
welp, unfortunately updating my drivers to the newest version and absolutely nothing happened. When I press render my whole computer locks up, monitor goes black for a few seconds and then blender doesn't respond. I opened blender in a terminal and this is exactly what came up when I pressed render:
Cycles: compiling OpenCL program split_subsurface_scatter...
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Cycles: compiling OpenCL program split_shadow_blocked_dl...
Cycles: compiling OpenCL progrAL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
am split_shadow_blocked_ao...
Cycles: compiling OpenCL program split_hAL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
oldout_emission_blurring_pathtermination_ao...
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Cycles: compiling OpenCL program split_lamp_emission...
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Kernel compilation of split_subsurface_scatter finished in 7.40s.
Cycles: compiling OpenCL program split_direct_lighting...
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Kernel compilation of split_shadow_blocked_ao finished in 20.25s.
Kernel compilation of split_holdout_emission_blurring_pathtermination_ao finished in 20.20s.
Cycles: compiling OpenCL program split_indirect_background...
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Cycles: compiling OpenCL program split_shader_eval...
Kernel compilation of split_lamp_emission finished in 16.91s.
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Cycles: compiling OpenCL program split_bundle...
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Kernel compilation of split_shadow_blocked_dl finished in 32.17s.
Kernel compilation of split_direct_lighting finished in 25.76s.
Kernel compilation of split_indirect_background finished in 15.66s.
Kernel compilation of split_shader_eval finished in 15.81s.
Kernel compilation of split_bundle finished in 22.15s.
Hope this helps at all...
Changed status from 'Resolved' to: 'Open'
Ok I will open this issue and ask AMD for support.
Please note that this is not actual blender related issue, but related to AMD/Windows.
Will also plan some time this week to do more testing.
We ask it all the time, but when having hardware issues, could you please provide us with the up-to-date
system-info.txt. The information inside the system-info.txt actual tell us something and helps us to reproduce OS/Driver related issues.Without this information I might spend hours on building machines that I could have spend on fixing stuff and make blender better :)
Ok here's my basic system specs:
OS: Windows 10.0.18362 Build 18362 (x64)
CPU: AMD Phenom II x4 910e, 2.6 GHz 4 cores (64-bit CPU)
GPU: RX 470 Sapphire
Motherboard: ASUS M3N78 PRO ACPI
Ram: 8 Gb of DDR2 RAM
Page file space: 5.25 Gb
Yeah, some of the stuff here is pretty old but I don't think that's the direct cause of the issue. Hope this helps :)
I was also super excited to hear that the drivers were released, but after updating I still crashed within 10 minutes of rendering :/
To add, I did notice that, like @MarinMyftiu , when I disabled the main display GPU, it rendered for hours just fine on my other one.
Sorry that you're still stuck with this issue when AMD should've already fixed it, Jeroen -- your time on this is very much appreciated though!
Also: @nah, the system info he's asking for you generate in blender under help > save system info~
system-info.txt
oh thanks, here's the text file{F8167274}
Cycles render crash GPU RX Vega 56to Cycles Render Crash Windows/AMD RX VegaTDRis a mechanism build inside windows that makes sure that the GPU driver where a screen is attached will keep responding. If windows detects that the GPU driver is not responsing (sending a command to the GPU driver, but not getting a response back quick enough) it will kill the driver and restart the driver. As a user you see this as the screen will be blanked.When the GPU is restarted again all existing commands in the GPU are gone, but blender is waiting for a result that will never be send back. The difference with the new driver is that is used to reset when rendering, now it resets even when compiling. I will check with AMD on this topic.
@idkartist3d please note that you're not using the latest drivers. (not that that makes a difference)
@nah seems like you have a polaris card, I haven't been able to reproduce it on any polaris card I have here, but I don't have any polaris cards on my windows systems. note that 8GB might not be enough RAM to actually compile cycles.
Added subscriber: @pianogineer
If it looks like a driver issue, why isnt it happening on 2.79 and why is motion blur affectin it ?
Also, at least in my case, the files I am working on were created on 2.79 and then ported to 2.81 mainly to use the new denoiser, so maybe it happens to files ported from previous versions..
It is not effective in Blender 2.79 as the opencl implementation is different. Blender 2.79/AMD wasn't able to stress the system. It is not related to motion blur at all, it can happen with any complex scene. As mentioned above it is related to Windows + AMD driver with a complete explanation so I am not going to repeat myself again. Please read the thread.
Wait but my RAM doesn't go up at all when compiling kernels so I don't think that's the problem
AMD has found an issue inside cycles. It seems that some data isn't initialized. Solution would be to clear the memory up front or always initialize all the data we pass to the kernel. The specific data is the
object_motionfield in__constant KernelData *data. I will try to confirm their findings and make a possible fix.Great job! Lets hope this is fixed for good, it was one of the reasons why I kept using 2.79...
Let us know when you've found something :)
Added subscriber: @Forshu-2
This issue was referenced by blender/cycles@9d022af85a
This issue was referenced by
f5e37af5a8Changed status from 'Open' to: 'Resolved'
Changed status from 'Resolved' to: 'Open'
woah, a bunch of stuff happened
Added subscriber: @nahh
So uh (I'm "nah" btw, just forgot my old login) I found an update in the drivers but still had the same issue. Not trying to rush or anything, but just wondering if this is actually still being worked on since this feed seems a little quiet
Added subscriber: @MaciejJutrzenka
Looks like 2.81a fixed it, so it was a blender bug after all. Glad to know its out anyway 😁
Added subscriber: @HADESBLACK
Well, I have the issue that Blender just stops rendering after a while and freezes. I have to kill Blender manually using the task manager.
This happens in 2.81a and in 2.82 beta as well.
However, this only happens, when I have Radeon Software installed, regardless of the Version or Edition. I tried Adrenalin 2018, 2019 and 2020. Nothing works.
When I uninstall my graphics driver completely in the device manager, Blender works flawless for me; 2.81a and 2.82 beta.
So. I guess, no GPU driver for me, until the issue is resolved. I'll survive it.
Note that I still need to test their latest drivers they released a week ago. But will test this week.
@MarinMyftiu AMD updated their drivers, but still the heavier the scene the more likely that it will happen. As it only happens on Windows, and not on Linux and only on the Display attached card it seems to be a driver issue.
Mine still crashes trying to render the default cube in cycles
Removed subscriber: @blenderscuba
Yep, still crashes
Vega 56
I7 8700k
Blender v2.82 Alpha 2020-01-02 17:14
Changed status from 'Confirmed' to: 'Resolved'
Added subscribers: @tibor81, @iss
Changed status from 'Resolved' to: 'Confirmed'
Added subscriber: @Cronos
Any updates on this yet? :
Judging from this comment,
I'm assuming the ball is in AMD's court at the moment. I've been watching this thread since July, so I hope you're ready to be strapped in for the long haul lmao
rip, I hope they fix it soon. Can't wait to resume using cycles
Hi everyone, just installed the 2.80 version ( 2.80a to slow on my pc ) fresh update driver from AMD and shes flying as before .:):) happy cycle to everyone
The stable 20.1.3 driver or the optional 20.2.1 ?
They haven't put out any fixes for this yet, or if they have they didn't include it in any release notes.
Not sure what they're on about tbh
Hmmmm the render that crashed before, didn't crash now on 20.1.3, but it was quite random for me, so need more time to see if it crashes or not.
03.02 2020 release
Tried 20.1.3 and 20.2.1 both crash from time to time on long renders :P
Vega
It does on old file, I recently bought 3d model made in blender 2.79 in version for 2.8 works fine. My old file still freezes once I hit cycles, on GPU computing previews are slow but the render is still 30-40% faster.
It can't just be one side to blame... it worked fine on my gear till stopped.. no updates to any hardware or software were done pron this, nothing suddenly it went off and we hunting for nameless fox. I tried any driver combinations with any blender it exist and for me it looks like windows issue. There's only few updates records but I remember that W run quick updates which are not in books. ??
If they haven't fixed the issue in any driver updates, it doesn't matter which driver or which version of blender you use. Any patterns you may be seeing in what files work/don't work is random at best. You do have a point about Windows being the only OS effected here, though.
Really, I think the only thing anyone can learn from this is to not buy AMD cards in the future lol (I certainly won't be). Nvidia wouldn't have let this issue exist for almost 8 months :/
Ye we know, Cronos just got my hopes up to try out new drivers. :P
Never buying amd gpu in the future, so many problems with drivers and lack of support. I've heard amd has a developer on payroll just to do opencl in cycles and even with that it has bugs like this.
Prolly gonna sell Vega and go for Nvidia.
Lol you do realize the person you're talking about is the one assigned to this task, right? https://devtalk.blender.org/t/4-february-2019/5255
I honestly feel like he's done what he can on this, he can't control how/when they roll out fixes on drivers.
Regardless, I'm kinda in the same boat. Wait for the 30 series to be announced/released, and pick up a card then - they're rumored to be pretty cheap, so either nab a new one, or a massively price reduced 20 series :/
Yes, i'm not saying that they're bad at their job, i'm just saying that amd have person working on opencl in cycles full time, and even with this we have a bug like this. Not even a small one, you can't render big scenes on vega, it makes it a costly paper weight for my use case. And rendering on cpu when you have such a monster of a gpu is so stupid. Even my old gtx 650 never had a driver crash through the 8 years i was using it.
Ye prolly gonna go for 20 series if i'll find good price on used one :P
Woo, everyone is jumping to nvidia because amd sucks, we sure we don't have any paid nvidia panicker here😂
Not saying it doesn't suck to have this issue, but looks more complex than just the driver to me, it's more a windows/blender implementation that happens on amd cards. Yes the driver fails, but that can also be because something else screws up.
Also it was fixed in some cases; personally I have 2 systems & 4 vega56s and not encountering it anymore for months, and thats on 6gb+ scenes rendering for up to 1 week and same for other people,..
Have you guys done the following besides clean install:
Hehehe i wish :P
It's quite random with crashes, from my experience it crashes more often if you have hair or dense fur in render.
Tried deleting kernel cache (which was around 2 gigs)
Tried resetting OC to stock
Can you write or point to a guide what gpu register entries have to be deleted ? I have not tried that one, i've used DDU before installing new drivers, not sure if it does it by itself.
Hmm, I think I went and deleted some amd keys myself in some lost area of the infinite & stupid registry, dont have a pc at hand now to look for them.
There's also this amd cleaning tool:
https://www.amd.com/en/support/kb/faq/gpu-601
... I also messed with the 'tdrdelay' key and those other similas keys, think I pumped them up to 120 seconds or something like that...that might help too because I notice blender seems totally frozen sometimes for 10-20 seconds, even in eevee.
Tried with the tdr delay, the only thing it changed is how long the driver was down, by default it almost instantly recovered, after change the display just froze for 120 and then recovered.
Gonna try the cleaning tool, really hope it helps.
And i don't care if it's a driver issue or a windows one, it crashes in stock when i need it working :P
Even if it's not amd's fault it's a pretty big reason to look the green side, at least for me.
Hahaha, I know, this stuff definitely sucks and it feels bad when vega was such a great rendering value; 1080ti ballpark for half the price.
Hope that cleaning app works and those tdr-related keys, I think there are 4 of them to tweak..
Added subscriber: @all
Please @MarinMyftiu, @Forshu-2, behave this is a bug tracker, not a forum. Adding noise in comments to this ticket that doesn't have value just makes it harder for issues to be solved!
Removed subscriber: @all
Sorry it's jut really frustrating that this issue was opened a year ago and the renders still crash.
The amd cleaning utility didn't help, but I installed the drivers that were shipped by Asus with my card 17.12 and that seems to fix the problem a bit, it still crashes but less often.
Yes, it is, been there and I can't figure what it was.
Just checked and I have both TdrDelay and TdrDdiDelay set at 90.
Another thing I dont have clear is; does this only happen on files created in 2.79 or new ones too?
Yet another thing that came to my mind is that I had an ssd upgrade and windows reinstalled on both machines around the time I stopped having issues,.. don't know if that is just a coincidence and that is quite drastic.. but if you have a spare ssd and some time in your hands its worth a try.
All my files are created new in 2.8, but most assets in them were imported from 2.79, and then i just appended them from one 2.8 file to another.
Tried playing with those Tdr values but like i said, it just changed how long the driver was down before recovery for me.
Gonna try reinstalling windows when i'll have time, but for now going to stick with occasional crashes on 17.12 drivers
I have an SSD and I reinstalled windows, didn't work. AMD just came out with a new update, didn't work... I really hope they fix this soon :(
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.1 26.20.15019.1003
Latest Drivers
Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash:
77d23b0bd7Crashes when rendering hair.
Updated to latest RADEON drivers, 20.2.2
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.2 26.20.15019.15019
Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash:
77d23b0bd7Worked: (optional)
Blender crashes when rendering hair
Added subscriber: @Matthewv1998
This comment was removed by @Matthewv1998
Ok, i’m sorry i really didnt mean to put this up for grabs, i just ment to comment!
But, anyway! I have the same issue
Sys specs
Windows 10, (completely blank install)
56gb of ram
2x v56
Amd 20.4.1 drivers
Broken version
2.82a.
I have a bit of a twist on this one. Single gpu is stable, however it completely craps out in dual gpu mode.
This is one of the characteristics of this crash: it only happens when the display GPU renders. In your case the single GPU might be the other non-display connected GPU (might try switching to the other option in the settings)... Other than that, try disabling motion blur, that has worked in some instances... For me new drivers and some cleanup solved the issue on both systems and all 4 vega 56.
Added subscriber: @FluxTape
Blender still crashes whenever I use cycles render at all, even in preview mode.
It's been almost a year since this bug was reported. Give up. Buy an Nvidia card. This bug isn't going to be fixed any time soon, if at all. Sorry.
Added subscriber: @ClaymoreTF2
Is this still not fixed? I sold my vega 5 months ago, and this bug still not fixed, fun...
My best guess is at this point they're just gonna wait until the cards are outdated enough that most people replace/upgrade them, until there's nobody left to ask for a fix :/
Kinda "ignore it till it goes away", ya know? I emailed AMD for an update, and they just gave me some basic troubleshooting steps.
I probably should've expected that after spending hundreds of dollars on a product that can't perform a basic task without fucking imploding, that the response to asking for a fix is a canned copy-paste basically telling me to buy a new card 🙃
Also: Happy almost 1-year birthday to this thread! 🎉 May as well close it, as we all know this will never get fixed.
Added subscriber: @Hexcate
I'm also having this issue w/ a RX Vega 64 and Radeon 20.7.2
It's nice to know I've got a 14.2 Teraflop brick when it comes to actually doing work.
Added subscriber: @DragonAlex
I've had same issue with my RX5700. When using GPU openCL rendering blender was crushing each time.
To me solution was to use not the latest driver (radeon 20.8.1) but the latest recommended driver (radeon 20.4.2 (WHQL)).
Now the Issue is gone.
I suggest you to try the same thing.
@Jeroen-Bakker Is it possible to add a workaround that renders volumes only on CPU while rendering everything else on GPU?
Oh man, I was so inside my own head that I forgot to report back to this thread!
Sooo, long story short, I got super fed up with the situation and posted a thread to /r/amd . Luckily the post got a tonne of visibility, and most importantly the attention of some AMD staff. I got into contact with them, and they got me in touch with a technical support engineer, who told me
"As I understand, based on your Service Request that you are experiencing crashes and hang in Blender with your Vega 56 Graphics.
The issue affecting Vega series graphics and Blender was under investigation and we believe that a fix coming out in the next Radeon Pro Software for Enterprise driver version 20.Q2.1 will resolve your issue."
He hooked me up with some Beta drivers, and although I've had a bluescreen or two, I no longer freeze and cut to black! So: If there's even anyone left that hasn't been beaten down by the harsh passage of time relative to the ever-marching exponential progress of technology (caved and bought a new card), go and download the newest Radeon Pro Enterprise drivers and see if they fix it for ya! And shoutout to Mickey and Ali from AMD ahah~ ❤
You are right, last driver is working for me.
Added subscriber: @chingis
Added subscriber: @ThomasDinges
Changed status from 'Confirmed' 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 your report, 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/