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

[karim_hassan777]

AMD released 19.7.4 driver... In evening I will try them...

EDIT: Thank heaven! In 19.7.4 AMD didn't touched OpenCL. Miner shows 19.7.3...

whait is the importance for that ?

[1713533099]

1713533099

[1713533099]

1713533099

[1713533099]

1713533099

[PhoenixMiner]

PhoenixMiner 4.5c is the new stable release. You can find the download link and other information in the first post of this thread. If you have already downloaded and installed it, there is no need to do this again - there is no change from 4.5c that was published as a beta version.

[Divinity666]

Why no timings for nvidia?((((

[jeca]

Hi, Phoenix!
For your miner to be perfect, all that remains is to implement the option to automatically increment tREF while maintaining clgreen. I don't know if it's possible, but I'm looking forward to it. Hugs!

[UnclWish]

AMD released 19.7.4 driver... In evening I will try them...

EDIT: Thank heaven! In 19.7.4 AMD didn't touched OpenCL. Miner shows 19.7.3...

whait is the importance for that ?

Importance is that we can update driver up to 19.7.4 and normal use Phoenix miner 4.5c.

[mariano_quilmes]

Hello, can I ask if I´m correct? When PM shows Shares: x/x/x, it is showing Shares: Accepted / Stale / Rejected?

Regards.

Mariano.

[YaStaer]

Hello, can I ask if I´m correct? When PM shows Shares: x/x/x, it is showing Shares: Accepted / Stale / Rejected?

Regards.

Mariano.

Yes

[anbe2305]

Mr. Phoenix...how can i set the new Phoenix 4.5c miner with Nvidia Inspector to run P0 mode, when im using it is reseting my settings made by nvidia inspector and lowers the core to -200 and memory to -1000 ( it stays in P0 mode) but the hashrate drops from 31 MHS to 24 MHS. Why is this version not working with nvidia inspector like the version 4.2c?

[ManDoneKTM]

i added -mt 1 and -mt 2 and i have the same result on the hashrate ... hmmm

[karim_hassan777]

Any progress with RX 5700 XT cards ?

[Mondos]

Phoenix 4.5c + 7x nVidia GTX 1080ti + 1x 1070ti + Windows 10, after few hours, or few minutes I see this error:

Code:

2019.08.02:12:44:36.932: main GPU1: 57C 69% 159W, GPU2: 54C 65% 160W, GPU3: 56C 68% 81W, GPU4: 48C 56% 160W, GPU5: 61C 74% 166W, GPU6: 57C 69% 158W, GPU7: 59C 72% 156W, GPU8: 58C 70% 161W
GPU1: cclock 1582 MHz, cvddc 775 mV, mclock 5737 MHz, p-state P0
GPU2: cclock 1582 MHz, cvddc 787 mV, mclock 5737 MHz, p-state P0
GPU3: cclock 1265 MHz, cvddc 712 mV, mclock 4463 MHz, p-state P0
GPU4: cclock 1607 MHz, cvddc 775 mV, mclock 5740 MHz, p-state P0
GPU5: cclock 1632 MHz, cvddc 725 mV, mclock 5737 MHz, p-state P0
GPU6: cclock 1569 MHz, cvddc 775 mV, mclock 5742 MHz, p-state P0
GPU7: cclock 1607 MHz, cvddc 762 mV, mclock 5740 MHz, p-state P0
GPU8: cclock 1607 MHz, cvddc 750 mV, mclock 5737 MHz, p-state P0
GPUs power: 1200.8 W
2019.08.02:12:44:39.385: main Eth speed: 397.244 MH/s, shares: 29/0/0, time: 0:07
2019.08.02:12:44:39.385: main GPUs: 1: 51.628 MH/s (3) 2: 51.900 MH/s (3) 3: 32.094 MH/s (1) 4: 52.577 MH/s (5) 5: 52.955 MH/s (6) 6: 51.677 MH/s (2) 7: 52.300 MH/s (3) 8: 52.114 MH/s (6)
2019.08.02:12:44:41.557: eths Eth: Received: {"jsonrpc":"2.0","method":"mining.notify","params":["00002d8a","a0275568be8c3f375891da2d277016f3449695d182f095c761d6d1e91a85a40b","270422a4e70bb25f969e3b0290cb04e468c82e9cfae1cdf0df04e8469d426d68",true],"id":null}
2019.08.02:12:44:41.557: eths Eth: New job #270422a4 from pps-etc-eu.adaminers.com:2222; diff: 4999MH
2019.08.02:12:44:41.638: GPU4 Eth: GPU4: ETH share found!
2019.08.02:12:44:41.638: eths Eth: Send: {"id":4,"method":"mining.submit","params": ["0xd3e37d13a40f5884177ef44aab7d45acecbfb4ce.1080ti","00002d8a","30083d8b6320"]}

2019.08.02:12:44:41.638: eths Eth: Share actual difficulty: 27.3 GH (!)
2019.08.02:12:44:41.751: eths Eth: Received: {"result":true,"error":null,"id":4}
2019.08.02:12:44:41.751: eths Eth: Share accepted in 113 ms
2019.08.02:12:44:44.477: main Eth speed: 397.237 MH/s, shares: 30/0/0, time: 0:07
2019.08.02:12:44:44.477: main GPUs: 1: 51.633 MH/s (3) 2: 51.891 MH/s (3) 3: 32.093 MH/s (1) 4: 52.578 MH/s (6) 5: 52.954 MH/s (6) 6: 51.677 MH/s (2) 7: 52.298 MH/s (3) 8: 52.114 MH/s (6)
2019.08.02:12:44:49.576: main Eth speed: 397.226 MH/s, shares: 30/0/0, time: 0:07
2019.08.02:12:44:49.576: main GPUs: 1: 51.629 MH/s (3) 2: 51.901 MH/s (3) 3: 32.093 MH/s (1) 4: 52.578 MH/s (6) 5: 52.938 MH/s (6) 6: 51.677 MH/s (2) 7: 52.298 MH/s (3) 8: 52.112 MH/s (6)
2019.08.02:12:44:51.686: eths Eth: Received: {"jsonrpc":"2.0","method":"mining.notify","params":["00002d8b","a0275568be8c3f375891da2d277016f3449695d182f095c761d6d1e91a85a40b","655b99a27173145991dd9b8973237f1702ade83a429021112b9c72e3d9ab3254",true],"id":null}
2019.08.02:12:44:51.686: eths Eth: New job #655b99a2 from pps-etc-eu.adaminers.com:2222; diff: 4999MH
2019.08.02:12:44:53.838: GPU5 Eth: GPU5: ETH share found!
2019.08.02:12:44:53.838: eths Eth: Send: {"id":4,"method":"mining.submit","params": ["0xd3e37d13a40f5884177ef44aab7d45acecbfb4ce.1080ti","00002d8b","400881f2c67b"]}

2019.08.02:12:44:53.838: eths Eth: Share actual difficulty: 20.6 GH (!)
2019.08.02:12:44:53.951: eths Eth: Received: {"result":true,"error":null,"id":4}
2019.08.02:12:44:53.951: eths Eth: Share accepted in 113 ms
2019.08.02:12:44:54.702: main Eth speed: 397.217 MH/s, shares: 31/0/0, time: 0:07
2019.08.02:12:44:54.702: main GPUs: 1: 51.624 MH/s (3) 2: 51.926 MH/s (3) 3: 32.093 MH/s (1) 4: 52.574 MH/s (6) 5: 52.912 MH/s (7) 6: 51.676 MH/s (2) 7: 52.301 MH/s (3) 8: 52.113 MH/s (6)
2019.08.02:12:44:59.821: main Eth speed: 397.239 MH/s, shares: 31/0/0, time: 0:08
2019.08.02:12:44:59.821: main GPUs: 1: 51.622 MH/s (3) 2: 51.956 MH/s (3) 3: 32.093 MH/s (1) 4: 52.571 MH/s (6) 5: 52.908 MH/s (7) 6: 51.676 MH/s (2) 7: 52.302 MH/s (3) 8: 52.110 MH/s (6)
2019.08.02:12:45:02.043: GPU7 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.071: GPU2 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.071: GPU4 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.071: GPU5 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.102: GPU3 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.102: GPU1 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.110: GPU7 GPU7 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU1 GPU1 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU3 GPU3 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU5 GPU5 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU2 GPU2 search error: unspecified launch failure
2019.08.02:12:45:02.110: GPU4 GPU4 search error: unspecified launch failure
2019.08.02:12:45:02.118: GPU6 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.118: GPU6 GPU6 search error: unspecified launch failure
2019.08.02:12:45:02.149: GPU8 CUDA error in CudaProgram.cu:456 : unspecified launch failure (719)
2019.08.02:12:45:02.149: GPU8 GPU8 search error: unspecified launch failure
2019.08.02:12:45:02.945: wdog Thread(s) not responding. Restarting.

 ---------- OR -------------

Code:

2019.08.02:12:34:26.269: GPU7 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.269: GPU7 GPU7 initMiner error: unspecified launch failure
2019.08.02:12:34:26.273: GPU1 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.273: GPU1 GPU1 initMiner error: unspecified launch failure
2019.08.02:12:34:26.278: GPU6 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.278: GPU6 GPU6 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU8 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU4 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU8 GPU8 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU4 GPU4 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU2 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU5 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.311: GPU2 GPU2 initMiner error: unspecified launch failure
2019.08.02:12:34:26.311: GPU5 GPU5 initMiner error: unspecified launch failure
2019.08.02:12:34:26.315: GPU3 CUDART error in CudaProgram.cu:265 : unspecified launch failure (4)
2019.08.02:12:34:26.315: GPU3 GPU3 initMiner error: unspecified launch failure
2019.08.02:12:34:26.950: wdog Thread(s) not responding. Restarting.

[karim_hassan777]

Any progress with RX 5700 XT ?

[Batmaxpt]

any alternative like straps to have a little more hash ?

[PhoenixMiner]

PhoenixMiner 4.5c supports the latest AMD Windows drivers 19.7.5 (although you will see them detected as 19.7.3 in the miner's console).

Why no timings for nvidia?((((

any alternative like straps to have a little more hash ?

   We are working on this and it may appear in the next release but it's not 100% certain for now. There are some stability problems we need to work out first.

Hi, Phoenix!
For your miner to be perfect, all that remains is to implement the option to automatically increment tREF while maintaining clgreen. I don't know if it's possible, but I'm looking forward to it. Hugs!

   We are exploring the option to include AMD custom memory timing settings but so far we lean to the view that AMD Memory Tweak tool is enough for advanced users.

Mr. Phoenix...how can i set the new Phoenix 4.5c miner with Nvidia Inspector to run P0 mode, when im using it is reseting my settings made by nvidia inspector and lowers the core to -200 and memory to -1000 ( it stays in P0 mode) but the hashrate drops from 31 MHS to 24 MHS. Why is this version not working with nvidia inspector like the version 4.2c?

  PhoenixMiner 4.5 will apply your -cclock and -mclock settings to Nvidia GPUs while the previous versions were able to overclock/underclock only AMD cards. Most probably you have a mixed righ with Nvidia and AMD cards and the clocks you set are now applied to both types of cards. You need to set the frequencies for each card individually. For example, if the first three cards are AMD RX570, and the next three cards are Nvidia, you can use the following options: -cclock 1100,1100,1100,0,0,0 -mclock 2000,2000,2000,+500,+500,+500  This will set the AMD core clocks to 1100 MHz, AMD memory clocks to 2000 MHz, will leave the Nvidia core clocks to their default values (0 means leave the default for this card), and will increase the Nvidia memory clicks by 500 MHz from the defaults. Obviously, you need to change this line with your own values, and rearrange them depending on order and types of the cards in your rig.

i added -mt 1 and -mt 2 and i have the same result on the hashrate ... hmmm

   This work only with relatively new drivers (i.e. 19.x.x). Also, even when working properly -mt 2 and -mt 1 are likely slower than the modded VBIOS memory timings if your card is modded.

Any progress with RX 5700 XT cards ?

   No, the drivers still haven't fixed the TLB limitation, even with the latest 19.7.5 release.

Phoenix 4.5c + 7x nVidia GTX 1080ti + 1x 1070ti + Windows 10, after few hours, or few minutes I see this error:
....

  In both cases GPU7 seems to be the first to fail, so check if the problem remains if you lower its memory clocks a little.

[inv1s1bl3]

Hi all,

I have tried using the commands to setup my min fan speed, but it does not seem to work, as they are working at 22-25%. Since it's summer, i'd like to keep the cards a bit colder and would like to boost the fan speed up to around 40-45% depending on how noisy they'd get.

I do not use any other 3rd party enhancers to control or setup the parameters on the GPUs other than the miner itself.

Should I setup the fan speed from the WATTMAN setting or am I doing something wrong here?

[Elange]

Hi.

Just curious. Why does every version of PhoenixMiner has limitation on DAG size? Like, when Ethereum moves to some new epoch, I need to upgrade miner in order to keep using it.

[dipepmining]

What is a good way to calculate how much is actually getting taken in fees using Phoenix Miner.

I was thinking just ignore the "every 90 minute, mines for 35 seconds" aspect. That is just Phoenix Miner telling us how they obtain the 0.65%.

Then just do the following math:

I mined 1 ETH in x amount of days running Phoenix Miner steadily... Now just subtract whatever 0.65% of 1 ETH is from 1 ETH.

Sorry to sound so dumb, but if someone can tell me how to do some math on this that would be great.

[anbe2305]

Mr. Phoenix thnx for answering me about my problem with NVIDIA setup, mixed rig AMD and Nvidia...it worked...

[jetwalsh]

Is there a -minspeed option in the PhoenixMiner to set a minimum mining speed before the miner automatically reboots? One my cards dropped out and lowered my hash rate with no user notification or automatic miner/system action taken to fix it.

[UselessGuru]

Code:

PhoenixMiner.exe -coin bci -mport -4000 -pool progpow.mine.zergpool.com:3200 -wal ********************************* -pass **********,c=BTC -gt 0 -mi 14 -nvidia -log 0 -wdog 0 -mclock 0 -gpus 1
Phoenix Miner 4.5c Windows/msvc - Release build
-----------------------------------------------

CUDA version: 10.0, CUDA runtime: 8.0
Available GPUs for mining:
GPU1: GeForce GTX 1080 Ti (pcie 1), CUDA cap. 6.1, 11 GB VRAM, 28 CUs
Nvidia driver version: 430.86
PP: the pool list contains 1 pool (1 from command-line)
PP: primary pool: progpow.mine.zergpool.com:3200
Starting GPU mining
PP: Connecting to progpow pool progpow.mine.zergpool.com:3200 (proto: Stratum)
Listening for CDM remote manager at port 4000 in read-only mode
GPU1: 41C 22% 18W
GPUs power: 17.6 W
PP: Connected to progpow pool progpow.mine.zergpool.com:3200 (103.249.70.7)
PP: Subscribed to progpow pool
PP: Worker 1GPSq8txFnyrYdXL8t6S94mYdF8cGqVQJF authorized
PP: New job #46d1b0c3 from progpow.mine.zergpool.com:3200; diff: 188MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #17
Light cache generated in 0.7 s (26.9 MB/s)
GPU1: ProgPOW seed set to 17

And then the miner falls back to the command prompt without any other action.

Mining with AMD works like charm.
What am I missing?

NVIDIA drivers are version 430.86, GPUs are any of GTX1060 6GB or 1080Ti