Wednesday, October 29th 2025

by Nomad76 Yesterday, 11:30

AMD has released its latest Adrenalin Edition 25.10.2 driver, adding support for the new Ryzen AI 5 330 processor alongside Battlefield 6 (DX12) and Vampire: The Masquerade - Bloodlines 2 (DX12). This new version also debuts Work Graphs support on Radeon RX 9000 series GPUs and expands Vulkan capabilities.

According to the release notes, the update resolves several issues, including crashes in The Last of Us Part II, Firebreak, and NBA 2K25, as well as graphical corruption in GTFO, Serious Sam 4, and VTOL VR. AMD also addressed stuttering seen in Baldur's Gate 3 and with certain VR headsets. A temporary workaround for VR users experiencing stutter at 80-90 Hz is to adjust the headset's refresh rate. AMD confirmed in the release note that several known issues (intermittent application crashes, driver timeouts, texture flickering, or corruption) with Cyberpunk 2077, Battlefield 6, Roblox Player, and Counter-Strike 2 (DX11) are yet to be resolved.

DOWNLOAD: AMD Software Adrenalin Edition 25.10.2 WHQL

AMD Ryzen AI 5 330

Battlefield 6 (DX12)

Vampire: The Masquerade - Bloodlines 2 (DX12)

VK_EXT_shader_float8

VK_KHR_video_decode_vp9

VK_KHR_video_encode_av1

VK_KHR_video_encode_quantization_map

VK_AMDX_dense_geometry_format

VK_KHR_shader_untyped_pointers

VK_KHR_present_mode_fifo_latest_ready

VK_EXT_present_mode_fifo_latest_ready

VK_KHR_present_id2

VK_KHR_present_wait2

Initial introduction of Work Graphs support on Radeon RX 9000 series graphics products.

When downgrading to previous version of AMD Software: Adrenalin Edition it is recommended to use AMD Cleanup Utility.

USB-C power charging has been disabled for Radeon RX 7900 series graphics products. Users requiring this feature are recommended to use AMD Software: Adrenalin Edition version 25.3.1.

Using a magic string that can be configured in SBIOS by customers, the driver will determine what codec must be disabled, this includes HEVC, H264, VP9 and AV1. This is available on Radeon RX 7000 and 9000 series graphics products.

New Game Support and Expanded Vulkan Extensions Support is available to Radeon RX 7000 and 9000 series graphics products.

Intermittent application crash may be observed while playing The Last of Us Part II on Radeon RX 7900 series graphics products.

Intermittent application crash may be observed while playing FBC: Firebreak on some AMD Ryzen processors such as the Ryzen AI 300 series and the Ryzen 8000 series.

Corruption (missing scan travel lines) may be observed while playing GTFO on Radeon RX 7000 series graphics products.

Stutter may be observed while playing games with some VR headsets at 80 Hz or 90 Hz refresh rate on some AMD Radeon Graphics Products such as the Radeon RX 7000 series. Users experiencing this issue are recommended to change the refresh rate as a temporary workaround.

Intermittent application crash may be observed while playing NBA 2K25 in MyCareer mode on Radeon RX 9070 series graphics products. AMD is actively working on a resolution to be released as soon as possible.

Stutter may be observed While playing Baldur's Gate 3 on some AMD Radeon Graphics Products such as the Radeon RX 9000 and 7000 series.

Texture flickering or corruption may appear while playing Serious Sam 4 on Radeon RX 6000 series graphics products.

Shadow corruption on left eye is seen while playing VTOL VR on Radeon RX 7000 series and Radeon RX 9000 series graphics products.

CVE-2023-4969 (RDNA only), CVE-2024-21969 (RDNA only), CVE-2024-36323, CVE-2024-36325, CVE-2024-36333, CVE-2025-61964, CVE-2025-61965, CVE-2025-61966, CVE-2025-61967, CVE-2025-61968

Intermittent application crash or driver timeout may be observed while loading a saved game in Cyberpunk 2077 with Path Tracing enabled. AMD is actively working on a resolution with the developer to be released as soon as possible.

Intermittent application crash or driver timeout may be observed while playing Battlefield 6 on AMD Ryzen AI 9 HX 370

Intermittent application crash or driver timeout may be observed while playing Roblox Player (Car Zone Racing & Drifting) when task switching between media on Radeon RX 7000 series products.

Texture flickering or corruption may appear while playing Battlefield 6 with AMD Record and Stream on some AMD Graphics Products.

Radeon Anti-Lag 2 option may not be available while playing Counter-Strike 2 (DX11) with Radeon Anti-Lag 2 enabled on some AMD Graphics Products, such as the Radeon RX 9070 XT. Users experiencing this issue are recommended to use the Vulkan API as a temporary workaround.

Related News

Issues with the installer. Some entries missing in .inf. Unable to install it on my 680M's laptop.



The driver is said to support it.

EDIT: a "combined" version landed and seems to work on my system.

drivers.amd.com/drivers/whql-amd-software-adrenalin-edition-25.10.2-win10-win11-oct-rdna3-combined.exe

based on the post I see on reddit inf files are missing for RDNA 1/2 so won't install on these also.

Also this link is broken.

drivers.amd.com/drivers/whql-amd-software-adrenalin-edition-25.10.2-win10-win11-oct-rdna3-combined.exe

Videocardz has a mirror up for the driver that Supports RX 5000/6000/7000/9000

videocardz.com/driver/amd-radeon-software-adrenalin-25-10-2

Work Graphs Support

Initial introduction of Work Graphs support on Radeon RX 9000 series graphics products.

LastDudeALiveI'd never heard of this before, so I went down a fun little rabbit hole. From what I can tell, it's essentially a DX12 feature that enables the GPU to create its own rendering work, meaning the CPU gives it less instructions. I'm not a game developer, so I don't understand all the technical aspects, but it seems cool, a way to minimize CPU limits in game rendering. It was released in 2024, so it's a fairly new DirectX feature.

When it released, Nvidia immediately added support for it to Ada and Ampere with a driver update.

The more time goes on, the more evidence there is that RDNA 4 was prematurely released. Extremely important features like FSR 4 override, ROCm, and now just plain DirectX components weren't ready for Day 1 release? It feels like AMD saw the Blackwell performance and pricing and thought they could undercut the 5080 with the 9070 XT, so they pushed the launch up, only to have it competing against the 5070-Ti, with the dearth of features forcing it to be significantly cheaper.RDNA4 wasn't premature, it was exactly as advertised. A cheap and cheerful (R&D/production cost wise) stopgap until UDNA. No point wasting R&D money on a low margin sector like gaming, when UDNA will theoretically let them spend money on AI GPU design which they can then cut down for gaming.

I was genuinely surprised it was as good as it is. Was expecting something much less power efficient, just slapped together.

razaronRDNA4 wasn't premature, it was exactly as advertised. A cheap and cheerful (R&D/production cost wise) stopgap until UDNA. No point wasting R&D money on a low margin sector like gaming, when UDNA will theoretically let them spend money on AI GPU design which they can then cut down for gaming.

I was genuinely surprised it was as good as it is. Was expecting something much less power efficient, just slapped together.Fair, and Blackwell was the same thing. An Ada refresh with FP4 to enable MFG and better scheduling and power management. I'm more talking about the specific release timeline. All these driver updates adding seemingly basic features to RDNA 4 make it feel like it was released 6 months earlier than they initially planned.

Maybe the fix the power consumption bug i found with my radeon 7800xt hellhound a few hours ago. Gaming profiles are not applied, broken, or the power consumption readout is totally wrong. GPU Clocks are not properly applied or the in game report display from the radoen drivers is broken in windows 11 pro 25h2.

_roman_Maybe the fix the power consumption bug i found with my radeon 7800xt hellhound a few hours ago. Gaming profiles are not applied, broken, or the power consumption readout is totally wrong. GPU Clocks are not properly applied or the in game report display from the radoen drivers is broken in windows 11 pro 25h2.i don't have any of these issues on my XTX.

But i'm on Win 10 so maybe that is specific to Win 11

Using a magic string that can be configured in SBIOS by customers, the driver will determine what codec must be disabled, this includes HEVC, H264, VP9 and AV1. This is available on Radeon RX 7000 and 9000 series graphics products.I'm utterly confused by this bit. Can someone clarify it for me? :wtf:

LastDudeALiveI'd never heard of this before, so I went down a fun little rabbit hole. From what I can tell, it's essentially a DX12 feature that enables the GPU to create its own rendering work, meaning the CPU gives it less instructions. I'm not a game developer, so I don't understand all the technical aspects, but it seems cool, a way to minimize CPU limits in game rendering. It was released in 2024, so it's a fairly new DirectX feature.

When it released, Nvidia immediately added support for it to Ada and Ampere with a driver update.

The more time goes on, the more evidence there is that RDNA 4 was prematurely released. Extremely important features like FSR 4 override, ROCm, and now just plain DirectX components weren't ready for Day 1 release? It feels like AMD saw the Blackwell performance and pricing and thought they could undercut the 5080 with the 9070 XT, so they pushed the launch up, only to have it competing against the 5070-Ti, with the dearth of features forcing it to be significantly cheaper.Nobody use NVIDIA for Work Graphs. This API is designed for AMD by AMD. NVIDIA had another solution for this problem, but Microsoft canned it because of Xbox. So they have to redesign the hadware for Work Graphs. But sure, it's a standard, so they have to support, but they are not very happy about it.

Looks like this driver has finally done away with stupid "Ai" AMD Chat thing that was constantly being pre-selected in driver install. Thank god, that nonsense was so annoying and it was like 30GB in size.

SuperJoeNobody use NVIDIA for Work Graphs. This API is designed for AMD by AMD. NVIDIA had another solution for this problem, but Microsoft canned it because of Xbox. So they have to redesign the hadware for Work Graphs. But sure, it's a standard, so they have to support, but they are not very happy about it.Work Graphs are a component of Direct 3D12 that allows shader threads to directly request other shaders to work, instead of having the CPU issue all instructions. It's not an external software. At least, that's what I've gathered by reading these articles from Microsoft and Nvidia.

In any case, if it is an AMD-driven feature, that's even more surprising that RDNA 4 didn't support it until now. That just emphasizes my point that RDNA 4 seems to be prematurely released. There wasn't enough time before the launch to integrate this and other features that should have been enabled from Day 1.

LastDudeALiveWork Graphs are a component of Direct 3D12 that allows shader threads to directly request other shaders to work, instead of having the CPU issue all instructions. It's not an external software. At least, that's what I've gathered by reading these articles from Microsoft and Nvidia.

In any case, if it is an AMD-driven feature, that's even more surprising that RDNA 4 didn't support it until now. That just emphasizes my point that RDNA 4 seems to be prematurely released. There wasn't enough time before the launch to integrate this and other features that should have been enabled from Day 1.Work Graphs are an independent API in D3D12 that enables task-based GPU scheduling, separate from the traditional graphics pipeline, and the existing command lists and barriers do not work the same way. It's not just a component, it fundamentally changes the D3D12 pipeline.

You should read the GPUOpen articles. They are much more informative about Work Graphs.

AMD prepared a Work Graphs driver for RDNA 4 graphics cards much earlier. Developers who requested it were able to access it. Now it has been included in the release drivers. Developers get access to these features much earlier than the end users. AMD already has a D3D12 implementation for a feature that Microsoft plans to introduce next spring, but users won't be able to access it before the end of next year. It doesn't really matter, because devs can use it now.

Not a Potato

RejZoRLooks like this driver has finally done away with stupid "Ai" AMD Chat thing that was constantly being pre-selected in driver install. Thank god, that nonsense was so annoying and it was like 30GB in size.This was the one thing I kept submitting to AMD as an issue since it got included earlier this year. They probably re-reviewed their own telemetry and found that only a few users actually install it.

Now if they can just stop using that "AMD Install Manager" in the big driver package (but I can agree that it can be part of the "AMD Auto-Detect and Install Tool"), that would be great.

USB-C power charging has been disabled for Radeon RX 7900 series graphics products. Users requiring this feature are recommended to use AMD Software: Adrenalin Edition version 25.3.1.

RX 5600 XT, I am getting error 182!

DBGTRX 5600 XT, I am getting error 182!you need to make sure you have using the combined driver download.

It looks like AMD has split the driver branch RDNA 3/4 was the first driver released.

The combined driver has support for RX 5000,6000,7000,9000

It would seem they're moving RDNA and RDNA 2 to a legacy branch, but if that is the case, I understand and support their reasons this time around. RDNA 1 has got to go.

And Battlefield 6 still crashing...

razaronRDNA4 wasn't premature, it was exactly as advertised. A cheap and cheerful (R&D/production cost wise) stopgap until UDNA. No point wasting R&D money on a low margin sector like gaming, when UDNA will theoretically let them spend money on AI GPU design which they can then cut down for gaming.

I was genuinely surprised it was as good as it is. Was expecting something much less power efficient, just slapped together.If I remember correctly it was rumored that RDNA4 was simply a "fix" to previous mistakes on RDNA3, so nothing major and as you said, kind of a stopgap until UDNA is ready.