Tuning AMD cards to mine PHI1612 Folm & LUX Updated

A few months ago I wrote an article on how to tune your AMD based miner to hash PHI1612 as quickly as possible. Back then LUX was the de facto PHI coin, on account of it being the only one. Today that has changed with the release of FOLM Coin, which at the time of writing is the more profitable coin to be mining.

The article helped a lot of people raise their PHI hash rates on their AMD hardware. However it is now out of date, and faster methods have been uncovered. Big thanks to user @PBFarmer who kindly pointed out some new methods. If you know something I don’t know, feel free to school me in the comments below.

Target Speeds:
RX580 16.5Mh/s (Stock), 18.5Mh/s (Overclocked)
RX480 15.5MH/s (Stock), 17.5Mh/s (Overclocked) 

Use SGMiner

SGMiner is the newest mining software for PHI, but it is actually slower than the older version. Try instead, you’ll find that it’s quicker at default settings, by as much as 10%. It’s not as stable as; i’ve found sometimes I have to reopen the miner a few times to get it to actually start mining. Once you’ve got it hashing, it runs fine. It may not be quicker on all systems than the newer 1.3, however it appears to give a speed which is consistently higher with less hassle and tuning involved. If it wont start, check if windows defender deleted your exe file. You may have to disable windows defender, or use 1.3.


Drivers don’t seem to make a huge amount of difference. If you have found different feel free to comment below, however I have tried old, new, and blockchain drivers and noticed almost no noticeable difference. I do recommend using an up-to-date package, and make sure crossfire is switched off, as this does seem to improve hash rates by a small amount.


Overclocking your GPU core is an important part of getting speeds up. If you are mining PHI, you should push your GPU Core up as high as it will go. Do not put the core voltage higher or increase the power limit unless you are monitoring the wattage, as in most cases the increase in hash rate will be offset by the increase in power consumption. I found that MSI Afterburner causes conflict with SGMiner, which meant that as long as afterburner started up with windows, my hash rate would drop, regardless of the settings in Afterburner. This started when I checked “force constant voltage”, but continued even after the option was unchecked. Uninstalling Afterburner was the only thing that solved it, and brought my hash rates back up. I would therefore suggest that if your cards seem to be going to slow, uninstall afterburner and try alternative software. You can downclock your GPU Memory with almost no negative effect, which can help lower the power consumption.

BIOS Mods & Memory Straps

Some of my cards are BIOS modded to improve etherium hash rates. However these mods which are so effective when hashing ETH make no difference at all on PHI. I would therefore actually suggest that you don’t need to bother ruining your warranty with BIOS flashing. If you do want to make changes via BIOS settings, the only goal is to push core speed as high as possible with the lowest possible voltage.

Config File Variables

With the 1.3 software, the config file variables make a huge difference to your hash speed. With the 1.1 software, I have noticed that it is less sensitive. However, modify the following values:

––worksize <value> Changing this does make some difference. It also seemed to make the values much more dynamic over time. I settled on a value of 128 as that seemed to give a stable and high result. 

––thread-concurrency <value> Now we are into territory that makes a difference. A RX580 card has 2304 shaders, so you need to use a multiple of this number. I tried most values, but eventually settled on 4608 has giving the best result over a longer period of time. 

––gpu-threads <value> This value makes a huge difference with the 1.3 software, however it seems less pronounced with 1.1. You will want a value of at least 2, however high values beyond this seem to make very little difference, and can cause crashing problems in some systems. I would therefore suggest ––gpu-threads  2





Leave a Reply

Your email address will not be published.