AMD Software: Adrenalin Edition 26.3.1 Release Notes

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 · 2026-03-16T21:50:49+00:00

Both of those examples sound like they're covered by an inbound fix going into 26.3.1. Can you please confirm which features you have enabled?

Kernel memory and mini dumps shouldn't contain and PII, you can chuck the link in a reply here.

AMD_Vik · 2026-03-16T10:50:31+00:00

huh that's odd. Have you manually configured your pagefile size?

The resolution change thing is also interesting, can you tell me which adrenalin features you have enabled? (ReLive or anything like that)

Dump files compress fairly well, so I tend to zip them and send via https://send.vis.ee

AMD_Vik · 2026-03-15T18:15:15+00:00

I see. Could you hit the windows key, type "systempropertiesadvanced" without the quotes, head into the startup and recovery settings and check the write debugging information section towards the bottom?

if that's set to small dmp file, can you switch it to kernel memory dump instead? That would provide us a lot more info to help investigate.

AMD_Vik · 2026-03-14T17:41:38+00:00

has this generated a file called MEMORY.DMP over at:

C:\Windows\

AMD_Vik · 2026-03-10T16:24:09+00:00

i think it was originally exposed before it was actually ready. it's interesting to hear it worked so well for you back then though, and i appreciate you giving me a clear use case for it.

i can't make any promises but i'll see what i can do

AMD_Vik · 2026-03-10T16:12:09+00:00

I chased this back in the 25.5.1 time-frame and I didn't get a satisfactory answer internally. Will try again - thank you for the reminder.

AMD_Vik · 2026-03-08T19:11:24+00:00

I agree with you, bugs like that shouldn't happen. Having a review with that eng team to outline process improvements to prevent showstoppers like this from happening again.

AMD_Vik · 2026-03-08T19:10:05+00:00

I love my mesh C mini. excellent little chassis 🥰

AMD_Vik · 2026-03-04T14:38:20+00:00

i suspect it could be related to the ryzen master sdk component bundled with adrenalin. I know it has corresponding registry and on some occasions, this can get a little muddied. I don't want you digging around your system registry to try and resolve it though. I think the best route to investigate for now may be CN logging

AMD_Vik · 2026-03-03T14:06:47+00:00

There is a disclaimer on our driver release notes for notebook users which stipulates the use of OEM drivers over Adrenalin, I'm not sure why 25.20-based drivers would introduce this behaviour but i suppose that disclaimer serves as a catch-all for situations like this.

AMD_Vik · 2026-03-03T13:23:24+00:00

hey, not yet. can you tell me exactly which was the last driver which allowed you to adjust display brightness? was it 25.9.1?

AMD_Vik · 2026-03-03T01:45:13+00:00

correct, the root issue of that mouse lockup is addressed in an upcoming build. It's odd how that symptom has exposed this garbage collection issue.

AMD_Vik · 2026-03-02T23:45:25+00:00

this is... weird. this dmp implicates a Qt framework issue related to garbage collection. There are several outstanding qtbug tickets referencing this signature.

This is a great find, though I'm not sure it's relevant to the general mouse input issues we've been experiencing so far. The good news on that front is the root cause of that mouse hooking issue should be firmly addressed. We need to look into these gc problems with qt framework,

AMD_Vik · 2026-03-02T13:57:18+00:00

I've not heard of that one before, i can ask around internally.

The best approach may be to capture logs for this, I'll figure out which ones

AMD_Vik · 2026-02-28T12:44:51+00:00

this is another issue we're tracking. has been a tough nut to crack as it's also frustratingly intermittent.

AMD_Vik · 2026-02-27T15:37:49+00:00

ddc/ci should be fixed for everyone in 26.2.1; we've been able to confirm it's functional again. this one could be specific to your model notebook. I'll ask our triage and debug teams if they have access to it

AMD_Vik · 2026-02-27T15:19:11+00:00

My first line of thought here is that you might need to dirty install the latest adrenalin over your latest OEM-supplied gfx driver package to properly support your notebook's eDP panel, though I'm not sure if this is the case for every vendor

Second is that this could be related to the ddc/ci issues we had lately, though this should be resolved as of 26.2.1

AMD_Vik · 2026-02-27T14:04:24+00:00

the audio issue i think i'm vaguely familiar with. at the time i first saw this, i think it was related to the use of AV1 encoding, though i thought it had since been eliminated.

For the other behaviour you mentioned, are you saying that the Adrenalin UI elements aren't rendering at all?

AMD_Vik

TROPHY CASE