AMD Radeon Software Adrenalin 23.10.2 driver download WHQL

Graphics cards - AMD Adrenaline (Windows 10/11) 467 Updated by Hilbert Hagedoorn

Click here to post a comment for AMD Radeon Software Adrenalin 23.10.2 driver download on our message forum
#6175080
https://forums.guru3d.com/data/avatars/m/287/287974.jpg
Reserved
#6175090
https://forums.guru3d.com/data/avatars/m/287/287974.jpg
Krteq:

Do NOT post direct link to driver installer files, those are behind akamai wall Correct link to KB/Release Notes //Also, do NOT ninja edit OP posts
Link to KB fixed , download link deleted.
#6175099
https://forums.guru3d.com/data/avatars/m/231/231333.jpg
I'm not surprised by AMD! As expected - WattMan reset on every boot is still there on Win11 with the latest update. 😕 I still use the workaround with ViVeTool: 
vivetool.exe /disable /id:42105254
#6175101
data/avatar/default/avatar21.webp
A Windows update introduced that bug, even on pre-existing installed drivers, not sure why people blame AMD. If you need to use ViveTool, a Microsoft thing, to disable whatever feature is causing that, I'd say it's MS's fault. Which is also not surprising considering their recent track record with Windows bugs.
#6175103
https://forums.guru3d.com/data/avatars/m/231/231333.jpg
Spider-Vice:

A Windows update introduced that bug, even on pre-existing installed drivers, not sure why people blame AMD. If you need to use ViveTool, a Microsoft thing, to disable whatever feature is causing that, I'd say it's MS's fault. Which is also not surprising considering their recent track record with Windows bugs.
If you want to use DirectX 13 for example, you should adapt your drivers with MS OS. It's simple. AMD had almost a year to adapt its code with the new MS features. How do you think AMD has a WDDM 3.2 preview driver already for an OS from the future? That's why MS provides Canarty, DEV, Beta and Preview builds.
#6175104
https://forums.guru3d.com/data/avatars/m/295/295610.jpg
Never thought i be skiping a driver just to stay on a preview driver 😀 That fix for system freezes is quite a surprise
#6175106
https://forums.guru3d.com/data/avatars/m/299/299841.jpg
The Creator:

I'm not surprised by AMD! As expected - WattMan reset on every boot is still there on Win11 with the latest update. 😕 I still use the workaround with ViVeTool: 
vivetool.exe /disable /id:42105254
Neither Forza 8 nor MW3 game-ready optimizations? "Corruption may be observed in Forza Motorsport when RT is enabled." Sheeit, at least its noted as a known issue; I've been worried my vram has been failing seeing the artifacts show up time to time.
#6175119
https://forums.guru3d.com/data/avatars/m/216/216235.jpg
Nice so far. I don't have the freezing issue with this one, as opposed to 23.9.1/2
#6175120
data/avatar/default/avatar39.webp
MerolaC:

Nice so far. I don't have the freezing issue with this one, as opposed to 23.9.1/2
I will assume issue with permanently working VRAM will also get fixed with this.
#6175122
https://forums.guru3d.com/data/avatars/m/293/293552.jpg
Adrenalin Edition 23.10.1 is a good driver. AC: Mirage is smoother in this driver version. But there is no AFMF features.:(
#6175125
https://forums.guru3d.com/data/avatars/m/216/216235.jpg
DimkaTsv:

I will assume issue with permanently working VRAM will also get fixed with this.
I haven't had this issue for a long time with my setup (unless I use 2 monitors at the same time) So, I can't say. 5~10 watts usage and 50~100 Mhz max on the memory when browsing and doing light stuff.
#6175129
data/avatar/default/avatar21.webp
MerolaC:

I haven't had this issue for a long time with my setup
Oh, i am not even supposed to have it. But 23.9.3 was broken in this term. For some people image got frozen, but for me VRAM was permanently working instead.
#6175132
https://forums.guru3d.com/data/avatars/m/251/251189.jpg
The Creator:

I'm not surprised by AMD! As expected - WattMan reset on every boot is still there on Win11 with the latest update. 😕
Well, that sucks, but arguably the freeze issue was way worse. 🙂 Checking if it's really gone and hoping this is also true for stuck medium VRAM clock states (though that dates back further).
#6175134
https://forums.guru3d.com/data/avatars/m/285/285027.jpg
The Creator:

If you want to use DirectX 13 for example, you should adapt your drivers with MS OS. It's simple. AMD had almost a year to adapt its code with the new MS features. How do you think AMD has a WDDM 3.2 preview driver already for an OS from the future? That's why MS provides Canarty, DEV, Beta and Preview builds.
It took MS 2 years to fix the windows weather app...it was displaying Fahrenheit instead of Celsius even if I selected Celsius in the settings. Please don't get me started on the usefulness of insider builds and MS fixing reported bugs. They shouldn't have fired almost all their QA team and rely on users to do their QA testing...
#6175138
data/avatar/default/avatar34.webp
The Creator:

If you want to use DirectX 13 for example, you should adapt your drivers with MS OS. It's simple. AMD had almost a year to adapt its code with the new MS features. How do you think AMD has a WDDM 3.2 preview driver already for an OS from the future? That's why MS provides Canarty, DEV, Beta and Preview builds.
WTF? MS introducing DX13 is not at all comparable to the current issue... That would be introducing a huge new technology that of course AMD would have to adapt to. Now a regular Windows update breaking the AMD control panel/Wattman is something else entirely. Considering you can fix it by reverting some change MS made, seems very clear to me it's MS's fault. Not that AMD can't work around it necessarily of course, but it broke it on all drivers so...
#6175141
https://forums.guru3d.com/data/avatars/m/299/299841.jpg
Spider-Vice:

WTF? MS introducing DX13 is not at all comparable to the current issue... That would be introducing a huge new technology that of course AMD would have to adapt to. Now a regular Windows update breaking the AMD control panel/Wattman is something else entirely. Considering you can fix it by reverting some change MS made, seems very clear to me it's MS's fault. Not that AMD can't work around it necessarily of course, but it broke it on all drivers so...
It took AMD almost one year to release a preview of FSR 3 after the announcement of DLSS 3. The Wattman reset has been around for damn near the same time frame. I don't think it's unreasonable to expect AMD to have adapted to the new MS features to fix the Wattman reset; it's not up to Microsoft to do AMD's job.
#6175154
data/avatar/default/avatar40.webp
aufkrawall2:

hoping this is also true for stuck medium VRAM clock states (though that dates back further).
Well, raw driver upgrade didn't help. But clean reinstall with AMD Cleanup Utility did return everything to normal (i just imported my settings later)
#6175164
data/avatar/default/avatar32.webp
cra3khead:

It took AMD almost one year to release a preview of FSR 3 after the announcement of DLSS 3. The Wattman reset has been around for damn near the same time frame. I don't think it's unreasonable to expect AMD to have adapted to the new MS features to fix the Wattman reset; it's not up to Microsoft to do AMD's job.
The point here is that it was something Microsoft did at some point that broke AMD's Wattman though. It was first seen in Canary and reported here on Guru3D, then Dev, then Beta, now release because it was never addressed. If disabling whatever MS did resolves the issue then I don't know at all how it's AMD's fault. Ah well, moving on.

Next Page