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

[fimatiku]

I got

0.05011 ETH + 0.03329 ETH in 24 hours...................how many dollars is that ? sounds like $43 in 24 hours

let me know how much u get with monero ? or whatever other crap zCash getto coin your wasting your time on........

lets not have smart asses here and keep it to original RX570/580 cards and not flash out GTX's

[janding]

What are we still happy with phoenixminer 2.9.e the stale shares are back again, while it was with the 2.9 .d away the joy is so short-lived unfortunately.

I am going to guess its your system, I have less stale shares as well as fewer incorrect ones being generated. I will say its been only around 7 hrs so far. What cards and drivers are you running?

Indeed the system, try re-installing your drivers.

I've been updating as the releases come out since 2.7c and to date 2.9d & 2.9e seem to stay under 0.10% in my case.

I'm using rx580 4 & 8Gb, one click patch, OC/UV done via Phoenix settings and running latest Adrenalin 18.2.3 feb 22.

Hope this helps, good luck.

I've tried lots of times to let people know that they're reading stale share incorrectly.
Your stale share rate is not 0.10% like you state.
First, pools don't report stale shares in percentages less than 1%
Second you don't get your real stales shares rate from the miner display.
You can ONLY know what your real stale share rate is at the pool, not the miner display.

I also have been tracking the stale shares when trying each version of PhoenixMiner.
I will say Phoenix has improved to the point it is almost as good as Claymore, but not quite as good.
I get between 1 and 4% stale shares from Phoenix and 1 to 3% on Claymore. SO, it is very close and with the slightly reduced fee it
makes it equal.

People should read all the info the miner developers publish and try to understand what they're looking at.

From page 1 of PhoenixMiner:

Q005: Why is the percentage of stale shares reported by PhoenixMiner smaller than the one shown by the pool?
   A: PhonixMiner can only detect the stale shares that were discovered after it has received a
   new job (i.e. the "very stale") shares. There is additional latency in the pool itself, and in
   the network connection, which makes a share stall even if it was technically found before the
   end of the block from the miner's point of view. As pools only reports the shares as accepted
   or rejected, there is no way for the miner to determine the stale shares from the pool's
   point of view.

[anbe2305]

These are my results:

Version 2.9e running very stable for 17 hours testing with :

GPU1 Nvidia GTX 1070, MICRON
GPU2 AMD RX 570 NITRO, MICRON
GPU3 Nvidia GTX 1070,MICRON

Power consumption 398W


*** 17:47 ***************************************************
Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 17:47
Eth speed: 96.655 MH/s, shares: 1534/0/0, time: 17:47
GPUs: 1: 32.608 MH/s (528) 2: 31.256 MH/s (470) 3: 32.791 MH/s (536)
Eth: Accepted shares 1534 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 35.3 TH (!!!)
Eth: Average speed (5 min): 96.613 MH/s
Eth: Effective speed: 95.82 MH/s; at pool: 95.82 MH/s

About stale shares miner reports zero, but on pool ETHERMINE average max 1 or 2%....


Keep up the good work...

[khafan11]

PhoenixMiner 2.9e is officially released. Note that there are changes since 2.9d, so if you are running 2.9d, you should upgrade to this version. Here is the list of changes since the last beta version 2.9e (the full list of changes since the last official release can be seen in the first post of this thread):

• Added detection of AMD Compute mode in the supported drivers and GPUs. The detection is performed when the miner starts and if the Compute mode is off on some of the GPUs, you will get warning messages.
• Added console command 'y' to turn on the AMD Compute mode if it is not turned on on some of the cards.
• Small improvement in the -logfile option: now you can insert $ chararcter in the name, which will be removed from the name but will force the miner to overwrite the log file on each startup, instead of appending to it.
• Fixed a problem with miner restart on some CUDA errors with Nvidia cards when the miner crashes instead of restarting.
• Some other small fixes and changes

You can download 2.9e from here: https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw

Checksums to verify your download:

Code:

   File: PhoenixMiner_2.9e.zip
   SHA-1: e2b9c72e561ac0fdb4e3c9ebddd7d703a35da36c
 SHA-256: 9817c89623025cf392a4e800a41cff96a87eee02e241d9f08d62dc43e0975e96
 SHA-512: 33c78a73a53791c01bbfff2ad830ffd40d4007f69ca329300815ab1c189f744aafdc6683033cfcb0315db7f322e6dee44181b9dff2922b1fb408b0f04dba163b

We are now working on 3.0, which will include auto-tuning capabilities and more.

i'm back to 2.8C , i had better hashrate with that ! RX580 8Gb MSI Gameing X

[Sandro6666]

PhoenixMiner 2.9e is officially released. Note that there are changes since 2.9d, so if you are running 2.9d, you should upgrade to this version. Here is the list of changes since the last beta version 2.9e (the full list of changes since the last official release can be seen in the first post of this thread):

• Added detection of AMD Compute mode in the supported drivers and GPUs. The detection is performed when the miner starts and if the Compute mode is off on some of the GPUs, you will get warning messages.
• Added console command 'y' to turn on the AMD Compute mode if it is not turned on on some of the cards.
• Small improvement in the -logfile option: now you can insert $ chararcter in the name, which will be removed from the name but will force the miner to overwrite the log file on each startup, instead of appending to it.
• Fixed a problem with miner restart on some CUDA errors with Nvidia cards when the miner crashes instead of restarting.
• Some other small fixes and changes

You can download 2.9e from here: https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw

Checksums to verify your download:

Code:

    File: PhoenixMiner_2.9e.zip
   SHA-1: e2b9c72e561ac0fdb4e3c9ebddd7d703a35da36c
 SHA-256: 9817c89623025cf392a4e800a41cff96a87eee02e241d9f08d62dc43e0975e96
 SHA-512: 33c78a73a53791c01bbfff2ad830ffd40d4007f69ca329300815ab1c189f744aafdc6683033cfcb0315db7f322e6dee44181b9dff2922b1fb408b0f04dba163b

We are now working on 3.0, which will include auto-tuning capabilities and more.

Unfortunately still crashes after  CUDA errors with Nvidia gtx 1070 cards. The last one that restart well after CUDa errors is 2.7c for me.

[murgorx]

These are my results:

Version 2.9e running very stable for 17 hours testing with :

GPU1 Nvidia GTX 1070, MICRON
GPU2 AMD RX 570 NITRO, MICRON
GPU3 Nvidia GTX 1070,MICRON

Power consumption 398W


*** 17:47 ***************************************************
Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 17:47
Eth speed: 96.655 MH/s, shares: 1534/0/0, time: 17:47
GPUs: 1: 32.608 MH/s (528) 2: 31.256 MH/s (470) 3: 32.791 MH/s (536)
Eth: Accepted shares 1534 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 35.3 TH (!!!)
Eth: Average speed (5 min): 96.613 MH/s
Eth: Effective speed: 95.82 MH/s; at pool: 95.82 MH/s

About stale shares miner reports zero, but on pool ETHERMINE average max 1 or 2%....


Keep up the good work...

What kind of GTX1070s do you have man? I am currently thinking of buying a couple and want to be sure I don't mess up with the order

[Watjila]

PhoenixMiner 2.9e is officially released.

The only reason why this miner is not running for more then a few days is because you guys keep releasing new versions! 

So far, 2.9e is quite stable.

[anbe2305]

These are my results:

Version 2.9e running very stable for 17 hours testing with :

GPU1 Nvidia GTX 1070, MICRON
GPU2 AMD RX 570 NITRO, MICRON
GPU3 Nvidia GTX 1070,MICRON

Power consumption 398W


*** 17:47 ***************************************************
Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 17:47
Eth speed: 96.655 MH/s, shares: 1534/0/0, time: 17:47
GPUs: 1: 32.608 MH/s (528) 2: 31.256 MH/s (470) 3: 32.791 MH/s (536)
Eth: Accepted shares 1534 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 35.3 TH (!!!)
Eth: Average speed (5 min): 96.613 MH/s
Eth: Effective speed: 95.82 MH/s; at pool: 95.82 MH/s

About stale shares miner reports zero, but on pool ETHERMINE average max 1 or 2%....


Keep up the good work...

What kind of GTX1070s do you have man? I am currently thinking of buying a couple and want to be sure I don't mess up with the order

GPU1 Gigabyte Windforce  TDP 51% , core clock +160, Memory +756 ( temp 45C fan 55%)  core can go over +200 and memory around +800 it can go much over 33MH ..
GPU3 MSI Armor TDP 52%, core clock +31 memory +772 (temp 54 fan 55%) core can go higher around +100 and memory around +800 it also can go higher then 33MH..


Both cards can get higher then 33 if power up  TDP, but then i get higher power consumption...

It does not matter which brand you would get just look which has more warranty, every GTX 1070 can go around 32 and 33 just need some time to test the settings...





  

[j2james]

Hi developers, is it possible to provide information about power usage? By rig and by a separate card. Or at least bu rig?

[Battousai1]

Hi guys, I would like to know, if you run two or more instances of Phoenix Miner, will the mining speed of those instances be reduced compared to running only on one instance? I am planning on running at least two instances of Phoenix Miner.

Lastly, when running another instance of Phoenix Miner, what is the best practice, should I just create another batch file in the same folder or create a new folder with a another executable file of Phoenix Miner? I am currently using two batch files with one executable file in a single folder and it is working fine.

Thank you in advance for any replies.

[od1n]

GPU1 Gigabyte Windforce  TDP 51% , core voltage +160, Memory +756 ( temp 45C fan 55%)  core can go over +200 and memory around +800 it can go much over 33MH ..
GPU3 MSI Armor TDP 52%, core voltage +31 memory +772 (temp 54 fan 55%) core can go higher around +100 and memory around +800 it also can go higher then 33MH..

Can you tell me what's the benefit of setting the TDP to such an low value together with increasing the core voltage? What speed (core clock) are your cards running at with these settings?

[j2james]

Looks like 2.9e on 6 GTX-1070 is less profitable then 2.8c.

My params are the following

-nvidia -cdm 2 -cdmport 3333 -cdmpass <password> -minRigSpeed 188 -rmode 2 -tstop 65 -tstart 40

PM 2.8c gives me 191.65MH and costs 750W (1MH costs 3.913W)
PM 2.9e gives me 192.5MH and costs 760W (1MH costs 3.948W)

It is not critical, of course, but...

Good news: PM 2.9e provides more stable hashrate then PM 2.8c or any Claymore or any Ethminer.
I have 0 stale shares during 1:25 (1 hour, 25 minutes).

[anbe2305]

GPU1 Gigabyte Windforce  TDP 51% , core clock +160, Memory +756 ( temp 45C fan 55%)  core can go over +200 and memory around +800 it can go much over 33MH ..
GPU3 MSI Armor TDP 52%, core clock +31 memory +772 (temp 54 fan 55%) core can go higher around +100 and memory around +800 it also can go higher then 33MH..

Can you tell me what's the benefit of setting the TDP to such an low value together with increasing the core voltage? What speed (core clock) are your cards running at with these settings?

Diferrent cards diffrent settings those are my cards:

Cards are getting 32.7MH and 32.8MH with these settings TDP 51% 52% low wattage, temperature , running very stable at these TDP no rejected shares and very low stale shares..

 

[od1n]

Do you really mean core voltage or isn't it core clock!?

[drgrog]

Add a newline character at the end of the request

You have to add new line (\n) after the end of your JSON request.

Thanks, that did the trick, and now kicking myself for not spotting it.
And makes sense given how JSON streams normally use line-delimiting framing.
Not sure why it ever worked in claymore, guess it's doing something funky.

[j2james]

My rig worked 5 hours 32 minutes with PM 2.9e. The stability of hashrate is perfect!!!

There was anly one time interval where hashrate was not stable. In this time interval I had the following results:
   Line 21821: 2018.04.16:17:40:19.980: main Eth speed: 190.554 MH/s, shares: 334/0/0, time: 4:43
   Line 21833: 2018.04.16:17:40:25.050: main Eth speed: 190.507 MH/s, shares: 334/0/0, time: 4:43
   Line 21846: 2018.04.16:17:40:30.120: main Eth speed: 192.407 MH/s, shares: 334/0/0, time: 4:43
   Line 21855: 2018.04.16:17:40:35.190: main Eth speed: 192.431 MH/s, shares: 334/0/0, time: 4:43
   Line 21859: 2018.04.16:17:40:40.260: main Eth speed: 192.505 MH/s, shares: 334/0/0, time: 4:43
   Line 21864: 2018.04.16:17:40:45.330: main Eth speed: 192.517 MH/s, shares: 334/0/0, time: 4:43
   Line 21867: 2018.04.16:17:40:50.400: main Eth speed: 192.501 MH/s, shares: 334/0/0, time: 4:43
   Line 21872: 2018.04.16:17:40:55.469: main Eth speed: 198.117 MH/s, shares: 334/0/0, time: 4:43
   Line 21879: 2018.04.16:17:41:00.571: main Eth speed: 198.311 MH/s, shares: 334/0/0, time: 4:43
   Line 21881: 2018.04.16:17:41:05.640: main Eth speed: 198.383 MH/s, shares: 334/0/0, time: 4:43

But all other time min value was 192.377, max value was 192.69. I do not know any miner which provides the stability like this one!

There is only one disadvantage - the power consumption increased by 10W. From 750W to 760W (

[janding]

Hi guys, I would like to know, if you run two or more instances of Phoenix Miner, will the mining speed of those instances be reduced compared to running only on one instance? I am planning on running at least two instances of Phoenix Miner.

Lastly, when running another instance of Phoenix Miner, what is the best practice, should I just create another batch file in the same folder or create a new folder with a another executable file of Phoenix Miner? I am currently using two batch files with one executable file in a single folder and it is working fine.

Thank you in advance for any replies.

I would guess that has been answered 10 times at least.
Search the forum ......

[sidaliroy]

Tested 2.9e for one day and here's my results:

x6 RX 580 4GB Sapphire (Stable 188mh/s - same hashrate as 2.8c)
x6 RX 570 4GB Armor (Very unstable 185mh/s - lower hashrate than 2.8c and it was more stable compared to 2.9e)
x6 RX 570 8GB Sapphire (Stable 193mh/s - lower hashrate than 2.8c)

Experiencing high stale shares on my RX 570 Armor Rig which wasn't the case in version 2.8c

Hopefully next update will be better.

[anbe2305]

Do you really mean core voltage or isn't it core clock!?

Yes it is core clock not core voltage....

[Mintycash]

My phoenixminer 2.9e always freeze when the miner trying to connect ethermine for dev fee mining. Anyone else experiencing the same?

I have the same problem with the 2.9e version on my 1060 3GB.

It gives a really good hashrate when mining ethash (small dag) but the moment the dev fee kicks in it crashes.

I believe this is because the dev fee is probably trying to mine ethereum, which has a dag file too big for a 3gb card used with a monitor.

If this is the case, could you set your dev fee to mine something else with a smaller dag fee so the miner doesn't crash? Or can you change any parameters on the dev fee mining so it does not consumes so much memory?