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

[vmgv]

Hello  

I had version 20.4.2 amd drivers and 5.2d PH but today I lost hashrate. I decided to upgrade to 5.2e and update drivers to 20.11.2 but it still has the same hashrate. I lost 1-2 mh/s per card.

(1) rx 570 4gb 23 mhs (I had 25-26 mhs)
(3) rx 580 4gb 26.5 mhs (had 28-29 mhs)

Windows 10
Amd 20.11.2 drivers, compute mode and OC

Any idea?

[1714690838]

1714690838

[1714690838]

1714690838

[STSMiner]

Read: "How to up your hashrate on PhoenixMiner" -

Read: "How to up your hashrate on PhoenixMiner"

Stop posting this crap here, it's not needed or wanted !!

[PhoenixMiner]

PhoenixMiner 5.2e is officially released. You can find the download link and the checksums in the first post of this thread.

It is the same release as the one that was released yesterday, so if you are already running it, there is no need to upgrade.

[batsonxl]

Hello,

Was using claymore until now and getting 32 Mh/s to all my 3 Rx 580s 8gbs..

Now switched to Phoenix 5.1e with this command -amd -acm -rxboost 21 -gser 2 -daglim 0
And only getting 28 Mh/s..

Tried without daglim and getting the same Mh/s..

Also every time i am starting the miner i get Disabling DAG pre allocation not enough vram..
But all my Gpus are 8 GBs..

Can anybody help ?

Thanks in advance,

rxboost 1 is enough or -vmr 25 and also add -mt1 you can try mt 2 but same results. with this you can get 30+, no other help i can do because im also came from clay, and no one helped me to get 32 again, even on claymore i was getting 33 on some cards. i tried trm and lolminer as well, having low speed. well i guess i will go back old good days flashing bios again. i think that is best way keep polais cards get good speed.

[BitKingRoss]

I am not a developer and wish I was. I have been mining since 2016. I would have had this miner well tested before deployment. I cannot comprehend to you the number of issues I have run into the latest Phoenix miner, DAG level, and Polaris cards when running large scale GPU farms. I manage and own a few, all running Windows Server with proper data center infrastructure management in place. It's as if Phoenix miner has only focused on development for Vega and Navi GPUs, but forgotten about Polaris as the DAG has limit increased. All of my Navi based rigs are fine for the most part. I manage many. Yes Claymore should be getting just as much backlash for not at all providing support but he is not available for commentary. Phoenix has been here and known about this encroaching issue. Please do something about this. We rely no stability.

I test the new version with -vmr 85
I am at 33.900Mhs

PH: 5.2e
amd driver 20.11.2

Thanks, will update tomorrow.

[BitKingRoss]

I am not a developer and wish I was. I have been mining since 2016. I would have had this miner well tested before deployment. I cannot comprehend to you the number of issues I have run into the latest Phoenix miner, DAG level, and Polaris cards when running large scale GPU farms. I manage and own a few, all running Windows Server with proper data center infrastructure management in place. It's as if Phoenix miner has only focused on development for Vega and Navi GPUs, but forgotten about Polaris as the DAG has limit increased. All of my Navi based rigs are fine for the most part. I manage many. Yes Claymore should be getting just as much backlash for not at all providing support but he is not available for commentary. Phoenix has been here and known about this encroaching issue. Please do something about this. We rely no stability.

HAHAHA....big time miner so he says...but just registered here today. 

His first post....way to soil the waters and remove all doubt about your idiocy.

Cool, look me up. I am not here to insult you. If you are not as displeased perhaps it is because you do not have a business and many many clients that rely on you to run there equipment. Who cares how old my BTCtalk is. I know my place. Cheers and happy mining!

[PhoenixMiner]

@PhoenixMiner Thanks for your hard work but why Turbo kernels (clkernel 3) not working anymore on my 2x RX 580 8GB ??
It says there is not enough VRAM for clkernel 3 but both my cards have 8GB memory and Windows never uses neither of them because my monitor connected to iGPU (Intel UHD).
....

  The turbo kernels require double the DAG space, so even on 8GB cards it is not possible any more if you mine ETC, and it is soon to be impossible for ETH. You can try adding -eres 0 -rvram -1 but even if this works, it will only be for a few more DAG epochs.

  The miner itself needs to be started "As Administrator" - right-click the .bat file and select "Run as Administrator" from the context menu. It is not enough to run it from user account that has administrator rights.

I do not use the .bat file, I run directly the miner with PhoenixMiner.exe "As Administrator" with "Run as Administrator" from the context menu.

  Check if all necessary files are in the same folder as PhoenixMiner.exe - EIO.exe, EIO.dll, IOMap64.sys. Also, -rxboost will only work on GDDR5 GPUs, and -starps only on Vega GPUs. Is this a Vega GPU you are running?

If you put rxboost (or vmr) too high you will have memory errors and the real hash will be half of what the miner shows. You have to check always the stats of the pool. It is good to use some memory errors tool or just watch the screen. If you see artifacts (like small blinking dots), you are above the possibility of the memory. For me, I can use like -rxboost 1 with the best hash on the pool without memory errors. It gives 32.4 Mh/s with moded timings (rx 580 8Gb).

  In the latest version (5.2e) you will see incorrect shares if the -vmr (or -rxboost) is excessive (or the miner will just crash/freeze).

Nice to see new version but my question still not answered not only me many people interested as well.
Will be there new version for new coming ETC fork with reduced dag size? there is only 6-8days left to fork, thanks

 Yes, we are working on it. It will be ready in a few days.

Edit: It would be really fantastic if we could select cards 0,1,2 to mine ETH and 3,4,5 for ETC under the same instance of PhoenixMiner...

  Too much work to make this happen, however you can run two independent instances of PhoenixMiner - first on the first three GPUs, and the next one for the other three (with the -gpus 123 for the first instance, and -gpus 456 for the second one).

Hi, I've got a 6800XT and Phoenixminer detects 36 CU at start.
This card has 72 CU, this is normal? maybe hashrate is half of that card can achive?
Thanks.

  Unfortunately, we are unable to get 6800XT or 6800 yet.

hi,

so i upgraded to 5.2e and have a couple of r9 380 4GB cards in one rig. i've got an 8GB card at position 1 to alleviate the DAG issue.

the rig fires up but my r9 380's are reporting <4 MH/s and i appear to get the "auto configure in progress" message perpetually...

also the TDP for these 2 isn't displayed, so i think they're doing nothing?

any ideas?

Win 10

PhoenixMiner.exe -pool us1.ethermine.org:4444 -pool2 eu1.ethermine.org:4444 -wal xxxxxxxxxxxxxxxxxxxxxxx -proto 3 -astats 1 -logfile my_log.txt$  -logdir c:\users\root\desktop

thanks

  Check the driver version (see the first post of this thread for the "good" AMD drivers for 4 GB cards). If you are running one of the good drivers, and the problem still remains, you need to lower the -daglim (by default it is 4023 on Window).

Any hopes for the 1070Ti ?
Any smart fixes ?

 What is the problem with 1070Ti? It is probably the only Pascal GPU that still does 30-31 MH/s without problems with bigger DAGs, while the 1070 are affected by the DAG size and won't mine with the former speed with these big DAG epochs.

hey i can't use the straps for RX580 o just for AMD VEGAS CARD ? comon guys <3

  We will be adding straps support for Polaris in a future version. For now, if you haven't modded the BIOS, use -mt 2, which works on most cards and increases the speed in comparison with the stock VBIOS.

Hello  

I had version 20.4.2 amd drivers and 5.2d PH but today I lost hashrate. I decided to upgrade to 5.2e and update drivers to 20.11.2 but it still has the same hashrate. I lost 1-2 mh/s per card.

(1) rx 570 4gb 23 mhs (I had 25-26 mhs)
(3) rx 580 4gb 26.5 mhs (had 28-29 mhs)

Windows 10
Amd 20.11.2 drivers, compute mode and OC

Any idea?

  This is the effect of not being able to use the full DAG size - with each new epoch, the hashrate will go down slightly. To maximize hashrate, use -rxboost 1. If your cards are not modded, also add -mt 2

[Wotan Wipeout]

Are you working on the 3080?

[batsonxl]

Nice to see new version but my question still not answered not only me many people interested as well.
Will be there new version for new coming ETC fork with reduced dag size? there is only 6-8days left to fork, thanks

 Yes, we are working on it. It will be ready in a few days.

hey i can't use the straps for RX580 o just for AMD VEGAS CARD ? comon guys <3

  We will be adding straps support for Polaris in a future version. For now, if you haven't modded the BIOS, use -mt 2, which works on most cards and increases the speed in comparison with the stock VBIOS.

Perfect !!! looking forward. Thanks for hard work.

[q1398590q]

In WINDOWS10 system, using "-li" "-gpow" will cause the CPU usage to become very high, can it be solved?

[giorgiokaan]

hey i can't use the straps for RX580 o just for AMD VEGAS CARD ? comon guys <3

  We will be adding straps support for Polaris in a future version. For now, if you haven't modded the BIOS, use -mt 2, which works on most cards and increases the speed in comparison with the stock VBIOS.

Amazing guys! Been waiting for this feature. Any idea if it will be available on Linux too? I would love to use HiveOS with memory straps without having to mod bios.

[Pe_Da]

I know, new card and driver but I got many invalid shares in connection with Nicehash on my new RX 6800.
At the moment no OC and anyone else optimizings active. Seems to be a problem with the many new DAG generation within the mining process.

2020.11.20:14:50:21.563: main Phoenix Miner 5.2c Windows/msvc - Release build
2020.11.20:14:50:21.563: main Cmd line: -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal 39d2gVnrTCRyUKxdWUiTtHjyiYjm5Z6nsA$0-Lvv+41KBzlKZvrdxo--nQA -proto 4 -amd -gpus 0 -wdog 0 -gbase 0 -mport 127.0.0.1:-4000
2020.11.20:14:50:21.995: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2020.11.20:14:50:21.995: main OpenCL platform: OpenCL 2.1 AMD-APP (3188.4)
2020.11.20:14:50:21.999: main Available GPUs for mining:
2020.11.20:14:50:21.999: main GPU0: AMD Radeon RX 6800 (pcie 43), OpenCL 2.0, 16 GB VRAM, 30 CUs
2020.11.20:14:50:22.000: main ADL library initialized
2020.11.20:14:50:22.469: main Eth: the pool list contains 1 pool (1 from command-line)
2020.11.20:14:50:22.469: main Eth: primary pool: daggerhashimoto.eu.nicehash.com:3353
2020.11.20:14:50:22.469: main Starting GPU mining
2020.11.20:14:50:22.469: main Matched GPU0 to ADL adapter index 0 (method 1)
2020.11.20:14:50:22.474: main GPU0: AMD driver 20.11.2
2020.11.20:14:50:22.474: main GPU0: Created ADL monitor for adapter 0; overdrive version: 8 (
2020.11.20:14:50:22.474: main GPU0: using AMD driver ver 20.11.2
2020.11.20:14:50:22.601: main Eth: Connecting to ethash pool daggerhashimoto.eu.nicehash.com:3353 (proto: Nicehash)

2020.11.20:15:06:10.307: main *** 0:15 *** 11/20 15:06 **************************************
2020.11.20:15:06:10.307: main Eth: Mining ETH on daggerhashimoto.eu.nicehash.com:3353 for 0:15
2020.11.20:15:06:10.307: main Eth: Accepted shares 29 (5 stales), rejected shares 1 (1 stales)
2020.11.20:15:06:10.307: main Eth: **Incorrect shares 4** (11.76%), est. stales percentage 20.76%
2020.11.20:15:06:10.307: main Eth: Maximum difficulty of found share: 85.8 GH (!)
2020.11.20:15:06:10.307: main Eth: Average speed (5 min): 58.397 MH/s
2020.11.20:15:06:10.307: main Eth: Effective speed: 62.83 MH/s; at pool: 59.99 MH/s

"Normal" ETC and ETH mining runs properly, but with very fluctuating (56-60Mhs) hashrate!

I would first update driver to a version that supports the 6000 series. 20.11 seems to be old isnt it?

, that is the newest driver from AMD.

Also with 5.2e still invalid shares (only) on Nicehash!

2020.11.23:09:42:25.028: main Phoenix Miner 5.2e Windows/msvc - Release build
2020.11.23:09:42:25.028: main Cmd line: -wdog 1 -rmode 0 -cdm 2 -cdmport 4029
2020.11.23:09:42:25.028: main No CUDA driver found
2020.11.23:09:42:27.712: main OpenCL driver version: 20.11.2
2020.11.23:09:42:27.919: main Available GPUs for mining:
2020.11.23:09:42:27.921: main GPU1: AMD Radeon RX 6800 (pcie 43), OpenCL 2.0, 16 GB VRAM, 30 CUs
2020.11.23:09:42:28.065: main ADL library initialized
2020.11.23:09:42:28.921: main Eth: Loading pools from epools.txt
2020.11.23:09:42:28.922: main Eth: the pool list contains 1 pool (0 from command-line)
2020.11.23:09:42:28.922: main Eth: primary pool: daggerhashimoto.eu.nicehash.com:3353
2020.11.23:09:42:28.925: main Starting GPU mining
2020.11.23:09:42:28.935: main Matched GPU1 to ADL adapter index 0 (method 1)
2020.11.23:09:42:29.061: main GPU1: AMD driver 20.11.2
2020.11.23:09:42:29.061: main GPU1: Created ADL monitor for adapter 0; overdrive version: 8 (
2020.11.23:09:42:29.062: main GPU1: using AMD driver ver 20.11.2
2020.11.23:09:42:29.182: wdog Starting watchdog thread
2020.11.23:09:42:29.184: main Eth: Connecting to ethash pool daggerhashimoto.eu.nicehash.com:3353 (proto: Nicehash)
2020.11.23:09:42:29.185: main GPU1: 30C 0% 6W
GPUs power: 6.0 W
2020.11.23:09:42:29.229: eths Eth: Connected to ethash pool daggerhashimoto.eu.nicehash.com:3353 (172.65.200.133)
2020.11.23:09:42:29.229: eths Eth: Send: {"id":1,"method":"mining.subscribe","params":["PhoenixMiner/5.2e","EthereumStratum/1.0.0"]}

2020.11.23:09:42:29.278: eths Eth: Received: {"id":1,"error":null,"result":[["mining.notify","d6cff9a8ec8d436b337d2771c6537ff3","EthereumStratum/1.0.0"],"5d6ee0"]}
2020.11.23:09:42:29.281: eths Eth: Extranonce set to 5d6ee0
2020.11.23:09:42:29.281: eths Eth: Subscribed to ethash pool
2020.11.23:09:42:29.281: eths Eth: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["39d2gVnrTCRyUKxdWUiTtHjyiYjm5Z6nsA.GPU","x"]}

2020.11.23:09:42:29.313: eths Eth: Received: {"id":3,"result":true,"error":null}
2020.11.23:09:42:29.313: eths Eth: Worker 39d2gVnrTCRyUKxdWUiTtHjyiYjm5Z6nsC.GPU authorized
2020.11.23:09:42:29.343: eths Eth: Received: {"id":2,"result":true,"error":null}
2020.11.23:09:42:29.343: eths Eth: Received: {"id":null,"method":"mining.set_difficulty","params":[0.626853]}
2020.11.23:09:42:29.345: eths Eth: Difficulty set to 0.626853
2020.11.23:09:42:29.345: eths Eth: Received: {"id":null,"method":"mining.notify","params":["000000004d3e7874","19812be3c654d239eb2737b845b435c2f2bfe870fe542d50748cfe7c2098fabb","46b35b4d4c7eb710f1781c1bbda72e0c798ab2e2e94f27d828701de8657664a1",true]}
2020.11.23:09:42:29.347: eths Eth: New job #46b35b4d from daggerhashimoto.eu.nicehash.com:3353; diff: 2692MH
2020.11.23:09:42:29.347: GPU1 GPU1: Starting up... (0)
2020.11.23:09:42:29.347: GPU1 GPU1: Generating ethash light cache for epoch #377
2020.11.23:09:42:29.401: main Listening for CDM remote manager at port 4029 in full mode
2020.11.23:09:42:32.039: eths Eth: Received: {"id":null,"method":"mining.notify","params":["000000004d3f49d9","19812be3c654d239eb2737b845b435c2f2bfe870fe542d50748cfe7c2098fabb","80659b7c4e03796414b9a17412b66d422201b21a24af30a3a8e63431dc669c8d",true]}
2020.11.23:09:42:32.039: eths Eth: New job #80659b7c from daggerhashimoto.eu.nicehash.com:3353; diff: 2692MH
2020.11.23:09:42:33.141: GPU1 Light cache generated in 3.8 s (16.6 MB/s)
2020.11.23:09:42:33.969: GPU1 GPU1: Using generic OpenCL kernels (device name 'gfx1030')
2020.11.23:09:42:34.356: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.11.23:09:42:34.954: GPU1 GPU1: Free VRAM: 15.922 GB; used: 0.063 GB
2020.11.23:09:42:34.955: GPU1 GPU1: Allocating DAG for epoch #377 (3.95) GB
2020.11.23:09:42:34.966: GPU1 GPU1: Generating DAG for epoch #377

2020.11.23:10:38:54.671: main *** 0:56 *** 11/23 10:38 **************************************
2020.11.23:10:38:54.671: main Eth: Mining ETH on daggerhashimoto.eu.nicehash.com:3353 for 0:56
2020.11.23:10:38:54.671: main Eth: Accepted shares 77 (5 stales), rejected shares 12 (10 stales)
2020.11.23:10:38:54.671: main Eth: Incorrect shares 13 (12.75%), est. stales percentage 17.07%
2020.11.23:10:38:54.671: main Eth: Maximum difficulty of found share: 678.9 GH (!)
2020.11.23:10:38:54.671: main Eth: Average speed (5 min): 62.739 MH/s

[UnclWish]

Also with 5.2e still invalid shares (only) on Nicehash!

Phoenix wrote already that he hasn't any of new 6800 cards yet. So he can't optimize his kernels for new cards. We must wait till he buy new card and work on it.

[melpheos]

Any hopes for the 1070Ti ?
Any smart fixes ?

 What is the problem with 1070Ti? It is probably the only Pascal GPU that still does 30-31 MH/s without problems with bigger DAGs, while the 1070 are affected by the DAG size and won't mine with the former speed with these big DAG epochs.

Unfortunately this won't be the case as soon as DAG 384 will be reached.

As soon as you reach this dag the performance drops by 50%

[melpheos]

Read: "How to up your hashrate on PhoenixMiner" - [removed]Read on Medium[/url]

Don't go there, it's just another ethpill scam. Just a new version to not get flagged on bitcointalk

The hint is the PS at the end which is exactly the same as other ethpill scams

P.S.: the project is being drowned by competitors, don’t trust anyone, check the information yourself

[Jonet]

Both 5.2e and 5.1c sometimes detect one extra card

2020.11.23:12:42:35.007: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2020.11.23:12:42:35.007: main GPU2: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2020.11.23:12:42:35.007: main GPU3: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
2020.11.23:12:42:35.007: main GPU4: Radeon RX 580 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 36 CUs
2020.11.23:12:42:35.007: main GPU5: Radeon RX 580 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
2020.11.23:12:42:35.007: main GPU6: Radeon RX 580 Series (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
2020.11.23:12:42:35.007: main GPU7: Radeon RX 580 Series (pcie , OpenCL 2.0, 8 GB VRAM, 36 CUs

There are 6 cards in this rig so GPU 1 and GPU 2 is the same card. Needless to say this does not end well

So far I have managed to run 5.1c over some time but not 5.2e
Windows 10

[q1398590q]

In WINDOWS10 system, using "-li" "-gpow" will cause the CPU usage to become very high, can it be solved?


I have nearly 10,000 cards affected, I hope to solve this problem, thank you

[king_pin]

Since yesterday I get:

Disabling DAG per-allocation (not enough VRAM)

ON 8GB   570/580

[KiparisD]

In WINDOWS10 system, using "-li" "-gpow" will cause the CPU usage to become very high, can it be solved?


I have nearly 10,000 cards affected, I hope to solve this problem, thank you

Go fix your 100000000000000 cards, why moaning here 

[vmgv]

When I put -rxboost 1 on bat file, I've this error https://prnt.sc/vogc65

I don't know why
AMD 20.11.2 drivers
5.2e PH
4gb rx 570 (1) and (3) rx 580 4 gb

regards