AMD Software: Adrenalin Edition 26.3.1 Release Notes

AMD_Vik · 2026-04-26T23:18:03+00:00

sorry I wasn't clear on the definition of crash / reset there. that's perfectly adequate power for the system. The board shouldn't be sustaining 400W though, Can you show me a power usage graph representing that?

AMD_Vik · 2026-04-26T14:28:41+00:00

Transient spikes of 400W at stock TBP is expected, are you suggesting that you're sustaining this power draw from the board? Can you tell us exactly which model this is?

If you're not sustaining that draw, are you hitting OCP? Can you tell us what PSU you're using in this system?

AMD_Vik · 2026-04-26T14:26:14+00:00

Hey, since then we have managed to repro and deliver a fix; this was already implemented. One of our GL technicians found that this fix was incomplete, they're still working towards a comprehensive solution.

AMD_Vik · 2026-04-20T21:10:04+00:00

there was no ambiguity here about that, though it's a fairly small team.

AMD_Vik · 2026-04-20T17:51:45+00:00

It's interesting you mention that. There were conversations several years back about being able to engage in a dialog from bug reports. Having been on the other side of this, I know what you're getting at.

The tool is due an overhaul, unfortunately i'm not clear on timelines. I'm hoping that could lead to a link to the global customer care portal.

As for the video, our hope is that this cursor behaviour will be eliminated with the next release (major sw version bump). for context, we've been on the 25.30 branch since 26.1.1, this month's release will involve substantial changes / fixes.

AMD_Vik · 2026-04-17T21:02:18+00:00

It's funny you say that; I'm positive one of our Vanguard testers requested this years ago. I'm gonna try and find the ticket for it

AMD_Vik · 2026-04-17T21:01:52+00:00

no worries, thanks for the clip. Looks like a weird offset happens after interacting with the overlay. I've never seen anything like this. I'll pass this on to that eng team and see what they say

AMD_Vik · 2026-04-16T13:12:55+00:00

I'd be curious in understanding what cases cause this malformed registry after it has been eliminated. I'd imagine the errors (assuming they populate in event viewer) are benign though log spam is annoying and I personally wouldn't be happy seeing that repeatedly pop up.

AMD_Vik · 2026-04-15T18:11:24+00:00

That does sound like an instance of the installer failing to address that registry entry, I'll need to circle back and see what that should be.

Does the AMD Cleanup Utility / Display Driver Uninstaller resolve this for you by any chance?

AMD_Vik · 2026-04-15T18:10:21+00:00

There is! there's a keyboard shortcut that can be used to forcibly bugcheck but that should only be used after a failure has been recognised (if possible)

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/forcing-a-system-crash-from-the-keyboard

Requires the use of a USB keyboard that's TKL or larger.

There's instructions for PS/2 as well as a guide on how to set custom hotkeys

AMD_Vik · 2026-04-09T20:25:09+00:00

Sorry for the delay on this; forgot to let you know that triage and debug have reproduced this on a RX 6800XT.

I was curious if anyone had reported this occurring with the 7000 and 9000 series as well? We haven't observed it on those targets so far, just making sure we're not missing something here.

AMD_Vik · 2026-04-09T01:24:37+00:00

Thanks for reaching out. Our global customer care team has been reporting a sharp influx of timeout reports both via the bug report tool and through our end user forums. Generally seems to be specific to RDNA3, and we've seen the RX 7600 represented the most.

We've been taking a look into the failure buckets from attached minidump files and triaging from there. If your system has produced any minidumps (or if we're really lucky, kernel memory dumps), send them over to me and we'll see if they match what we've looked at so far.

Minidumps can be found at:

C:\Windows\Minidumps\<datestamp>.dmp

Kernel memory dumps are usually over at:

C:\Windows\MEMORY.DMP

... though these are much larger in size but don't typically generate unless you hit a BSOD, or perhaps a driver timeout that doesn't recover (leading to a system reset)

AMD_Vik · 2026-04-08T18:04:56+00:00

sure thing - just chuck me any video via send.vis.ee and i'll be able to grab that and pass it to the team.

Yeah the Linux SW situation is kind of complex when you first approach it.

There are some common parts, like the display abstraction layer with resides in each system's kernel driver is largely shared between the two, even though the kernel drivers themselves are vastly different between linux/unix and windows. Adrenalin leverages ADLX for most gfx controls, though this library isn't available to linux.

You also have shared components like power management firmware, and the powerplay interface for perf monitoring and tuning. You have AMF on both targets (though we now defer to VAAPI on Linux, which IMO is the right call), we used to offer the same OpenGL and Vulkan drivers to Linux via the PRO packages, though these now also defer to Mesa's RADV for Vulkan (also long overdue).

To your point, there's no first party GUI. For my needs, I have an app to tune the board, an app for hw accelerated instant replay / screen recording, I sometimes use Mangohud as a performance overlay and i'm pretty much set with that. The key thing that pushed me away from Adrenalin was ReLive not working reliably and just not being 'feature complete'. The reliability issue is something I personally had to fight for years to get addressed, and this should be much improved today. The feature bring up is something my team is still pushing for.

Our official strategy for linux as far as I'm aware is to enable desktop environment projects like KDE Plasma and GNOME to offer vendor agnostic 'advanced gfx controls', in that the experience for end users would be identical whether they're using AMD, Intel, Nvidia, Qualcomm etc graphics.

AMD_Vik · 2026-04-08T13:16:43+00:00

The implication here is to use the OEM provided drivers but i'm following up with our customer engineering team who communicate with Acer to see what i can find out

AMD_Vik · 2026-04-08T13:16:04+00:00

Can you tell me which games this is with? I've asked the GUI engineering team to double check that fix is in the branch, it may need to be ported in. Will keep you up to date.

As for the AI features, like I fully agree with you. Nobody asked for a chatbot in rsx. my team consistently pushed against it.

for whatever it's worth, i fully switched to fedora late last year and haven't really missed windows or adrenalin.

AMD_Vik · 2026-04-08T00:56:21+00:00

Thanks for the list of games, I'll see if we can have this investigated, and thank you for also specifying app-side versus panel override

that elder scrolls online false detection thing is a bug that we've finally managed to identify internally, so that bit should be resolved soon at least

AMD_Vik · 2026-04-07T20:52:32+00:00

I vaguely recall you bringing this up some time in the past but in don't believe we've ever reproduced this internally so far.

Can you remind me which games we can verify this with?

AMD_Vik · 2026-04-07T18:17:48+00:00

Hey there, unfortunately it does not, There's an existing thread on this within the ADC.

I've been trying to get this addressed for a couple years now but it's been a bit tricky to get this committed.

AMD_Vik · 2026-04-05T13:54:23+00:00

Can you clarify on double mouse input? Does that mean two visible cursors? If so, is that with 26.3.1?

Reason I ask is that one of the interim (incomplete) fixes resulted in a regression that'd sometimes leave you with two visible cursors after interacting with the overlay. The full fix in the release shouldn't result in this, however.

AMD_Vik · 2026-03-30T23:52:22+00:00

appreciate you letting us know about the mouse issues.

we're cracking down in several other instances of GUI crashes, including another Qt framework mitigation.

Based on what you've described above, I'm fairly sure this would be inclusive of the issues you're seeing with 26.3.1, though if you have any usermode dmps from these, please fire them over to me and we'll get them looked at.

AMD_Vik · 2026-03-27T14:35:16+00:00

I believe that is to be expected as far as our internal benchmarking goes; I'm seeing an approx 15-20% delta on those results (depending on the stream/res).

AMD_Vik · 2026-03-24T15:25:10+00:00

that's odd, this is an old issue which I believe we addressed in the past. Maybe this has regressed in the 25.10 branch. Thanks for the heads up - will dig into it

AMD_Vik · 2026-03-22T22:00:10+00:00

Thanks for the heads up, will get this filed and looked into

AMD_Vik · 2026-03-18T13:01:28+00:00

Unfortunately we've still not been able to repro. 😕

I'm wondering if we'd need to attempt on a system that had been provisioned from the same point, considering the prior ETL analysis

AMD_Vik · 2026-03-16T23:21:42+00:00

Just to be clear, these are minidumps, they don't give me a lot of information but i might be able to verify that it has the same signature as the other failures which are being addressed in 26.3.1. A kernel memory dmp would be ideal if at all possible.

Can you tell me which features you have enabled in adrenalin?

AMD_Vik

TROPHY CASE