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

[UnclWish]

hi,

there is one more problem,
for pausing a single gpu, i press 1..9, but what if i have more then 10 gpus, and i need to pause #12 ?

thanks

Shift + #. For 12 GPU you need to press Shift+2.

[j2james]

Hi PM developers. I have caught 719 error again two times

2018.04.30:18:28:55.438: main *** 67:17 ***************************************************
2018.04.30:18:28:55.438: main Eth: Mining ETH on eth-eu1.nanopool.org:9999 for 67:17
2018.04.30:18:28:55.438: main Eth speed: 192.436 MH/s, shares: 4483/0/0, time: 67:17
2018.04.30:18:28:55.438: main GPUs: 1: 32.080 MH/s (759) 2: 32.077 MH/s (728) 3: 32.071 MH/s (742) 4: 32.076 MH/s (742) 5: 32.071 MH/s (772) 6: 32.061 MH/s (740)
2018.04.30:18:28:55.438: main Eth: Accepted shares 4483 (0 stales), rejected shares 0 (0 stales)
2018.04.30:18:28:55.438: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.04.30:18:28:55.438: main Eth: Maximum difficulty of found share: 437.9 TH (!!!)
2018.04.30:18:28:55.438: main Eth: Average speed (5 min): 192.436 MH/s
2018.04.30:18:28:55.438: main Eth: Effective speed: 185.05 MH/s; at pool: 185.05 MH/s
2018.04.30:18:28:55.438: main 
2018.04.30:18:29:00.508: main Eth speed: 192.436 MH/s, shares: 4483/0/0, time: 67:17
2018.04.30:18:29:00.508: main GPUs: 1: 32.080 MH/s (759) 2: 32.078 MH/s (728) 3: 32.070 MH/s (742) 4: 32.076 MH/s (742) 5: 32.071 MH/s (772) 6: 32.061 MH/s (740)
2018.04.30:18:29:02.221: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.255: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.262: GPU3 GPU3 search error: unspecified launch failure
2018.04.30:18:29:02.262: GPU2 GPU2 search error: unspecified launch failure
2018.04.30:18:29:02.271: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.271: GPU6 GPU6 search error: unspecified launch failure
2018.04.30:18:29:02.319: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.319: GPU1 GPU1 search error: unspecified launch failure
2018.04.30:18:29:02.319: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.319: GPU5 GPU5 search error: unspecified launch failure
2018.04.30:18:29:02.326: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.326: GPU4 GPU4 search error: unspecified launch failure
2018.04.30:18:29:02.832: wdog Thread(s) not responding. Restarting.
2018.04.30:18:29:03.566: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:18:29:03.639: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x883fa91730edc42848c2f91f1a5945dc86876f0ee669a2484b39733c2662cd06","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:18:29:05.656: main Eth speed: 192.435 MH/s, shares: 4483/0/0, time: 67:17
2018.04.30:18:29:05.656: main GPUs: 1: 32.081 MH/s (759) 2: 32.078 MH/s (728) 3: 32.069 MH/s (742) 4: 32.076 MH/s (742) 5: 32.071 MH/s (772) 6: 32.061 MH/s (740)

2018.04.30:23:54:18.043: main *** 5:24 ***************************************************
2018.04.30:23:54:18.043: main Eth: Mining ETH on eth-eu1.nanopool.org:9999 for 5:24
2018.04.30:23:54:18.043: main Eth speed: 192.454 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:18.043: main GPUs: 1: 32.077 MH/s (55) 2: 32.079 MH/s (65) 3: 32.077 MH/s (55) 4: 32.079 MH/s (60) 5: 32.075 MH/s (46) 6: 32.069 MH/s (63)
2018.04.30:23:54:18.043: main Eth: Accepted shares 344 (0 stales), rejected shares 0 (0 stales)
2018.04.30:23:54:18.043: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.04.30:23:54:18.043: main Eth: Maximum difficulty of found share: 338.2 TH (!!!)
2018.04.30:23:54:18.043: main Eth: Average speed (5 min): 192.450 MH/s
2018.04.30:23:54:18.043: main Eth: Effective speed: 176.88 MH/s; at pool: 176.88 MH/s
2018.04.30:23:54:18.043: main 
2018.04.30:23:54:18.823: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:18.823: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xb788eab","0xdc186dc6449f3ed8555c0ee3383c94cfb7efe302fed5427f9733ac049b2035cd"]}

2018.04.30:23:54:18.873: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x983050918378fb6f287be2d4985c47405b9cef936795b53105fca0ae77b70e91","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:23.113: main Eth speed: 192.454 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:23.113: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.079 MH/s (60) 5: 32.075 MH/s (46) 6: 32.068 MH/s (63)
2018.04.30:23:54:23.519: main GPU1: 46C 47%, GPU2: 47C 48%, GPU3: 46C 48%, GPU4: 44C 47%, GPU5: 51C 51%, GPU6: 44C 47%
2018.04.30:23:54:26.085: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:26.085: eths Eth: New job #1fb12e59 from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.04.30:23:54:28.183: main Eth speed: 192.453 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:28.183: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.078 MH/s (55) 4: 32.078 MH/s (60) 5: 32.075 MH/s (46) 6: 32.067 MH/s (63)
2018.04.30:23:54:28.838: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:28.887: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:33.253: main Eth speed: 192.455 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:33.253: main GPUs: 1: 32.076 MH/s (55) 2: 32.078 MH/s (65) 3: 32.078 MH/s (55) 4: 32.079 MH/s (60) 5: 32.075 MH/s (46) 6: 32.069 MH/s (63)
2018.04.30:23:54:38.323: main Eth speed: 192.453 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:38.323: main GPUs: 1: 32.076 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.078 MH/s (60) 5: 32.075 MH/s (46) 6: 32.069 MH/s (63)
2018.04.30:23:54:38.853: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:38.853: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xb788e1f","0xdc186dc6449f3ed8555c0ee3383c94cfb7efe302fed5427f9733ac049b2035cd"]}

2018.04.30:23:54:38.902: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:43.393: main Eth speed: 192.453 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:43.393: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.078 MH/s (60) 5: 32.075 MH/s (46) 6: 32.068 MH/s (63)
2018.04.30:23:54:48.463: main Eth speed: 192.452 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:48.463: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.078 MH/s (60) 5: 32.074 MH/s (46) 6: 32.068 MH/s (63)
2018.04.30:23:54:48.868: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:48.918: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:51.610: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.614: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.629: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.645: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.653: GPU4 GPU4 search error: unspecified launch failure
2018.04.30:23:54:51.653: GPU5 GPU5 search error: unspecified launch failure
2018.04.30:23:54:51.653: GPU3 GPU3 search error: unspecified launch failure
2018.04.30:23:54:51.653: GPU1 GPU1 search error: unspecified launch failure
2018.04.30:23:54:51.676: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.676: GPU2 GPU2 search error: unspecified launch failure
2018.04.30:23:54:51.692: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.692: GPU6 GPU6 search error: unspecified launch failure
2018.04.30:23:54:51.912: main GPU1: 45C 47%, GPU2: 47C 48%, GPU3: 45C 48%, GPU4: 43C 46%, GPU5: 51C 51%, GPU6: 44C 47%
2018.04.30:23:54:52.316: wdog Thread(s) not responding. Restarting.
2018.04.30:23:54:53.533: main Eth speed: 192.452 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:53.533: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.079 MH/s (60) 5: 32.074 MH/s (46) 6: 32.068 MH/s (63)

I use PM 2.9e with the following params

set miner_params=-nvidia -cdm 2 -cdmport 3333 -cdmpass 123 -minRigSpeed 188 -rmode 2 -tstop 65 -tstart 40 -logsmaxsize 0

Rig configuration in my footer.

[DireWolfM14]

hashrate with gtx 1070 ?

These are my stable settings:
Driver: 391.01
Using MSI Afterburner set as:
  Core Voltage (%): 0
  Power Limit (%): 55
  Temp Limit (%): 83 (linked with Power Limit)
  Core Clock (MHz): -200
  Memory Clock (MHz): 635

Is your core clock set to negative 200 mhz?  I'm getting similar hash rates with my MSI GTX 1070s, (just two for the time being.)  Here are my afterburner settings:

Core Voltage: 0%
Power: 65%
Temp: 67 degrees Centigrade (linked with power)
Core Clock: +99
Mem Clock: +650

[j2james]

Core Clock: +99

You do not need to overclock core clock for ETH. Use +0.

[anbe2305]

Core clock should be use to lower the load on memmory but should never get over +150, and this also lower the power to get the card running between 80 and 100 watts with reduced power limit between 50 and 60%

Here you have a good guide how to overclock  nvidia cards https://mining.help/nvidia-ethereum-mining/

[_Art_]

It is difficult to run the miner on the system)))

https://www.virustotal.com/#/file/a531b7b0bb925173d3ea2976b72f3d280f64751bdb094d5bb980553dfa85fb07/detection

[anbe2305]

You dont need any antivirus  on the system if your running miner.This miner is 100% clean and is the fastest miner you can get with its lowest fee.

[nitrobg]

It is difficult to run the miner on the system)))

https://www.virustotal.com/#/file/a531b7b0bb925173d3ea2976b72f3d280f64751bdb094d5bb980553dfa85fb07/detection

Oh no!
Name me one miner that is not flagged as a virus.

[anbe2305]

Miner must be agressive if you want to get the the benefit from mining..

[Kgonla]

I think the "Every 5 seconds" shown speed or the average 5 min. are wrong.
With my 2 x RX580 & -clKernel 0
I have been looking carefully for some 15 min. periods, at the screen I see:

70 % of time 64+ MH/s (rarely up to 65)
15 % 62 MH/s
15 % 58.1-58.2

The average 5 min. shown is 57.9 to 58 after 15 min., lowest than the lowest 5 seconds speed.
Also the average goes lower within time while the 5 sec. are the same.
I think the same happens with Kernel 1 but differences are small & it is harder to know for sure, I have not tested it carefully yet.

Looks like the 5 min. average is metering the lowest H/s or I don't know what.

More:

I checked it again this time for more than 30 min.

The lowest 5 sec. have never been below 58.15 (Most of time between 58.2+ & 64.7+) while the highest average 5 min. have never reached 58.1 MH/s (58.08 at most, usually below 58).
So, something is not OK.

[pinamalina]

hashrate with gtx 1070 ?

These are my stable settings:
Driver: 391.01
Using MSI Afterburner set as:
  Core Voltage (%): 0
  Power Limit (%): 55
  Temp Limit (%): 83 (linked with Power Limit)
  Core Clock (MHz): -200
  Memory Clock (MHz): 635

Is your core clock set to negative 200 mhz?  I'm getting similar hash rates with my MSI GTX 1070s, (just two for the time being.)  Here are my afterburner settings:

Core Voltage: 0%
Power: 65%
Temp: 67 degrees Centigrade (linked with power)
Core Clock: +99
Mem Clock: +650

Yes, I run my core clock as low as possible to preserve power, lower the overall GPU temperature. Ethash PoW is memory hard. High core clock has very little impact on hash rate. So no real gain increasing the core clock.

My new settings (stable for the last 24h) are:

  Core Voltage (%): +0
  Power Limit (%): 58
  Temp Limit (%): 83 (linked with Power Limit)
  Core Clock (MHz): -200 (minus two hundred)
  Memory Clock (MHz): +685

With PhoenixMiner stats are:
Hash:
1: 32.114 MH/s (4419) 2: 32.113 MH/s (4435) 3: 32.098 MH/s (4351) 4: 32.116 MH/s (4478/3)
6: 32.128 MH/s (4469) 7: 32.119 MH/s (4390) 12: 32.120 MH/s (4489)

Temperature:
GPU1: 58C 38%, GPU2: 60C 41%, GPU3: 57C 36%, GPU4: 56C 35%, GPU6: 58C 39%, GPU7: 60C 41%, GPU12: 57C 36%, GPU13: 53C 0%

While running on the default configuration I would be getting around 26 MH/s while the GPU temperature would stabilise at 72oC.
By reducing the core/power limit both the GPU temperature and power usage is reduced.

In the above stats I have removed the RX580 figures as this reply is focusing on nvidia GTX 1070.
The above GPUs are all Gigabyte - GV-N1070WF2OC-8GD (GIGABYTE GTX 1070 8GB GDDR5)

[pinamalina]

One of my rigs stopped mining earlier today. Turned out it was Windows Defender that moved the PhoenixMiner.exe into the quarantine categorised as "Trojan:Win32/Tilken.B!cl"
Did restore the .exe and disabled Windows Defender. The threat in my opinion is Windows Defender, not the miner.

Windows Defender Details:
Trojan:Win32/Tilken.B!cl
Alert level: Severe
Status: Active
Date: 02/05/2018
Recommended action: Remove threat now.

Category: Trojan
Details: This program is dangerous and executes commands from an attacker.

Affected items:
file: C:\dev\Ethereum\PhoenixMiner_2.9e\PhoenixMiner.exe
process: pid:10100,ProcessStart:131683638871312779

[pinamalina]

Core clock should be use to lower the load on memmory but should never get over +150, and this also lower the power to get the card running between 80 and 100 watts with reduced power limit between 50 and 60%

Here you have a good guide how to overclock  nvidia cards https://mining.help/nvidia-ethereum-mining/

In my opinion the guide above (and other guides on the web) are 80% great but inaccurate at 20%. A great start for newcomers - it helped me to get the whole picture when I started to build first rig, but inaccurate at many aspects and details.
Advice: Proceed with caution.

Again: My personal opinion.

[Fabietto75QV]

when phoenix in hive os???

[human75]

One of my rigs stopped mining earlier today. Turned out it was Windows Defender that moved the PhoenixMiner.exe into the quarantine categorised as "Trojan:Win32/Tilken.B!cl"
Did restore the .exe and disabled Windows Defender. The threat in my opinion is Windows Defender, not the miner.

Windows Defender Details:
Trojan:Win32/Tilken.B!cl
Alert level: Severe
Status: Active
Date: 02/05/2018
Recommended action: Remove threat now.

Category: Trojan
Details: This program is dangerous and executes commands from an attacker.

Affected items:
file: C:\dev\Ethereum\PhoenixMiner_2.9e\PhoenixMiner.exe
process: pid:10100,ProcessStart:131683638871312779

You should not use any AV. included WD.

[janding]

One of my rigs stopped mining earlier today. Turned out it was Windows Defender that moved the PhoenixMiner.exe into the quarantine categorised as "Trojan:Win32/Tilken.B!cl"
Did restore the .exe and disabled Windows Defender. The threat in my opinion is Windows Defender, not the miner.

Windows Defender Details:
Trojan:Win32/Tilken.B!cl
Alert level: Severe
Status: Active
Date: 02/05/2018
Recommended action: Remove threat now.

Category: Trojan
Details: This program is dangerous and executes commands from an attacker.

Affected items:
file: C:\dev\Ethereum\PhoenixMiner_2.9e\PhoenixMiner.exe
process: pid:10100,ProcessStart:131683638871312779

You should not use any AV. included WD.

That's really bad advice.
Just configure your AV to exclude certain directories that your miners are located.

[UnclWish]

Who can say - why sometimes speed 1 of cards drops from 31M to 25M untill restarting miner?

[sidaliroy]

Who can say - why sometimes speed 1 of cards drops from 31M to 25M untill restarting miner?

Overclock reset. It happens sometimes don't know why though.

[Lunga Chung]

Who can say - why sometimes speed 1 of cards drops from 31M to 25M untill restarting miner?

Overclock reset. It happens sometimes don't know why though.

I have these hash drops also but it comes back in couple of minutes. Sometime OverdriveNtool loses OC setting for one card usually, just down OC

[roptix]

Hi,

I recently installed the PhoenixMiner 2.9e, moving from Claymore where I was mining ETH to now mine PIRL and am having some issues, hoping you all can help me resolve.  I get a CUDA error 377 out of memory error on the nVidia cards (1060 3 GB),  the AMD cards work fine.

Rig:

ASRosk HTC110 Mobo
3 AMD 570 gpus
8 nVidia 1060 3 GB GPUs
8 GB RAM
250 GB HD

nvidia driver 388.59 (I've tried an older 37X.xx version, did not help)
Virtual Memory - minimum set to 60,000, max set to 160,000.
Set to mine PIRL so that the DAG is not a problem

REM
REM Example bat file for starting PhoenixMiner.exe to mine ETH
REM PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
REM

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

REM IMPORTANT: Replace the ETH address with your own ETH wallet address in the -wal option (Rig001 is the name of the rig)
PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xac1CbCB36704BD0BE0A773cDAFE98c72a70707e2.CocoSpency -eres 0 -lidag 3
pause

This rig has been successfully with claymore on ETH for several months. Then MS pushed the update that 'killed' the 1060's 3GB from being able to mine ETH.  Switched to your miner and PIRL to keep using them.

Would welcome any thoughts, I can't seem to find any solutions online.