Phoenix Miner 3.0c Download

Changes in version 3.0c (since 2.9e):

  • Implemented auto-tune function which will find the best GT value for each GPU. You can activate it by either omitting the -gt parameter in the command line, or by pressing ‘z’ in the console. Note that auto-tune process takes about 3 to 5 minutes on average and during this time the hashrate will be lower and will go up and down. You can abort the auto-tuning by pressing the ‘g’ key in the console window.
  • Added support for ‘x’ key in console window. This will allow you to select a single GPU for manual or automatic GT tuning.
  • Added support for direct mining (without DAG switching for DevFee) of the following coins: Nekonium (NUKO), MIX, EtherGem (EGEM), AURA, Hotelbyte Coin (HBC), Genom (GEN), EtherZero (ETZ), Callisto   (CLO). See the -coin option documentation below for details how to specify the coin you are mining.
  • Added support for on-the-fly reload of config.txt file and applying the new options by pressing the key ‘c’ in the console window. Note that most options require restart in order to change. Currently the follwing options can be changed without restarting: -mi, -gt, -clf, -nvf, and all hardware control parameters (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc). This allows more convenient adjustment and fine-tuning of the mining rigs
  • Added -cdmrs option to reload the settings if config.txt is edited/uploaded by a remote manager. This allows you to change and reload the config.txt options via remote manager without access to the console window of the miner.
  • Small improvements in AMD kernels
  • Added -nvf 3 setting that could solve some problems with unstable Nvidia cards (but may affect hashrate negatively)
  • Added option -acm to turn on AMD compute mode on the supported GPUs. This is equivalent of pressing ‘y’ in the miner console.
  • Added option -retrydelay that sets the pause between the reconnection attempts in seconds (min value 0, default value: 20)
  • Added option -resetoc to reset the HW overclocking setting on startup to their default values
  • Added option -gpureset, which forces full reset of the GPU when the miner is paused (or before DAG generation when switching DAG epochs). This is designed to avoid problems like the hashrate drop of GeForce GTX1080 Ti after pause/resume. This option can be specified per GPU and is turned on by default for GTX1080 Ti.
  • Added option -gser for serializing of DAG creation if your PSU(s) can’t take all GPUs generating DAG simultaneously.
  • Graceful shutdown when closed by the close button of the console window (including reseting OC settings to defaults)
  • Added option -gsi to set the speed stats interval (5-30 seconds, default 5; 0 turns off the speed stats). The detailed stats are still shown every 45 seconds and aren’t affected by the -gsi value
  • Fixed crashing with Vega cards with AMD drivers 18.4.1 and newer
  • Many small fixes and changes

PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.

The speed is generally faster than Claymore’s Ethereum miner in eth only mode
(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and – keys while the miner is running).

If you have used Claymore’s Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore’s command-line options and confirguration
files with the notable exception of the dual mining feature (yet).

Please note that PhoenixMiner is extensively tested on many mining rigs but this is the
first public release and there still may be some bugs. Additionally, we are actively working on
bringing many new features in the future releases. If you encounter any problems or have
feature requests, please post them here (in this thread). We will do our best to answer in timely




Mobile Sliding Menu