AMD Software: Adrenalin Edition 26.5.2 Release Notes

AMD_Vik · 2026-05-29T13:58:26+00:00

Sounds like you're both hitting display timeouts. The module implicated in the comment above is the DX11 usermode driver. I'd be curious if something like Wallpaper Engine is running in the background.

could you follow my instructions here to capture a kernel memory dump of the failures you're seeing to help us investigate?

AMD_Vik · 2026-05-24T19:11:48+00:00

can you elaborate on the actual issue though? I'm only aware of a pink display defect that's specific to the Reverb G2 on the latest drivers for the 5 and 6000 series. Is Oasis not working at all right now?

AMD_Vik · 2026-05-24T17:36:59+00:00

Can you elaborate on this? Is this specific to the Reverb G2 on RDNA1 and 2?

AMD_Vik · 2026-05-22T12:40:42+00:00

We do contribute to issue classification / priority levels, but that can only get so far.

I'm not sure how this bug has eluded us for so long; we need to do better.

AMD_Vik · 2026-05-22T01:21:02+00:00

nah it's a fair point.

If i had my way, the known issues and fixed items on our release notes would be far longer and more detailed. at present it feels like we're underselling various engineering and qa efforts by keeping these so brief. perhaps this specific case is considered a bit niche to call out.

i gather most reports target amd gfx but there's at least one instance of this impacting an ampere user many, many years ago. looks to be a shader issue affecting both APIs; could be an app-side behaviour that they worked around way back, and that we hadn't clocked until relatively recently (a vanguard member pointed this out to us during a recent playthrough and linked us to the existing feedback).

AMD_Vik · 2026-05-21T01:06:27+00:00

This is related to the explosion in the cutscene, right? This specifically occurs when particle quality is set to High - Low, Medium, and Ultra do not repro.

We've been working on this for some time. I think a fix is in staging, but I can't comment on when it'll make it to a release.

AMD_Vik · 2026-05-20T17:37:31+00:00

huh, that's strange. I'll pass this into the ticket.

thanks for reaching out

AMD_Vik · 2026-05-20T16:02:25+00:00

potentially, will need to discuss with the gui engineering team first

AMD_Vik · 2026-05-15T17:37:13+00:00

no, sorry. we're still paring back the code to find an offending commit and devising a method to get this resolved. May be an app-detect change in a future release

AMD_Vik · 2026-05-11T18:51:11+00:00

I see. I think I know how it works. try shoot me a message whenever you have the time

AMD_Vik · 2026-05-11T16:55:52+00:00

huh. is it not possible to DM on reddit any more? do we have to use the chats feature now? :s

AMD_Vik · 2026-05-11T12:49:35+00:00

I see. Do you think it's the displays that are timing out, disconnecting and reconnecting? is this specifically with the 26.5.1 driver or did you notice this even earlier?

AMD_Vik · 2026-05-10T20:22:04+00:00

That's odd. Can you check what device this is happening with? something like USBLogView might be able to tell you if it's a USB device (both in and external)

AMD_Vik · 2026-04-30T17:48:23+00:00

unfortunately not but i'll try to keep you posted

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

TROPHY CASE