Phoenixminer 5

Phoenixminer 5 DEFAULT
placeholder image 1
Fast & Easy

Effective Ethereum mining speed is higher by 3-5% because of a completely different miner code - much less invalid and outdated shares, higher GPU load, optimized OpenCL code, optimized assembler kernels.

placeholder image 2
Works On All Devices

Supports both AMD and nVidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64.

Download Now

Stability & Reliability

The watchdog timer checks periodically if any of the GPUs freezes and if it does, restarts the miner. Supports memory straps for AMD/NVIDIA cards. Use the command-line option to activate it.

Getting Started

Step 1: Download the miner

Click here to download PhoenixMiner
Once the download is complete, extract the contents of the .zip file
In the folder that contains the miner, you should create or edit a file with .bat extension. You can do this in any text editor (for example, Notepad). When you save the file, it’s important to choose ‘All Files’ as a file type, not ‘txt’. Otherwise, you’ll have .bat.txt at the end of the file name, and miner won’t be able to open this file. Your bat file (let’s say it’s called 1_Ehereum-nanopool.bat) should contain the following text (Step 2):

Attention! For security reasons, Windows may stop you from opening the bat file. In this case, you should permit it to open in the pop-up window.

Step 2: Enter the following command:

Step 3: Configure the miner with your settings

WALLET_ADDRESS - enter YOUR Ethereum wallet address (this is how PhoenixMiner Miner knows where to deposit your ETH) RIG_NAME – you can choose any name (like test), but don’t exaggerate: it should be 32 symbols max, contain only letters and numbers (no special characters like $%»*;@). Make sure to replace the pool and wallet address by what you're using in all files.

Step 4: Start mining

Double click your Bat file to start the miner. The miner will start, run the setx commands to set those environment variables, initialize each of your GPU’s, build the DAG file on each of your GPU’s and start hashing away. Let it run for about 20 seconds and then click “s” to display your Hashing speed. If you’ve followed the steps above you should see this screen.

Getting Started With Ethereum Mining

How to check how much you’ve mined?

Now that your miner is set up, you’re able to sit back and watch as your video cards gain you passive income every day in the form of Ethereum. It is important to consider any variable costs that you may incur during the mining to determine your profitability. Variable costs may be electrical costs, maintenance costs, pool fees, dev fees, exchange fees, etc.

Every pool has a different interface but the principle stays the same. You’ll need to go to your pools website and type in your public wallet address. Let us use Ethermine pool as an example.

You type your public wallet address in the search bar and you’ll be able to see all of the information about your Ethereum mining efforts. In the case of Ethermine pool once your balance reaches 0.01 ETH it will get sent to your wallet address that you’ve typed into the start.bat file earlier.

If you would like to donate Hashing power - 8503c4f68ebab097178eeb3a175b48398F4ed040



How does Ethereum mining work?

The result of digital mining is called proof of work system. ... However, mining Ethereum means more than increasing the volume of Ether in circulation. It is also necessary for securing the Ethereum network as it creates, verifies, publishes, and propagates blocks in the blockchain.

What do you need to mine Ethereum?

  1. An Ethereum wallet to hold all of your newly found currency;
  2. GPU drivers;
  3. A mining application (PhoenixMiner AMD+NVIDIA GPU Miner);
  4. A mining pool address if you're going to mine within a mining pool;
  5. A graphics card (GPU) with at least 4gb of RAM.

How many Ethereum can be mined?

Most Ethereum blocks are around 2mb. A new Ethereum block is created every 14 seconds. 18 Million Ether are mined every year.

PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.0e or later version to continue mining after DAG epoch 350 (both ETH and ETC has already passed DAG epoch 350). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0e and later:
If your rig is using Intel CPU, use the integrated graphics as primary display adapter. To do this, go to motherboard’s BIOS setup and change the “Primary display adapter” to iGPU (or integrated GPU). Also, if you are using actual monitor or HDMI plug, put it in the motherboard video output.
If you can’t use integrated GPU, replace the primary GPU with one with 6 or 8 GB VRAM.
Do not upgrade to a new AMD driver unless it is explicitly supported by PhoenixMiner. With 4 GB AMD cards, this will not only lower your hashrate but it will make impossible to mine when the DAG epoch is above 350.
After the DAG epoch becomes more than 350, the optimal -gt value for the 4 GB AMD cards may change. So, we recommend to run auto-tune again after DAG epoch 350 to find the best GT values for the cards.

After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers:
Good drivers. These are versions from to 19.7.5 (inclusive), and from 19.12.2 to 20.8.1 (inclusive). These will allow you to mine until DAG epoch 372-373 and won’t need restart of PhoenixMiner on each DAG epoch change.
Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).
If you are using a pool with automatic switching between the coins (like nicehash for example), you should use one of the good drivers above, and shouldn’t use the -dagrestart option.
Drivers older than 18.1.1 were not tested for 4 GB DAG operation. Specifically, there are multiple reports that the old blockchain drivers from 2017 doesn’t work with 4 GB cards beyond epoch 350. If you are still using the blockchain drivers, you must upgrade to newer drivers if you have 4 GB AMD cards. After that, do not forget to turn on the Compute mode for all cards in AMD control center.

Under Linux all relatively recent drivers (i.e. last 24-36 months) allow mining until epoch 378-380 but there are much more driver bugs, so if you are happy with your current driver version, do not change it.

Changes in version 5.1c (since 5.0e):

Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
Added new parameter -nvmem to force using straps even on unsupported Nvidia GPUs (use -nvmem 1 for GDDR5 cards, or -nvmem 2 for GDDR5X cards)
Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
Added support for latest AMD drivers 20.8.1 under Windows and 20.20-1089974 under Linux
Fixed long-standing problems with -gpow option, which now works properly
Removed some dead ethash-based altcoins and updated the support for the rest of them
Many other small improvements and fixes
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 Linux 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.

PhoenixMiner also supports Ubqhash for mining UBQ, ProgPOW for mining BCI, and dual mining
Ethash/Ubqhash with Blake2s.

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

Easy Plug&Play OS Linux with our miner:

Please note that PhoenixMiner is extensively tested on many mining rigs but 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 fashion.



  1. Quick start

You can download PhoenixMiner 5.0e from here: (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file only if you want to mine BCI with Nvdia cards under Windows):
SHA-1: 19eb7292d34593576e069ccfec96ede30ed135a0
SHA-256: 97c1e17afc501c41643e4c5d54bc8b705041931fa69ce89bf6ebcbd6de2a4c0f
SHA-512: f6671f1afa373bd01769e4e20d0d171f6b8df8c9d49f2858d81ea51f49969ab76c9390de28cffdbb62efdcaad22309b0a7eac637b5db7b6151074590d1511c23

SHA-1: edf362bffc3291a4038c4deef80cad2131743b30
SHA-256: 3d98b14bd9753cbd0a0e2c5cc2de8136f6963c52db74df252fe33e5ad6b21df7
SHA-512: 3c1ffe93a323b0e9cbdd06a540f790b0f83030efe5c7cf87107b49a77808c1177ac2b19e493af083fc5abf546b618f78a99b7960e6befdebc14a712c4e0c8f1c

SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

Here are the command line parameters for some of the more popular pools and coins: (ETH):
PhoenixMiner.exe -pool -pool2 -wal YourEthWalletAddress.WorkerName -proto 3 (ETH, secure connection):
PhoenixMiner.exe -pool ssl:// -pool2 ssl:// -wal YourEthWalletAddress.WorkerName -proto 3 (ETH):
PhoenixMiner.exe -pool -pool2 -wal YourEthWalletAddress.WorkerName -proto 3 (ETH):
PhoenixMiner.exe -pool -wal YourEthWalletAddress/WorkerName -pass x
nicehash (ethash):
PhoenixMiner.exe -pool stratum+tcp:// -wal YourBtcWalletAddress -pass x -proto 4 -stales 0
f2pool (ETH):
PhoenixMiner.exe -epool -ewal YourEthWalletAddress -pass x -worker WorkerName
miningpoolhub (ETH):
PhoenixMiner.exe -pool -wal YourLoginName.WorkerName -pass x -proto 1 (ETH):
PhoenixMiner.exe -pool -wal YourLoginName.WorkerName -pass x -proto 1 (ETC):
PhoenixMiner.exe -pool -wal YourEtcWalletAddress.WorkerName (ETC):
PhoenixMiner.exe -pool -pool2 -worker WorkerName -wal YourEtcWalletAddress -pass x -retrydelay 2 (ethash auto-switching):
PhoenixMiner.exe -pool -wal YourEthWalletAddress -worker WorkerName -proto 2 (EXP):
PhoenixMiner.exe -pool -wal YourExpWalletAddress/WorkerName
miningpoolhub (MUSIC):
PhoenixMiner.exe -pool -wal YourLoginName.WorkerName -pass x -proto 1 (UBIQ):
PhoenixMiner.exe -pool -wal YourUbqWalletAddress -worker WorkerName -coin ubq (UBIQ):
PhoenixMiner.exe -pool -wal YourUbqWalletAddress -pass x -worker WorkerName -coin ubq (UBIQ):
PhoenixMiner.exe -pool -wal YourUbqWalletAddress.WorkerName -pass x -proto 4 -coin ubq (PIRL):
PhoenixMiner.exe -pool -wal YourPirlWalletAddress -pass x -worker WorkerName (Metaverse ETP):
PhoenixMiner.exe -pool -wal YourMetaverseETPWalletAddress -worker Rig1 -pass x (Ellaism):
PhoenixMiner.exe -pool -wal YourEllaismWalletAddress -worker Rig1 -pass x (ETH PPS):
PhoenixMiner.exe -pool -wal YourEthWalletAddress.WorkerName -proto 4 -pass x (ETH HVPPS):
PhoenixMiner.exe -pool -wal YourEthWalletAddress.WorkerName -proto 4 -pass x (CLO):
PhoenixMiner.exe -pool -pool2 -worker WorkerName -wal YourEthWalletAddress -pass x -coin clo -retrydelay 2 (CLO):
PhoenixMiner.exe -pool -wal YourEthWalletAddress -pass x -coin clo -worker rigName

Dual-mining command-line examples:

ETH on ETH, Blake2s on Nicehash:
PhoenixMiner.exe -pool ssl:// -pool2 ssl:// -wal YourEthWalletAddress.WorkerName -proto 3 -dpool -dwal YourBtcWalletAddress -dcoin blake2s
Nicehash (Ethash + Blake2s):
PhoenixMiner.exe -pool stratum+tcp:// -wal YourBtcWalletAddress -pass x -proto 4 -stales 0 -dpool -dwal YourBtcWalletAddress -dcoin blake2s

ProgPOW command-line examples:
BCI on BCI-Server:
PhoenixMiner.exe -pool -wal YourBciWalletAddress.Rig1 -coin bci -proto 1

  1. Features, requirements, and limitations
  • Supports AMD RX5700, Radeon VII, Vega, 580/570/480/470, 460/560, Fury, 390/290 and older AMD GPUs with enough VRAM
  • Supports Nvidia 20x0, 16x0, 10x0 and 9x0 series as well as older cards with enough VRAM
  • Highly optimized OpenCL and CUDA cores for maximum ethash mining speed
  • Optional “green” kernels for RX580/570/560/480/470/460 to lower the power consumption by 2-3% with small, or no drop in hashrate
  • Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes)
  • Dual mining ethash/Blake2s with lowest devfee of 0.9% (35 seconds defvee mining per each 65 minutes)
  • Advanced statistics: actual difficulty of each share, effective hashrate at the pool, and optional showing of estimated income in USD
  • DAG file generation in the GPU for faster start-up and DAG epoch switches
  • Supports all ethash mining pools and stratum protocols
  • Supports secure pool connections (e.g. ssl:// to prevent IP hijacking attacks
  • Detailed statistics, including the individual cards hashrate, shares, temperature, fan speed, clocks, voltages, etc.
  • Unlimited number of fail-over pools in epools.txt configuration file (or two on the command line)
  • Automatic GPU tuning for the AMD GPUs to achieve maximum performance with your rig
  • Supports devfee on alternative ethash currencies like ETC, EXP, Music, UBQ, Pirl, Ellaism, Metaverse ETP, PGC, Akroma, WhaleCoin, Victorium, Nekonium, Mix, EtherGem, Aura, HBC, Genom, EtherZero, Callisto, DubaiCoin, MOAC, Ether-1, and EtherCC. This allows you to use older cards with small VRAM or low hashate on current DAG epochs (e.g. GTX970).
  • Full compatibility with the industry standard Claymore’s Dual Ethereum miner, including most of command-line options, configuration files, and remote monitoring and management.
  • Supports the new Ubqhash algorithm for the UBQ coin. Please note that you must add -coin ubq to your command line (or COIN: ubq to your epools.txt file) in order to mine UBQ
  • Supports the ProgPOW algorithm for the Bitcoin Interest (BCI) coin mining. Please note that you must add -coin bci to your command line (or COIN: bci to your epools.txt file) in order to mine BCI
  • Supports the ProgPOW algorithm for mining BCI.
  • More features coming soon!

PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.), or Linux x64 (tested on Ubuntu LTS
and Debian stable).

PhoenixMiner also supports dual mining (simultaneous mining of ethash/ubqhash and other cryptocoin algorithm).
Currently we support only Blake2s as secondary algorithm for dual mining. Note that when using dual mining,
there is no devfee on the secondary coin but the devfee on the main coin is increased to 0.9%. In other words,
if you are using the dual mining feature PhoenixMiner will mine for us for 35 seconds every 65 minutes.

Solo mining is supported since version 2.7c.

While the miner is running, you can use some interactive commands. Press the key ‘h’ while the
miner’s console window has the keyboard focus to see the list of the available commands. The
interactive commands are also listed at the end of the following section.

  1. Command-line arguments

Note that PhoenixMiner supports most of the command-line options of Claymore’s dual Ethereum miner
so you can use the same command line options as the ones you would have used with Claymore’s miner.

Pool options:
-pool host:port Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
-wal <wallet> Ethash wallet (some pools require appending of user name and/or worker)
-pass <password> Ethash password (most pools don’t require it, use ‘x’ as password if unsure)
-worker <name> Ethash worker name (most pools accept it as part of wallet)
-proto <n> Selects the kind of stratum protocol for the ethash pool:
1: miner-proxy stratum spec (e.g. coinotron)
2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools
3: qtminer (e.g. ethpool)
4: EthereumStratum/1.0.0 (e.g. nicehash)
5: EthereumStratum/2.0.0
-coin <coin> Ethash coin to use for devfee to avoid switching DAGs:
auto: Try to determine from the pool address (default)
eth: Ethereum
etc: Ethereum Classic
exp: Expanse
music: Musicoin
ubq: UBIQ
pirl: Pirl
ella: Ellaism
etp: Metaverse ETP
pgc: Pegascoin
akroma: Akroma
whale: WhaleCoin
vic: Victorium
nuko: Nekonium
mix: Mix
egem: EtherGem
aura: Aura
hbc: Hotelbyte Coin
gen: Genom
etz: EtherZero
clo: Callisto
dbix: DubaiCoin
moac: MOAC
etho: Ether-1
etcc: EtherCC
yoc: Yocoin
b2g: Bitcoiin2Gen
esn: Ethersocial
ath: Atheios
reosc: REOSC
qkc: QuarkChain
bci: Bitcoin Interest
-stales <n> Submit stales to ethash pool: 1 - yes (default), 0 - no
-pool2 host:port Failover ethash pool address. Same as -pool but for the failover pool
-wal2 <wallet> Failover ethash wallet (if missing -wal will be used for the failover pool too)
-pass2 <password> Failover ethash password (if missing -pass will be used for the failover pool too)
-worker2 <name> Failover ethash worker name (if missing -worker will be used for the failover pool too)
-proto2 <n> Failover ethash stratum protocol (if missing -proto will be used for the failover pool too)
-coin2 <coin> Failover devfee Ethash coin (if missing -coin will be used for the failover pool too)
-stales2 <n> Submit stales to the failover pool: 1 - yes (default), 0 - no
-dpool host:port Dual mining pool address
-dwal <wallet> Dual mining wallet
-dpass <password> Dual mining pool password (most pools don’t require it, use ‘x’ as password if unsure)
-dworker <name> Dual mining worker name
-dcoin blake2s Currently only the Blake2s algorithm is supported for dual mining. If you want to put
all dual mining pools in dpools.txt, you need to set -dcoin blake2s in the command-line or in config.txt
to force the miner to load the dual mining pools from dpools.txt
-dstales <n> Submit stales to the dual mining pool: 1 - yes (default), 0 - no
General pool options:
-fret <n> Switch to next pool afer N failed connection attempts (default: 3)
-ftimeout <n> Reconnect if no new ethash job is receved for n seconds (default: 600)
-ptimeout <n> Switch back to primary pool after n minutes. This setting is 30 minutes by default;
set to 0 to disable automatic switch back to primary pool.
-retrydelay <n> Seconds to wait before reconnecting (default: 20)
-gwtime <n> Recheck period for Solo/GetWork mining (default: 200 ms)
-rate <n> Report hashrate to the pool: 1 - yes, 0 - no (1 is the default), 2 - (for solo mining only)
use alternative name of the report method “eth_submitHashRate” instead of “eth_submitHashrate”
Benchmark mode:
-bench [<n>],-benchmark [<n>] Benchmark mode, optionally specify DAG epoch. Use this to test your rig.
If you specify only the -bench option, you will benchmark the ethash algorithm. If you want to bench
the dual mining, use the options -bench <n> -dcoin blake2s. If you want to benchmark the ProgPOW BCI
algorithm, use the options -bench <n> -coin bci
Remote control options:
-cdm <n> Selects the level of support of the CDM remote monitoring:
0: disabled
1: read-only - this is the default
2: full (only use on secure connections)
-cdmport <port> Set the CDM remote monitoring port (default is 3333). You can also specify
<ip_addr:port> if you have a secure VPN connection and want to bind the CDM port to it
-cdmpass <pass> Set the CDM remote monitoring password
-cdmrs Reload the settings if config.txt is edited/uploaded remotely. Note that most options require restart in order to change.
Currently the follwing options can be changed without restarting: -mi, -gt, -sci, -clf, -nvf, and all hardware control parameters
(-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc).
Mining options:
-amd Use only AMD cards
-acm Turn on AMD compute mode on the supported GPUs. This is equivalent of pressing ‘y’ in the miner console.
-nvidia Use only Nvidia cards
-gpus <123 …n> Use only the specified GPUs (if more than 10, separate the indexes with comma)
-mi <n> Set the mining intensity (0 to 14; 12 is the default for the new kernels). You may specify this option per-GPU.
-gt <n> Set the GPU tuning parameter (6 to 400). The default is 15. You can change the
tuning parameter interactively with the ‘+’ and ‘-’ keys in the miner’s console window.
If you don’t specify -gt or you specify value 0, the miner will start auto-tuning to determine the best GT value for each GPU
Note that when the GPU is dual-mining, it ignores the -gt values, and uses -sci instead.
-sci <n> Set the dual mining intensity (1 to 1000). The default is 30. As you increase the value of -sci,
the secondary coin hashrate will increase but the price will be higher power consumption and/or
lower ethash hashrate.
You can change the this parameter interactively with the ‘+’ and ‘-’ keys in the miner
console window. You may specify this option per-GPU. If you set -sci to 0,
the miner will use auto-tuning to determine the best value, while trying to maximize the
ethash hashrate regardless of the secondary coin hashrate.
-clKernel <n> Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative, 3 - turbo (1 is the default)
-clGreen <n> Use the power-efficient (“green”) kernels (0: no, 1: yes; default: 0).
You may specify this option per-GPU. Note that you have to run auto-tune again as the
optimal GT values are completely different for the green kernels
-clNew <n> Use the new AMD kernels (0: no, 1: yes; default: 1)
-clf <n> AMD kernel sync (0: never, 1: periodic; 2: always; default: 1)
-nvKernel <n> Type of Nvidia kernel: 0 auto (default), 1 old (v1), 2 newer (v2), 3 latest (v3).
Note that v3 kernels are only supported on GTX10x0 GPUs. Also note that dual mining is
supported only by v2 kernels. You may specify this option per-GPU.
-nvdo <n> Enable Nvidia driver-specific optimizations (0 - no, the default; 1 - yes). Try -nvdo 1 if your
are unstable. You may specify this option per-GPU.
-nvNew <n> Use new Nvidia kernels if supported (0: no, 1: yes; default: 1)
-nvf <n> Nvidia kernel sync (0: never, 1: periodic; 2: always; 3: forced; default: 1). You may specify this option per-GPU.
-mode <n> Mining mode (0: dual mining if dual pool(s) are specified; 1: ethash only even if dual pools are specified).
You may specify this option per-GPU.
-list List the detected GPUs devices and exit
-gbase <n> Set the index of the first GPU (0 or 1, default: 1)
-minRigSpeed <n> Restart the miner if avg 5 min speed is below <n> MH/s
-eres <n> Allocate DAG buffers big enough for n epochs ahead (default: 2) to
avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability
-dagrestart <n> Restart the miner when allocating buffer for a new DAG epoch. The
possible values are: 0 - never, 1 - always, 2 - auto (the miner decides depending on the driver version).
This is relevant for 4 GB AMD cards, which may have problems with new DAG epochs after epoch 350.
-lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs
(0-3, default: 0 - fastest, 3 - slowest).
-gser <n> Serializing DAG creation on multiple GPUs (0 - no serializing, all GPUs generate the DAG simultaneously, this is the default;
1 - partial overlap of DAG generation on each GPU; 2 - no overalp (each GPU waits until the previous one has finished generating the DAG);
3-10 - from 1 to 8 seconds delay after each GPU DAG generation before the next one)
-gpureset <n> Fully reset GPU when paused (0 - no, 1 - yes; default: no, except on 1080Ti). You may specify this option per-GPU.
-altinit Use alternative way to initialize AMD cards to prevent startup crashes
-rvram <n> Minimum free VRAM in MB (-1: don’t check; default: 384 for Windows, and 128 for Linux)
-wdog <n> Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The watchdog timer checks
periodically if any of the GPUs freezes and if it does, restarts the miner (see the -rmode
command-line parameter for the restart modes)
-wdtimeout <n> Watchdog timeout (30 - 300; default 45 seconds). You can use this parameter to increase
the default watchdog timeout in case it restarts the miner needlessly
-rmode <n> Selects the restart mode when a GPU crashes or freezes:
0: disabled - miner will shut down instead of restarting
1: restart with the same command line options - this is the default
2: reboot (shut down miner and execute reboot.bat)
-log <n> Selects the log file mode:
0: disabled - no log file will be written
1: write log file but don’t show debug messages on screen (default)
2: write log file and show debug messages on screen
-logfile <name> Set the name of the logfile. If you place an asterisk (*) in the logfile name, it will be
replaced by the current date/time to create a unique name every time PhoenixMiner is started. If there
is no asterisk in the logfile name, the new log entries will be added to end of the same file. If you
want to use the same logfile but the contents to be overwritten every time when you start the miner,
put a dollar sign ($) character in the logfile name (e.g. -logfile my_log.txt$).
-logdir <path> Set a path where the logfile(s) will be created
-logsmaxsize <n> Maximum size of the logfiles in MB. The default is 200 MB (use 0 to turn off the limitation).
On startup, if the logfiles are larger than the specified limit, the oldest are deleted. If you use a
single logfile (by using -logfile), then it is truncated if it is bigger than the limit and a new one
is created.
-config <name> Load a file with configuration options that will be added to the command-line options.
Note that the order is important. For example, if we have a config.txt file that contains -cclock 1000
and we specify command line -cclock 1100 -config config.txt, the options from the config.txt file will take
precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100)
then the second option takes precedence and the resulting -cclock will be 1100. Note that only one -config
option is allowed. Also note that if you reload the config file with ‘c’ key or with the remote interface,
its options will take precedence over whatever you have specified in the command-line.
-timeout <n> Restart miner according to -rmode after n minutes
-pauseat hh:mm Pause the miner at hh::mm (24 hours time). You can specify multiple times: -pauseat 6:00,12:00
-resumeat hh:mm Resume the miner at hh::mm (24 hours time). You can specify multiple times: -resumeat 8:00,22:00
-gswin <n> GPU stats time window (5-30 sec; default: 15; use 0 to revert to pre-2.8 way of showing momentary stats)
-gsi <n> Speed stats interval (5-30 sec; default: 5; use 0 to disable). The detailed stats are still
shown every 45 seconds and aren’t affected by the -gsi value
-astats <n> Show advanced stats from Web sources (0: no; 1: yes). By default the coin exchange rates are updated every
4 hours, and the coin difficulty is updated every 8 hours. You can increase these periods by specifying
for example -astats 12, which will increase update periods to 12 and 24 hours respectively
-gpow <n> Lower the GPU usage to n% of maximum (default: 100). If you already use -mi 0 (or other low value) use -li instead
-li <n> Another way to lower the GPU usage. Bigger n values mean less GPU utilization; the default is 0.
-resetoc Reset the hardware overclocking settings on startup
-leaveoc Do not reset overclocking settings when closing the miner
Hardware control options, use comma to specify different values for each GPU:
-tt <n> Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards,
1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n 😵
-hstats <n> Level of hardware monitoring: 0 - temperature and fan speed only; 1 - temperature, fan speed, and power;
2 - full (include core/memory clocks, voltages, P-states). The default is 1.
-pidle <n> Idle power consumption of the rig in W. Will be added to the GPU power consumption when
calculating the total power consumption of the rig.
-ppf <n> The power usage of each GPU will be multiplied by this value to get the actual usage. This value is
in percent, so for example if the GPU reports 100 W power usage and you have specified -ppf 106 the GPU
power usage will be calculated to be 100 * (106 / 100) = 106 W. This allows you to correct for the efficiency
of the PSUs and the individual GPUs. You can also specify this value for each GPU separately.
-prate <n> Price of the electricity in USD per kWh (e.g. -prate 0.1). If specified the miner will calculate the
rig daily electricity cost
-fanmin <n> Set fan control min speed in % (-1 for default)
-fanmax <n> Set fan control max speed in % (-1 for default)
-fcm <n> Set fan control mode (0 - auto, 1 - use VBIOS fan control, 2 - forced fan control; default: 0)
-tmax <n> Set fan control max temperature (0 for default)
-powlim <n> Set GPU power limit in % (from -75 to 75, 0 for default)
-cclock <n> Set GPU core clock in MHz (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)
-cvddc <n> Set GPU core voltage in mV (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)
-mclock <n> Set GPU memory clock in MHz (0 for default)
-mvddc <n> Set GPU memory voltage in mV (0 for default)
-tstop <n> Pause a GPU when temp is >= n deg C (0 for default; i.e. off)
-tstart <n> Resume a GPU when temp is <= n deg C (0 for default; i.e. off)
-mt <n> VRAM timings (AMD under Windows only): 0 - default VBIOS values; 1 - faster timings; 2 - fastest timings.
The default is 0. This is useful for mining with AMD cards without modding the VBIOS. If you have modded BIOS,
it is probably faster than even -mt 2
General Options:
-v,–version Show the version and exit
-vs Show short version string (e.g. “4.1c”) and exit
-h,–help Show information about the command-line options and exit

Per-GPU options
Some of the PhoenixMiner options can provide either the same setting for all GPUs, or a different
setting for each of the GPUs. For example, to specify the -gt value for all cards you would write
-gt 90 but if you want to specify a different GT value for each of the cards, use something like this:
-gt 20,15,40,90,90 for a five-GPU mining rig. This would set GT to 20 for the first GPU, 15 for the second
GPU, and so on. If you specify less values than you have GPUs, the rest of the GPUs will use the default
value for the parameter.

You can also use another, more flexible way of specifying different values for the different cards.
This is best explained by example: -cclock *:1100,1-3:1090,4:1300 - here we are setting core clock
to 1100 MHz for all cards, except the cards 1 to 3, on which it is set to 1090 MHz, and card 4 to 1300 MHz.

The part before the colon (:) is the selector, which selects the GPUs for which the value after the colon is applied. The selector can be:

  • single GPU index: e.g. 5:1000 sets 1000 for the 5th GPU
  • range of GPU indexes: e.g 2-5:1200 sets 1200 for the GPUs 2,3,4, and 5
  • asterisk, which sets the value for all GPUs
  • label amd or nvidia: e.g. amd:1090 sets the value to 1090 for all AMD cards
  • arbitrary string that starts with letter and can contain letters, numbers and asterisks,
    which is matched with the GPU name as listed by PhoenixMiner. Example: gtx*1070:+500 will
    set value +500 for all cards which contain ‘gtx’ and ‘1070’ in their names with anything
    between them. This will match ‘Nvidia GeForce GTX 1070’ but not ‘Nvidia GeForce 1070’.

Note that if more than one selector matches given card, than only the last one counts.
Example: -cclock *:1100,1-4:1090,2:1300 will set card 2 to 1300; cards 1,2, and 4 to 1090;
and the rest of the cards to 1100 MHz core clock.

Additionally, while the miner is running, you can use the following interactive commands
in the console window by pressing one of these keys:
s Print detailed statistics
1-9 Pause/resume GPU1 … GPU9 (if you have more than 9 GPUs, type 010 for card 10, 011 for card 11, etc.)
p Pause/resume the whole miner
+,- Increase/decrease GPU tuning parameter
g Reset the GPU tuning parameter (and stop auto-tuning if active)
x Select the GPU(s) for manual or automatic GT tuning
z Start AMD auto-tune process
r Reload epools.txt and switch to primary ethash pool
e Select the current ethash pool (if you have more than 9 pools in the list, type 010 for pool 10, 011 for pool 11, etc.)
d Select the current dual-mining pool
y Turn on AMD Compute mode if it is off on some of the GPUs
c Reload the config.txt file (some settings require restart, see -cdmrs option above for details)
h Print this short help

  1. Configuration files

Note that PhoenixMiner supports the same configuration files as Claymore’s dual Ethereum miner
so you can use your existing configuration files without any changes.

Instead of using command-line options, you can also control PhoenixMiner with configuration
files. If you run PhoenixMiner.exe without any options, it will search for the file config.txt
in the current directory and will read its command-line options from it. If you want, you can
use file with another name by specifying its name as the only command-line option
when running PhoenixMiner.exe.

You will find an example config.txt file in the PhoenixMiner’s directory.

Instead of specifying the pool(s) directly on the command line, you can use another configuration
file for this, named epools.txt. There you can specify one pool per line (you will find an example
epools.txt file in the PhoenixMiner’s directory).

For the dual mining pools, you can use the dpools.txt file, which has the same format as epools.txt
but for the secondary coin. You will find an example epools.txt file in the PhoenixMiner’s directory.
Note that unlike the epools.txt, which is loaded each time when the miner starts, the dpools.txt file
is only read if you specify a dual mining pool on the command line with -dpool, or at least add
the -dcoin blake2s command-line option.

The advantages of using config.txt and epools.txt/dpools.txt files are:

  • If you have multiple rigs, you can copy and paste all settings with these files
  • If you control your rigs via remote control, you can change pools and even the miner options by
    uploading new epools.txt files to the miner, or by uploading new config.txt file and restarting
    the miner.
  1. Remote monitoring and management

Phoenix miner is fully compatible with Claymore’s dual miner protocol for remote monitoring and
management. This means that you can use any tools that are build to support Claymore’s dual miner,
including the “Remote manager” application that is part of Claymore’s dual miner package.

We are working on much more powerful and secure remote monitoring and control functionality and
control center application, which will allow better control over your remote or local rigs and some
unique features to increase your mining profits.

  1. Hardware control options

Here are some important notes about the hardware control options:
Hardware control options are supported for both AMD and Nvidia cards under Windows. Under Linux most options are supported only for AMD cards.
If you specify a single value (e.g. -cvddc 1150), it will be used on all cards. Specify different values for each card like this (separate with comma): -cvddc 1100,1100,1150,1120,1090 If the specified values are less than the number of GPUs, the rest of GPUs will use the default values.
We have tested only on relatively recent AMD GPUs (RX460/470/480/560/570/580, Vega, Radeon VII, RX5700). Your results may vary with older GPUs.
The blockchain beta drivers from AMD show quite unstable results - often the voltages don’t stick at all or revert back to the default after some time. For best results use the newer drivers from AMD: 18.5.1 or later, where most of the bugs are fixed.
-tmax specifies the temperature at which the GPU should start to throttle (because the fans can’t keep up).
If you use other programs for hardware control, conflicts are possible and quite likely. Use something like GPU-Z to monitor the voltages, etc. MSI Afterburner also seems to behave OK (so you can use it to control the Nvidia cards while AMD cards are controller by PhoenixMiner).
This should be obvious but still: if given clocks/voltages are causing crashes/freezes/incorrect shares when set with third-party program, they will be just as much unstable when set via PhoenixMiner hardware control options.
If you have problems with hardware control options of PhoenixMiner and you were using something else to control clocks, fans, and voltages (MSI Aftrerburner, OverdriveNTool, etc.), which you were happy with, it is probably best to keep using it and ignore the hardware control options of PhoenixMiner (or use only some of them and continue tweaking the rest with your third-party tools).

1 ReplyLast reply Sours:
  1. Miniature objects for crafts
  2. Electric fuel pump walmart
  3. 2005 silverado brake pads
  4. Grey laminate stairs
  5. Pine trails apartments

PhoenixMiner v5.5c: AMD/NVIDIA GPU Miner for Windows & Linux (Step by Step Guide)

phoenix miner 5.5c

PhoenixMiner – is a high performance Ethereum (ETH) and ERC20 miner with official full Windows / Linux support. PhoenixMiner is one of the most efficient and convenient miners to date, which is why it has received universal miner recognition. It is the fastest (arguably the fastest) Ethash miner (ETH, ETC, Muiscoin, EXP, UBQ, etc.) and supports AMD and Nvidia cards (including mixed mining rigs). Development fee is 0.65% (the lowest in the industry). This means that every 90 minutes the miner will mine for us, our developers, for 35 seconds.

Changes in v5.5c

  • Added native kernels for AMD RX6800 and RX6900 GPUs. This is faster than
  • common cores and produces a lot less legacy stock
  • Updated cores for AMD Polaris, Vega and Navi GPUs that are slightly faster and use
  • less energy than before when mining ETH. To use these updated kernels, you need to use
  • drivers 20.5.1 or newer under Win10 or 20.10.x or newer under Linux
  • Nvidia mining cards (P106, P104, etc.) Can now use belts and hardware control.
  • options (power limitation, memory overclocking, maximum temperature, etc.) under Windows
  • Added support for the latest driver AMD for Windows 21.1.1.
  • Added a new parameter -mcdag to reset memory overclocking on Nvidia cards during
  • DAG generation. This may allow you to set higher memory overclocks on your Nvidia cards.
  • without the risk of damaging the DAG buffer, which could lead to excessive amounts of invalid
  • promotions. Use -mcdag 1 (default 0, which means disabled) to use this
  • new feature.
  • The -tt option is now only for controlling fan behavior. For example. -tt 60 sets
  • speed of an automatic fan with a set temperature of 60C; -tt -70 sets the fixed fan speed to 70%; and
  • -tt 0 disables fan control. All of this can be specified for each GPU.
  • There is a new option -hwm to control the frequency of the hardware.
  • monitoring, which was also done by -tt in previous versions of PhoenixMiner.
  • Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use these drivers
  • only if you have an RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs will not work with these
  • drivers!
  • Automatically install -ttli instead of -tmax if not supported later
  • Driver. This will reduce the performance of the GPUs when they reach the set temperature.
  • to avoid overheating
  • Other minor improvements and fixes

Step by Step Guide PhoenixMiner

  • Step 1. Install GPUs and set up your computer.
  • Step 2 – Download the latest PhoenixMiner
  • Step 3 – Get an Ethereum wallet (Mist or MyEtherWallet)
  • Step 4 – Join the mining pool.
  • Step 5 – Start mining!

Setting up a batch file for Ethereum

  • phoenix miner настройка PhoenixMiner 4.5c - AMD+NVIDIA GPUs Miner
  1. PhoenixMiner.exe – this key indicates which program will be launched. Leave it as it is
  2. -pool – pool server. Change to another pool or leave ethermine
  3. : 4444 the pool port. It appears after the colon
  4. -wal is the address of your digital wallet
  5. -worker Rig1 is the name of your farm worker. Used for the convenience of tracking statistics on the pool. You can specify any
  6. -pass x – password on the pool. Almost never used on pools. The x value means that there is no password
  7. -log 0 – is responsible for maintaining the miner’s event log. 0 – means not to log. If you set -log 1 , then the log will be kept without showing debug messages on the screen, if -log 2 – write the log and display debug messages on the screen
  8. -tt 70 – setting the target temperature of the fan control (special values: 0 – no control on all cards, 1-4-only monitoring on all cards with an interval of 30-120 seconds, negative values ​​- fixed speed fan (in%)
  9. -tstop 85 – means that the video card will be suspended when the temperature reaches 85 °
  10. -tstart 70 – means that the card will start again when its temperature drops to 70 °
  11. -fanmin 30 – the minimum rotation speed of the video card fans. if MSI Afterburner or other software does not start the fan equation
  12. pause – means that if you set something incorrectly, i.e. o the miner will not close immediately, but will display an error code

Setting up a batch file for dual mining Ethereum (Ethereum + Blake2s)

  • PhoenixMiner_4.0b_dual mining пример

Starting from version 4.0 of PhoenixMiner, you can mine two coins at the same time. This is ideal for those with cheap electricity. Dual mode increases the power consumption and heat dissipation of video cards. Currently, only the Blake2s algorithm is supported, for example, the Verge coin works on this algorithm.

  1. -pool ssl: // 5555 – enter the address of the pool of the first coin. The first (main) coin must necessarily work on the ethash algorithm. It will not be possible to make another algorithm the main one, as well as the Blake2s + Blake2s combination
  2. -wal after the -wal option, enter the address of the digital wallet of the first (main) coin
  3. -dpool enter the address of the pool of the second (for dual mining) coin. It must work on the Blake2s algorithm. It will not work to combine Ethash + Ethash in the dual (for example Ethereum and Ethereum Classic)
  4. -dwal – after the -dwal option, enter the address of the second coin
  5. dcoin blake2s option means that you will mine the second coin using the blake2s algorithm. Currently only this algorithm is supported for dual.

This is where the differences end. For completeness, you can specify additional options as in the example with Ethereum.

We recommend that you specify the parameters:

In order to save video cards and protect them from overheating and any unforeseen circumstances in case of failure to start the cooler control.

Run PhoenixMiner

At the first start, the program will tell us the following information:

  • запуск phoenx miner
  1. The top line will contain everything that we specified in the batch file
  2. Program version
  3. No CUDA driver found – Nvidia driver was not found. Because we have AMD, then you shouldn’t be afraid of this inscription
  4. Version of your video card driver
  5. All available devices for mining
  6. The program starts connecting to the pool

After waiting a little longer, we finally see the hash rate of video cards and other data:

  • работа консоли программы
  1. Incorrectly resolved share 0, (0%), obsolete share is also 0%. Very good!
  2. The maximum difficulty of the found balls is 186.8 GH
  3. Average mining speed for 5 minutes – 174 Mh / s
  4. Effective speed – 155.74 Mh / s. Why is it smaller? Because we have just launched the program and the time of the first launch, the creation of the DAG file, etc. is taken into account. If you wait for some time, then this speed will become completely the same with an average speed of 174 Mh / s
  5. Temperature of each video card and fan blade speed in percent. The color scheme can be changed. See below
  6. Video card # 5 found a ball. I must say that miners are paid exactly for the found shares.
  7. Pool sent a new job and indicated the difficulty
  8. Hashrate of each video card separately

We have reviewed the basic settings that will already allow you to start mining. It is recommended to do the first launch with minimal or no overclocking of video cards and test PhoenixMiner for stability.

Ethereum –

Ethereum –

Ethereum –

Posted in AMD GPUs, Cryptocurrency Miners, Mining, New Releases, NVIDIA GPUs, Software, user manualsTagged DOWNLOAD PhoenixMiner, PhoenixMinerSours:

And pumped her up very thoughtfully, and at that time I put his wife on all fours and fucked her from behind. This constancy came in handy for me later. All the remaining days his wife visited me and brightened my loneliness. In my opinion, her husband was only glad of this, because he had a strong crush on his daughter-in-law and practically did not get off her.

And his son liked older ladies more, he eagerly fucked Rosa and felt that he really liked sex with his own mother.

5 phoenixminer

Nose. - Okay. can I think until evening. - But why think, just if you are against, I will go right now and give the camera to Diman, which it will lie unnecessarily.

Top 3 Ethereum GPU Miners

Now I am almost a warrior, and Yar has not yet killed or wounded anyone. The mood soured when I saw the slaves captured by the Warrior. Why does he need an old woman, why does he take this stupid girl who has not reached the age of a bride. How could she please him in bed.

You will also like:

I could no longer sit still, walked around the room, squeezing my hips as much as possible, crossing my legs, dancing, bending over, I really wanted to write. The bladder was already hurting, to endure I squatted down and pressed the crotch with my heel and bent very strongly, from this a terrible pain chipped my. Bladder. Kolya, seeing my torment, said that I could take off my jeans to make it easier and nothing would put pressure on the already overflowing bubble.

4563 4564 4565 4566 4567