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
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.

8 Comments on AMD Radeon GPU Drivers 26.5.1 Break Blender Cycles Path-Tracing Engine
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?
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.
26.5.2 Break Blender Cycles Path-Tracing Engine too