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

[restless]

AN unexpected bug or smthing.
using 2.3b
Win10, driver 17.12.2, 2 cards, 570 in main pci-e slot and 470 in "slave" slot
It worked when Display was connected to 570, but then the Radeon Setting CP didn't allow to switch 470 into compute mode.
Switched Display connector  -reatarted, Radeon CP allowed to switch to compute, Claymore works normally, but Phoenix crashes... the log is:

Code:

17546:23:00:13.259: main Cmd line: -pool eth-eu.dwarfpool.com:8008 -wal wallet -cdm 2 -cdmport 3334 
17546:23:00:13.259: main No CUDA driver found
17546:23:00:13.474: main Available GPUs for mining:
17546:23:00:13.474: main GPU1: Radeon (TM) RX 470 Graphics (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
17546:23:00:13.474: main GPU2: Radeon RX 570 Series, OpenCL 2.0, 4 GB VRAM, 32 CUs
17546:23:00:13.474: main ADL library initialized
17546:23:00:13.779: main Listening for CDM remote manager at port 3334 in full mode
17546:23:00:13.779: main Eth: the pool list contains 3 pools
17546:23:00:13.779: main Eth: primary pool: eth-eu.dwarfpool.com:8008
17546:23:00:13.780: main Eth: Connecting to ethash pool eth-eu.dwarfpool.com:8008
17546:23:00:13.846: eths Eth: Connected to ethash pool eth-eu.dwarfpool.com:8008
17546:23:00:13.846: eths Eth: Starting GPU mining
17546:23:00:13.846: eths Matched GPU1 to ADL adapter index 0
17546:23:00:13.861: eths Created ADL monitor for adapter 0; overdrive version: 7
17546:23:00:13.861: eths ADL adapter index not found for GPU2
17546:23:00:13.861: wdog Starting watchdog thread
17546:23:00:13.861: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"pmethash","params":["wallet"]}

17546:23:00:13.922: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
17546:23:00:13.922: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17546:23:00:13.983: eths Eth: Received: {"result":["0xd9869b8a711dd7eff00734610dc56c48290f815c8b4c8ed14c9f4f72c10a6715","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":5}
17546:23:00:13.983: eths Eth: New job #d9869b8a from eth-eu.dwarfpool.com:8008; diff: 2000MH
17546:23:00:13.983: GPU1 GPU1: Starting up...
17546:23:00:13.984: GPU1 Eth: Generating light cache for epoch #163
17546:23:00:14.000: GPU2 GPU2: Starting up...

result from list

Code:

.\PhoenixMiner.exe -list
Phoneix Miner 2.3 Windows/msvc - Release
----------------------------------------

No CUDA driver found
Available GPUs for mining:
GPU1: Radeon (TM) RX 470 Graphics (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
GPU2: Radeon RX 570 Series, OpenCL 2.0, 4 GB VRAM, 32 CUs

[DavidC1]

Only for noobs that don't switch workload from graphics to compute

For all the knowledge you have, you should act more civilized.

Blockchain is faster for some, even with the compute enabled on the latest drivers. It also has another advantage, that you don't need to manually switch to compute mode every single time on a driver install.

[santan]

Finally managed to run on my superfast K2100M card with "-nvidia" switch..... Getting lightning hashing speed of ..... 3.9 MH/s

[PhoenixMiner]

AN unexpected bug or smthing.
using 2.3b
Win10, driver 17.12.2, 2 cards, 570 in main pci-e slot and 470 in "slave" slot
It worked when Display was connected to 570, but then the Radeon Setting CP didn't allow to switch 470 into compute mode.
Switched Display connector  -reatarted, Radeon CP allowed to switch to compute, Claymore works normally, but Phoenix crashes... the log is:

This is related the the bug in AMD drivers 17.12.2 where the reporting of bus ID of OpenCL devices is completely broken (somebody already reported the bug to AMD: https://community.amd.com/thread/224200, but it won't be fixed before the next driver release). We have implemented a workaround in PhoenixMiner 2.3 but it appears that it doesn't fix the problem in your case (the second log you've send shows that you were running the beta version of PhoenixMiner 2.3).

Even so, the worst effect should be incorrect or entirely missing GPU monitoring information (temperature and fan speed), not a crash. We've tried tried to reproduce the problem on similar setup (with RX580 and RX570) but without success. Maybe try to go back to PhoenixMiner 2.2b, or install the blockchain drivers - the latest drivers doesn't appear to be any faster than the blockchain drivers anyway and we've had some issues with controlling GPU/memory clocks under them.

Finally managed to run on my superfast K2100M card with "-nvidia" switch..... Getting lightning hashing speed of ..... 3.9 MH/s

This seems about right as (according to Wikipedia) K2100M has 48 GB/s memory bandwidth so even if it is entirely memory bandwidth constrained it should be making 4-5 MH/s max. Still even if the laptop consumes 100W, you are making 0.3 USD per day (assuming electricity costs 0.1 USD per KWh)!   Just make sure that it is cooled very well or else it could broke down quite fast.

[restless]

Only for noobs that don't switch workload from graphics to compute

For all the knowledge you have, you should act more civilized.

Blockchain is faster for some, even with the compute enabled on the latest drivers. It also has another advantage, that you don't need to manually switch to compute mode every single time on a driver install.

Switching display connection and restarting  "fixed" it... but yea, latest AMD driver is borked , now controlling clock&voltages is erratic...

[PhoenixMiner]

PhoenixMiner 2.3 is officially released. There are no changes from the beta so if you were using 2.3 beta, no need to download and install again (only the Readme.txt is updated).

We are working on 2.4, which should include a fix for the reconnect issue, and support for mining Pegascoin (PGC) without DAG switches for defvee.

[jendabenda]

PhoenixMiner 2.3 is officially released. There are no changes from the beta so if you were using 2.3 beta, no need to download and install again (only the Readme.txt is updated).

We are working on 2.4, which should include a fix for the reconnect issue, and support for mining Pegascoin (PGC) without DAG switches for defvee.

Thanks guys, keep up great work. You have best radeon miner now (from what i tried). Looking foreward to reconnect issue solution in 2.4

[Branko]

Only for noobs that don't switch workload from graphics to compute

For all the knowledge you have, you should act more civilized.

Blockchain is faster for some, even with the compute enabled on the latest drivers. It also has another advantage, that you don't need to manually switch to compute mode every single time on a driver install.

I have yet to see situation where new drivers are slower...only saw same performance (most cases) or better. Also, newer drivers usually use less power, too.




Btw, this is now my miner of choice for Ethash algo

[twotwosix]

Awesome work, i Hope you can add commands -cvddc -mvdcc -cclock -mclock for control the gpu.

THX for your work

[Golempl]

Today I had strange problem with 2.2b version (just updated to 2.3 for tests now)
17547:22:37:18.737: eths Eth: New job #290ce567 from eth-eu1.nanopool.org:9999; diff: 10000MH
17547:22:37:18.850: eths Eth: Unable to read pool response: The semaphore timeout period has expired
17547:22:37:18.850: eths Eth: Reconnecting in 10 seconds...
17547:22:37:20.712: main GPU1: 49C 90%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17547:22:37:26.948: GPU5 Unable to submit share - pool disconnected
17547:22:37:28.867: unkn Eth: Connecting to ethash pool eth-eu1.nanopool.org:9999
17547:22:37:29.802: GPU3 Unable to submit share - pool disconnected
17547:22:37:32.117: unkn Eth: Connection attempt aborted

Then it switched to 2 other failovers but they could not connect to any.
I had to close program and start it again. There were no connection/network problems. Tried ping and that worked, other rigs were working without problems.

Any hints on it ?



Is there any option like -minspeed ?

Other bug:
Using blockchain drivers, having these results with 2.3:
17547:23:08:20.300: main GPU1: 48C 90%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A

No difference over 2.2b with fan/temp reporting.



* Found a reason of disconnect. Miner doesn't reconnect when connection is reset without any confirmation from remote side.

[DavidC1]

I am using PhoenixMiner on one of my machines as a test. It will take few days to verify.

Same hash rate on client side, even though peak is higher in some cases. The effective hash rate looks better, but as I said it will take few days to verify. Stales seem somewhat higher than Claymore. The ability to use nearly identical settings as Claymore is a plus, because it makes migration easier.

[PhoenixMiner]

Then it switched to 2 other failovers but they could not connect to any.
I had to close program and start it again. There were no connection/network problems. Tried ping and that worked, other rigs were working without problems.
Any hints on it ?

This is the infamous reconnection issue. We are working on it, and it should be fixed in 2.4. It is maddeningly inconsistent - during the tests a hundred reconnects in a row go without a hitch and then it strikes again.

Is there any option like -minspeed ?

Not yet but we are considering it. However to be truly useful, it should probably have the ability to set a per-GPU minimal speed also if the GPUs are not the same.

Other bug:
Using blockchain drivers, having these results with 2.3:
17547:23:08:20.300: main GPU1: 48C 90%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
No difference over 2.2b with fan/temp reporting.

This is interesting, as HW info reporting problems were only observed on the latest Adrenalin drivers up until now. Could you please send us a full log from a test run? To avoid posting your wallet address, you can run

Code:

PhoenixMiner.exe -bench

for a minute or so (until you see the first GPU temperature/fan report) and then send us the log file contents (on PM if you want to, we can receive PMs from all members).

[Golempl]

Code:

17548:11:05:49.192: main Cmd line: -bench 
17548:11:05:49.192: main No CUDA driver found
17548:11:05:49.650: main Available GPUs for mining:
17548:11:05:49.650: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
17548:11:05:49.650: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
17548:11:05:49.650: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
17548:11:05:49.650: main GPU4: Radeon RX 570 Series (pcie 7), OpenCL 2.0, 4 GB VRAM, 32 CUs
17548:11:05:49.650: main GPU5: Radeon RX 570 Series (pcie 10), OpenCL 2.0, 4 GB VRAM, 32 CUs
17548:11:05:49.650: main GPU6: Radeon RX 570 Series (pcie 11), OpenCL 2.0, 4 GB VRAM, 32 CUs
17548:11:05:49.650: main GPU7: Radeon RX 570 Series (pcie 12), OpenCL 2.0, 4 GB VRAM, 32 CUs
17548:11:05:49.665: main ADL library initialized
17548:11:05:49.912: main Benchmark mode. DAG epoch #2
17548:11:05:49.912: main Matched GPU1 to ADL adapter index 6
17548:11:05:49.927: main Created ADL monitor for adapter 6; overdrive version: 7
17548:11:05:49.927: GPU1 GPU1: Starting up...
17548:11:05:49.927: GPU1 Eth: Generating light cache for epoch #2
17548:11:05:49.933: main ADL adapter index not found for GPU2
17548:11:05:49.933: GPU2 GPU2: Starting up...
17548:11:05:49.951: main ADL adapter index not found for GPU3
17548:11:05:50.033: GPU3 GPU3: Starting up...
17548:11:05:50.042: main ADL adapter index not found for GPU4
17548:11:05:50.043: GPU4 GPU4: Starting up...
17548:11:05:50.060: main ADL adapter index not found for GPU5
17548:11:05:50.060: GPU5 GPU5: Starting up...
17548:11:05:50.074: main ADL adapter index not found for GPU6
17548:11:05:50.074: GPU6 GPU6: Starting up...
17548:11:05:50.089: main ADL adapter index not found for GPU7
17548:11:05:50.089: GPU7 GPU7: Starting up...
17548:11:05:50.107: wdog Starting watchdog thread
17548:11:05:51.372: GPU3 GPU3: Allocating DAG buffer (1.02 GB)
17548:11:05:51.414: GPU3 GPU3: Using optimized OpenCL kernels (device name 'Ellesmere')
17548:11:05:51.547: GPU3 GPU3: Generating DAG for epoch #2
17548:11:05:51.615: GPU4 GPU4: Allocating DAG buffer (1.02 GB)
17548:11:05:51.657: GPU4 GPU4: Using optimized OpenCL kernels (device name 'Ellesmere')
17548:11:05:51.783: GPU4 GPU4: Generating DAG for epoch #2
17548:11:05:51.853: GPU6 GPU6: Allocating DAG buffer (1.02 GB)
17548:11:05:51.895: GPU6 GPU6: Using optimized OpenCL kernels (device name 'Ellesmere')
17548:11:05:52.023: GPU6 GPU6: Generating DAG for epoch #2
17548:11:05:52.097: GPU7 GPU7: Allocating DAG buffer (1.02 GB)
17548:11:05:52.141: GPU7 GPU7: Using optimized OpenCL kernels (device name 'Ellesmere')
17548:11:05:52.284: GPU7 GPU7: Generating DAG for epoch #2
17548:11:05:52.380: GPU1 GPU1: Allocating DAG buffer (1.02 GB)
17548:11:05:52.435: GPU1 GPU1: Using optimized OpenCL kernels (device name 'Ellesmere')
17548:11:05:52.531: GPU1 GPU1: Generating DAG for epoch #2
17548:11:05:52.606: GPU5 GPU5: Allocating DAG buffer (1.02 GB)
17548:11:05:52.648: GPU5 GPU5: Using optimized OpenCL kernels (device name 'Ellesmere')
17548:11:05:52.774: GPU5 GPU5: Generating DAG for epoch #2
17548:11:05:52.831: GPU2 GPU2: Allocating DAG buffer (1.02 GB)
17548:11:05:52.873: GPU2 GPU2: Using optimized OpenCL kernels (device name 'Ellesmere')
17548:11:05:52.875: GPU2 GPU2: Generating DAG for epoch #2
17548:11:05:53.062: GPU3 GPU3: DAG  94%
17548:11:05:53.158: GPU3 GPU3: DAG generated in 1.6 s (645.6 MB/s)
17548:11:05:53.298: GPU4 GPU4: DAG  94%
17548:11:05:53.394: GPU4 GPU4: DAG generated in 1.6 s (645.6 MB/s)
17548:11:05:53.542: GPU6 GPU6: DAG  94%
17548:11:05:53.638: GPU6 GPU6: DAG generated in 1.6 s (644.0 MB/s)
17548:11:05:53.805: GPU7 GPU7: DAG  94%
17548:11:05:53.901: GPU7 GPU7: DAG generated in 1.6 s (643.2 MB/s)
17548:11:05:54.050: GPU1 GPU1: DAG  88%
17548:11:05:54.252: GPU1 GPU1: DAG generated in 1.7 s (604.3 MB/s)
17548:11:05:54.282: GPU5 GPU5: DAG  94%
17548:11:05:54.379: GPU5 GPU5: DAG generated in 1.6 s (648.4 MB/s)
17548:11:05:54.380: GPU2 GPU2: DAG  94%
17548:11:05:54.476: GPU2 GPU2: DAG generated in 1.6 s (650.0 MB/s)
17548:11:05:59.477: main Eth speed: 206.804 MH/s, time: 0:00
17548:11:05:59.477: main GPUs: 1: 28.627 MH/s 2: 29.686 MH/s 3: 29.710 MH/s 4: 29.697 MH/s 5: 29.699 MH/s 6: 29.694 MH/s 7: 29.692 MH/s
17548:11:06:04.556: main Eth speed: 207.638 MH/s, time: 0:00
17548:11:06:04.556: main GPUs: 1: 29.220 MH/s 2: 29.730 MH/s 3: 29.745 MH/s 4: 29.734 MH/s 5: 29.737 MH/s 6: 29.737 MH/s 7: 29.736 MH/s
17548:11:06:09.647: main Eth speed: 207.510 MH/s, time: 0:00
17548:11:06:09.647: main GPUs: 1: 29.091 MH/s 2: 29.730 MH/s 3: 29.747 MH/s 4: 29.735 MH/s 5: 29.736 MH/s 6: 29.736 MH/s 7: 29.735 MH/s
17548:11:06:10.663: main GPU1: 47C 91%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17548:11:06:14.739: main Eth speed: 206.053 MH/s, time: 0:00
17548:11:06:14.739: main GPUs: 1: 28.912 MH/s 2: 29.725 MH/s 3: 29.480 MH/s 4: 29.470 MH/s 5: 29.469 MH/s 6: 29.477 MH/s 7: 29.520 MH/s
17548:11:06:19.816: main Eth speed: 207.337 MH/s, time: 0:00
17548:11:06:19.816: main GPUs: 1: 29.325 MH/s 2: 29.305 MH/s 3: 29.748 MH/s 4: 29.738 MH/s 5: 29.738 MH/s 6: 29.746 MH/s 7: 29.736 MH/s
17548:11:06:24.895: main Eth speed: 207.584 MH/s, time: 0:00
17548:11:06:24.895: main GPUs: 1: 29.138 MH/s 2: 29.730 MH/s 3: 29.751 MH/s 4: 29.739 MH/s 5: 29.740 MH/s 6: 29.748 MH/s 7: 29.737 MH/s
17548:11:06:26.927: main GPU1: 48C 90%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17548:11:06:29.974: main Eth speed: 206.797 MH/s, time: 0:00
17548:11:06:29.974: main GPUs: 1: 28.357 MH/s 2: 29.730 MH/s 3: 29.750 MH/s 4: 29.738 MH/s 5: 29.738 MH/s 6: 29.747 MH/s 7: 29.737 MH/s
17548:11:06:35.055: main Eth speed: 207.323 MH/s, time: 0:00
17548:11:06:35.055: main GPUs: 1: 28.880 MH/s 2: 29.738 MH/s 3: 29.748 MH/s 4: 29.738 MH/s 5: 29.738 MH/s 6: 29.745 MH/s 7: 29.735 MH/s
17548:11:06:40.134: main Eth speed: 207.477 MH/s, time: 0:00
17548:11:06:40.134: main GPUs: 1: 29.024 MH/s 2: 29.742 MH/s 3: 29.749 MH/s 4: 29.739 MH/s 5: 29.738 MH/s 6: 29.748 MH/s 7: 29.737 MH/s
17548:11:06:43.182: main GPU1: 48C 90%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17548:11:06:45.213: main Eth speed: 206.287 MH/s, time: 0:00
17548:11:06:45.213: main GPUs: 1: 29.003 MH/s 2: 29.743 MH/s 3: 29.484 MH/s 4: 29.526 MH/s 5: 29.526 MH/s 6: 29.536 MH/s 7: 29.469 MH/s
17548:11:06:50.291: main Eth speed: 207.369 MH/s, time: 0:01
17548:11:06:50.291: main GPUs: 1: 29.185 MH/s 2: 29.478 MH/s 3: 29.749 MH/s 4: 29.739 MH/s 5: 29.738 MH/s 6: 29.743 MH/s 7: 29.736 MH/s
17548:11:06:55.371: main Eth speed: 207.565 MH/s, time: 0:01
17548:11:06:55.371: main GPUs: 1: 29.137 MH/s 2: 29.726 MH/s 3: 29.749 MH/s 4: 29.738 MH/s 5: 29.737 MH/s 6: 29.750 MH/s 7: 29.728 MH/s
17548:11:06:59.434: main GPU1: 49C 91%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17548:11:07:00.449: main Eth speed: 207.490 MH/s, time: 0:01
17548:11:07:00.449: main GPUs: 1: 29.044 MH/s 2: 29.740 MH/s 3: 29.749 MH/s 4: 29.739 MH/s 5: 29.736 MH/s 6: 29.747 MH/s 7: 29.734 MH/s
17548:11:07:05.552: main Eth speed: 207.631 MH/s, time: 0:01
17548:11:07:05.552: main GPUs: 1: 29.184 MH/s 2: 29.743 MH/s 3: 29.748 MH/s 4: 29.739 MH/s 5: 29.735 MH/s 6: 29.750 MH/s 7: 29.733 MH/s
17548:11:07:10.649: main Eth speed: 207.672 MH/s, time: 0:01
17548:11:07:10.649: main GPUs: 1: 29.218 MH/s 2: 29.742 MH/s 3: 29.748 MH/s 4: 29.740 MH/s 5: 29.736 MH/s 6: 29.748 MH/s 7: 29.739 MH/s
17548:11:07:15.728: main Eth speed: 206.226 MH/s, time: 0:01
17548:11:07:15.728: main GPUs: 1: 29.005 MH/s 2: 29.742 MH/s 3: 29.532 MH/s 4: 29.469 MH/s 5: 29.470 MH/s 6: 29.477 MH/s 7: 29.530 MH/s
17548:11:07:15.728: main GPU1: 49C 90%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17548:11:07:20.819: main Eth speed: 207.373 MH/s, time: 0:01
17548:11:07:20.819: main GPUs: 1: 29.183 MH/s 2: 29.475 MH/s 3: 29.751 MH/s 4: 29.739 MH/s 5: 29.738 MH/s 6: 29.744 MH/s 7: 29.744 MH/s
17548:11:07:25.897: main Eth speed: 207.549 MH/s, time: 0:01
17548:11:07:25.897: main GPUs: 1: 29.076 MH/s 2: 29.750 MH/s 3: 29.749 MH/s 4: 29.738 MH/s 5: 29.742 MH/s 6: 29.747 MH/s 7: 29.747 MH/s
17548:11:07:30.976: main Eth speed: 207.488 MH/s, time: 0:01
17548:11:07:30.976: main GPUs: 1: 29.004 MH/s 2: 29.748 MH/s 3: 29.750 MH/s 4: 29.740 MH/s 5: 29.748 MH/s 6: 29.749 MH/s 7: 29.749 MH/s
17548:11:07:32.000: main GPU1: 49C 91%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17548:11:07:36.075: main Eth speed: 207.313 MH/s, time: 0:01
17548:11:07:36.075: main GPUs: 1: 28.835 MH/s 2: 29.749 MH/s 3: 29.751 MH/s 4: 29.739 MH/s 5: 29.750 MH/s 6: 29.745 MH/s 7: 29.745 MH/s
17548:11:07:41.154: main Eth speed: 207.735 MH/s, time: 0:01
17548:11:07:41.154: main GPUs: 1: 29.256 MH/s 2: 29.748 MH/s 3: 29.751 MH/s 4: 29.739 MH/s 5: 29.748 MH/s 6: 29.746 MH/s 7: 29.747 MH/s
17548:11:07:46.232: main Eth speed: 206.232 MH/s, time: 0:01
17548:11:07:46.232: main GPUs: 1: 29.046 MH/s 2: 29.746 MH/s 3: 29.481 MH/s 4: 29.469 MH/s 5: 29.481 MH/s 6: 29.531 MH/s 7: 29.477 MH/s
17548:11:07:48.264: main GPU1: 49C 90%, GPU2: N/A, GPU3: N/A, GPU4: N/A, GPU5: N/A, GPU6: N/A, GPU7: N/A
17548:11:07:51.311: main Eth speed: 207.120 MH/s, time: 0:02
17548:11:07:51.311: main GPUs: 1: 28.921 MH/s 2: 29.477 MH/s 3: 29.752 MH/s 4: 29.737 MH/s 5: 29.742 MH/s 6: 29.745 MH/s 7: 29.746 MH/s
17548:11:07:56.403: main Eth speed: 207.696 MH/s, time: 0:02
17548:11:07:56.403: main GPUs: 1: 29.221 MH/s 2: 29.745 MH/s 3: 29.751 MH/s 4: 29.738 MH/s 5: 29.746 MH/s 6: 29.748 MH/s 7: 29.747 MH/s
17548:11:08:01.482: main Eth speed: 207.391 MH/s, time: 0:02
17548:11:08:01.482: main GPUs: 1: 28.919 MH/s 2: 29.745 MH/s 3: 29.749 MH/s 4: 29.741 MH/s 5: 29.746 MH/s 6: 29.745 MH/s 7: 29.746 MH/s
17548:11:08:02.625: unkn Quitting...
17548:11:08:05.358: wdog Stopping watchdog thread

If you need any more details let me know.

[Marvell2]

does this miner solve this issue :

so sick of this

 LBC - Total Speed: 115.426 Mh/s, Total Shares: 4286, Rejected: 24
 LBC: GPU0 off, GPU1 64.873 Mh/s, GPU2 50.553 Mh/s, GPU3 off, GPU4 off, GPU5 off, GPU6 off
Code:

Code:

Socket was closed remotely (by pool)
ETH: Connection lost, retry in 20 sec...

LBC: 01/17/18-04:36:08 - New job from lbry.suprnova.cc:6256
ETH: Stratum - connecting to 'eu1.ethpool.org' <91

happens every day and kills the miner or then i get cards that start hashing less or the machine dies entirely

claymore needs to fix this shit.  Its not even the pool since it happens on multiple pools

seems to happend every day no matter what pool, claymore gets that error socket closed remotely by pool

then the miner freezes , sometimes crashes, other rigs have cards suddenly hashing at lilke  7.8 or  just reboot or die completley.

The eorry happens on every rig m the Nvidia rigs seem to mostly recover AMD rigs mostly are fucked.

[Marvell2]

testing this miner on some of my rigs ,  hash rate starts out good , then some cards start doing the claymore twostep

from 29.8 mhs to 15 mhs or lower.

Some rigs crash as well.  Do you want copies of the log files ?  This happens on claymore too but faster on this miner , and not even after a disconect and reconnect

its defintaly faster than claymore but seems more unstable , cards lose hash rate fast

[DavidC1]

testing this miner on some of my rigs ,  hash rate starts out good , then some cards start doing the claymore twostep

from 29.8 mhs to 15 mhs or lower.

Some rigs crash as well.  Do you want copies of the log files ?  This happens on claymore too but faster on this miner , and not even after a disconect and reconnect

its defintaly faster than claymore but seems more unstable , cards lose hash rate fast

You sure the problem is not due to the hardware/driver? Get something like OpenCL hangs on GPU 0, moments later the application starts itself only to get lower hash rate. That's likely a hardware problem, because I have an older GPU that does that occasionally. Not always, just when I wake up the display to use the system.

[Marvell2]

testing this miner on some of my rigs ,  hash rate starts out good , then some cards start doing the claymore twostep

from 29.8 mhs to 15 mhs or lower.

Some rigs crash as well.  Do you want copies of the log files ?  This happens on claymore too but faster on this miner , and not even after a disconect and reconnect

its defintaly faster than claymore but seems more unstable , cards lose hash rate fast

You sure the problem is not due to the hardware/driver? Get something like OpenCL hangs on GPU 0, moments later the application starts itself only to get lower hash rate. That's likely a hardware problem, because I have an older GPU that does that occasionally. Not always, just when I wake up the display to use the system.

nothing hangs though,  hash rate just drops on certain boxes , these are newer cards rx 470s and 570s 580s

These are not related to app restarts , actually a restart tends to fix the issue.  Its something with these miners , genoli minder does not do this as far as i know

[DavidC1]

nothing hangs though,  hash rate just drops on certain boxes , these are newer cards rx 470s and 570s 580s

These are not related to app restarts , actually a restart tends to fix the issue.  Its something with these miners , genoli minder does not do this as far as i know

Do you dual mine? Or you used to and they are older cards? Are they overclocked to the maximum?

Genoil performs much less than either of the miners we are discussing so the demand on the card would be naturally much less.

[Marvell2]

nothing hangs though,  hash rate just drops on certain boxes , these are newer cards rx 470s and 570s 580s

These are not related to app restarts , actually a restart tends to fix the issue.  Its something with these miners , genoli minder does not do this as far as i know

Do you dual mine? Or you used to and they are older cards? Are they overclocked to the maximum?

Genoil performs much less than either of the miners we are discussing so the demand on the card would be naturally much less.

Ive dual mined beofre yeah , mild OC on the cards but they are only a few months old

[DavidC1]

Ive dual mined beofre yeah , mild OC on the cards but they are only a few months old

I'm talking about memory overclocks.

You said 29.8MH/s. You need to overclock quite high to get that, not a "mild" overclock. Plus just a few months dual mining could have your cards start working weird.