Monday, May 11th 2026

AMD Radeon GPU Drivers 26.5.1 Break Blender Cycles Path-Tracing Engine

AMD's latest Adrenalin Edition 26.5.1 WHQL Drivers are causing problems for Blender users, according to the latest Blender issue tracker. Blender 5.1.1 is crashing with these drivers, particularly when using the Cycles path-tracing render engine. The issue appears to be a ROCm runtime mismatch. Blender 5.1.1 uses ROCm 6 runtimes, but the latest AMD driver 26.5.1 only includes ROCm 7, leading to compatibility issues that prevent the application from running smoothly. Multiple users have reported crashes, and we now understand the background.

Developer involved in AMD evosystem Sahar A. Kashi confirmed that when a factory reset is performed and the system is installed from scratch, the amdhip64_6.dll file is removed, causing Blender Cycles to attempt loading ROCm 7 kernels. However, since Blender version 5.1.1 is compiled only for ROCm 6, this runtime mismatch results in application crashes. To resolve this issue on AMD GPU systems, users should install the older 26.3.1 drivers and use them until Blender version 5.2 is released, and the Cycles path-tracing render engine achieves full ROCm 7 compatibility.
Source: Blender
Add your own comment

8 Comments on AMD Radeon GPU Drivers 26.5.1 Break Blender Cycles Path-Tracing Engine

#1
Shihab
Well, DLL hell is eternal...

A quick googling led me to a download page for the HIP RT SDK page that lists v 6.x which naturally includes the runtime. Wouldn't installing it fix the issue without rolling back the drivers?
Posted on Reply
#2
Mysteoa
To resolve this issue on AMD GPU systems, users should install the older 26.4.1 drivers
There is no 26.4.1 driver. It got postponed, and released as 26.5.1. You meant 26.3.1
Posted on Reply
#3
WannaBeOCer
Skipping driver 26.5.1. It's causing random gray screens and consistent crashes in Crimson Desert (specifically when entering houses). Reverted back to 26.3.1 and everything is rock solid again. Hope these regressions get fixed in the next driver.
Posted on Reply
#4
m4gicfour
26.5.1 was causing random crash to desktop on Helldivers 2 for me, as well. Standing around on the ship, everything's fine. Deploy, and the game will crash after anywhere from a few seconds to 20 minutes or so. Rolling back to 26.3.1 and everything is perfect again.

The first driver in a LONG time that I have had any issues with. Makes me wonder whether they've started vibe coding the driver suite. I sure hope not.
Posted on Reply
#5
Gmr_Chick
Crap....I have that driver version installed and am currently running Blender 5.1.1, working on a project for Sims 4. I haven't experienced any problems with Blender crashing yet though. I'm using the EEVEE rendering engine.
Posted on Reply
#6
RejZoR
I don't have any issues so far.
Posted on Reply
#7
Shihab
Gmr_ChickCrap....I have that driver version installed and am currently running Blender 5.1.1, working on a project for Sims 4. I haven't experienced any problems with Blender crashing yet though. I'm using the EEVEE rendering engine.
It’s an issue with fresh installs and Cycles only. Upgrades from older drivers should still leave the old runtime, and Eevee is basically a traditional game renderer; it doesn’t do any tracing to speak of, so I don’t think it ever touches HIP/ROCm.
Posted on Reply
#8
Alain De Loin

26.5.2 Break Blender Cycles Path-Tracing Engine too

Posted on Reply
Nov 15th, 2026 07:48 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts