Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 465. (Read 784954 times)

thanks and good job
with 2.6 i make 169mh/s, now with 2.7b 171mh/s.
i have a better hashrate with fury x, same for rx470.

-tt Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards,
     1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n %)

New beta version with added hardware control features: PhoenixMiner 2.7b. It can be downloaded from here:
  https://mega.nz/#F!HI9lnDAS!gIFL-f82FK1MK16amCv_iQ

  Here are the checksums to verify the download:

   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.

17589:11:17:58.925: unkn Eth: Can't resolve host us1.ethermine.org:4444 - The requested name is valid, but no data of the requested type was found
17589:11:17:58.925: unkn Eth: Giving up after 3 retries, switching to next pool
17589:11:17:58.925: unkn Eth: Reconnecting in 20 seconds...
17589:11:18:02.646: GPU4 Unable to submit share - pool disconnected
17589:11:18:07.786: main GPU1: 59C 44%, GPU2: 59C 41%, GPU3: 53C 17%, GPU4: 59C 39%, GPU5: 59C 43%, GPU6: 59C 43%, GPU7: 59C 42%
17589:11:18:18.940: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444
17589:11:18:18.940: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - The requested name is valid, but no data of the requested type was found
17589:11:18:18.940: unkn Eth: Reconnecting in 20 seconds...
17589:11:18:19.049: GPU5 Unable to submit share - pool disconnected
17589:11:18:29.791: GPU7 Unable to submit share - pool disconnected
17589:11:18:35.860: main GPU1: 59C 44%, GPU2: 59C 41%, GPU3: 53C 17%, GPU4: 59C 39%, GPU5: 59C 44%, GPU6: 59C 42%, GPU7: 59C 42%
17589:11:18:38.949: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444
17589:11:18:38.950: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - The requested name is valid, but no data of the requested type was found
17589:11:18:38.950: unkn Eth: Reconnecting in 20 seconds...
17589:11:18:39.469: GPU7 Unable to submit share - pool disconnected
17589:11:18:58.954: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444
17589:11:18:58.954: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - The requested name is valid, but no data of the requested type was found
17589:11:19:00.813: unkn Eth: Giving up after 3 retries, switching to next pool
17589:11:19:00.813: unkn Eth: Reconnecting in 20 seconds...
17589:11:19:03.868: main GPU1: 55C 44%, GPU2: 55C 41%, GPU3: 49C 17%, GPU4: 55C 39%, GPU5: 54C 43%, GPU6: 55C 42%, GPU7: 55C 42%
17589:11:19:20.816: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444
17589:11:19:20.950: eths Eth: Connected to ethash pool us1.ethermine.org:4444 (18.219.59.155)
17589:11:19:20.950: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-CIU19IR"]}

17589:11:19:21.080: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
17589:11:19:31.871: main GPU1: 45C 36%, GPU2: 46C 33%, GPU3: 44C 0%, GPU4: 48C 33%, GPU5: 44C 36%, GPU6: 46C 35%, GPU7: 45C 35%
17589:11:19:59.936: main GPU1: 42C 0%, GPU2: 45C 0%, GPU3: 44C 0%, GPU4: 48C 0%, GPU5: 42C 0%, GPU6: 45C 0%, GPU7: 44C 0%
17589:11:20:27.943: main GPU1: 43C 0%, GPU2: 45C 0%, GPU3: 44C 0%, GPU4: 49C 0%, GPU5: 43C 0%, GPU6: 45C 0%, GPU7: 44C 0%

I have tried your miner in my 2 GPU rig, miner starts and after 20-25 seconds later simply exits without giving any warning or error

here is the log :

17563:13:31:45.586: main Phoneix Miner 2.6b Windows/msvc - Release
17563:13:31:45.586: main Cmd line: -pool eu1.ethermine.org:4444 -wal 0xxxxxxxx0c03865F898F82e95fEaDcC33b301047e.zig5 -pass x -proto 3
17563:13:31:46.307: main Available GPUs for mining:
17563:13:31:46.333: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17563:13:31:46.333: main GPU2: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
17563:13:31:46.343: main ADL library initialized
17563:13:31:46.345: main NVML library initialized

any help?

New beta version with added hardware control features: PhoenixMiner 2.7b.

running 2.7b and using the -tt 65 flag.

working excellent, and now the power draw has dropped 30W.

228MH/s with 1090W at the wall. before -tt fan control on 2.6 it was pulling 1120W from the wall.

back to the same power draw as claymore, and kept the higher hashrate. i'm not sure what it is about the lack of fan control causing high power draw, maybe the VRMs not getting enough airflow and becoming very inefficient.

either way, i like it! good job team.

running 2.7b and using the -tt 65 flag.

working excellent, and now the power draw has dropped 30W.

228MH/s with 1090W at the wall. before -tt fan control on 2.6 it was pulling 1120W from the wall.

back to the same power draw as claymore, and kept the higher hashrate. i'm not sure what it is about the lack of fan control causing high power draw, maybe the VRMs not getting enough airflow and becoming very inefficient.

either way, i like it! good job team.

you have too much overclock...

turn off all the nvidia audiodevices in devicemanager. for me it helped to solve some weird (driver i think) related stuff.

Same as you i have 2 righs completly the same 1070 Dual OCs , they are basicaly mirrors.
1 works fine the other has the error you had, i have the latest windows 10 1709 and i am still getting that error after 10/12 hours of running.
Drives me crazy.

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.

New beta version with added hardware control features: PhoenixMiner 2.7b. It can be downloaded from here:
  https://mega.nz/#F!HI9lnDAS!gIFL-f82FK1MK16amCv_iQ

  Here are the checksums to verify the download:

   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.

would these controls be also working for NVidias?

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.

whenever i try to mine
ELLA or PIRL
i get error
am i doing anything wrong in the batch file?

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.

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.

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

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