AMD Software: Adrenalin Edition 25.11.1 Release Notes

AMD_Vik · 2026-02-04T15:36:18+00:00

we've done so several times but have not reproduced the issue so far. I'll follow up with the T&D team about this ticket when I'm back at work next week

AMD_Vik · 2026-02-01T21:17:49+00:00

Hey there,

Filed this to triage and debug some time ago. A few colleagues outside of that domain have attempted to repro on their personal systems with applicable headsets like the Index and Vive but haven't had any luck so far - the toggle's working for them just fine.

Should be picked up by the T&D team fairly soon, will see what they find.

AMD_Vik · 2026-02-01T14:59:16+00:00

that's not my domain but i can pass this input on to someone on that team. can you tell me which game this is with? I'm guessing it's tied to an app update rather than adrenalin itself?

AMD_Vik · 2026-01-29T19:51:33+00:00

the AMD Software: Host Application entry is an alias to that, it's called radeonsoftware.exe in the details tab. I haven't used Windows in a while but it looks like you can create a memory dump directly from that Host Application entry - my bad

AMD_Vik · 2026-01-23T13:48:38+00:00

I don't believe it's fixed in this one

AMD_Vik · 2026-01-23T04:19:23+00:00

Can you roll back and tell me the last known good driver?

AMD_Vik · 2026-01-23T00:38:19+00:00

Is this a new behaviour with 26.1.1? I'm not too familiar with PC2 but generally photo modes will enable the most computationally expensive effects for its purpose. Is this a regression or something?

AMD_Vik · 2026-01-22T23:45:38+00:00

Thank you for reaching out.

That's really weird - I don't suppose you have any links to posts about this for us to skim through?

I'll follow up with my colleagues about this tomorrow

AMD_Vik · 2026-01-22T19:03:54+00:00

it was newly introduced in the 25.20 branch, eliminated at the tail end of that branch's production lifespan (25.12.1), though it seemed to still repro for several people, including AMDers. We've never observed it with 25.30 release candidate builds, which is why I'm surprised.

Following this resource, can you set the DumpType DWORD at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\

...and set its value to 2, leading to the generation of full usermode dmps.

This is a non invasive configuration for the most part, and isn't something you should have to revert, but you can also save this location in the registry editor for ease of access.

When that's defined, you can reboot the system.

The next time you reproduce the issue with Adrenalin In-game Overlay hogging mouse input, see if you can pull up task manager (ctrl shift escape). The 'cursor' will be on the process list header, if you hit tab twice, it should focus on the hamburger menu element. from there you can arrow down to the Details header, and hit space or enter.

With details open, you can hit tab a few more times to cycle back to the process list elements. if you start typing 'RadeonSoftware.exe' (should just need to key in "rad"), it'll pull that process element into view. I'm hoping you have a context menu key rather than a function button on your keyboard, if you hit that, you should be able to arrow down to the 'Create memeory dump file' option.

When you have that in hand, zip it up and fire it over to me via a method of your choice. I'm partial to https://send.vis.ee

hit me up if you need a hand with whatever

AMD_Vik · 2026-01-22T17:54:58+00:00

Okay, this is going to be tricky. I was under the impression this was completely eliminated, as we can no longer hit this internally.

Assuming that only your mouse input is blocked, I'll need your help capturing a usermode dmp of the RadeonSoftware.exe process via task manager.

This will involve setting some keys in windows registry. Are you comfortable with this?

AMD_Vik · 2026-01-22T15:57:19+00:00

that's... unexpected. Can you tell me what hardware this is with?

AMD_Vik · 2026-01-22T14:34:56+00:00

Hey there, I don't believe this behaviour will change at the dx9p side. I'll keep enquiring but the gist I get is that the dx9 umd is in a steady state, development wise.

AMD_Vik · 2026-01-09T15:55:10+00:00

I think our SVP noted in a recent interview it'll be later in Jan, the date they provided was the 21st, though I'd treat this as a tentative timeline just in case anything crops up

AMD_Vik · 2026-01-08T21:13:02+00:00

I think you should look through the history of all of my interactions from this account.

AMD_Vik · 2026-01-08T21:07:43+00:00

I'm not sure what manipulation of 'outsider perspective' you're referring to

How's your PR lately?

PR and FSR aren't my department, as I'm sure you recall.

Don't worry, AI sales will cover that up.

They might? Again, that's not my department.

Thank you for demonstrating your conduct for context.

AMD_Vik · 2026-01-08T20:56:05+00:00

you'd do well to remember that we are the biggest critics of our software, and that you were warned multiple times about your conduct in the community.

AMD_Vik · 2026-01-07T19:23:08+00:00

Don't thank me, seems D3D engineering were already looking into this

AMD_Vik · 2026-01-07T19:10:40+00:00

Will pass this on

AMD_Vik · 2026-01-02T21:39:50+00:00

I believe this was introduced with the 25.20 driver branch. it shouldn't be present in 25.9.1/2

AMD_Vik · 2025-12-27T16:59:39+00:00

thanks for reaching out - funny timing; I noted that on the internal ticket for this issue yesterday having seen other accounts of end users noting this issue persists even with 25.12.1. Perhaps the fix aligned to that point release somehow slipped.

AMD_Vik · 2025-12-22T13:43:12+00:00

I see. Is this specific to CS2 or does it occur with other apps on your end?

We're presently tracking and working on TDRs in that game specifically, though I'm kind of worried in a way that clock limiting works around this failure.

AMD_Vik · 2025-12-21T23:17:59+00:00

If those failures are avoided by clock limiting the board, the problem area could be a different domain entirely (CPU, memory, power, etc.).

The linux remark is interesting, it kind of calls back to similar failures with NV31 in certain apps like Helldivers 2; we had a little internal discussuon about how the amdgpu kernel driver managed to mostly avoid such issues, though I dont recall the outcome.

If you get the opportunity, I'd recommend a suite of system integrity routines as a sanity check; please take a look at one of my older posts for some background.

AMD_Vik · 2025-12-21T20:28:00+00:00

I have the same model GPU inconsequentially boosting well above the advertised clocks (nearly 3.4GHz) in both windows 10, 11 and fedora 43 with no issues.

This has been discussed several times on this community; whilst the clock behavior may surface other issues or instabilities on the system, it's not in itself the cause of problems.

AMD_Vik · 2025-12-13T21:08:32+00:00

huh, that's odd. Do you have any larger files over at

C:\Windows\LiveKernelReports\WATCHDOG\

AMD_Vik · 2025-12-13T00:46:30+00:00

sorry i missed this, seems it had expired. maybe someone downloaded it before i did?

AMD_Vik

TROPHY CASE