Author

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

jr. member
Activity: 48
Merit: 1
Im getting this issue:

Code:
2020.08.25:00:27:09.070: main Eth speed: 187.593 MH/s, shares: 38/4/0, time: 0:48
2020.08.25:00:27:09.070: main GPUs: 1: 23.703 MH/s (2) 2: 23.705 MH/s (8) 3: 20.720 MH/s (4) 4: 22.702 MH/s (5) 5: 26.831 MH/s (7) 6: 23.687 MH/s (10) 7: 23.601 MH/s (3) 8: 22.645 MH/s (3)
2020.08.25:00:27:14.164: main Eth speed: 187.630 MH/s, shares: 38/4/0, time: 0:48
2020.08.25:00:27:14.164: main GPUs: 1: 23.711 MH/s (2) 2: 23.714 MH/s (8) 3: 20.697 MH/s (4) 4: 22.704 MH/s (5) 5: 26.854 MH/s (7) 6: 23.706 MH/s (10) 7: 23.586 MH/s (3) 8: 22.659 MH/s (3)
2020.08.25:00:27:14.567: main GPU1: 71C 84% 79W, GPU2: 70C 88% 76W, GPU3: 84C 84% 65W, GPU4: 75C 59% 114W, GPU5: 74C 38% 79W, GPU6: 80C 79% 82W, GPU7: 80C 80% 73W, GPU8: 85C 60% 117W
GPUs power: 685.7 W
2020.08.25:00:27:15.187: main Stratum thread not responsive for 51 s
2020.08.25:00:27:15.187: wdog Fatal error detected. Restarting.

Any idea why Im gettig this issue?

Im getting this new issue:
Code:
2020.08.28:15:54:12.837: main Eth speed: 187.861 MH/s, shares: 2109/15/2, time: 13:48
2020.08.28:15:54:12.837: main GPUs: 1: 23.708 MH/s (248) 2: 23.705 MH/s (268) 3: 21.074 MH/s (260) 4: 22.703 MH/s (280) 5: 26.852 MH/s (283/1) 6: 23.713 MH/s (257) 7: 23.446 MH/s (279) 8: 22.662 MH/s (249/1)
2020.08.28:15:54:13.469: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x8646d0302e578f9568e49c30e7263eb5c0c2f02c71bd76b29d44bd12e4319d6e","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080b"]}
2020.08.28:15:54:13.470: eths Eth: New job #8646d030 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:13.844: main 
2020.08.28:15:54:13.844: main *** 13:48 *** 8/28 15:54 **************************************
2020.08.28:15:54:13.846: main Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 0:00
2020.08.28:15:54:13.846: main Eth: Accepted shares 2109 (4 stales), rejected shares 15 (0 stales)
2020.08.28:15:54:13.846: main Eth: Incorrect shares 2 (0.09%), est. stales percentage 0.19%
2020.08.28:15:54:13.846: main Eth: Maximum difficulty of found share: 2508.3 GH (!)
2020.08.28:15:54:13.846: main Eth: Average speed (5 min): 187.132 MH/s
2020.08.28:15:54:13.846: main Eth: Effective speed: 170.98 MH/s; at pool: 169.77 MH/s
2020.08.28:15:54:13.846: main 
2020.08.28:15:54:17.455: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x8bef475007357a0bb56b55f92960f2fdff3e765b85b0775715965309ccf9ed59","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080b"]}
2020.08.28:15:54:17.455: eths Eth: New job #8bef4750 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:17.896: main Eth speed: 187.785 MH/s, shares: 2109/15/2, time: 13:48
2020.08.28:15:54:17.896: main GPUs: 1: 23.705 MH/s (248) 2: 23.704 MH/s (268) 3: 20.957 MH/s (260) 4: 22.704 MH/s (280) 5: 26.851 MH/s (283/1) 6: 23.713 MH/s (257) 7: 23.491 MH/s (279) 8: 22.659 MH/s (249/1)
2020.08.28:15:54:17.928: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x0322f784d1c1863edf9c8089175fedbfcc322eea8e06027171607330ce9b5a35","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080c"]}
2020.08.28:15:54:17.928: eths Eth: New job #0322f784 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:18.204: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xc36d4250eafbe2100f0aec35f26385dd959ed827daabcd3b7a306b19ccc06ced","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080c"]}
2020.08.28:15:54:18.205: eths Eth: New job #c36d4250 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:19.076: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xa5746d305c50595e276704b865b43d917f62c6a91453f7866526ad28744fa0d8","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080d"]}
2020.08.28:15:54:19.076: eths Eth: New job #a5746d30 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:19.365: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x31630536d420b41969824c7660f865c912bd361cf03e9eaa00c1418c0c101415","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080d"]}
2020.08.28:15:54:19.365: eths Eth: New job #31630536 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:22.951: main Eth speed: 187.740 MH/s, shares: 2109/15/2, time: 13:48
2020.08.28:15:54:22.951: main GPUs: 1: 23.702 MH/s (248) 2: 23.707 MH/s (268) 3: 20.926 MH/s (260) 4: 22.705 MH/s (280) 5: 26.850 MH/s (283/1) 6: 23.710 MH/s (257) 7: 23.489 MH/s (279) 8: 22.652 MH/s (249/1)
2020.08.28:15:54:23.344: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x8b727bf2c2d97fb1836ed027304b3a72ac5a0e9bb0ae0e6f8c545d9591e6deda","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080d"]}
2020.08.28:15:54:23.344: eths Eth: New job #8b727bf2 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:26.185: main GPU1: 71C 84% 79W, GPU2: 76C 99% 77W, GPU3: 83C 81% 51W, GPU4: 74C 56% 114W, GPU5: 74C 38% 79W, GPU6: 80C 79% 77W, GPU7: 80C 81% 77W, GPU8: 83C 59% 117W
GPUs power: 671.7 W
2020.08.28:15:54:28.034: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x3905cc40d9470e83cc9a06ee869279cb37ec022aa0df671c7851c1aa4b6735a7","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080d"]}
2020.08.28:15:54:28.034: eths Eth: New job #3905cc40 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:28.061: main Eth speed: 187.796 MH/s, shares: 2109/15/2, time: 13:48
2020.08.28:15:54:28.061: main GPUs: 1: 23.708 MH/s (248) 2: 23.714 MH/s (268) 3: 21.050 MH/s (260) 4: 22.705 MH/s (280) 5: 26.850 MH/s (283/1) 6: 23.714 MH/s (257) 7: 23.402 MH/s (279) 8: 22.651 MH/s (249/1)
2020.08.28:15:54:33.105: main Eth speed: 187.794 MH/s, shares: 2109/15/2, time: 13:48
2020.08.28:15:54:33.105: main GPUs: 1: 23.712 MH/s (248) 2: 23.716 MH/s (268) 3: 21.077 MH/s (260) 4: 22.708 MH/s (280) 5: 26.851 MH/s (283/1) 6: 23.717 MH/s (257) 7: 23.355 MH/s (279) 8: 22.658 MH/s (249/1)
2020.08.28:15:54:33.120: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x802ae65529d3eee5d2f441687420b7803edee593c55cec1e055296db2396347d","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080d"]}
2020.08.28:15:54:33.120: eths Eth: New job #802ae655 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:38.152: main Eth speed: 187.759 MH/s, shares: 2109/15/2, time: 13:48
2020.08.28:15:54:38.152: main GPUs: 1: 23.713 MH/s (248) 2: 23.712 MH/s (268) 3: 21.080 MH/s (260) 4: 22.707 MH/s (280) 5: 26.850 MH/s (283/1) 6: 23.712 MH/s (257) 7: 23.324 MH/s (279) 8: 22.662 MH/s (249/1)
2020.08.28:15:54:38.206: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2d80bc197695d05f0273cb61497781776cd5e33c6f5cbc3bf86c1e7043027ea4","0xf7f6e04564e6b37fb9017324dc2577bd24cd25977037cfe8cd95b590009e2391","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xa4080e"]}
2020.08.28:15:54:38.206: eths Eth: New job #2d80bc19 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2020.08.28:15:54:38.354: main Stratum thread not responsive for 51 s
2020.08.28:15:54:38.354: wdog Fatal error detected. Restarting.

Phoenixminer closes alone, any idea why is this happening?
full member
Activity: 269
Merit: 102
Hello all. Does anyone have a MSI Evoke 5700? I also have a Mech 5700. Both flashed to the same BIOS (5700 XT + Strap mode), same BIOS mod 1500 straps and yet the Evoke barely hits 52MH/s where the Mech is hitting 55MH/s easily. I have another Evoke on the way as well as a Mech so I can confirm whether or not the Mech is just a better card or not. I have tweaked all the clock settings to find the optimal for stability and speed but that Evoke just won't hash as well as the Mech.

So what I am trying to figure out if others are having similar issues or not.

Hello, msi xt 5700 8 Gb EVOKE OC. You must edit only 1 ts bios straps copy 1550 and down!
The second bios must be unchanged! Otherwise, the cards will not give a higher hash
Can edit both, be fine, only the one for your memory type gets used so just change both.

The display monitor will hash noticeably slower.  Also, check memory temperature, if memory hits 105C it will throttle core.
I too have only 2 EVOKE's thankfully. I only buy the Mech's if I find them at a decent price since I know I can get the 55MH/s out of them. I was wondering if it was just mine but it does appear that they only get 52MH/s no matter what you do. Maybe someone will find a trick to kick them up a notch..
sr. member
Activity: 449
Merit: 251
Hello all. Does anyone have a MSI Evoke 5700? I also have a Mech 5700. Both flashed to the same BIOS (5700 XT + Strap mode), same BIOS mod 1500 straps and yet the Evoke barely hits 52MH/s where the Mech is hitting 55MH/s easily. I have another Evoke on the way as well as a Mech so I can confirm whether or not the Mech is just a better card or not. I have tweaked all the clock settings to find the optimal for stability and speed but that Evoke just won't hash as well as the Mech.

So what I am trying to figure out if others are having similar issues or not.

Hello, msi xt 5700 8 Gb EVOKE OC. You must edit only 1 ts bios straps copy 1550 and down!
The second bios must be unchanged! Otherwise, the cards will not give a higher hash
Can edit both, be fine, only the one for your memory type gets used so just change both.

The display monitor will hash noticably slower.  Also, check memory temperature, if memory hits 105C it will throttle core.
newbie
Activity: 5
Merit: 0
Hello all. Does anyone have a MSI Evoke 5700? I also have a Mech 5700. Both flashed to the same BIOS (5700 XT + Strap mode), same BIOS mod 1500 straps and yet the Evoke barely hits 52MH/s where the Mech is hitting 55MH/s easily. I have another Evoke on the way as well as a Mech so I can confirm whether or not the Mech is just a better card or not. I have tweaked all the clock settings to find the optimal for stability and speed but that Evoke just won't hash as well as the Mech.

So what I am trying to figure out if others are having similar issues or not.

Hello, msi xt 5700 8 Gb EVOKE OC. You must edit only 1 ts bios straps copy 1550 and down!
The second bios must be unchanged! Otherwise, the cards will not give a higher hash
legendary
Activity: 3808
Merit: 1723
If I ping "eth-eu1.nanopool.org" from cmd, it is 75 ms but the share acceptance time is 215 ms with same server.  Is it okay?  Yet, there were no invalid or stale shares, and I am getting around 30 shares per hour for 85 mh/s.

ping will send smaller packet than the share itself. I was mining through VPN for some time with 250ms response time and practically got the same results as with direct connection, so you should be fine with 215ms.

Regards,
zeezoo

You can mine Bitcoin with a large ping such as that but if you are mining any coins with an average block time of ~15 seconds or so you will run into too many stale shares. Generally you are creditted for stale shares however keep in mind that you will make more money overall with a faster ping time.

Imagine you and someone else finds a block at the same time, the other guy has a ping of 50ms and yours is 250ms, what will happen is his will get accepted first and their pool will get the credit and not yours and you will make less money overtime.
newbie
Activity: 42
Merit: 0
If I ping "eth-eu1.nanopool.org" from cmd, it is 75 ms but the share acceptance time is 215 ms with same server.  Is it okay?  Yet, there were no invalid or stale shares, and I am getting around 30 shares per hour for 85 mh/s.

ping will send smaller packet than the share itself. I was mining through VPN for some time with 250ms response time and practically got the same results as with direct connection, so you should be fine with 215ms.

Regards,
zeezoo
newbie
Activity: 33
Merit: 0
If I ping "eth-eu1.nanopool.org" from cmd, it is 75 ms but the share acceptance time is 215 ms with same server.  Is it okay?  Yet, there were no invalid or stale shares, and I am getting around 30 shares per hour for 85 mh/s.
newbie
Activity: 17
Merit: 0
Dear Phoenix. Is it possible to improve the performance of Nvidia 1070-series by splitting the DAG file?
jr. member
Activity: 48
Merit: 1
Im getting this issue:

Code:
2020.08.25:00:27:09.070: main Eth speed: 187.593 MH/s, shares: 38/4/0, time: 0:48
2020.08.25:00:27:09.070: main GPUs: 1: 23.703 MH/s (2) 2: 23.705 MH/s (8) 3: 20.720 MH/s (4) 4: 22.702 MH/s (5) 5: 26.831 MH/s (7) 6: 23.687 MH/s (10) 7: 23.601 MH/s (3) 8: 22.645 MH/s (3)
2020.08.25:00:27:14.164: main Eth speed: 187.630 MH/s, shares: 38/4/0, time: 0:48
2020.08.25:00:27:14.164: main GPUs: 1: 23.711 MH/s (2) 2: 23.714 MH/s (8) 3: 20.697 MH/s (4) 4: 22.704 MH/s (5) 5: 26.854 MH/s (7) 6: 23.706 MH/s (10) 7: 23.586 MH/s (3) 8: 22.659 MH/s (3)
2020.08.25:00:27:14.567: main GPU1: 71C 84% 79W, GPU2: 70C 88% 76W, GPU3: 84C 84% 65W, GPU4: 75C 59% 114W, GPU5: 74C 38% 79W, GPU6: 80C 79% 82W, GPU7: 80C 80% 73W, GPU8: 85C 60% 117W
GPUs power: 685.7 W
2020.08.25:00:27:15.187: main Stratum thread not responsive for 51 s
2020.08.25:00:27:15.187: wdog Fatal error detected. Restarting.

Any idea why Im gettig this issue?
newbie
Activity: 23
Merit: 0
I have 6x radeon vii and today I have this error:

GPU1: Unable to set GPU clocks to 1775 MHz (Vddc 975 mv) - error -8

Temps seem ok, cclock and cvddc are low, power usage low and card is hashing at only 36 MH/s. I rebooted the system several times, checked settings but can't figure out why it happened all of a sudden.


2020.08.24:15:46:58.314: main GPU1: 58C 23% 78W, GPU2: 60C 71% 195W, GPU3: 61C 63% 233W, GPU4: 67C 76% 215W, GPU5: 64C 75% 194W, GPU6: 63C 79% 200W
GPU1: cclock 700 MHz, cvddc 737 mV, mclock 1120 MHz, mvddc 850 mV, Tj 65C, Tmem 66C
GPU2: cclock 1765 MHz, cvddc 975 mV, mclock 1125 MHz, mvddc 850 mV, Tj 77C, Tmem 71C
GPU3: cclock 1751 MHz, cvddc 975 mV, mclock 1125 MHz, mvddc 850 mV, Tj 85C, Tmem 74C
GPU4: cclock 1744 MHz, cvddc 968 mV, mclock 1124 MHz, mvddc 850 mV, Tj 96C, Tmem 76C
GPU5: cclock 1748 MHz, cvddc 975 mV, mclock 1120 MHz, mvddc 850 mV, Tj 87C, Tmem 74C
GPU6: cclock 1750 MHz, cvddc 975 mV, mclock 1120 MHz, mvddc 850 mV, Tj 99C, Tmem 71C


Here is my startup parameter
-cclock 1775,1775,1775,1775,1775,1775 -mclock 1120,1125,1125,1125,1120,1120 -cvddc 975,970,970,965,970,975 -powlim 0,0,0,0,0,0


Any ideas?
newbie
Activity: 42
Merit: 0
Hi guys, settings to Nvidia 1060 6gb mining ETH? I have PL 65, MC +550, CC +110 but is jump all time, I was try with differents and still jump, anyone have a good settings? Thanks

Do you undervolt? If not watch this video: https://www.youtube.com/watch?v=oO50uMU7L-E
You can lock certain frequency by pressing L in "Voltage/Frequency curve editor". I run my 1070 at 1809MHz, 825mV on Core and +800 Memory, with recent strap settings I can get 29,2MH/s.
My friend had Asus Mining cards that were equivalent to 1060 6GB and I've set core at 1800MHz, 825mV and +650 to memory. It was getting 24,8MH/s about 1,5 months ago but now he sold his miner and due to DAG size it will probably be lower than that. Strap settings didn't work for him.

Regards,
zeezoo
newbie
Activity: 42
Merit: 0
Hi guys, settings to Nvidia 1060 6gb mining ETH? I have PL 65, MC +550, CC +110 but is jump all time, I was try with differents and still jump, anyone have a good settings? Thanks
newbie
Activity: 32
Merit: 0
hi, i found this error:
2020.08.23: 19: 09: 42.070: edev DevFee: Could not connect to ethash pool ssl: //eu1.ethermine.org: 5555: Not enough buffer space or queue full. Unable to perform operation on socket
2020.08.23: 19: 09: 42.071: edev DevFee: Giving up after 1 retries, switching to next pool
2020.08.23: 19: 09: 42.071: edev DevFee: Reconnecting in 3 seconds ...
newbie
Activity: 42
Merit: 0
Does anyone know if Phoenix can auto-ignore unsuitable GPUs?

When DAG allocation fails, I just want it to keep mining on the GPUs that have enough RAM. This is useful for automated benchmarking: just mine on the GPUs that work.

Some miners automatically exclude GPUs that are unsuitable for mining. Phoenix doesn't, though.

First of all, what you are using? if RX 500 series you are capable of using Phoenix miner 5.0e but make sure that you increase your Virtual Memory, how to do it, just go to my computer, property then advance system setting,  under performance select setting, go to advance, you can there the virtual memory, click change, uncheck the automatically manage paging size, click custom size, then put on the box at least 40000, then on the lower box put 50000 to 70000, then you all set. And by the way you should have Radeon Driver 20.4.2

I guess that's not what he meant....

I don't think such an auto-disable-option exist in PhoenixMiner. Once hashrate hits 0 miner automatically restarts. You can, however use -gpus option to disable mining certain coin (ETC?) on 4GB cards and then start another instance of PhoenixMiner selecting them to mine other coins with lower DAG size (ETH with lower epoch). My 4GB 470 and 570 are mining ETH with exactly same speeds for past 2 years. Just updated drivers to recommended ones.

Regards,
zeezoo
hero member
Activity: 2114
Merit: 562
Does anyone know if Phoenix can auto-ignore unsuitable GPUs?

When DAG allocation fails, I just want it to keep mining on the GPUs that have enough RAM. This is useful for automated benchmarking: just mine on the GPUs that work.

Some miners automatically exclude GPUs that are unsuitable for mining. Phoenix doesn't, though.

First of all, what you are using? if RX 500 series you are capable of using Phoenix miner 5.0e but make sure that you increase your Virtual Memory, how to do it, just go to my computer, property then advance system setting,  under performance select setting, go to advance, you can there the virtual memory, click change, uncheck the automatically manage paging size, click custom size, then put on the box at least 40000, then on the lower box put 50000 to 70000, then you all set. And by the way you should have Radeon Driver 20.4.2
full member
Activity: 269
Merit: 102
Has anyone modified their RX 5600 XT memory timings with straps yet? I am experimenting on that and wanted to get some input from someone who has done this already.
newbie
Activity: 15
Merit: 0
Does anyone know if Phoenix can auto-ignore unsuitable GPUs?

When DAG allocation fails, I just want it to keep mining on the GPUs that have enough RAM. This is useful for automated benchmarking: just mine on the GPUs that work.

Some miners automatically exclude GPUs that are unsuitable for mining. Phoenix doesn't, though.
newbie
Activity: 1
Merit: 0
Hello.

Can PhoenixMiner follow GPU Memory temperature? I red the GDDR6 specification and maximum operating temperature is 95C and AMD lets it go beyond it. Furthermore I would like the memory to run always "cool" at about 80C.

To be more precise I would like to follow the Memory temperature, increase fan speed if too hot and eventually throttle calculation down to spare the GDDR6 memories. The maximum fan speed before throttling could also be parametrized.

Nice miner btw, I am new to the business.  Grin
newbie
Activity: 25
Merit: 0
Hi, I'm having problem on one my rig with 5 GTX 1070/1070Ti and PhoenixMiner v5.1c. Rig is crashing every time while DAG file is created. On other rigs with 4 GPU I do not have problems with Rigs crashing. Also Clay is working without problem on this rig with 5GPUs. I would like to use PhoenixMiner but I do not know what is the problem. Also I've tried few nVidia drivers no difference. This Rig was off for last year and I've started back mining few days ago. Does someone have idea what could be problem with this Rig? Thanks

Just quick update, in my case problem was faulty riser card. After replacing with new one PhoenixMiner is working just fine. But only what is really confusing how Clay was working with faulty riser when PhoenixMiner didn't want even to start.

i notice claymore using less power

Not in my case, for me they are almost the same.
newbie
Activity: 12
Merit: 0
So, with -straps 2 on my 1080ti, I get around 48 mh/s on the MINER, but the reported hashrate on the pool (2miners) is only 35 mh/s
On average hashrate on the pool, 35mh/s too

So it does not work well ?

How you managed to run the miner with -straps 2. When I try to use it it give me an error message?

Launch bat file from CMD in administrator mode

Already tried that, but it gives me an error that phoenixminer.exe is not a recognised command.

right click on phoenixminer.exe, select properties,click on the compatibility tab, check run as admin.
                              or
include the full path to phoenixminer.exe in you bat file. (c:\folderwherephoenixminer.exe is\phoenixminer.exe ). run cmd as admin, then you bat file



I tried all the steps everyone has provided and I still get "Invalid option: -straps" or "Invalid option: - nvmem" when I try to put those commands on the batch file

Can someone please give any directions on where I'm making a mistake?
Jump to: