AMD Software: Adrenalin Edition 22.10.3 - Driver download and discussion

Thanks... Tbh direct hash comparsion would also be applicable, but diffeence is clearly can be seen even with filesize and file name.
Strange that driver version that GPU-Z reports is exactly the same (31.0.12029.4013 for both), just one of them is beta, and another one is WHQL

 

The hash and size are most likely different because of the newer signature.

To download it yourself.
Go to the driver page, open dev tools in chrome and change the url of the driver download. (append whql-)

 

@masterfaster Can you upload the driver?

 

Upload is on the way. I will edit the post, when the upload is completed.

https://krakenfiles.com/view/GnZKhYIZ5H/file.html

 

Did you try disabling MPO, cos this the first time i hear some one with say they have it with 10 bit color depth, does it stop if you set it to 8bit and then back to 10 bit color depth ?

 

Thanks @masterfaster
The drivers are whql but you need to make sure that you ticked the factory reset for the certificate to update.

 

I have not tried disabling MPO as of yet. I did try 8 bit, then back to 10 bit, but it still occurred. I've actually since reconnected the display port cable, seems to be fine thus far, hoping that it stays that way!

 

Yeah, bad DisplayPort connection and/or cable can cause troubles. Level1Techs made video on this issue before, idk if you had seen it already.
Flickering Issues With AMD GPUs? We've Got You Covered! Driver Settings And Choosing Proper Cables - YouTube

 

Anyone know why mine states 12.1 for direct 3d api?

 

Thank you for the link! Here is something odd I just found out. With the 22.5.1 drivers and free sync enabled, zero issues. So, with 22.10.3 drivers (and below) with free sync enabled, black screens and display time outs. If I disable free sync, no issues. This Viewsonic monitor is g-sync compatible (used to use NVidia) but surely this would not be an issue?

I have plenty of display port cables, this latest one is Cables Matter one. Just at a loss, seems odd.

Edit- Well disabling free sync and it lasted for around 2 hours, then black screen. So, I guess it's back to the 22.5.1 driver. With the Nvidia card, there were no issues. But, then again, this monitor does not state free sync compatible.

 

Hmm... maybe with optimisations for DX11 and beginning of MPO practical adaptation (as they stepped into ocean of issues) they also touched code for transmitting display output? I also have, like, own personalized issue it seems. . .
I do know for sure that VRAM goes to power down mode (RivaTuner shows 0 mHz, and HWINFO deletes related line), after some time of idling (even if there is game in background/minimized and it is still technically rendering on very slow pace). And returning from power down mode you can meet several related issues, few of them forcing you to either relaunch game or to hard reset system.
Basically rendering engine begins to reload all assets from what i understand, and normally game should get it's image frozen for 1-2 seconds at same instant you foreground it. No delays.
But at some point of messing with driver settings this behaviour can change. Instead of instant asset reloading, game will run for 1-2 seconds and THEN begin to reload assets. This delay is not a thing that supposed to happen, as i witnessed too often (especially with 22.10.1) how this can randomly cause complete game freeze, system freeze and black screen issues. Also frequency of sound stutters (when alt-tabbing from game to browser) and asset rebuilding increases when behaviour changes (when it breaks, everything becomes more frequent). Problem seems to be as if VRAM is not coming back from power down state fast enough at times it is needed and then... not enough data to render even single frame. And this doesn't seem to be HW related issue, as clean reinstall of driver (AMD CleanUp Utility helps better in this case compared to DDU for some reason), fixes issue.

As emulation of change and driver crashing bug at same time.
1) Run BDO (Black Desert Online).
2) Minimize it to tray. (escape, minimize to tray... cool feature actually)
3) Wait for VRAM to go in power down mode (when line Memory frequency will disappear)
4) Start screen recording (i use HEVC, but encoder isn't cause there, likely)
5) [Optional, but makes bug more frequent] Launch MSI Kombustor artifact test (i use last one as it is really fast to catch VRAM frequency related artifacts) and confirm that VRAM is at 0 mHz via RivaTuner overlay (it also easens up bug replication on next step)
6) Maximize BDO from tray.
7) Aaand... driver crash (BDO is actually really good at recovering image after driver crash)
In normal situation BDO would've been frozen for 1-2 seconds at moment you open it. But when you enable recording, there is something wonky with synchronisation going on. And driver delays asset rebuilding. So when you maximize BDO WITH recording enabled, you will get 1-2 seconds of normal FPS, then it will freeze and then driver will crash.
It also works without MSI Kombustor step, just chance becomes less than 100%.
And, of cours you cannot record this bug with desktop recording)

Here is another my post with showcase of wonky stuff with VRAM management after it going to power down mode with MSI Kombustor alone:
https://community.amd.com/t5/driver...nagement-on-sudden-load-after-idle/m-p/556273

P.S. Just recorded video with both driver crash AND WTF is going on there, it isn't supposed to happen at all MSI Kombustor behaviour. Yay, i guess? Wanna see what i meant?

 

Strange... Why your WHQL 22.10.3 have DX support as 12_2 reported in GPU-Z, but only 12.1 in Adrenalin? My old Beta 22.10.3 shows 12.2 for both

 

Maybe Windows 10 doesn't support DirectX XII ULTIMATE.

 

Now both links (old and new) from AMD give the same setup file with 2022.11.05 digital signature and SHA1: 989dab836958ac58383d4b5c5f72b5cb7d0464fe

 

windows 10 supports ultimate.

 

Can confirm as well. Downloaded again today. File name is same, size and hash are different. Unlike day ago


------------------------------------------
SHA256:
1) amd-software-adrenalin-edition-22.10.3-win10-win11-oct28.exe (old one)
7B0F2E64A032EF78337F21590726DE7229D5F162334DC93CC6F068E2FEF767F4
2) amd-software-adrenalin-edition-22.10.3-win10-win11-oct28 (2).exe (new one from today)
2742908803095EF34CD3AFEC09BD3CE60539EF14876C79004BD1335F831F23D5

SHA512
1) amd-software-adrenalin-edition-22.10.3-win10-win11-oct28.exe (old one)
5C4EF350F24833B76E17293D5A73614632F1058AABB6252C6022A000988B2A7F8105EC5D07258977534880CBD9E8B65887664075CCFBC13C5D9C7AD31BD9DF16
2) amd-software-adrenalin-edition-22.10.3-win10-win11-oct28 (2).exe (new one from today)
53C9C9E24537D0132E1F65A03E9050B2A0FCECD1BA47588FD35442DF53FBC7AB383ECE03A61162F5AF62D41C60BCA03666EBE702AE53BB9E0508B0310579670E

----------------
P.S. Ngl, i mostly tested hashing speed in addition. SHA512 supposed to be faster than SHA256 on x64 systems from what i heard... But it is about 2.22 times slower for me (540 MB/s vs 1.2 GB/s). Maybe it is TeraCopy implementation that suffers?

 

Found out by coincidence if i set gpu scaling i trigger a blackscreen consistently that turns pink or grey with MPO enabled and disabled, if it does not trigger the first time setting gpu scaling it does it the 2e time, recommendation don't touch gpu scaling and leave it off, i think its broken.
Seems to happen with wallpaper engine running.

edit: starting to suspect system freezes being caused by windows autohdr as well in wow if had 3 system freezes today but i cant find any memory errors at all so far gonna run it again tonight, if been testing memory for the last couple of days without any errors.
Disabled HDR and autohdr cos i know autohdr also works via overlay mode, probably causing the video scheduler to freeze.

 

Decided to reinstall 22.10.3 with a Factory Reset, and as you can see the Mobility package was also updated

 

the uwp driver thread has a driver which is basically like this, same component versions, expect with updated opengl driver.
Seems to have less chrome stutter but it's still there.

 

I have not updated from 22.5.1 since trying out the 22.6.1, or was it the 22.5.2 which had the major stuttering issue, but now I have bought Spider-Man Remastered so I needed to install a driver with optimization for the game, but this latest driver 22.10.3 seems also janky, which is unbelievable to me. I have only tried out Spider-Man, which was smooth, but SMAA was broken which might be related to the game - who knows, but Rocket League has this ever so slight micro stutter which I of course instantly noticed because I play the game so often. Also I don't know how the following is possible, but now some framerate capping options in the game's menu are gone, such as my preferred 160 FPS. The game has not updated since changing driver. I'm trying out stuff now to see if I can get Rocket League to work smoothly, but I suspect that this all is related to the DX11 execution rework, even though I play on RX 5700 XT. Darned, if this really is a driver related issue, which it very much seems like, I'm starting strongly to lean on Nvidia when I upgrade GPU. Perhaps I should have done a clean install, which I'm about to do, so let's see...

EDIT. Okay I reinstalled, first using DDU, and now Rocket League is smooth and all the FPS cap options are back. This underlines the importance of clean install, which is of course available directly in the driver setup too. Remember to do so even if it might be an annoyance!

22.10.3 seems good!