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

[dragonmike]

Are 5700 performing the same as 5700XT's on EThash?
What max hashrates can be achieved reliably now? I saw people managed 60 MH/s but got a lot of invalid shares...

That 60mh is not really 60mh, since card can't handle that much at this moment, and yes 5700 and 5700xt do same amount on ethash from 51 to 54mh depending of clock of memory.

Thanks... Does the XT bios add voltage to the memory, like the Vega 64 does compared to the 56 bios? That would give it quite an edge in memory intensive algos accordingly...

[cikusa]

Are 5700 performing the same as 5700XT's on EThash?
What max hashrates can be achieved reliably now? I saw people managed 60 MH/s but got a lot of invalid shares...

That 60mh is not really 60mh, since card can't handle that much at this moment, and yes 5700 and 5700xt do same amount on ethash from 51 to 54mh depending of clock of memory.

Thanks... Does the XT bios add voltage to the memory, like the Vega 64 does compared to the 56 bios? That would give it quite an edge in memory intensive algos accordingly...

As far i know i think mem voltage is same 0.85v

[Binary100100]

I've installed 19.9.3 drivers and switched back to PM 4.7b from claymore's miner, now mixed rig is working flawlessly, thank you @PhoenixMiner. BTW claymore's miner consumed 10 watts less and hashrate was just 0.8 MH/s lower for RX 5700.

Any significant improvements?

For me PM always was better, but previous version was unstable with 19.9.1 drivers and with 19.9.2 didn't work at all. Now it looks like stability problem solved, however i see one reboot during last night. Also i've noticed that 5700 card after some time begins to give +2 Mh/s, but after dag switching this speedup is gone and again after some time miner shows +2Mh/s until dag switch.

I updated everything shortly after posting to see for myself. I figured that I could always revert back.
I can say that it seems less stable in my experience.
I didn't have any reboots (maybe one every three days or so) but since the updates my miner crashed slightly more than usual. Crashes (not reboots) at 11:53pm, 1:57am, 6:26am and at 9:10am.
No reboots yet. I can't explain the crashes, I didn't do anything but install the updates. I'm considering on rolling back the drivers.

[MATHReX]

AMD released 19.10.1 drivers. Anyone tried allready? Miner support them?

Working with 19.10.1 drivers.
Vega 56 @ 1110 mhz memory, @1050 mhz core 900mv
42.3 MH/s

[Quake4]

Reject all progpow shares on rx584 at zergpool. (rx562 work fine)

Code:

2019.10.09:09:34:19.318: main Phoenix Miner 4.7b Windows/msvc - Release build
2019.10.09:09:34:19.318: main Cmd line: -pool stratum+tcp://progpow.mine.zergpool.com:3200 -wal xxx -pass c=BTC,Work -wdog 0 -proto 1 -cdmport 3350 -amd -eres 1 -log 1 -gsi 30 -coin bci
2019.10.09:09:34:21.246: main Available GPUs for mining:
2019.10.09:09:34:21.246: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 36 CUs
2019.10.09:09:34:21.247: main ADL library initialized
2019.10.09:09:34:22.145: main PP: the pool list contains 1 pool (1 from command-line)
2019.10.09:09:34:22.145: main PP: primary pool: progpow.mine.zergpool.com:3200
2019.10.09:09:34:22.145: main Starting GPU mining
2019.10.09:09:34:22.145: main Matched GPU1 to ADL adapter index 0 (method 1)
2019.10.09:09:34:22.162: main GPU1: Created ADL monitor for adapter 0; overdrive version: 7 (7)
2019.10.09:09:34:22.163: main GPU1: using AMD driver ver 19.5.2
2019.10.09:09:34:22.268: main PP: Connecting to progpow pool progpow.mine.zergpool.com:3200 (proto: Stratum)
2019.10.09:09:34:22.268: main GPU1: 55C 50% 5W
GPUs power: 5.0 W
2019.10.09:09:34:22.379: eths PP: Connected to progpow pool progpow.mine.zergpool.com:3200 (103.249.70.7)
2019.10.09:09:34:22.380: eths PP: Send: {"id":1,"method":"mining.subscribe","params":[]}

2019.10.09:09:34:22.470: main Listening for CDM remote manager at port 3350 in read-only mode
2019.10.09:09:34:22.477: eths PP: Received: {"id":1,"result":[null,"a20640b90000565b"],"error":null}
2019.10.09:09:34:22.478: eths PP: Subscribed to progpow pool
2019.10.09:09:34:22.478: eths PP: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["xxx","c=BTC,Work"]}

2019.10.09:09:34:22.572: eths PP: Received: {"id":null,"method":"mining.set_target","params":["00000016c16aaaaaaaab00000000000000000000000000000000000000000000"]}
2019.10.09:09:34:22.865: eths PP: Received: {"id":2,"result":false,"error":[20,"Not supported.",null]}
2019.10.09:09:34:22.865: eths PP: Received: {"id":3,"result":true,"error":null}
2019.10.09:09:34:22.865: eths PP: Worker xxx authorized
2019.10.09:09:34:22.865: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d0c1","a3007f2775f93f56b2eed1d8ee122c9a77ede95ebfbffba2927fd87bba9acdbe","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.10.09:09:34:22.865: eths PP: New job #a3007f27 from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:09:34:22.866: GPU1 GPU1: Starting up... (0)
2019.10.09:09:34:22.866: GPU1 GPU1: Generating ethash light cache for epoch #21
2019.10.09:09:34:23.961: GPU1 Light cache generated in 1.1 s (17.0 MB/s)
2019.10.09:09:34:24.247: GPU1 GPU1: ProgPOW seed set to 21
2019.10.09:09:34:24.987: GPU1 GPU1: Allocating DAG for epoch #21 (1.16) GB
2019.10.09:09:34:24.989: GPU1 GPU1: Generating DAG for epoch #21
2019.10.09:09:34:26.534: GPU1 GPU1: DAG  47%
2019.10.09:09:34:28.036: GPU1 GPU1: DAG  93%
2019.10.09:09:34:28.258: GPU1 GPU1: DAG generated in 3.3 s (364.6 MB/s)
2019.10.09:09:34:42.380: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x81b629","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:34:47.217: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d0c2","cf748592706a4ad4741b3541e084e85b3165e3491d941d2003b7a2a993e27aab","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",true]}
2019.10.09:09:34:47.218: eths PP: New job #cf748592 from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:09:34:50.289: main GPU1: 66C 72% 125W
GPUs power: 124.9 W
2019.10.09:09:34:52.289: main PP speed: 8.475 MH/s, shares: 0/0/0, time: 0:00
2019.10.09:09:35:00.865: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:35:02.382: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x81750c","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:35:07.299: main  
2019.10.09:09:35:07.299: main *** 0:00 *** 10/9 09:35 **************************************
2019.10.09:09:35:07.299: main PP: Mining BCI on progpow.mine.zergpool.com:3200 for 0:00
2019.10.09:09:35:07.299: main PP: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.10.09:09:35:07.299: main PP: Incorrect shares 1 (100.00%), est. stales percentage 0.00%
2019.10.09:09:35:07.299: main PP: Average speed (5 min): 8.482 MH/s
2019.10.09:09:35:07.299: main  
2019.10.09:09:35:18.512: main GPU1: 67C 74% 125W
GPUs power: 125.0 W
2019.10.09:09:35:22.314: main PP speed: 8.347 MH/s, shares: 0/0/1, time: 0:01
2019.10.09:09:35:22.383: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x80dccc","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:35:24.536: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:35:42.254: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d0c3","3bb67cfe3a4f4344dde030d2450ae5f7ca078e2330b2db5694c0bbbbca0f78cb","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.10.09:09:35:42.254: eths PP: New job #3bb67cfe from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:09:35:42.384: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x815f8a","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:35:46.504: main GPU1: 70C 80% 135W
GPUs power: 134.8 W
2019.10.09:09:35:47.360: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:35:52.308: main  
2019.10.09:09:35:52.308: main *** 0:01 *** 10/9 09:35 **************************************
2019.10.09:09:35:52.308: main PP: Mining BCI on progpow.mine.zergpool.com:3200 for 0:01
2019.10.09:09:35:52.308: main PP: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.10.09:09:35:52.308: main PP: Incorrect shares 3 (100.00%), est. stales percentage 0.00%
2019.10.09:09:35:52.308: main PP: Average speed (5 min): 8.496 MH/s
2019.10.09:09:35:52.308: main PP: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.10.09:09:35:52.308: main  
2019.10.09:09:35:52.508: main PP speed: 8.628 MH/s, shares: 0/0/3, time: 0:01
2019.10.09:09:35:56.058: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:36:02.385: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x81dc1c","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:36:14.526: main GPU1: 71C 84% 135W
GPUs power: 134.8 W
2019.10.09:09:36:19.552: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:36:22.386: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x821ff2","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:36:22.531: main PP speed: 8.600 MH/s, shares: 0/0/5, time: 0:02
2019.10.09:09:36:37.288: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d0c4","5332d1e8c11bc6a87595c92116be040576af2b198479bb1402e3c5f1feffaf4f","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.10.09:09:36:37.288: eths PP: New job #5332d1e8 from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:09:36:37.484: main  
2019.10.09:09:36:37.484: main *** 0:02 *** 10/9 09:36 **************************************
2019.10.09:09:36:37.485: main PP: Mining BCI on progpow.mine.zergpool.com:3200 for 0:02
2019.10.09:09:36:37.485: main PP: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.10.09:09:36:37.485: main PP: Incorrect shares 5 (100.00%), est. stales percentage 0.00%
2019.10.09:09:36:37.485: main PP: Average speed (5 min): 8.537 MH/s
2019.10.09:09:36:37.485: main PP: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.10.09:09:36:37.485: main  
2019.10.09:09:36:42.387: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x824df5","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:36:42.689: main GPU1: 71C 88% 134W
GPUs power: 134.0 W
2019.10.09:09:36:46.275: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:36:52.694: main PP speed: 8.607 MH/s, shares: 0/0/6, time: 0:02
2019.10.09:09:36:55.148: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:37:02.388: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x827025","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:37:08.603: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:37:10.714: main GPU1: 71C 88% 135W
GPUs power: 134.6 W
2019.10.09:09:37:22.389: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x82922d","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:37:22.522: main  
2019.10.09:09:37:22.522: main *** 0:03 *** 10/9 09:37 **************************************
2019.10.09:09:37:22.522: main PP: Mining BCI on progpow.mine.zergpool.com:3200 for 0:03
2019.10.09:09:37:22.522: main PP: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.10.09:09:37:22.522: main PP: Incorrect shares 8 (100.00%), est. stales percentage 0.00%
2019.10.09:09:37:22.522: main PP: Average speed (5 min): 8.557 MH/s
2019.10.09:09:37:22.522: main PP: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.10.09:09:37:22.522: main  
2019.10.09:09:37:22.722: main PP speed: 8.636 MH/s, shares: 0/0/8, time: 0:03
2019.10.09:09:37:32.317: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d0c5","6657af8ef5a2c827d8d3c2594dabadfe1bd329ffc06885a46bae046af7cc50e4","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.10.09:09:37:32.317: eths PP: New job #6657af8e from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:09:37:38.768: main GPU1: 72C 88% 134W
GPUs power: 134.5 W
2019.10.09:09:37:42.390: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x82a576","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:37:50.119: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:37:52.776: main PP speed: 8.645 MH/s, shares: 0/0/9, time: 0:03
2019.10.09:09:38:02.391: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x82be0d","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:38:06.987: main GPU1: 72C 88% 134W
GPUs power: 134.4 W
2019.10.09:09:38:07.587: main  
2019.10.09:09:38:07.587: main *** 0:03 *** 10/9 09:38 **************************************
2019.10.09:09:38:07.587: main PP: Mining BCI on progpow.mine.zergpool.com:3200 for 0:03
2019.10.09:09:38:07.587: main PP: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.10.09:09:38:07.587: main PP: Incorrect shares 9 (100.00%), est. stales percentage 0.00%
2019.10.09:09:38:07.587: main PP: Average speed (5 min): 8.569 MH/s
2019.10.09:09:38:07.587: main PP: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.10.09:09:38:07.587: main  
2019.10.09:09:38:22.392: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x82c7b5","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:38:23.174: main PP speed: 8.596 MH/s, shares: 0/0/9, time: 0:04
2019.10.09:09:38:27.346: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d0c6","916f238eea43ad00181a20eba6116778c332176211a318cd0c712db393337b0a","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.10.09:09:38:27.346: eths PP: New job #916f238e from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:09:38:32.452: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:38:34.980: main GPU1: 72C 88% 134W
GPUs power: 133.9 W
2019.10.09:09:38:36.274: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:38:42.393: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x82daa9","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:38:52.595: main  
2019.10.09:09:38:52.595: main *** 0:04 *** 10/9 09:38 **************************************
2019.10.09:09:38:52.595: main PP: Mining BCI on progpow.mine.zergpool.com:3200 for 0:04
2019.10.09:09:38:52.595: main PP: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.10.09:09:38:52.595: main PP: Incorrect shares 11 (100.00%), est. stales percentage 0.00%
2019.10.09:09:38:52.595: main PP: Average speed (5 min): 8.576 MH/s
2019.10.09:09:38:52.595: main PP: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
2019.10.09:09:38:52.595: main  
2019.10.09:09:38:53.195: main PP speed: 8.597 MH/s, shares: 0/0/11, time: 0:04
2019.10.09:09:39:02.394: eths PP: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x82e0f9","0x96e6e3d2983ff9a90b67bf2f1ed2a41c75f6ddeab627711b66ee335b9b44dda4"]}

2019.10.09:09:39:02.999: main GPU1: 72C 88% 134W
GPUs power: 133.8 W
2019.10.09:09:39:10.285: GPU1 PP: Incorrect ETH share from GPU1
2019.10.09:09:39:13.604: unkn Quitting...
2019.10.09:09:39:14.154: main Exit code: 0

Exit on run at 1080ti

Code:

2019.10.09:22:48:10.135: main Phoenix Miner 4.7b Windows/msvc - Release build
2019.10.09:22:48:10.135: main Cmd line: -pool stratum+tcp://progpow.mine.zergpool.com:3200 -wal xxx -pass c=BTC,Test -wdog 0 -proto 1 -cdmport 3360 -nvidia -eres 1 -log 1 -nvdo 1 -coin bci
2019.10.09:22:48:10.449: main CUDA version: 10.0, CUDA runtime: 8.0
2019.10.09:22:48:10.450: main Available GPUs for mining:
2019.10.09:22:48:10.450: main GPU1: GeForce GTX 1080 Ti (pcie 1), CUDA cap. 6.1, 11 GB VRAM, 28 CUs
2019.10.09:22:48:10.459: main NVML library initialized
2019.10.09:22:48:10.481: main Nvidia driver version: 430.86
2019.10.09:22:48:11.311: main PP: the pool list contains 1 pool (1 from command-line)
2019.10.09:22:48:11.311: main PP: primary pool: progpow.mine.zergpool.com:3200
2019.10.09:22:48:11.311: main Starting GPU mining
2019.10.09:22:48:11.439: main PP: Connecting to progpow pool progpow.mine.zergpool.com:3200 (proto: Stratum)
2019.10.09:22:48:11.477: main GPU1: 49C 40% 15W
GPUs power: 15.1 W
2019.10.09:22:48:11.568: eths PP: Connected to progpow pool progpow.mine.zergpool.com:3200 (103.249.70.7)
2019.10.09:22:48:11.568: eths PP: Send: {"id":1,"method":"mining.subscribe","params":[]}

2019.10.09:22:48:11.650: eths PP: Received: {"id":1,"result":[null,"971cc93a0000580d"],"error":null}
2019.10.09:22:48:11.650: eths PP: Subscribed to progpow pool
2019.10.09:22:48:11.650: eths PP: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["xxx","c=BTC,Test"]}

2019.10.09:22:48:11.687: main Listening for CDM remote manager at port 3360 in read-only mode
2019.10.09:22:48:11.733: eths PP: Received: {"id":null,"method":"mining.set_target","params":["00000016c16aaaaaaaab00000000000000000000000000000000000000000000"]}
2019.10.09:22:48:11.860: eths PP: Received: {"id":2,"result":false,"error":[20,"Not supported.",null]}
2019.10.09:22:48:11.860: eths PP: Received: {"id":3,"result":true,"error":null}
2019.10.09:22:48:11.860: eths PP: Worker xxx authorized
2019.10.09:22:48:11.860: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d448","10ed67b950fce7f575c56a41a5ce342e593f7dc3e9b6eea8f1b25aa52ddb6b4b","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",true]}
2019.10.09:22:48:11.860: eths PP: New job #10ed67b9 from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:22:48:11.861: GPU1 GPU1: Starting up... (0)
2019.10.09:22:48:11.861: GPU1 GPU1: Generating ethash light cache for epoch #21
2019.10.09:22:48:12.642: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d449","6d200f0af681ae6b57e816fc57f2f3071e44cbb6e8dc98567bc6730e1fc6a49a","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.10.09:22:48:12.644: eths PP: New job #6d200f0a from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:22:48:14.323: GPU1 Light cache generated in 2.5 s (7.6 MB/s)
2019.10.09:22:48:14.794: GPU1 GPU1: ProgPOW seed set to 21

Code:

2019.10.09:22:48:35.400: main Phoenix Miner 4.7b Windows/msvc - Release build
2019.10.09:22:48:35.400: main Cmd line: -pool stratum+tcp://progpow.mine.zergpool.com:3200 -wal xxx -pass c=BTC,Test -wdog 0 -proto 1 -cdmport 3360 -nvidia -eres 0 -log 1 -coin bci
2019.10.09:22:48:35.715: main CUDA version: 10.0, CUDA runtime: 8.0
2019.10.09:22:48:35.716: main Available GPUs for mining:
2019.10.09:22:48:35.716: main GPU1: GeForce GTX 1080 Ti (pcie 1), CUDA cap. 6.1, 11 GB VRAM, 28 CUs
2019.10.09:22:48:35.725: main NVML library initialized
2019.10.09:22:48:35.746: main Nvidia driver version: 430.86
2019.10.09:22:48:36.577: main PP: the pool list contains 1 pool (1 from command-line)
2019.10.09:22:48:36.577: main PP: primary pool: progpow.mine.zergpool.com:3200
2019.10.09:22:48:36.577: main Starting GPU mining
2019.10.09:22:48:36.712: main PP: Connecting to progpow pool progpow.mine.zergpool.com:3200 (proto: Stratum)
2019.10.09:22:48:36.719: main GPU1: 48C 35% 15W
GPUs power: 14.6 W
2019.10.09:22:48:36.812: eths PP: Connected to progpow pool progpow.mine.zergpool.com:3200 (103.249.70.7)
2019.10.09:22:48:36.814: eths PP: Send: {"id":1,"method":"mining.subscribe","params":[]}

2019.10.09:22:48:36.906: eths PP: Received: {"id":1,"result":[null,"aa76240e0000580e"],"error":null}
2019.10.09:22:48:36.908: eths PP: Subscribed to progpow pool
2019.10.09:22:48:36.909: eths PP: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["xxx","c=BTC,Test"]}

2019.10.09:22:48:36.937: main Listening for CDM remote manager at port 3360 in read-only mode
2019.10.09:22:48:37.028: eths PP: Received: {"id":null,"method":"mining.set_target","params":["00000016c16aaaaaaaab00000000000000000000000000000000000000000000"]}
2019.10.09:22:48:37.140: eths PP: Received: {"id":2,"result":false,"error":[20,"Not supported.",null]}
2019.10.09:22:48:37.140: eths PP: Received: {"id":3,"result":true,"error":null}
2019.10.09:22:48:37.140: eths PP: Worker xxx authorized
2019.10.09:22:48:37.140: eths PP: Received: {"id":null,"method":"mining.notify","params":["000000000000000000000000000000000000000000000000000000000000d449","6d200f0af681ae6b57e816fc57f2f3071e44cbb6e8dc98567bc6730e1fc6a49a","cdf42a47e552f9b4eb01d44a7b6a2b057fbfa1070f3148fd8e7f937a417ffdc1","00000016c16aaaaaaaab00000000000000000000000000000000000000000000",false]}
2019.10.09:22:48:37.140: eths PP: New job #6d200f0a from progpow.mine.zergpool.com:3200; diff: 188MH
2019.10.09:22:48:37.141: GPU1 GPU1: Starting up... (0)
2019.10.09:22:48:37.141: GPU1 GPU1: Generating ethash light cache for epoch #21
2019.10.09:22:48:39.659: GPU1 Light cache generated in 2.5 s (7.4 MB/s)
2019.10.09:22:48:40.294: GPU1 GPU1: ProgPOW seed set to 21

[PhoenixMiner]

PhoenixMiner 4.7c is the new stable varsion (see the first post for details). You can download PhoenixMiner 4.7c from here:

(MEGA links are no longer active)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

   File: PhoenixMiner_4.7c_Windows.zip
    ===================================
   SHA-1: 444b9bca05692f51cfaf8100c91a2bd6adbb5055
 SHA-256: 9a4bd6eba5614f754d5ec5ae78558c4928b502136dccf47702f3df54c0027883
 SHA-512: 4bdfedd21d09b8e59cc91a09661fb47ff2ed6b01ad0128185900d427bf96e7035d64d363ca9e11fe70371622f912af96b2f1b253e12f7d2dad4f6163d2caec4f

    File: PhoenixMiner_4.7c_Linux.tar.gz
    ====================================
   SHA-1: 56ab80ae3ce1843ba842e837f10d3e0f894539ff
 SHA-256: 184e31bf92cd84a5062fa60cf2d2a7db17433681df7d60500f3b70189a79f38d
 SHA-512: 04521956dbdccd3dedf8e7d27b0fde0d59bfc92222d8063bced0ac5b67d6c858f3343637f8e45fa3bb483910e3f49cf2fad00c775d5a7923e3519e76b8ac93cf

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The changes since the 4.7b beta version are another small change in Navi kernels and other small improvements.

Changes in version 4.7c (since 4.6c):

• New kernels for Navi (RX5700) with better stability. Should solve the freezing and restarts that some miners are experiencing with Navi cards
• Reduced VRAM usage for both AMD and Nvidia cards on Windows and Linux
• Added command-line option -config to load a config.txt file. This allows combining command-line options and config.txt file.
• Added support for mining QuarkChain (QKC) without DAG switching on devfee (use -coin qkc)
• Added support for the latest AMD Windows drivers up to 19.10.1
• Other small improvements and fixes.

When using the new -config option, please note the following:

• The order of the options is important. For example, if we have a config.txt file that contains -cclock 1000 and we specify command line -cclock 1100 -config config.txt, the option from the config.txt file will take precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100) then the second option takes precedence and the resulting -cclock will be 1100.
• Only one -config option is allowed
• If you reload the config file with 'c' key or with the remote interface, its options will take precedence over whatever you have specified in the command-line.

[PhoenixMiner]

Reject all progpow shares on rx584 at zergpool. (rx562 work fine)
...

  We tested with similar card (RX580 4 GB) on the same pool without any problems. 100% incorrect shares usually indicate that there was an error during the DAG creation, so probably the memory is too overclocked or undervolted.

Exit on run at 1080ti

 Nvidia cards require several additional files in order to work with ProgPow. These files are in the file file PhoenixMiner_NVRTC_Windows.zip, which you can download from the same folder as PhoenixMiner. Then, you need to extract the files from PhoenixMiner_NVRTC_Windows.zip and put them in the same folder as PhoenixMiner.exe.

[jeca]

When you add support for new AMD drivers, does it mean that these are the most suitable or can we continue to use 18.6.1 for example?

[ZombieWorm]

AMD released 19.10.1 drivers. Anyone tried allready? Miner support them?

Working with 19.10.1 drivers.
Vega 56 @ 1110 mhz memory, @1050 mhz core 900mv
42.3 MH/s

I updated and after a few hours the miner had crashed or the card (vega 56) reset as it was mining about 30% less. Used same settings where it mined perfectly at 41 mh/s for good watts. Just reporting back in case it happens for too many users and a fix is eeked out. On 19.9.3 drivers and this is not an aggressive profile.

[strelly83]

Hi, do you have experience with the Sapphire RX 5700 Pulse? I can't change the board parameters into the program (4.6c), the board seems to be locked ... especially the memory voltage locked to 0.85V (and Tmem is always approx 80°)... do you have any suggestions?

[ZombieWorm]

I updated and after a few hours the miner had crashed or the card (vega 56) reset as it was mining about 30% less. Used same settings where it mined perfectly at 41 mh/s for good watts. Just reporting back in case it happens for too many users and a fix is eeked out. On 19.9.3 drivers and this is not an aggressive profile.

OK so it wasnt a one off and happened again about 3 hours in. Is there an auto ramp feature thats tweaking it and pushing it too far causing the miner to crash? After the crash it drops from 41 to 35 Mh/s and uses more power.

Will switch over to see if it happens on another miner.

[MATHReX]

Hi,

I have a problem with ETH mining speed. My miner is connected to NiceHash and when they start mining ETH, first few minutes the speed is stable at around 62 MH/s. After generated new DAG file the speed drops by 10 MH/s (so to around 51 MH/s).

I have 2 Nvidia cards. 1x GTX 1070, 1x GTX 1070 ti

Why is this happening?

It used to happen with me in my 6x RX580 rig. After the new DAG, the hash rate went from 182 MH/s to 179 MH/s. It is not such a huge impact but closing the miner and restarting the system did the trick for me and the hash rate was back.

Also, reset any OC that you have on the card and after the restart, apply it again.

[MATHReX]

I updated and after a few hours the miner had crashed or the card (vega 56) reset as it was mining about 30% less. Used same settings where it mined perfectly at 41 mh/s for good watts. Just reporting back in case it happens for too many users and a fix is eeked out. On 19.9.3 drivers and this is not an aggressive profile.

OK so it wasnt a one off and happened again about 3 hours in. Is there an auto ramp feature thats tweaking it and pushing it too far causing the miner to crash? After the crash it drops from 41 to 35 Mh/s and uses more power.

Will switch over to see if it happens on another miner.

My sapphire RX Vega 56 is flashed with 64 air bios, then using powerplay tables to reduce the core and mem voltage. Using OverdriveNtool to OC memory, undervolt core and voltages, 65% fan speed.

No issues at all like this.

What are you using to OC? Did you have any other parameter in the claymore bat file for tweaking?

[cikusa]

Hi, do you have experience with the Sapphire RX 5700 Pulse? I can't change the board parameters into the program (4.6c), the board seems to be locked ... especially the memory voltage locked to 0.85V (and Tmem is always approx 80°)... do you have any suggestions?

Memory voltage is locked on Navi cards, also tmem can get high u run card on high voltage, try running card on 1300mhz/750mv and put mem on 900-930, that should lower temps on card alot.

[ZombieWorm]

I updated and after a few hours the miner had crashed or the card (vega 56) reset as it was mining about 30% less. Used same settings where it mined perfectly at 41 mh/s for good watts. Just reporting back in case it happens for too many users and a fix is eeked out. On 19.9.3 drivers and this is not an aggressive profile.

OK so it wasnt a one off and happened again about 3 hours in. Is there an auto ramp feature thats tweaking it and pushing it too far causing the miner to crash? After the crash it drops from 41 to 35 Mh/s and uses more power.

Will switch over to see if it happens on another miner.

My sapphire RX Vega 56 is flashed with 64 air bios, then using powerplay tables to reduce the core and mem voltage. Using OverdriveNtool to OC memory, undervolt core and voltages, 65% fan speed.

No issues at all like this.

What are you using to OC? Did you have any other parameter in the claymore bat file for tweaking?

I run it undervolted and Overdriven too, 41 mh/s fairly cool no where near its bench limits. It may be the driver so I installed the latest one to do more testing (19.10.1). It happened after I updated both gpu driver and PM but since the switch, this profile used to run absolutely solid. Dialled it back to test more and will see.

[MATHReX]

I run it undervolted and Overdriven too, 41 mh/s fairly cool no where near its bench limits. It may be the driver so I installed the latest one to do more testing (19.10.1). It happened after I updated both gpu driver and PM but since the switch, this profile used to run absolutely solid. Dialled it back to test more and will see.

Sounds good. Did you flash 64 bios? It'll make a ton of difference in the hash rate. I was able to hit 1125 mhz in mem clock (samsung memory vendor) but it crashed after a while. So settled for 1095 mhz (stable).

[motomart]

Hi, do you have experience with the Sapphire RX 5700 Pulse? I can't change the board parameters into the program (4.6c), the board seems to be locked ... especially the memory voltage locked to 0.85V (and Tmem is always approx 80°)... do you have any suggestions?

Memory voltage is locked on Navi cards, also tmem can get high u run card on high voltage, try running card on 1300mhz/750mv and put mem on 900-930, that should lower temps on card alot.

How did you get the card to run at 750mV? Mine never goes under 800mV regardless of -cvddc setting in Phoenixminer. Fan is at 70-90% all the time and power 112-118W.

[ZombieWorm]

I run it undervolted and Overdriven too, 41 mh/s fairly cool no where near its bench limits. It may be the driver so I installed the latest one to do more testing (19.10.1). It happened after I updated both gpu driver and PM but since the switch, this profile used to run absolutely solid. Dialled it back to test more and will see.

Sounds good. Did you flash 64 bios? It'll make a ton of difference in the hash rate. I was able to hit 1125 mhz in mem clock (samsung memory vendor) but it crashed after a while. So settled for 1095 mhz (stable).

No I never did as its Hynix memory. Its the main card in my multipurpose rig rather than a dedicated mining machine. I try to get less power draw on good hash speed rather than red line it. If im lucky I may get another when they go on the sales but since the profits are now negative its on the long finger wish list.

[strelly83]

Hi, do you have experience with the Sapphire RX 5700 Pulse? I can't change the board parameters into the program (4.6c), the board seems to be locked ... especially the memory voltage locked to 0.85V (and Tmem is always approx 80°)... do you have any suggestions?

Memory voltage is locked on Navi cards, also tmem can get high u run card on high voltage, try running card on 1300mhz/750mv and put mem on 900-930, that should lower temps on card alot.

How did you get the card to run at 750mV? Mine never goes under 800mV regardless of -cvddc setting in Phoenixminer. Fan is at 70-90% all the time and power 112-118W.

Same problem...it seems that the settings are not followed by the card...and this reflects on the memory temp (approx 80°C)...

[Andreuf88]

Hello friends, I have a problem I am mining with a rig connected to solar panels, this allows me to use the GPU to the maximum during the hours of the sun but during the night I need to restrict the use of these to consume half, I try to use the -gpow command but nothing changes still working the same way can someone help me? Thank you