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

[StarLordRammi]

whenever i try to mine
ELLA or PIRL
i get

connection closed by Pool

error

am i doing anything wrong in the batch file?

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 pool.ellaism.org:8008 -wal Wallet.Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2

[flatounet]

whenever i try to mine
ELLA or PIRL
i get

connection closed by Pool

error

am i doing anything wrong in the batch file?

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 pool.ellaism.org:8008 -wal Wallet.Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2

try to change wallet.worker  with wallet/worker

(im on nanopool here , and work with the /   )


any help to made watchdog for phoenix ?
[ windows 10 (64) ]

Code:

:kill
taskkill /F -IM wd616.exe
taskkill /F -IM start.bat
taskkill /F -IM PhoenixMiner.exe
ping www.google.com -n 20
:start
start wd616.exe
ping www.google.com -n 20
start start.bat
ping www.google.com -n 40
:loop
taskkill /im "PhoenixMiner.exe" /fi "STATUS eq NOT RESPONDING" /f >nul && goto kill
goto loop

wd616 is app for my watchdog usb key ,if windows froz ....
start.bat is bat file with my config for start phoenixminer.exe...

and script is for check if phoenixminer is alive
when no answers kill exe & bat ,and restart bat  .....
any help is welcome here

[18TommyBoy18]

+1 for Claymore, have more hashes...

[Iamtutut]

+1 for Claymore, have more hashes...

No stale share reported by claymore.
Check on your mining pool to be sure.

[Hodlmyhand]

For me Phoenix Miner gives more stale shares on the pool than is reported in the software.  Generally Claymore gives less stale shares I find.

[janding]

For me Phoenix Miner gives more stale shares on the pool than is reported in the software.  Generally Claymore gives less stale shares I find.

I don't find that to be true in my case.

1st, Phoenix can't report stale shares in their console display that are stale at the pool in all cases. They have already discussed
that in prior statements. So they can only show you stale shares in certain cases. I don't think Claymore even attempts
to report stale shares in their console window.

The only accurate way to know stale shares on either miner is to look at the pool stats.
I my case they are close but Phoenix hour by hour at the pool is showing less stale shares than Claymore.

As always "your results may vary"

[gsrcrxsi314]

Phoenix/OP:

i have 2 systems running just fine on Phoenix2.6

but now on a 3rd system with a brand new fresh install of win10 x64. and a single MSI GTX 1080ti im hitting the following error:

Code:

17586:19:01:11.605: GPU1 GPU1: DAG generated in 5.9 s (403.2 MB/s)
17586:19:01:13.312: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17586:19:01:14.641: GPU1 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17586:19:01:14.641: GPU1 GPU1 search error: unspecified launch failure
17586:19:01:15.117: wdog Thread(s) not responding. Restarting.
17586:19:01:17.460: GPU1 GPU1: Starting up...
17586:19:01:17.497: GPU1 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17586:19:01:17.497: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable

I have DDU'd my driver, and reinstalled to no avail. nvidia driver 390.77, same driver as my other nvidia based rig thats working just fine

[miner_in_bkk]

Hi All,

I recently updated to 2.7a. Prior to this update i had quite the stable rig, that required very little attention. Now it seems its quite the opposite. The latest mystery. I have a 5 x RX 580 rig / win 10 / Corsair HX750i & 1200W server PSU / 4gb / 16 Vram.

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 asia1.ethermine.org:4444 -pool2 asia1.ethermine.org:14444 -ewal xxx.xxx -pass x -minspeed 147 -rmode 2 -mi 11 -coin eth -ptimeout 20

It had been hashing for 24 hours, when one of the GPU's for a minute went from 30 to 23. This then triggered the minspeed alert and reboot.

For the next 4 hours (while i was asleep) the computer kept rebooting as the DAG file couldn't be allocated/generated. Here is the first time stamp/log file.

17587:04:45:12.458: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xf15054bbbde12d86505537865e7cd869691425338635099ac1b04703df152974","0xa9b0e0c9aca72c07ba06b5bbdae8b8f69e61878301508473379bb4f71807d707","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4e95ae"]}
17587:04:45:12.458: eths Eth: New job #f15054bb from asia1.ethermine.org:4444; diff: 4000MH
17587:04:45:12.459: GPU1 GPU1: Starting up... (0)
17587:04:45:12.459: GPU1 Eth: Generating light cache for epoch #171
17587:04:45:12.462: GPU2 GPU2: Starting up... (0)
17587:04:45:12.477: GPU3 GPU3: Starting up... (0)
17587:04:45:12.498: GPU4 GPU4: Starting up... (0)
17587:04:45:12.527: GPU5 GPU5: Starting up... (0)
17587:04:45:14.974: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x168febd9cda4f35857736a1c4d7bdc2556ec02f684adc531b9c3839fee7f1552","0xa9b0e0c9aca72c07ba06b5bbdae8b8f69e61878301508473379bb4f71807d707","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4e95ae"]}
17587:04:45:14.974: eths Eth: New job #168febd9 from asia1.ethermine.org:4444; diff: 4000MH
17587:04:45:17.185: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17587:04:45:17.185: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0)
17587:04:45:22.201: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17587:04:45:22.201: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0)
17587:04:45:22.368: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17587:04:45:57.978: main *** 0:00 ***************************************************
17587:04:45:57.978: main Eth: Mining ETH on asia1.ethermine.org:4444
17587:04:45:57.978: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17587:04:45:57.978: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0)
17587:04:45:57.978: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
17587:04:45:57.978: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
17587:04:45:57.978: main Eth: Average speed (5 min): 0.000 MH/s
17587:04:45:57.978: main 
17587:04:45:58.002: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xc22d3f55e9a2339f73260a49b30ae5a3f29f729c57a18ae6a193076acfac45b9","0xa9b0e0c9aca72c07ba06b5bbdae8b8f69e61878301508473379bb4f71807d707","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4e95b2"]}
17587:04:45:58.002: eths Eth: New job #c22d3f55 from asia1.ethermine.org:4444; diff: 4000MH
17587:04:46:02.390: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

<SKIP AHEAD>

17587:04:46:42.470: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x32bc355ed2f08d162ac3d0c92ce9fb67e0ae819c3282ec5f10af9bdd4b3b690f","0xa9b0e0c9aca72c07ba06b5bbdae8b8f69e61878301508473379bb4f71807d707","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4e95b3"]}
17587:04:46:42.991: wdog GPU1 not responding
17587:04:46:42.991: wdog GPU2 not responding
17587:04:46:42.991: wdog GPU3 not responding
17587:04:46:42.991: wdog GPU4 not responding
17587:04:46:42.991: wdog GPU5 not responding
17587:04:46:42.991: wdog Thread(s) not responding. Restarting.
17587:04:46:44.214: main 
17587:04:46:44.214: main *** 0:01 ***************************************************
17587:04:46:44.214: main Eth: Mining ETH on asia1.ethermine.org:4444
17587:04:46:44.214: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
17587:04:46:44.214: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0)
17587:04:46:44.214: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
17587:04:46:44.214: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
17587:04:46:44.214: main Eth: Average speed (5 min): 0.000 MH/s
17587:04:46:44.214: main Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
17587:04:46:44.214: main


All of a sudden at 8.10 after about 20+ reboots (same as above) it suddenly starts allocating/generating DAG file.

Any ideas why this might be the case, or is the 7a release a bit buggy compared to earlier versions ?

Many thanks.

[flatounet]

Phoenix/OP:

i have 2 systems running just fine on Phoenix2.6

but now on a 3rd system with a brand new fresh install of win10 x64. and a single MSI GTX 1080ti im hitting the following error:

Code:

17586:19:01:11.605: GPU1 GPU1: DAG generated in 5.9 s (403.2 MB/s)
17586:19:01:13.312: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17586:19:01:14.641: GPU1 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17586:19:01:14.641: GPU1 GPU1 search error: unspecified launch failure
17586:19:01:15.117: wdog Thread(s) not responding. Restarting.
17586:19:01:17.460: GPU1 GPU1: Starting up...
17586:19:01:17.497: GPU1 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17586:19:01:17.497: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable

I have DDU'd my driver, and reinstalled to no avail. nvidia driver 390.77, same driver as my other nvidia based rig thats working just fine

i got this error one time , it's about OC for me ....
reset OC ,and re-test or check/change  riser after .....

[flatounet]

have you try to set :
-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

or with luck :

-lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs
      (0-3, default: 0 - fastest, 3 - slowest). This option works only on AMD cards

here i have remove " -minspeed "

because Nanopool made me minning sometime slowly ( 60 mhs )
but the miner ( black line on nanopool ) work @ 150 mhs ....

and rig have free reboot for nothing ....

[gsrcrxsi314]

Phoenix/OP:

i have 2 systems running just fine on Phoenix2.6

but now on a 3rd system with a brand new fresh install of win10 x64. and a single MSI GTX 1080ti im hitting the following error:

Code:

17586:19:01:11.605: GPU1 GPU1: DAG generated in 5.9 s (403.2 MB/s)
17586:19:01:13.312: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17586:19:01:14.641: GPU1 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17586:19:01:14.641: GPU1 GPU1 search error: unspecified launch failure
17586:19:01:15.117: wdog Thread(s) not responding. Restarting.
17586:19:01:17.460: GPU1 GPU1: Starting up...
17586:19:01:17.497: GPU1 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17586:19:01:17.497: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable

I have DDU'd my driver, and reinstalled to no avail. nvidia driver 390.77, same driver as my other nvidia based rig thats working just fine

i got this error one time , it's about OC for me ....
reset OC ,and re-test or check/change  riser after .....

There was no overclock applied. It was completely stock.

But I don’t know what it was but after updating to the most recent version of Windows 10, the problem seems to have gone away.

Old version: 1511
New version: 1709

Works fine now.

[cdrx]

When undervolt with claymore 6 rx and 900 900 consume 860W ... to trick and make undervolt in phoenix as above says, you start claymore, overdriventool, close claymore, start phoenix.

But phoenix will consume 875W  ... so 15 more. Yet, is more stable for me (27H and no crash), while lately claymore crashed rig when using low voltage... after an hour, 17 or more.

Conclusion : in my case, undervolt works better with phoenix. Waiting for 2.7  

[flatounet]

When undervolt with claymore 6 rx and 900 900 consume 860W ... to trick and make undervolt in phoenix as above says, you start claymore, overdriventool, close claymore, start phoenix.

But phoenix will consume 875W  ... so 15 more. Yet, is more stable for me (22H and no crash), while lately claymore crashed rig when using low voltage... after an hour, 17 or more.

Conclusion : in my case, undervolt works better with phoenix. Waiting for 2.7 

it's not only for you ,
i do the same here,
i have better minning with phoenix
i think guy have poor , dont know how to UC / setting CG or miner. ...

phoenix about minning is better than claymore ....

im asking few options but
ur minning @t home ,phoenix is perfect

[StarLordRammi]

whenever i try to mine
ELLA or PIRL
i get

connection closed by Pool

error

am i doing anything wrong in the batch file?

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 pool.ellaism.org:8008 -wal Wallet.Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2

try to change wallet.worker  with wallet/worker

(im on nanopool here , and work with the /   )

that didnt work  

Edit: problem Fixed

-wal WalletAddress -cdm 0 -amd -wdog 0 -log 0 -rmode 2 -worker WorkerName

Worker name need its own command not right next to wallet address

[DjKhaledJr]

My rig keeps restarting when I use PhoenixMiner 2.6. I've no problem running Claymore, it's very stable but I'd like to try Phoenix as a lot of people have a good opinion about it. Here is the log of Phoenixminer ( https://imgur.com/uiFEcPm ). From what I can see, it hungs one of my gpus and then restars the system, no error so to say. Am I missing some parameteres? My settings are the same as in Claymore, i just ported the start.bat. Any ideas appreciated.

[JoepMeloen]

So for the Awsome Miners out there.. There is a little bug in AM in combination with PM. If you get a connection error its probably due to this error: AM adds the workername/number to your adress and the server rejects the connection.. you UNcheck the "add workername"  box in the miner settings/managed template and you should be ok. You can check in the console when the miner is loading, it will add something to your adress.

Bug is reported to AM dev.

Update: -eworker isnt passed by AM,so it puts the workername behind the address,and server rejects. will be fixed in AM update.

[Reed1981]

This miner keeps crashing on me, when claymore is not. Running 3x 1060s (one 3Gb, two 6Gb). Within 10 minutes it'll start to print a new line (in green I think), and it stops on the first letter, 'E'.

Doesn't respond to anything. Hard crash.

[Njeroe]

r7 370 2g can be mining eth with this program?

No, to mine ETH you need at least 3GB VRAM videocard...

[PhoenixMiner]

New beta version with added hardware control features: PhoenixMiner 2.7b. It can be downloaded from here:
  (MEGA links are no longer active)

  Here are the checksums to verify the download:

Code:

   File: PhoenixMiner_2.7b.zip
   SHA-1: e7eae3645429cb06178aa69728235e842c2548a8
 SHA-256: b872fed471b72911e6980d08496c3da03867dd82e3175241a9d67b2686921c9f
 SHA-512: c787e1383048af9c67ab2f26f1f5eadf061c8fb32a9ae4592c876acd881cdb6ffca2baa2f669204671fd27d4add4d10dd20762f9d35324e89f86f8c49eef68f4

   Note that this is not an official release and the solo mining features are not included in it (they will be included in the final 2.7 release). The changes are:

• Added support for controlling fans, clocks and voltages on AMD cards (use the command-line options -tt, -fanmin, -fanmax, -tmax, -powlim, -cclock, -cvddc, -mclock, -mvddc)
• Improved GPU matching code to fix a problem with mismatched temperatures/fan speeds on Nvidia GPUs

  Here are some important notes about the hardware control options:

• 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 and Vega). 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 newest drivers from AMD: 18.1.1 or 18.2.1, 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 crahses/freezes/incorrect shares when set with third-party program, they will be just as much unstable when set via PhoenixMiner hardware control options.

[PhoenixMiner]

would these controls be also working for NVidias?

 Not at this time. We had our hands full with AMD's semi-documented library and the Nvidia doesn't provide any documentation for the overclocking features of NVAPI. But we will definitely try to make it work in the future, but no promises as to when it will be ready.

Developers please make option like Claymores -altnum, but in oposite. I want my GPUs be numbered from ZERO as all other miners and gpu settings software do. First GPU should be GPU0. Thanks. Your numbering starting from 1 makes me more diffucult to identify while tuning cards.

 Well, as C programmers we can certainly see the appeal of indexes starting from 0 We'll include in the TODO list of nice-to-have options, but no ETA.

whenever i try to mine
ELLA or PIRL
i get

connection closed by Pool

error
am i doing anything wrong in the batch file?

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 pool.ellaism.org:8008 -wal Wallet.Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2

  This pool seems to require the worker to be specified separately like this (-wal must contain only the wallet address):

Code:

PhoenixMiner.exe -pool pool.ellaism.org:8008 -wal Wallet -worker Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2

Hi All,

I recently updated to 2.7a. Prior to this update i had quite the stable rig, that required very little attention. Now it seems its quite the opposite. The latest mystery. I have a 5 x RX 580 rig / win 10 / Corsair HX750i & 1200W server PSU / 4gb / 16 Vram.

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 asia1.ethermine.org:4444 -pool2 asia1.ethermine.org:14444 -ewal xxx.xxx -pass x -minspeed 147 -rmode 2 -mi 11 -coin eth -ptimeout 20

It had been hashing for 24 hours, when one of the GPU's for a minute went from 30 to 23. This then triggered the minspeed alert and reboot.

For the next 4 hours (while i was asleep) the computer kept rebooting as the DAG file couldn't be allocated/generated. Here is the first time stamp/log file.

....

All of a sudden at 8.10 after about 20+ reboots (same as above) it suddenly starts allocating/generating DAG file.

Any ideas why this might be the case, or is the 7a release a bit buggy compared to earlier versions ?

Many thanks.

 There seems to be a problem with light cache generation, which normally shoudn't take more than 5-15 seconds and is done entirely on the CPU. Probably something else loads the CPU to 100% with high priority task and the light cache just can't be generated in time so the watchdog is kicking in. Check the CPU load in Task Manager if this behavior repeats and note which program "eats" the CPU time (PhoenixMiner.exe should only load one core to 100% during light cache generation and then keep it at nearly idle during normal operation).

My rig keeps restarting when I use PhoenixMiner 2.6. I've no problem running Claymore, it's very stable but I'd like to try Phoenix as a lot of people have a good opinion about it. Here is the log of Phoenixminer ( https://imgur.com/uiFEcPm ). From what I can see, it hungs one of my gpus and then restars the system, no error so to say. Am I missing some parameteres? My settings are the same as in Claymore, i just ported the start.bat. Any ideas appreciated.

  If it is always the same card probably it is either overclocked with Clyamore's dual miner and PhoenixMiner just ignores these options and runs the cards with their stock settings, or the cards is "on the edge" clock/voltage wise and the small increase of mining speed from PhoenixMiner pushes it over the edge. Lower the clock speed or up the voltage just a little bit on GPU2 and see if this fixes the problem (you can also try the new PhoenixMiner 2.7b which has support for the hardware control options).

r7 370 2g can be mining eth with this program?

  You can mine Pirl, Ellaism, Ubq, Expanse, etc. The profitability is usually about 80-90% of ETH, so  2 GB cards are still quite usable for mining.