4 Replies Latest reply on Jun 27, 2017 6:28 AM by amdmatt

    R9 390 - Crimson 17.4.4 DX Error

      • Desktop

      Radeon Software Version - 17.4.4

      Radeon Software Edition - Crimson ReLive

      Graphics Chipset - AMD Radeon (TM) R9 390 Series

      Memory Size - 8192 MB

      Memory Type - GDDR5

      Core Clock - 1040 MHz

      Windows Version - Windows 10 (64 bit)

      System Memory - 16 GB

      CPU Type - Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz


      • Display Device
        • HP 2311xi



        • ASRock   H97 Anniversary
      • Power Supply
        • Can't remember 600W

      Describe your issue:

      • Provide a detailed description of the issue you are experiencing and the steps required to reproduce the issue.

                Some games such as BeamNG drive, CSGO, LoL and BF4 along with XSplit will not open and give directX errors. I can however launch Rust, Arma 3, PUBG

      • All games are up to date and have been reinstalled multiple times.
      • Graphical settings used in the application/game (resolution and 3D settings)

                I can't even open them

      • If possible, include a screenshot or video link of the issue













      Message was edited by: Matt B We have updated the title of this discussion with relevant details to better describe your issue.

        • Re: DirectX is not working for certain programs/games

          Unable to use some programs that use DirectX: R9 390

          You should have posted the info back on that thread, for amdmatt to offer further suggestions.

          1 of 1 people found this helpful
          • Re: DirectX is not working for certain programs/games

            I am seeing the same errors, though on different games, like for instance the Win10-compatible versions of Might & Magic 6,7,8, & 9--yes, all four.  Additionally, I'm seeing "no DX renderer found"-type errors in other older games from GOG (also updated to be Win10-compatible).  Also, these are games that used to run without difficulty under pre-Creator's Update Win10x64.  But as you say, oddly enough, many other DX games run fine.  However, I am running the Insider Windows builds--now on Win10x64 build 16215--and I believe that these are problems that Microsoft introduced with the CU release of Win10x64.  Don't know for sure, but build 16215 fixed some problems I'd been having in all of the post CU builds I had tested, 16188, 16193, 16199.  I think that if you are using a version of Win10x64 that is older than the CU, then it's got to be a driver problem.  But if you are using the CU or newer, as I am, it could very likely be the problem of the drivers.  However, again I have to reiterate that prior to the CU build I had not experienced these problems.  I really don't know at this stage what the problem is...assuming it is the Windows build I'm running, but it might not be...;)


            Windows10x64 build 16215, running on the following hardware:

            MSI 970A Gaming mboard UEFI version 22.4 (M4)/Corsair CX-750M PSU (62a x1 12v rail)/AMD FX-8320E @ 3.2 GHz/RAM 16GB 4x4GB, 2133MHz interleaved, dual channel, 11-12-12-30-48-1T/LG MultiDrive DVD/Boot:Samsung EVO 850 256GB (UEFI boot partition)/2x 1TB WDC WD10EZEX Blue 7200 rpm in RAID 0/ST2000DM 006 2DM164 SATA (2TB)/Asus AMD RX-480 8GB/Realtek 1150 sound/Crimson 17.6.1 GPU drivers