windows 10 15.200.1023.10 Driver

Discussion in 'Videocards - AMD Radeon Drivers Section' started by endbase, Jul 8, 2015.

  1. MontyB

    MontyB Guest

    Messages:
    4
    Likes Received:
    0
    GPU:
    GTX 1060 6GB Windforce
    15.200.1036.0. Windows Update refused to give me 1040.
    I did try 1040 manually, but didn't notice any difference.
    Still, might just be placebo.
     
  2. theoneofgod

    theoneofgod Ancient Guru

    Messages:
    4,677
    Likes Received:
    287
    GPU:
    RX 580 8GB
    1040 is still the overall leader here :)
     
  3. WarDocsRevenge

    WarDocsRevenge Guest

    Messages:
    295
    Likes Received:
    0
    GPU:
    Fury-x Crossfire
    1040 was the buggiest mess of a driver i ever did use and had less fps then 1023.5
     
  4. N0bodyOfTheGoat

    N0bodyOfTheGoat Member Guru

    Messages:
    192
    Likes Received:
    0
    GPU:
    Sapphire Nitro R9 390 8GB
    I might well be about to remove the 1040 DLLs from pCARS' root folder for the last time, because I think these new 1023.10s by themselves give fractionally better frametime when driving solo for me and they are at least an equal in terms of fps. :)
     

  5. Dygaza

    Dygaza Guest

    Messages:
    536
    Likes Received:
    0
    GPU:
    Vega 64 Liquid
    These drivers are a bit fasters than 1040 driver for me. Though 3dmark api test can go to margin of error. Games are working smoothly.
     
  6. theoneofgod

    theoneofgod Ancient Guru

    Messages:
    4,677
    Likes Received:
    287
    GPU:
    RX 580 8GB
    I'll delete my 1040 dll's and give the entire driver a whirl.
     
  7. Fox2232

    Fox2232 Guest

    Messages:
    11,808
    Likes Received:
    3,371
    GPU:
    6900XT+AW@240Hz
    Get your device ID from device manager. Find it in driver INF file.
    For Fury it is like:
    "%AMD67B0.1%" = ati2mtag_Hawaii, PCI\VEN_1002&DEV_7300&SUBSYS_0B361002

    Bold is code/settings used. Fury X proper one is ati2mtag_R7000.

    At bottom of driver is another interesting section with settings:
    [ati2mtag_Hawaii.GeneralConfigData]
    MaximumDeviceMemoryConfiguration=256
    MaximumNumberOfDevices=4

    [ati2mtag_R7000.GeneralConfigData]
    MaximumDeviceMemoryConfiguration=128
    MaximumNumberOfDevices=4

    Wonder if that does anything or just says that it can address 128GB of virtual memory.
     
  8. jaju123

    jaju123 Guest

    Messages:
    355
    Likes Received:
    3
    GPU:
    2x AMD R9 290 Crossfire
  9. theoneofgod

    theoneofgod Ancient Guru

    Messages:
    4,677
    Likes Received:
    287
    GPU:
    RX 580 8GB
  10. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    8,125
    Likes Received:
    969
    GPU:
    Inno3D RTX 3090
    My guess is that you refer to Device Strong Name in the Device Manager properties of the card.

    For mine I get this:
    Code:
    oem26.inf:cb0ae41405cb194b:ati2mtag_R575:15.200.1040.0:pci\ven_1002&dev_6798&subsys_3001174b
    
    So If you wish to change driver path, how do you actually go about doing it?
     

  11. MatrixNetrunner

    MatrixNetrunner Guest

    Messages:
    125
    Likes Received:
    0
    GPU:
    Powercolor PCS+ R9 270X
    There was talk yesterday of a 15.20 Catalyst release for Linux at Phoronix. They had info that release is imminent. Fingers crossed.

    Anybody taking bets on the greek alphabet letter they will use?
     
  12. jaju123

    jaju123 Guest

    Messages:
    355
    Likes Received:
    3
    GPU:
    2x AMD R9 290 Crossfire
  13. Fox2232

    Fox2232 Guest

    Messages:
    11,808
    Likes Received:
    3,371
    GPU:
    6900XT+AW@240Hz
    In your case just look for 6798, it will find line like this:
    "%AMD6798.1%" = ati2mtag_R575, PCI\VEN_1002&DEV_6798

    Change bold part for something you see at same place around.
    Then take AMD6798.1
    And look for it at bottom of file for actual naming:
    AMD679A.1 = "AMD Radeon HD 7900 Series (Engineering Sample - WDDM v2.0)"
    Change Magenta name to something distinctive as you want to do manual installation of driver and pick that corresponding name.

    There are likely to be many 6798 devices/revisions listed at top of INF file and many corresponding names at bottom. If you have trouble finding your custom name during driver installation or other more compatible device ID is overriding yours, then you can safely remove those other names and similar device IDs from INF.

    And btw, benchmarking:
    Dead Island:
    15.200.1040 - Hawaii code path (Tahiti path did not enable me to get downsampling from 2160p.)
    Maxed out. Texture LOD settings "-1" enforced via RadeonPRO.
    1080p: 120fps (limit set in RP)
    1440p: 107~115 (locked by game, even main menu before loading any geometry runs on that fps)
    2160p: 107~115 (locked by game, even main menu before loading any geometry runs on that fps)
    In all resolutions fps was limited by software and GPU not fully utilized. DirectX 9 game.
    ----------
    W10 Driver 15.200.1023.10 Fiji code path:
    1080p: 207fps+
    1440p: 198fps+
    2160p: 124fps+
    What a change.
     
    Last edited: Jul 8, 2015
  14. Phyxsyus

    Phyxsyus Guest

    Messages:
    65
    Likes Received:
    0
    GPU:
    Zotac GTX 1070 Mini
    Thank you man! Just installed on windows 10 10162 and Sapphire r9 280...

    Did a clean install using DDU, But just as a heads up, OpenCL doesn't seem to be enabled acording to GPU-Z.

    VSR and frame limiter working good.
     
  15. OneB1t

    OneB1t Guest

    Messages:
    263
    Likes Received:
    0
    GPU:
    R9 290X@R9 390X 1050/1325
    interesting.. will it work also for hawaii?
     

  16. PrMinisterGR

    PrMinisterGR Ancient Guru

    Messages:
    8,125
    Likes Received:
    969
    GPU:
    Inno3D RTX 3090
    Thanks for this. I'll try my card with the Fiji codepath, because why the hell not.
     
  17. ReaperXL2

    ReaperXL2 Member Guru

    Messages:
    179
    Likes Received:
    69
    GPU:
    EVGA 2080ti Hybrid
    Ok peeps :)

    So I installed 15.200.1023.10 on my GCN 1.0 MSI twin frozr III r7870 OC...

    They give me virtually the same performance as 15.200.1023.7 (which I received officially via WU)... The difference is 7 points faster in heaven benchmark and 22 points faster in HeavensWard FF benchmark...

    The trade off is micro stutter introduced back into GTA V (15.200.1023.7 run my games perfectly with improved performance, latest & last gen)...

    So for me, the only Win10 driver to work correctly & boost GPU output for my GCN 1.0 card is 15.200.1023.7...

    Cheers peeps :thumbup:
     
  18. sammarbella

    sammarbella Guest

    Messages:
    3,929
    Likes Received:
    178
    GPU:
    290X Lightning CFX (H2O)
    Thanks for you post, this info is golden.

    Now more work with 15.7 WHQL.

    Good times for test junkies!

    :D
     
  19. Fox2232

    Fox2232 Guest

    Messages:
    11,808
    Likes Received:
    3,371
    GPU:
    6900XT+AW@240Hz
    Another benchmarking:
    W10 Driver 15.200.1023.10 Fiji
    1080p: 128~205fps
    1440p: 130~202fps
    2160p: 95~192fps
    Improvement on lower resolution is notable. At 2160p card is quite utilized, so no improvement there:
    [​IMG]
    It is 3times same section of game where hordes of smaller orks are sieging camp on ground, and then at end there is 1st ground boss fight.
     
  20. alexrose1uk

    alexrose1uk Guest

    Messages:
    81
    Likes Received:
    1
    GPU:
    3080 10GB
    Well on initial testing these seem to be running nicely, and my core clocks are sitting happy compared to some of the older Win 10 drivers where they seemed to fluctuate more.

    Within stones throw of my best Firestrike run with these (which was on 1040), only ~70 marks difference, and everything seems to be working so far :)
     

Share This Page