WDDM 2.3 driver - 23.20.780.3 - 10/10/2017 8:00:00 PM

Discussion in 'Videocards - AMD Radeon Catalyst Drivers Section' started by Chastity, Oct 14, 2017.

  1. Chastity

    Chastity Master Guru

    Messages:
    794
    Likes Received:
    56
    GPU:
    Sapph Nitro 390 BP
    Just got this from WU along with 16299.19 update:

    https://1drv.ms/u/s!ArwXzixQ74JbgbA4-9ur5UGvIsMV7g

    Driver File Version: 23.20.0780.0003 (English)
    Driver Version: 23.20.780.3
    DDI Version: 12
    Feature Levels: 12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
    Driver Model: WDDM 2.3
    Driver Attributes: Final Retail
    Driver Date/Size: 10/10/2017 8:00:00 PM, 1956808 bytes

    Just a driver update over my existing 17.10.1 install

    [​IMG]
     
    Last edited: Oct 14, 2017
    Krteq, AlleyViper, Rambo and 2 others like this.
  2. LocoDiceGR

    LocoDiceGR Master Guru

    Messages:
    972
    Likes Received:
    27
    GPU:
    Gigabyte R9 380 4G
    I hope this will get released in monday/tuesday. o_O
     
  3. Rambo

    Rambo Master Guru

    Messages:
    205
    Likes Received:
    12
    GPU:
    RX 560 w8 4 Vega 56
    My PCs (17017 and 16299.19) didn't get that package. Could you upload it?
     
  4. SacredKnight27

    SacredKnight27 Master Guru

    Messages:
    214
    Likes Received:
    2
    GPU:
    Sapphire R9 280 Dual X
    Sh*t. Anything WDDM 2.3 hard shuts down my system on any game launch. I really wish I had a spare PSU laying around to see if this is a hardware issue. I have an old 400w but I don't think that's enough for my system as it is. But if its hardware it still doesn't make sense why this is only happening when these and the 17.10.1's. Anything earlier and I'm right as rain.
     

  5. Chastity

    Chastity Master Guru

    Messages:
    794
    Likes Received:
    56
    GPU:
    Sapph Nitro 390 BP
    Added download link in OP.
     
    Jackalito likes this.
  6. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    13,524
    Likes Received:
    143
    GPU:
    Sapphire R9 Fury OC
    Interesting, these don't have the "amdh265enc32.dll" and "amdh265enc64.dll" from the previously uploaded package but it could just be differences in packaging on the Microsoft servers since 265 codec support requires a 400 series GPU or newer as far as I know.

    That also shows up in the INF file with the lines for these files missing.

    And for other changes the INF shows these as being from October 11th (September 27th for the previous drivers.) with (As seen in the thread title.) driver version 23.20.780.3 compared to 23.20.768.12 in the older driver.
    (Those were also just 17.40, these are 17.40.1013 though it probably doesn't mean much.)

    The older registry value also still calls these 17.7 as with the previous driver, might confuse some software but shouldn't be a issue other than that.
    HKR,,RadeonSoftwareVersion,,"17.7"


    EDIT: From comparing atiapfxx.blb (Via Atiapfxx.exe -r -sys -s test.xml to dump a copy of the blob file as a xml readable document.) the profiles in this driver has a couple of differences compared to the previous one.

    First there's AMD Chill profiles for Destiny 2, Total War Warhammer 2 and Shadow of War.
    (I think 17.9.2 added these already so they're not completely new.)

    No differences in Crossfire profiles between the previous driver, there is a number of DXX profile changes however.

    Battlefield 4
    Project Cars
    Battlefield Hardline
    Grand Theft Auto 5
    Dragon Age Inquisition
    Fallout 4
    PUBG
    Shadow of War

    With a new profile for.
    Assassin's Creed Origins
    (ACOrigins.exe which I guess is the shipped name of the executable and scimitar_engine_win64_vs2015_px.exe which I guess is the development exe.)

    For OpenGL the Solidworks software had this property added to it compared to the previous driver.
    <value Property="GRFThdurjik8375">0x00800000</value>
     
    Last edited: Oct 14, 2017
    Jackalito, OnnA, Rambo and 1 other person like this.
  7. Chastity

    Chastity Master Guru

    Messages:
    794
    Likes Received:
    56
    GPU:
    Sapph Nitro 390 BP
    Maybe it's a different package for pre-400 series. Remember I use a 390.
     
  8. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    13,524
    Likes Received:
    143
    GPU:
    Sapphire R9 Fury OC
    Yeah that's what I'm thinking too, if you use the Microsoft Catalogue to browse for updates you can see they have a lot of separate drivers for different GPU's even if it's the same driver version and even if the Nvidia, AMD or Intel driver downloaded from their own website would have supported all the GPU models.

    It doesn't make too much of a difference, though GPU owners for the 400 series and above might lose out on hardware video playback support for the h265 format if they install this package. :)
    (EDIT: Well, depending on how the driver has set that entire thing up.)

    Files and such other than those two .dll's and their removal in the INF should be identical, I mostly just pulled the AMD profiles from the .blb file as I'm going to wait with the 17.40.xx branch drivers until AMD gets a official release out which can't be too far away now, took Nvidia a few driver revisions for the 387.xx driver to work out some quirks so I'm playing it a bit safer with these drivers although the known issues section for the first AMD website release might still grow a bit compared to 17.30.xx but we'll see, hopefully nothing too severe. :)
    (There's already the quirks with Wattman and certain GPU models that need to be resolved to name one thing in the existing drivers, something is up with Overwatch too for a game specific issue and that is taking some time to resolve too.)


    EDIT: Will be interesting to see if AMD can get a WHQL out too or if it'll initially be another beta classed driver.
    (The only difference lately seems to be the MS signature though, but some people prefer the driver to be fully signed.)
     
    LocoDiceGR likes this.
  9. Chastity

    Chastity Master Guru

    Messages:
    794
    Likes Received:
    56
    GPU:
    Sapph Nitro 390 BP
    Wanted to add that the stuttering in SWTOR when panning the camera or moving was fixed with these drivers. Yay!

    EDIT: Nope, came back. Just less often. Grrr.... back to forcing FlipQueue = 1
     
    Last edited: Oct 15, 2017
    Jackalito likes this.
  10. Rambo

    Rambo Master Guru

    Messages:
    205
    Likes Received:
    12
    GPU:
    RX 560 w8 4 Vega 56
    Checked on my RX 560. I had to restart my PC 3 times because I had black screen after POST screen. Memory frequency slider still doesn't work but it seems that they fixed Flux and similary soft.
     

  11. inouext

    inouext Member Guru

    Messages:
    115
    Likes Received:
    0
    GPU:
    R7 Series
    Installed fine on my APU A10-7860k
     
  12. DmitryKo

    DmitryKo Member Guru

    Messages:
    180
    Likes Received:
    13
    GPU:
    R9 290X 4GB
    Jackalito likes this.
  13. Valerys

    Valerys Master Guru

    Messages:
    321
    Likes Received:
    6
    GPU:
    Sapphire R290 Tri-X OC
    Ran it since it rolled out with no issues, played through Evil Within 2 with no issues as well. At the same time the driver rolled out I also received build 17017, maybe the build helped? I didn't have issues with the older wddm 2.3 drivers on 16299 either though.

    17.10.1 and 17.9.3 were the ones having issues for me, crashing and reloading the tab with the Facebook page randomly. Not a big deal but didn't happen anymore with this driver.
     
    Last edited: Oct 16, 2017
  14. Chastity

    Chastity Master Guru

    Messages:
    794
    Likes Received:
    56
    GPU:
    Sapph Nitro 390 BP
    played for several hours yesterday, no performance issues, or crashes. @DmitryKo if you are locking up I suspect it isn't the driver.
     
  15. OnnA

    OnnA Ancient Guru

    Messages:
    3,585
    Likes Received:
    100
    GPU:
    Nitro Fiji-X HBM 1150/570
    Please try FH3 :rolleyes:
     

  16. DmitryKo

    DmitryKo Member Guru

    Messages:
    180
    Likes Received:
    13
    GPU:
    R9 290X 4GB
    I tend to run a lot of browser tabs (in excess of 500) with several browsers and IE11 eats a lot of resources doing that, so it's a kind of stress test situation.
     
  17. Chastity

    Chastity Master Guru

    Messages:
    794
    Likes Received:
    56
    GPU:
    Sapph Nitro 390 BP
    How much memory are you running your system with? And how much is being eaten by your wonderous collection of tabs?
     
  18. Chastity

    Chastity Master Guru

    Messages:
    794
    Likes Received:
    56
    GPU:
    Sapph Nitro 390 BP
    Would be difficult as I don't own that game. :p
     
  19. thatguy91

    thatguy91 Ancient Guru

    Messages:
    6,557
    Likes Received:
    55
    GPU:
    XFX RX 480 RS 4 GB
    Overclocking can do that when it isn't truly 100 percent stable. Just because it passes stability tests it doesn't mean it's actually stable, driver updates can be coded differently and these code change can trigger instability. I've had that argument online with several people before, if they drop their overclock it becomes 100 percent stable even on the updated drivers, yet it's apparently the drivers fault :). It can be both CPU and GPU overclocks that are affected like this.
     
  20. DmitryKo

    DmitryKo Member Guru

    Messages:
    180
    Likes Received:
    13
    GPU:
    R9 290X 4GB
    16 GB system RAM, of which 6-8 GB is taken by the browser when I open a lot of tabs.

    The problem is not memory however, but CPU time and GDI resource hogging, that's why it makes a good stress test...
     

Share This Page