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

[Dowper_]

-cdmport is not working in the new version...

It is working fine here (read-only access).


CMD-Line used:
PhoenixMiner.exe -amd -eres 1 -mi 12 -pool DAGGERHASHIMOTO.eu.nicehash.com:3353 -wal ************************.********** -pass x -proto 4 -log 0 -wdog 0 -cdmport 4001 -gpus 2

On latest 5.2a version it's not working.

Still not working in 5.2c, when this will be fixed?

EDIT: OK, it's working now.

[7anonminer7]

Hello.

I'm using PhoenixMiner 5.2c on Windows 10 with Adrenaline 19.7.5 drivers,  4 x 570RX 4GB cards in "compute mode" (VGA output connected to intergrated Intel GPU) with following settings:

Code:

-acm
-eres 1
-lidag 2
-tt -60,-45,-60,-60
-cclock 1050,1050,1050,1050
-cvddc 900,950,900,900
-mclock 1970,1970,1970,1970
-mvddc 850,850,850,850
-daglim 3990

Yet after DAG generation I get 0 Mh/s on every card, please advise what could be wrong, thank you.

PS. https://pastebin.com/Mb1asrvP <- the the log - I couldn't pinpoint anything strange or any errors that are in there though.

[Mr.merson]

What are the drivers specifically recommended for Windows 7 64 bits?

I have installed 20.4.2, 20.9.2, 19.12.2, 20.1.3, 20.1.2 beta blockchain and they all send me the following error when writing the dag file "GPU1: Allocating buffers failed with: clCreateBuffer (-61)." (some don't even show the error)

4GB VRAM graphics card
Archive pag file 20GB

On the other hand, in windows 10 I have no problem, but I use windows 7 for more comfort

Likewise I have no problem with other mining software with the mentioned drivers, something related to windows 7?

[SiNeReiNZzz]

MALWARE SCAM / DONT QUOTE CONTENT / SEE ARCHIVE LINK BELOW

https://archive.is/4XPNj#msg55587991

I've reported this malware post:

ᗌ ETHPIL-Link (Github) #2 ᗏ

Thread: https://bitcointalk.org/index.php?topic=2647654.msg55587991#msg55587991 <---- DELETE PLEASE

Virus Total: https://www.virustotal.com/gui/file/8e90944c2a3fc8cce71b0176dbad8f0c5c67b7e970bfc5d1473d35260067cabf/details

Profile Link: jro238 <---- BAN PLEASE

Archive- LINK

Code:

https://ethereumpill.info/ProjectEthereumPill.zip

[fomkas]

I need help. I used to mine with Claymore 15, Blokchain driver  and RX570 nitro+. My speeds were 32.5 Mh/s and I switched to Phoenix miner but my speed is 31.5 and I cant change -mvddc value. If I put -mvddc it wont start mining just crashes. I can mine without that value but my power usage goes up a lot when compared to Claymore. I tried 20.8.1 drivers but only get 10 Mh/s and I can get it to work with -mvddc 900. Any ideas?

if you have more 11 Mh, you card on compute mode already

you need "Memory Tweak"
ref 30

PS
31.5-->32.8 for me )

sorry for my russian)))

[adaseb]

Hello.

I'm using PhoenixMiner 5.2c on Windows 10 with Adrenaline 19.7.5 drivers,  4 x 570RX 4GB cards in "compute mode" (VGA output connected to intergrated Intel GPU) with following settings:

Code:

-acm
-eres 1
-lidag 2
-tt -60,-45,-60,-60
-cclock 1050,1050,1050,1050
-cvddc 900,950,900,900
-mclock 1970,1970,1970,1970
-mvddc 850,850,850,850
-daglim 3990

Yet after DAG generation I get 0 Mh/s on every card, please advise what could be wrong, thank you.

PS. https://pastebin.com/Mb1asrvP <- the the log - I couldn't pinpoint anything strange or any errors that are in there though.

Basically the DAG is very large and life is ending for 4GB cards. If you really want you can do a few solutions

1) Switch to bigger GPUs like >6GB. And put the largest GPU in the first PCIe slot, and maybe your 4GB might work.

2) Use Linux. Install Ubuntu and run Phoenixminer on Linux and you should be good for another month or so.

3) Use a miner like lolminer which lets you mine >4GB however its at reduced speeds. At first its not so bad but with every new DAG it will hash slower and slower.

Besides this, not much else to do really except upgrade your farm to all 8GB GPUs.

[volig]

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

[batsonxl]

Does 5.2c support for new ETC algo after dag reduction? and i was not able straps 1 work on polaris cards? is it for VEGA only? thanks

[batsonxl]

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

yes im having that problem too. it looks like 5.2a 5.2b 5.2c has that problem, also developer do not recommend 20.9.1 driver

[Dowper_]

Does 5.2c support for new ETC algo after dag reduction?

I hope so.

[Kiawpqe]

GPU1: 64C 77% 90W, GPU2: 65C 62% 81W, GPU3: 64C 57% 91W, GPU4: 65C 49% 87W, GPU5: 65C 25% 82W, GPU6: 65C 59% 83W, GPU7: 65C 47% 79W
GPU1: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU2: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU3: cclock 1165 MHz, cvddc 868 mV, mclock 2112 MHz
GPU4: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU5: cclock 1165 MHz, cvddc 868 mV, mclock 2112 MHz
GPU6: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU7: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPUs power: 593.5 W; cost: 2.14 USD/day
Eth speed: 213.104 MH/s, shares: 3007/0/24, time: 2:10
GPUs: 1: 30.484 MH/s (385/12) 2: 30.393 MH/s (427) 3: 30.463 MH/s (420/7) 4: 30.517 MH/s (485) 5: 30.413 MH/s (445/2) 6: 30.385 MH/s (425/3) 7: 30.449 MH/s (420)

*** 2:10 *** 11/14 11:19 **************************************
Eth: Mining ETH on ethash.poolbinance.com:8888 for 2:10
Eth: Accepted shares 3007 (1 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 24 (0.79%), est. stales percentage 0.02%
Eth: Maximum difficulty of found share: 547.6 GH (!)
Eth: Average speed (5 min): 213.029 MH/s
Eth: Effective speed: 205.05 MH/s; at pool: 205.05 MH/s

Eth: GPU6: ETH share found!
Eth: Share actual difficulty: 2598 MH
Eth: Share accepted in 101 ms
Eth: GPU4: ETH share found!
Eth: Share actual difficulty: 1630 MH
Eth: Share accepted in 275 ms
Eth speed: 213.110 MH/s, shares: 3009/0/24, time: 2:10
GPUs: 1: 30.482 MH/s (385/12) 2: 30.394 MH/s (427) 3: 30.465 MH/s (420/7) 4: 30.517 MH/s (486) 5: 30.413 MH/s (445/2) 6: 30.389 MH/s (426/3) 7: 30.450 MH/s (420)
Eth: GPU7: ETH share found!
Eth: Share actual difficulty: 576 MH
Eth: Share accepted in 71 ms
Eth: New job #5b69f3d0 from ethash.poolbinance.com:8888; diff: 536MH
Eth: New job #96e38a96 from ethash.poolbinance.com:8888; diff: 536MH
Eth speed: 213.124 MH/s, shares: 3010/0/24, time: 2:10
GPUs: 1: 30.482 MH/s (385/12) 2: 30.396 MH/s (427) 3: 30.465 MH/s (420/7) 4: 30.518 MH/s (486) 5: 30.411 MH/s (445/2) 6: 30.403 MH/s (426/3) 7: 30.449 MH/s (421)
Eth: GPU5: ETH share found!
Eth: Share actual difficulty: 19.3 GH (!)
Eth: Share accepted in 51 ms
Eth: GPU4: ETH share found!
Eth: Share actual difficulty: 820 MH
Eth: Share accepted in 35 ms
Eth: GPU2: ETH share found!
Eth: Share actual difficulty: 6497 MH
Eth: Share accepted in 289 ms
DevFee: Connecting to ethash pool asia1.ethpool.org:3333 (proto: EthProxy)
DevFee: Connected to ethash pool asia1.ethpool.org:3333 (172.65.215.159)
DevFee: New job #cfbb698f from asia1.ethpool.org:3333; diff: 4000MH
Eth: GPU4: ETH share found!
Eth: Share actual difficulty: 1425 MH
Eth: GPU3: ETH share found!
Eth: Share actual difficulty: 2451 MH
Eth speed: 213.121 MH/s, shares: 3013/0/24, time: 2:10
GPUs: 1: 30.483 MH/s (385/12) 2: 30.395 MH/s (428) 3: 30.464 MH/s (420/7) 4: 30.517 MH/s (487) 5: 30.412 MH/s (446/2) 6: 30.401 MH/s (426/3) 7: 30.449 MH/s (421)
Eth: Share accepted in 217 ms
Eth: Share accepted in 152 ms


 
pool.binance.com
wow

3000 shareds in 2 hours

3-msi Rx-580 8gb
3-gts xxx Rx-580 8gb
1 powercolor Rx-580 8gb

[Ursul0]

PhoenixMiner 5.2c (still beta) is ready with speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2c from here (this is only the Windows version, the Linux version will be ready in a few days):

https://mega.nz/folder/HJVTkYjD#5CConQEPniyjCeluCpeDZA  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.2c_Windows.zip
    ===================================
   SHA-1: 7d4cdb429522caa5244f05bd58bb42e21c1d94fb
 SHA-256: cfb4b6a48dc15667e17dca3906cae8ef6668d4d741f692541a9cf8feda630b68
 SHA-512: 01dc553015c2553353a3af5c6bdf811c9084b37bfb157f963898def1bb9b8b6e6f847a78b01ad36baada413213eab34a0a5e91333636a6adf2728b1cf42f32ba

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The fixes in this release (since 5.1) include the following:

• The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This will get the hashrate back to 100% on current epoch, and the next epoch will only lose about 2-3% of the hashrate.
• The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
• AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
• Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
• The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
• Many other small improvements and fixes

Here are some additional notes:

• With PhoenixMiner 5.2c either remove the -daglim option entirely, or set it to -daglim 4023, which should work on all 470/480/570/580/590 cards with "good" drivers (see bellow)
• The -daglim option works only on Polaris cards (RX470, RX480, RX570, RX580, RX590). It limits the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 374 on Windows (or after 380-383 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit), or 1 (automatic DAG limit size, usually around 4023 MB under Windows; this is the default option). Note that the  hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example -daglim 3990
• It is also important to use auto-tune (do not specify -gt values in the command line) because the optimal -gt value may change with each new epoch, and will definitely be different than before.
• If you cards doesn't work with the default DAG limit of 4023 and require substantial decrease to 4006 or 3990, you need to update to one of the "good" AMD drivers for Windows: from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.11.1 (inclusive)
• Using -rxboost, -vmr, or -straps on AMD cards requires running as administrator (or as root under Linux), so you need to run PhoenixMiner as administrator for the VRAM timing options to work. Note that the -mt option will still work without running as administrator/root.
• The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
• The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.

Please let us know if you have any problems or questions related to PhoenixMiner 5.2c.

As advertised. Now 4023MB can be manually set for each 4GB GPU and it will allocate current epoch no problem. (doing ZIL in parallel is not possible though - the rigs will crash on a new dag. TRM will do ZIL no problem, it seem to be able to hold once allocated buffer always reserved, it's less stable than phoenix though and tiny bit slower too)
 
Also theres a problem that I guess is windows related: long pcie device chains get fucked up at the end - if I have 12GPUs the 12th would be able to allocate not above 3960 (or so) also same story with 11 devices - the 11th one would have reduced space for allocation.

[Ursul0]

Does 5.2c support for new ETC algo after dag reduction?

I hope so.

good question.
@PhoenixMiner I suppose you do have plans to release ETC new algo?

[Cryptomining2003]

where can i find the drivers compatibility list? is 20.20 still the latest amd driver supported in linux?

and what about the new above 4gb dag size for etc....i still get invalid shares when mining etc....who has to fix the wrong 32bit value? mining software/pool software?

[batsonxl]

*** 2:10 *** 11/14 11:19 **************************************
Eth: Mining ETH on ethash.poolbinance.com:8888 for 2:10
Eth: Accepted shares 3007 (1 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 24 (0.79%), est. stales percentage 0.02%
Eth: Maximum difficulty of found share: 547.6 GH (!)
Eth: Average speed (5 min): 213.029 MH/s
Eth: Effective speed: 205.05 MH/s; at pool: 205.05 MH/s

E
 
pool.binance.com
wow

3000 shareds in 2 hours

3-msi Rx-580 8gb
3-gts xxx Rx-580 8gb
1 powercolor Rx-580 8gb

3000shares in 2hours looks great, could you also share how much ETH you got in this 2 hour mining? it looks like miracle 3000shares in 2hours with 7gpus.

[Kiawpqe]

*** 4:33 *** 11/14 13:43 **************************************
Eth: Mining ETH on ethash.poolbinance.com:8888 for 4:33
Eth: Accepted shares 6267 (1 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 55 (0.87%), est. stales percentage 0.01%
Eth: Maximum difficulty of found share: 1764.0 GH (!)
Eth: Average speed (5 min): 213.132 MH/s
Eth: Effective speed: 203.96 MH/s; at pool: 203.96 MH/s

GPU1: 65C 67% 89W, GPU2: 65C 56% 81W, GPU3: 65C 53% 91W, GPU4: 65C 44% 87W, GPU5: 65C 25% 82W, GPU6: 65C 54% 83W, GPU7: 65C 42% 79W
GPU1: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU2: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU3: cclock 1165 MHz, cvddc 868 mV, mclock 2112 MHz
GPU4: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU5: cclock 1165 MHz, cvddc 868 mV, mclock 2112 MHz
GPU6: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPU7: cclock 1160 MHz, cvddc 868 mV, mclock 2112 MHz
GPUs power: 593.1 W; cost: 2.14 USD/day
Eth: Share accepted in 77 ms
Eth: GPU4: ETH share found!
Eth: Share actual difficulty: 542 MH
Eth: Share accepted in 56 ms
Eth: GPU4: ETH share found!
Eth: Share actual difficulty: 1180 MH
Eth: Share accepted in 42 ms
Eth speed: 213.112 MH/s, shares: 6270/0/55, time: 4:33
GPUs: 1: 30.482 MH/s (847/34) 2: 30.392 MH/s (943/1) 3: 30.464 MH/s (872/13) 4: 30.517 MH/s (935) 5: 30.411 MH/s (903/3) 6: 30.395 MH/s (847/4) 7: 30.452 MH/s (923)
Eth: GPU7: ETH share found!
Eth: Share actual difficulty: 3718 MH
Eth: New job #16bc0a31 from ethash.poolbinance.com:8888; diff: 536MH
Eth: Share accepted in 38 ms
Eth: GPU6: ETH share found!
Eth: Share actual difficulty: 12.6 GH (!)
Eth: Share accepted in 46 ms
Eth speed: 213.108 MH/s, shares: 6272/0/55, time: 4:34
GPUs: 1: 30.482 MH/s (847/34) 2: 30.394 MH/s (943/1) 3: 30.464 MH/s (872/13) 4: 30.517 MH/s (935) 5: 30.412 MH/s (903/3) 6: 30.388 MH/s (848/4) 7: 30.451 MH/s (924)
Eth: New job #eb780a4f from ethash.poolbinance.com:8888; diff: 536MH
Eth: New job #92ba392d from ethash.poolbinance.com:8888; diff: 536MH
Eth speed: 213.119 MH/s, shares: 6272/0/55, time: 4:34
GPUs: 1: 30.483 MH/s (847/34) 2: 30.394 MH/s (943/1) 3: 30.463 MH/s (872/13) 4: 30.518 MH/s (935) 5: 30.413 MH/s (903/3) 6: 30.398 MH/s (848/4) 7: 30.450 MH/s (924)
Eth: GPU6: ETH share found!
Eth: Share actual difficulty: 783 MH
Eth: Share accepted in 35 ms
Eth: New job #df730eab from ethash.poolbinance.com:8888; diff: 536MH
Eth: New job #143449a1 from ethash.poolbinance.com:8888; diff: 536MH
Eth: GPU5: ETH share found!
Eth: Share actual difficulty: 5215 MH
Eth: Share accepted in 42 ms
Eth: GPU5: ETH share found!
Eth: Share actual difficulty: 1656 MH
Eth: Share accepted in 38 ms





7 GPUs Rx-580=GPUs power: 593.1 W
psu EVGA SuperNova 1000 G3

6272 shareds  in 4 hours 30 min=0.00214165 ETH

[Kiawpqe]

Mining in Pool:
Pool.binance.com

Diff low

[batsonxl]

Mining in Pool:
Pool.binance.com

Diff low

Dude it nearly same like all pools according ETH earnings. dont know why binance.com gives so many shares.

[Kiawpqe]

I don,t know brooo

[miner29]

Low Difficulty shares wont make more esrnings.  im mining eth at 4000mh not the 536mh binance is using.  Yes you get more shares but they are worth less than the nearly 3000 shares an hour im getting.  In the end earnings should be identical for same gh in.