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

[Vicks-Berg]

Could anybody tell me how to properly assign email in nano pool config? When i try wallet/workername/email the nano pool shows invalid worker name.
I also tried wallet.workername/email  - the same output.

don't put -worker command line ... just use -wal walletaddress/workername/email

Also, what does "unable to get fan speed - unknown error (999) " mean? Does that mean video card crashed?

Have you tried to lowering your OC setting?

[GreenDust]

Could anybody tell me how to properly assign email in nano pool config? When i try wallet/workername/email the nano pool shows invalid worker name.
I also tried wallet.workername/email  - the same output.

don't put -worker command line ... just use -wal walletaddress/workername/email

Also, what does "unable to get fan speed - unknown error (999) " mean? Does that mean video card crashed?

Have you tried to lowering your OC setting?

I lowered the OC and it seems to run stable but hashing lower then claymore for some reason. I am getting 32mh per card and only 27 or 26 on phoenix. Is the -gt parameter has any effect on cuda?

[Vicks-Berg]

I lowered the OC and it seems to run stable but hashing lower then claymore for some reason. I am getting 32mh per card and only 27 or 26 on phoenix. Is the -gt parameter has any effect on cuda?

i never used -gt command line, and here my start.bat (it's not config.txt)

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -pool us-east.ethash-hub.miningpoolhub.com:20535 -wal vickyzz.eth01 -pass x -proto 1 -coin eth -ftimeout 120 -nvidia
pause

with core -200, memory + 800 and PL 70% I get 32 Mh/s stable hashrate as reported by phoenixminer

[hesido]

I tried this today (in benchmark mode because my miner currently has no internet connection until I sort out some things), VERY promising.

One thing I noticed that it constantly tries to set the OC for my second gpu (Rx580) in my 13 GPU rig, it's the one that seems unstable (A bad samsung mem, perhaps), it cannot go above 30 without crashing to 0 h/sec. Even when I keep it below 30 for stability, where it doesn't crash, I see Phoenix trying to set the voltages every few minutes.  Is that GPU a dud?

[FRosterdam]

It seems that option -ftimeout doesnt work. Test on 3.0c both Nvidia and AMD cards. Tried to set -ftimeout 60.

From original text:
-ftimeout <n> Reconnect if no new ethash job is receved for n seconds (default: 600)

[GreenDust]

Exactly same issue

[r1pst4rt]

It looks like the "autotune" process overrides my cclock mlock and cvdcc I've imported from Claymore.  Thus is bumps up power usage/heat.  I have -ethi and -dcri set in claymore how do these transpose across?  The autotune pushes my cards too much causing too much power/heat.

[john1010]

I tried phoenix before but I got lots of error.. Hey guys what is your experience in this latest version, is it now by pass the claymore speed and reliability? I will going turn on my mining again.. Hope all the alts will now recover.

[simcity4]

-coin moac is not an option can you add it ? or add -nofee and lower hashrate or something to mine other coin that is not in the list.
thanks

in next version of miner to see support for moac coin  will be great
thanks

[pinamalina]

I using PM 3.0c and every 5 sometimes 6 days PM stop working. What happend and how to fix this?
Have maybe someone .bat file for auto restar/reboot PM if PB stop working?

Code:

2018.07.26:00:42:06.959: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:06.959: eths Eth: New job #da40f35d from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.07.26:00:42:07.210: GPU3 GPU3: Starting up... (0)
2018.07.26:00:42:07.210: GPU3 Eth: Generating light cache for epoch #201
2018.07.26:00:42:07.370: GPU2 GPU2: Starting up... (0)
2018.07.26:00:42:07.396: GPU4 GPU4: Starting up... (0)
2018.07.26:00:42:07.396: GPU5 GPU5: Starting up... (0)
2018.07.26:00:42:07.422: GPU1 GPU1: Starting up... (0)
2018.07.26:00:42:07.429: GPU6 GPU6: Starting up... (0)
2018.07.26:00:42:10.009: GPU6 GPU6: Generating DAG for epoch #201
2018.07.26:00:42:10.009: GPU5 GPU5: Generating DAG for epoch #201
2018.07.26:00:42:10.010: GPU3 GPU3: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU4 GPU4: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU2 GPU2: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU1 GPU1: Generating DAG for epoch #201
2018.07.26:00:42:11.238: main Eth speed: 0.000 MH/s, shares: 3574/0/22, time: 52:09
2018.07.26:00:42:11.238: main GPUs: 1: 0.000 MH/s (582) 2: 0.000 MH/s (595) 3: 0.000 MH/s (591) 4: 0.000 MH/s (596) 5: 0.000 MH/s (592) 6: 0.000 MH/s (618/22)
2018.07.26:00:42:11.511: GPU5 GPU5: DAG  19%
2018.07.26:00:42:11.515: GPU2 GPU2: DAG  19%
2018.07.26:00:42:11.515: GPU3 GPU3: DAG  19%
2018.07.26:00:42:11.518: GPU4 GPU4: DAG  19%
2018.07.26:00:42:11.528: GPU6 GPU6: DAG  19%
2018.07.26:00:42:12.519: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.07.26:00:42:12.546: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:13.011: GPU5 GPU5: DAG  41%
2018.07.26:00:42:13.036: GPU6 GPU6: DAG  41%
2018.07.26:00:42:13.223: GPU3 GPU3: DAG  44%
2018.07.26:00:42:13.225: GPU2 GPU2: DAG  44%
2018.07.26:00:42:13.230: GPU4 GPU4: DAG  44%
2018.07.26:00:42:13.698: GPU1 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.700: GPU1 GPU1 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU3 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU3 GPU3 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU4 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU4 GPU4 initMiner error: unspecified launch failure
2018.07.26:00:42:13.785: GPU6 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.785: GPU6 GPU6 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU2 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU5 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU2 GPU2 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU5 GPU5 initMiner error: unspecified launch failure

I would mitigate this problem using the option -lidag:
  -lidag <n> Slow down DAG generation to avoid crashes when switching DAG epochs
      (0-3, default: 0 - fastest, 3 - slowest). You may specify this option per-GPU.
     Currently the option works only on AMD cards
So try with "-lidag 2".

From your above logs the problem with the gpus happened during the DAG generation. DAG generation is more intensive compared to normal hashing and when your OC is on the limit, it will crash the GPUs.

[4play]

I using PM 3.0c and every 5 sometimes 6 days PM stop working. What happend and how to fix this?
Have maybe someone .bat file for auto restar/reboot PM if PB stop working?

Code:

2018.07.26:00:42:06.959: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:06.959: eths Eth: New job #da40f35d from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.07.26:00:42:07.210: GPU3 GPU3: Starting up... (0)
2018.07.26:00:42:07.210: GPU3 Eth: Generating light cache for epoch #201
2018.07.26:00:42:07.370: GPU2 GPU2: Starting up... (0)
2018.07.26:00:42:07.396: GPU4 GPU4: Starting up... (0)
2018.07.26:00:42:07.396: GPU5 GPU5: Starting up... (0)
2018.07.26:00:42:07.422: GPU1 GPU1: Starting up... (0)
2018.07.26:00:42:07.429: GPU6 GPU6: Starting up... (0)
2018.07.26:00:42:10.009: GPU6 GPU6: Generating DAG for epoch #201
2018.07.26:00:42:10.009: GPU5 GPU5: Generating DAG for epoch #201
2018.07.26:00:42:10.010: GPU3 GPU3: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU4 GPU4: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU2 GPU2: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU1 GPU1: Generating DAG for epoch #201
2018.07.26:00:42:11.238: main Eth speed: 0.000 MH/s, shares: 3574/0/22, time: 52:09
2018.07.26:00:42:11.238: main GPUs: 1: 0.000 MH/s (582) 2: 0.000 MH/s (595) 3: 0.000 MH/s (591) 4: 0.000 MH/s (596) 5: 0.000 MH/s (592) 6: 0.000 MH/s (618/22)
2018.07.26:00:42:11.511: GPU5 GPU5: DAG  19%
2018.07.26:00:42:11.515: GPU2 GPU2: DAG  19%
2018.07.26:00:42:11.515: GPU3 GPU3: DAG  19%
2018.07.26:00:42:11.518: GPU4 GPU4: DAG  19%
2018.07.26:00:42:11.528: GPU6 GPU6: DAG  19%
2018.07.26:00:42:12.519: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.07.26:00:42:12.546: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:13.011: GPU5 GPU5: DAG  41%
2018.07.26:00:42:13.036: GPU6 GPU6: DAG  41%
2018.07.26:00:42:13.223: GPU3 GPU3: DAG  44%
2018.07.26:00:42:13.225: GPU2 GPU2: DAG  44%
2018.07.26:00:42:13.230: GPU4 GPU4: DAG  44%
2018.07.26:00:42:13.698: GPU1 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.700: GPU1 GPU1 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU3 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU3 GPU3 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU4 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU4 GPU4 initMiner error: unspecified launch failure
2018.07.26:00:42:13.785: GPU6 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.785: GPU6 GPU6 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU2 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU5 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU2 GPU2 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU5 GPU5 initMiner error: unspecified launch failure

I would mitigate this problem using the option -lidag:
  -lidag <n> Slow down DAG generation to avoid crashes when switching DAG epochs
      (0-3, default: 0 - fastest, 3 - slowest). You may specify this option per-GPU.
     Currently the option works only on AMD cards
So try with "-lidag 2".

From your above logs the problem with the gpus happened during the DAG generation. DAG generation is more intensive compared to normal hashing and when your OC is on the limit, it will crash the GPUs.

Tnx for advice. I will try this. Thx a lot

[hogito]

Anyone have answer for this behavior,i have 5 rigs and all are crazy on phoenix or is it normal ?

https://imgur.com/a/BuqBtzN

https://imgur.com/a/oFSCLaU

Tried many drivers with overdriventool,win 10 ltsb,no memory errors,compute enabled etc so its not oc,ping is normal around 30-40ms.Images are pool side,miner side looks stable and ok,variations in miner are 1-2mhs up and down sometimes,tried clkernel 2 but drops are worse miner side.Anyone have any clue?thx

Have you ever mined before?  Are you saying on a different miner you have different looking graphs?  If so you should post both.

[okiesmokie]

Anyone have answer for this behavior,i have 5 rigs and all are crazy on phoenix or is it normal ?

https://imgur.com/a/BuqBtzN

https://imgur.com/a/oFSCLaU

Tried many drivers with overdriventool,win 10 ltsb,no memory errors,compute enabled etc so its not oc,ping is normal around 30-40ms.Images are pool side,miner side looks stable and ok,variations in miner are 1-2mhs up and down sometimes,tried clkernel 2 but drops are worse miner side.Anyone have any clue?thx

Have you ever mined before?  Are you saying on a different miner you have different looking graphs?  If so you should post both.

Mate im not mining from yesterday
Anyway,it does have strange behavior,doesent matter which kernel you use or mi seetings hash rate isnt "stable" by that i mean one second rig have 185mhs after few sec random card drop and total hash rate is 182 or 181 etc then comes back to 185 on every rig i have thats why i asked.On claymore hash rate is fixed and doesent have that random drops but hashrate total is a bit lower.Cards are mixed 470+570 total 31 some are elpida some are samsung undervolted with overdriventool vcore 860 and mem 860 no errors and 1125 core 2000-2075 mem range.

[jimsta]

I have 1 rig on phoenix and 1 on claymore and both my rigs look like that.  I've been mining since january, is it NOT normal that expected hashrate rarely matches pool hash? Figured it was just part of it.

Anyone have answer for this behavior,i have 5 rigs and all are crazy on phoenix or is it normal ?

https://imgur.com/a/BuqBtzN

https://imgur.com/a/oFSCLaU

Tried many drivers with overdriventool,win 10 ltsb,no memory errors,compute enabled etc so its not oc,ping is normal around 30-40ms.Images are pool side,miner side looks stable and ok,variations in miner are 1-2mhs up and down sometimes,tried clkernel 2 but drops are worse miner side.Anyone have any clue?thx

Have you ever mined before?  Are you saying on a different miner you have different looking graphs?  If so you should post both.

Mate im not mining from yesterday
Anyway,it does have strange behavior,doesent matter which kernel you use or mi seetings hash rate isnt "stable" by that i mean one second rig have 185mhs after few sec random card drop and total hash rate is 182 or 181 etc then comes back to 185 on every rig i have thats why i asked.On claymore hash rate is fixed and doesent have that random drops but hashrate total is a bit lower.Cards are mixed 470+570 total 31 some are elpida some are samsung undervolted with overdriventool vcore 860 and mem 860 no errors and 1125 core 2000-2075 mem range.

[GreenDust]

Is there a way to make the miner benchmark itself? I am using 1070's

[sirkorro]

Hi.

Thanks for great piece of software.

While I appreciate Claymore-like API, maybe it would be good to create something better.
I would like to have something similar to Excavator devices endpoint. https://github.com/nicehash/excavator/tree/master/api#devices-get
You can also add hash rates to each GPU and maybe hash per watt since all the data is there.

OC settings for Nvidia would be appreciated too.

Regards.

[promomei]

Hey guys i want miner to restart every 12 hours
what line i use -timeout 12  
 12 i use hour or i need put minutes like   -timeout 720  or seconds ?

[Vicks-Berg]

Hey guys i want miner to restart every 12 hours
what line i use -timeout 12  
 12 i use hour or i need put minutes like   -timeout 720  or seconds ?

-timeout is a minutes value, so if you want to restart every 12 hours use -timeout 720

[promomei]

Hey guys i want miner to restart every 12 hours
what line i use -timeout 12  
 12 i use hour or i need put minutes like   -timeout 720  or seconds ?

-timeout is a minutes value, so if you want to restart every 12 hours use -timeout 720

thanks pal 

[promomei]

Hey guys i want miner to restart every 12 hours
what line i use -timeout 12  
 12 i use hour or i need put minutes like   -timeout 720  or seconds ?

Is there a good reason for this? thought set it and forget it was a better practice 

Maybe 

Im experimenting this miner