To begin you need to download the latest driver package you want to MOD,next go ahead and download a legacy package(found in the downloads section) you want to use for modding the new drivers. After downloading and extracting all the driver packages to their default locations you can begin using FLEM to start modding the new driver.

Modding just got even simpler !

1. Download all the required driver files and extract them to their default locations.
    When searching for the legacy drivers make sure you download the correct ones for your card type.
Legacy packages supported in Automatic Mod mode: Simply download and extract them using the driver installer(setup.exe) to their default locations. Once extracted close the installer window because you don't want to install that driver just to extract it.
These packages have to be the correct ones, there are other versions that have the same numbering but are not legacy, carefully pick the correct ones(the proper packages look like the ones described below).

DX9 GPUs- X1xxx to HD2300

10.2 legacy driver -  10-02_legacy_vista32-64_dd_ccc  
9.11 legacy driver for OpenGL functionality -   9-11_legacy_vista32-64_dd_ccc

DX10 and above GPUs-  HD2350 to 4XXX
13.1 legacy driver  -  13-1-legacy_vista_win7_win8_64_dd_ccc  or  13-1-legacy_vista_win7_win8_32_dd_ccc
13.9 legacy driver   - 13-9-legacy_vista_win7_64_dd_ccc  or  13-9-legacy_vista_win7_32_dd_ccc

5xxx to 8xxx GPUs

Non-GCN 16.2.1 driver(32bit): - Non-WHQL-32Bit-NIEG-Radeon-Crimson-16.2.1-Win10-Win8.1-Win7-Feb27
Non-GCN 16.2.1 driver(64bit): - Non-WHQL-64Bit-NIEG-Radeon-Crimson-16.2.1-Win10-Win8.1-Win7-Feb27

2. Click on the Browse button above and select the ROOT/MAIN directory of the driver package you want to modify.
Example: C:\AMD\Support\13-4_vista_win7_win8_32_dd_ccc_whql
After you receive a confirmation that the package is loaded, FLEM will try to  locate and automatically load the required legacy files from its default location.

3. Click Modify and let it finish, if asked to sign the driver pick Yes . That's it !! The driver should be modded.


* Tip : Drivers supported by FLEM are the regular WHQL drivers and the Beta releases of the newer and latest drivers, 
the tool does not support modding the Legacy drivers directly. Trying to MOD a legacy driver will result in the driver not installing on your machine.

 1. Click on the Browse button above and select the MAIN Directory of the driver package you want to modify.



2. After you receive a confirmation that the package is loaded, continue to select the tasks you want to do.

                                                                           Task selection

3.You can select individual tasks or opt to fully mod the drivers. In-order to achieve the best results Full Mod is the recommended way to mod the drivers on most systems, for flexibility and convenience you can select individual tasks when needed.

Task Selection
 Full MOD  ** Recommended --> Assuming that you have downloaded and unpacked the legacy driver of your choice, you can go ahead and select this task.

This the best and simplest way to mod any driver, just select this and choose the legacy files you want to add to your driver in the "cocktailmaker", selecting only the basic files (see illustration below) is recommended for beginners and is enough for a proper MOD. Click Modify and you are done, its that SIMPLE !.

                Below is an example of modding a 32bit driver using the 10.2 legacy drivers

32bitMOD Instruction


                 Here is an example of modding a 64bit driver using the 10.2 legacy drivers

64bitdriverMod Instruction

 Add support for my card in (.inf) files --> Adds your detected card info to the driver, selecting it is essential
        and a "MUST" for the driver to work.

Tweak the drivers(unlock ccc options etc.) --> "This is Optional". Adds a few tweaks and unlocks
        some basic CCC options.

 Driver cocktail maker -use older legacy files. --> Select different files from different(older) legacy driver versions
       for compatibility, selecting it is essential and "Must be selected" for the driver to work.

       There are 4 basic but essential files for 32bit drivers and 7 basic/essential files for 64bit drivers,


These files MUST BE LEGACY and compatible with your card type i.e DirectX9 or Directx 10

If you experience difficulties or the driver does not install properly on a 64bit system then use the 8 files instead of the 7.

  In some cases it is wise to use all 8 files on the left side of cocktailmaker for compatibility with 64bit cards.

  Note: AGP card users please use the files from a latest hotfix for your card type.


MOD Types: 32bit & 64bit

32bit MOD - Uses only 4 files
       You need to add the basic legacy files for the driver to install correctly.
       See the illustration below of the basic files that are necessary for any mod to succeed and function properly.
       Click on the Browse button next to a filename and traverse to the specific file in the legacy driver package, selection has been simplified to avoid confusion.  The example of legacy files and the location  below is for a 32bit driver package using the 10.2 legacy files.


****E.g: C:\ATI\Support\10-02_legacy_vista32-64_dd_ccc\Packages\Drivers\Display\LH_INF\B_95503





64bit MOD - Uses 7 or 8 files, 8 recommended !


The next illustration is for a 64bit MOD from the 10.2 legacy 64bit driver package





For DirectX 10 cards here is an example using the 13.4 Beta drivers, This is how the cocktailmaker of a 32 bit MOD should look like.




32bit mod example



For DirectX 10 cards here is another example using the 13.4 Beta drivers, This is how the cocktailmaker of a 64bit MOD should look like.







       Notice how the 2 MODS use different folder locations for the legacy files, that is because the files types have to match with the driver type being modded.


This should be the roadmap to modding all drivers.


      Just to emphasize I repeat the file structure below so you can grasp and understand the basic concept of modding with flem.


      There are 4 basic but essential files for 32bit drivers and 7 basic/essential files for 64bit drivers,
       hese files MUST BE LEGACY and compatible with your card type i.e DirectX9 or Directx 10.




Tips and precautions


If you experience difficulties or the driver does not install properly on a 64bit system then use the 8 files instead of the 7.


In some cases it is wise to use all 8 files on the left side of cocktailmaker for compatibility with 64bit cards.


        Note: AGP card users please use the files from a latest hotfix for your card type.


 * Warning: DONOT use 64 bit driver files with a 32bit driver package 


                 DONOT use 32bit driver files with a 64bit driver package.


                 This may cause un-desirable results.


For DirectX 9 cards the files must be Dx9 Compatible! Use legacy 10.2 or 9.11. Drivers earlier than 9.3  are also compatible. Give drivers files from your Laptop/Desktop manufacturer a try, in some cases the performance gains are exponential since they are specifically designed to work on your machine.e.g manufacturer driver files (from laptop model driver downloads):


atiumdag.dl_ and atiumdva.dl_ + atiumdva-ca_   could result in performance gains and a restored DXVA.

 DirectX10 card users can use files from any of the newer legacy drivers:  12.6 legacy , 13.1 legacy and any future legacy releases.

Changing the basic files alone is enough to get your new driver up and running.If you don't know what
you are doing then stick to changing only the basic files and leaving the rest of the files as they are.


The rest of the files are optional but may significantly boost performance and application compatibility,
 emphasis is always on using files that are compatible with your card type and platform.


4. After selecting the tasks and the driver files you are all set to start modding.Click on Modify and wait for it to finish.




OK i'm done modding the driver so what's next?


Signing the Modded Driver


Driver signing is now possible option after the mod process completes, to do it at a later time or if you want to sign another driver use the option in the Advanced options.


You must have Windows kits installed on your system for this to work. 




 Installing the Modded Driver


 Follow these steps to install the modified driver:


        1.  Uninstall your previous drivers and AMD Catalyst Install Manager first.


 2. Cleanup driver leftovers, you can use the AMD uninstall utility and then run Display Driver Uninstaller (DDU) for a thorough clean .


 3. Clear the leftover registry entries using a registry cleaner of your choice, you could use CCleaner its free.
 4. Disable Driver Signature enforcement(F8) when restarting windows, this step must be repeated every time you restart your machine.
 5. Install using Setup.exe nomally.


 6. Reboot and Disable Driver Signature enforcement.



In some cases Catalyst Control Center and the other options are not available in the install manager when you click on Setup.exe to install the driver in the normal way, this is common for packages after the Radeon 14.4. In this case you need to install the driver from Device Manager manually and MOD another earlier package e.g the 14.4 to get Catalayst Control Center to install.




What to do if the package you modded does not contain anything installable in the install manager. There is no driver and Catalyst Control Center in the list!


This is common if you MOD a driver after the 14.4 driver package. For the modded driver to work you will have to install it manually and use another package for Catalyst Control Center.




To install the driver manually from device manager use the steps below.


  • Uninstall the current driver using Display Driver Uninstaller(DDU) and reboot with Driver Signature Enforcement Disabled.
  • Open Device Manager and right click Microsoft Basic Display Adapter
  • Select "Browse my computer for driver software"
  • Then select "Let me Pick from a list of device drivers on my computer"
  • Click "Have disk"
  • Browse to the WHQL folder and in the drivers subfolder select the inf that corresponds to the version of Windows you are using :C0xxxxxxx.inf(for windows 10 64bit), CTxxxxxxx.inf(for Windows 10 32bit) or CBxxxxx.inf(for windows 8.1 32bit) or CUxxxxx.inf(for windows 8.164bit)  or CWxxxxxx.inf(for Windows 7 32bit) or C7xxxxxx.inf(for Windows 7 64bit). Depending on your OS choose the right file.
  • Install and reboot.
  • Disable Driver Signature Enforcement on restart.


How to install an earlier version of Catalyst Control Center if the other modded package's Install manager does not contain anything to install.

  1. Download AMD Catalyst WHQL 14.4 and extract it to the default folder.
  2. Open FLEM, select the 14.4 package and select option 4 only in FLEMs task selector, click customize driver.
  3. After FLEM is done customizing that package goto where you extracted the package and run Setup.exe.
  4. Make sure you uncheck the driver and AMD gaming evolved app in the list then go ahead and install the package.
  5. Reboot (Disabling Driver Signature Enforcement again).


Step by Step example of modding the latest 32bit drivers (32bit MOD)

This guide applies to most DirectX 9 cards (Any card before and including ATI HD 2300) . *** DirectX 10 cards users need to use the 13.9 legacy drivers as their base drivers for modding, apart from that the procedure is the same for both types of GPUs.

  What you need

The Process

Step 1

* MOD the 15.7.1 and select the 4 files from the 10.2 legacy package within FLEM(Driver Cocktailmaker). The first four from the list of files. 

32bit mod example

Step 2

* Now choose the the 14.4 package from the FLEM browse button and MOD that one too. After it completes you are done modding the drivers.

Step 3

This option is given to you after modding the driver, if you want to do it later you can do it as shown below.
Optional but recommended** to avoid headaches with disabling Driver Signature Enforcement at every boot.

Setting your machine into Test Mode. Set in the Advanced options section.


Using the method is the same manual process below, it is enought to set it in FLEM.

*** Manual way of enabling testmode - Not necessary if done using the method above.

From an elevated command prompt (Run as Admin): Run the commands below, copy and paste them into the Command prompt you just opened.

bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

bcdedit.exe -set TESTSIGNING ON


 Next launch DDU to Clean out the current drivers, it requires a reboot into safe mode which is done automatically, let it reboot into safe mode.

After Booting from safe mode(after cleaning out the drivers) you must disable Driver Signature Enforcement. **** important step Applies if you did not enable Test Mode above.

After cleaning out the drivers and rebooting.

* Go into Device Manager and install the driver manually from the 15.7.1 Package.
* After it is done installing now we are going to install the Catalyst Control Center , open the folder location of the 14.4 driver package
   and click on setup.exe. In the list of options make sure you un-check the display driver and the amd gaming evolved app(known to cause issues with modded drivers).
* Wait for the Install Manager to finish.
 * Reboot again.
 must disable Driver Signature Enforcement again **** important step This step applies only if you did not set your machine into Test Mode in the above step.

Step by Step example of modding the latest 64bit drivers (64bit MOD)

Step 1:  Same as above, the only difference is that instead of 4 files you will use 8 files from the 64bit folder.


Step 2: Same as above.

Step 3: Same as above.

Another handy option is the option to reboot into safe mode - Just click on this button if you want restart in safemode and remove old drivers.


   After correct installation and rebooting, your Catalyst Control Center should look something like the example below


 Good luck and enjoy your modded drivers.





Right Click

No right click