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

Pm 3.0c working on my rig 36h

PhoenixMiner can you please add feature to check graphic cards wattage like Bminer did with their miner?

guys i need to restart .bat file for phoenix miner..i dont know how i must make?can you explain and send me examples pls..i want my rigs restart when miner freeze or something like that..i looked everywhere and  confused already.. ty

you need this to get the hash rate bakc with the new drivers or turn on compute under workload in the game section of the driver andf afterburner 4.5 has finally been fixed works with all AMD drivers again with rigs 4 or more cards .
I'm sharing it from my google drive because i forgot were i got it form

https://drive.google.com/file/d/1leSgKMvTltAba8pp3FS_LTSh4iE_7Gmz/view?usp=sharing

I'm no newbie on the forums my other account was hacked and i can't get it back .

Hi to all, I have a little problem with phenixminer, I try 3.0a , b and c

Actually I use claymore with mi rig ( 5x rx580 8gb) and the hashrate for any card is about 31.2 to 32 mh/s with a consumption about 87w for card with driver amd for blockchain; card are not flashed, original bios

If I try phenixminer, but  the consumption go to 135w/card.
I read to change driver wiht latest version (adrenalin) , but the hash rate go down to 18 mh/s

What's the problem ?

Thanks in advance

you have an idea how to use the rig with tablet

   Not a stupid request at all. We are going to add such feature in one of the later releases.


   Please try to specify -nvf 3 and/or -nvnew 0 to fix the problem.


   Generally auto-tuning is supposed to be used only in the period of initial tuning of the rig, or after the OC settings are changed, or after other significant changes (e.g. new kernels, trying out -clkernel 2 and so on). After that you can press the 's' key in the console or check the miner console output from the remote manager and see the auto-tuned GT values, and copy them into your config.txt for permanent usage. However we can add a command-line option to append the found best -gt values to the config.txt file in a future version.

   Make sure that the AMD Compute mode is turned on. PhoenixMiner will print a warning on startup if a card supports Compute mode but it is not turned on (or you are using too old drivers that doesn't support Compute mode). Another possibility is that you are using older cards like 280X or 970, which have a steep drop off in hashrate on bigger DAG and there is no workaround for this. In such case you are better off mining Pirl or some other ethash coin with small DAG instead of using Nicehash.

   Thanks a lot, much appreciated


   Yes, the OC settings work reliably only on 18.x.x drivers.

   Auto-tune has no effect on Nvidia cards. Could you please send us logs from the crashes on 1080ti?

   Can you tell us what cards are having problems and what drivers you are using?

   This is highly unusual, perhaps some temporary problem with the pool. Please send us a log to be able to diagnose the problem any further.

   Yes, at least a generic Linux version should be ready in about a month. 

Thank you author. I have 7*1080ti work without problems, 390mH/s, with a tablet.

https://b.radikal.ru/b19/1806/4b/71c3cf073049.png

2018.06.02:19:55:25.574: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x8577d571d380bb455a2009be9efc8a85f54681ac73e5433aa3dd6c9e0d7d6ee8","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574adf"]}
2018.06.02:19:55:26.465: main Eth speed: 182.769 MH/s, shares: 4070/0/0, time: 25:02
2018.06.02:19:55:26.465: main GPUs: 1: 30.552 MH/s (680) 2: 30.317 MH/s (653) 3: 30.573 MH/s (690) 4: 30.578 MH/s (692) 5: 30.250 MH/s (686) 6: 30.499 MH/s (669)
2018.06.02:19:55:26.624: GPU2 Eth: GPU2: ETH share found!
2018.06.02:19:55:26.624: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xb58994edc6011b45","0x8577d571d380bb455a2009be9efc8a85f54681ac73e5433aa3dd6c9e0d7d6ee8","0xcb0919ddf7213e414a3231ddab780c97230fcdcc554d04d4e2ab1d83820085e7"]}

2018.06.02:19:55:26.624: eths Eth: Share actual difficulty: 100.8 GH (!)
2018.06.02:19:55:26.670: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.06.02:19:55:26.670: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
2018.06.02:19:55:26.670: eths Eth: Share accepted in 46 ms
2018.06.02:19:55:31.544: main Eth speed: 182.648 MH/s, shares: 4071/0/0, time: 25:02
2018.06.02:19:55:31.544: main GPUs: 1: 30.396 MH/s (680) 2: 30.331 MH/s (654) 3: 30.577 MH/s (690) 4: 30.576 MH/s (692) 5: 30.272 MH/s (686) 6: 30.496 MH/s (669)
2018.06.02:19:55:35.529: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.06.02:19:55:35.575: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x8577d571d380bb455a2009be9efc8a85f54681ac73e5433aa3dd6c9e0d7d6ee8","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574adf"]}
2018.06.02:19:55:36.623: main Eth speed: 182.646 MH/s, shares: 4071/0/0, time: 25:02
2018.06.02:19:55:36.623: main GPUs: 1: 30.402 MH/s (680) 2: 30.333 MH/s (654) 3: 30.578 MH/s (690) 4: 30.574 MH/s (692) 5: 30.410 MH/s (686) 6: 30.348 MH/s (669)
2018.06.02:19:55:38.451: main GPU1: 59C 50%, GPU2: 61C 70%, GPU3: 59C 57%, GPU4: 59C 43%, GPU5: 59C 56%, GPU6: 59C 47%
2018.06.02:19:55:41.701: main Eth speed: 182.493 MH/s, shares: 4071/0/0, time: 25:02
2018.06.02:19:55:41.701: main GPUs: 1: 30.423 MH/s (680) 2: 30.321 MH/s (654) 3: 30.418 MH/s (690) 4: 30.572 MH/s (692) 5: 30.412 MH/s (686) 6: 30.347 MH/s (669)
2018.06.02:19:55:45.530: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.06.02:19:55:45.530: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xae45362","0x37967872ac784c54b7dc4a3920f908d8d184317d717faabff497c62e177c0c23"]}

2018.06.02:19:55:45.576: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x8577d571d380bb455a2009be9efc8a85f54681ac73e5433aa3dd6c9e0d7d6ee8","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574adf"]}
2018.06.02:19:55:46.811: main Eth speed: 182.616 MH/s, shares: 4071/0/0, time: 25:02
2018.06.02:19:55:46.811: main GPUs: 1: 30.565 MH/s (680) 2: 30.320 MH/s (654) 3: 30.418 MH/s (690) 4: 30.575 MH/s (692) 5: 30.410 MH/s (686) 6: 30.328 MH/s (669)
2018.06.02:19:55:51.890: main Eth speed: 182.799 MH/s, shares: 4071/0/0, time: 25:02
2018.06.02:19:55:51.890: main GPUs: 1: 30.555 MH/s (680) 2: 30.320 MH/s (654) 3: 30.437 MH/s (690) 4: 30.577 MH/s (692) 5: 30.412 MH/s (686) 6: 30.496 MH/s (669)
2018.06.02:19:55:53.052: GPU2 Eth: GPU2: ETH share found!
2018.06.02:19:55:53.052: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0xb58994ee53e8d5c4","0x8577d571d380bb455a2009be9efc8a85f54681ac73e5433aa3dd6c9e0d7d6ee8","0xf98ba9b7ca3a2c0f50213adb5359d761f5dd1b8d2e0293e5dee5770f262c4d56"]}

2018.06.02:19:55:53.052: eths Eth: Share actual difficulty: 6287 MH
2018.06.02:19:55:53.099: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.06.02:19:55:53.099: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
2018.06.02:19:55:53.099: eths Eth: Share accepted in 47 ms
2018.06.02:19:55:55.531: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.06.02:19:55:55.578: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x8577d571d380bb455a2009be9efc8a85f54681ac73e5433aa3dd6c9e0d7d6ee8","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574adf"]}
2018.06.02:19:55:56.984: main Eth speed: 182.939 MH/s, shares: 4072/0/0, time: 25:02
2018.06.02:19:55:56.984: main GPUs: 1: 30.552 MH/s (680) 2: 30.321 MH/s (655) 3: 30.580 MH/s (690) 4: 30.579 MH/s (692) 5: 30.410 MH/s (686) 6: 30.497 MH/s (669)
2018.06.02:19:55:57.253: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x1190c10dc6a9b3c6018b82ac10d08729d6e798e96954241afec6f7cdd49b5327","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574ae0"]}
2018.06.02:19:55:57.253: eths Eth: New job #1190c10d from ssl://eu1.ethermine.org:5555; diff: 4000MH
2018.06.02:19:55:57.890: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x1bfbef1a7b2eb6faf830e43a85a1b5a5daa42b75eaf76ec70f6ae6874071853e","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574ae0"]}
2018.06.02:19:55:57.890: eths Eth: New job #1bfbef1a from ssl://eu1.ethermine.org:5555; diff: 4000MH
2018.06.02:19:56:00.246: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xb01f02d8563dd5d552ea68003209c1327753c409220cacb761886258365132f6","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574ae1"]}
2018.06.02:19:56:00.246: eths Eth: New job #b01f02d8 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2018.06.02:19:56:02.063: main 
2018.06.02:19:56:02.063: main *** 25:02 ***************************************************
2018.06.02:19:56:02.063: main Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 25:02
2018.06.02:19:56:02.063: main Eth speed: 182.780 MH/s, shares: 4072/0/0, time: 25:02
2018.06.02:19:56:02.063: main GPUs: 1: 30.551 MH/s (680) 2: 30.320 MH/s (655) 3: 30.575 MH/s (690) 4: 30.434 MH/s (692) 5: 30.405 MH/s (686) 6: 30.494 MH/s (669)
2018.06.02:19:56:02.063: main Eth: Accepted shares 4072 (1 stales), rejected shares 0 (0 stales)
2018.06.02:19:56:02.063: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.02%
2018.06.02:19:56:02.063: main Eth: Maximum difficulty of found share: 26.1 TH (!!!)
2018.06.02:19:56:02.063: main Eth: Average speed (5 min): 182.751 MH/s
2018.06.02:19:56:02.063: main Eth: Effective speed: 180.64 MH/s; at pool: 180.64 MH/s
2018.06.02:19:56:02.063: main 
2018.06.02:19:56:05.532: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.06.02:19:56:05.532: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xae49005","0x37967872ac784c54b7dc4a3920f908d8d184317d717faabff497c62e177c0c23"]}

2018.06.02:19:56:05.579: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xb01f02d8563dd5d552ea68003209c1327753c409220cacb761886258365132f6","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574ae1"]}
2018.06.02:19:56:06.938: main GPU1: 59C 50%, GPU2: 61C 69%, GPU3: 59C 56%, GPU4: 59C 43%, GPU5: 59C 56%, GPU6: 59C 47%
2018.06.02:19:56:07.141: main Eth speed: 182.758 MH/s, shares: 4072/0/0, time: 25:02
2018.06.02:19:56:07.141: main GPUs: 1: 30.554 MH/s (680) 2: 30.318 MH/s (655) 3: 30.574 MH/s (690) 4: 30.417 MH/s (692) 5: 30.404 MH/s (686) 6: 30.491 MH/s (669)
2018.06.02:19:56:12.220: main Eth speed: 182.759 MH/s, shares: 4072/0/0, time: 25:02
2018.06.02:19:56:12.220: main GPUs: 1: 30.556 MH/s (680) 2: 30.319 MH/s (655) 3: 30.573 MH/s (690) 4: 30.417 MH/s (692) 5: 30.402 MH/s (686) 6: 30.492 MH/s (669)
2018.06.02:19:56:15.533: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.06.02:19:56:15.579: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.06.02:19:56:15.580: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xb01f02d8563dd5d552ea68003209c1327753c409220cacb761886258365132f6","0x7538728108738be6e9c6144f1b4c22b5fc45e645bf474d84a4d6ae0fb0e71f59","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x574ae1"]}
2018.06.02:19:56:17.299: main Eth speed: 182.783 MH/s, shares: 4072/0/0, time: 25:03
2018.06.02:19:56:17.299: main GPUs: 1: 30.562 MH/s (680) 2: 30.171 MH/s (655) 3: 30.573 MH/s (690) 4: 30.579 MH/s (692) 5: 30.402 MH/s (686) 6: 30.495 MH/s (669)

Reduce core to -150 (minus 150) or even - 200
Increase mem gradually in 20 increments... I have it at +820. Hashing at 33.2 MH/s

Sorry if this is a stupid request, but would it be possible to add a feature for naming gpu's?  I know you can re-number them, but custom alphanumeric naming might help me take out some frustration on poorly performing cards.

have been trying to use Phoenix on one of my small rigs -- keep getting a variety of cuda errors sometimes including illegal instruction -- with the miner crashing right after start -- it also now has decided not to write logfiles so i don't know what the problem is now -- running win 10  with 4gig ddr3 with  2-1060 3gb 2-1060 6gb 2 r9 280x and 1 rx570 8gb -- currently using claymore with no issues.  Have increased the virtual memory to 60 gig from 30 gig added the -log 2 commands -- still crashes right away -- any suggestions would be appreciated.  The rig is really just a spare parts rig -- but hashes quite well.

ok turns out part of this is win 10 -- lets just say it sucks .

The cuda errors are still happening will run for 20 minutes and then will crash -- running on ubq so dag shoud not be an issue -- cards are overclocked but not by much -- did try it with stock and same thing happens

Possible feature request.

How does PM handle the auto-tune settings? Are they “remembered” in any way? Or do you waste 5-10mins of sub optimal hashrates at the beginning of every time you start the miner?

If they aren’t remembered, maybe you could have the miner auto-append the config.txt or the start.bat file with the optimized gt values? That way you won’t have to auto-tune when simply re-running the miner.

hI!

Anybody know how to mining Daggerhashimoto in Nicehash? Because if Nicehash "send" an small DAG it works at 22-23Mh but when goes to mining ethereum, drop to 8-9Mh.

Thanks.

Wanted to share the stats with the forum. These are the current stats of one of my rigs running on the PhoenixMiner 2.9e:

*** 1142:28 ***************************************************
Eth: Mining ETH on eu1.ethermine.org:4444 for 80:00
Available GPUs for mining:
GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU2: Radeon RX 580 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU3: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU4: Radeon RX 580 Series (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU5: Radeon RX 580 Series (pcie 9), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU6: Radeon RX 580 Series (pcie 10), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU7: Radeon RX 580 Series (pcie 12), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU8: Radeon RX 580 Series (pcie 13), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU9: Radeon RX 580 Series (pcie 15), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU10: Radeon RX 580 Series (pcie 16), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU11: Radeon RX 580 Series (pcie 17), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU12: Radeon RX 580 Series (pcie 18), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU13: Radeon RX 580 Series (pcie 19), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU1: 54C 92%, GPU2: 57C 86%, GPU3: 57C 85%, GPU4: 56C 85%, GPU5: 54C 79%, GPU6: 52C 44%, GPU7: 52C 41%, GPU8: 58C 86%, GPU9: 54C 84%, GPU10: 54C 99%, GPU11: 52C 43%, GPU12: 62C 81%, GPU13: 49C 0%
Eth: Accepted shares 407093 (40 stales), rejected shares 3 (0 stales)
Eth: Incorrect shares 169 (0.04%), est. stales percentage 0.01%
Eth: Maximum difficulty of found share: 12954.2 TH (!!!)
Eth: Average speed (5 min): 407.232 MH/s
Eth: Effective speed: 395.92 MH/s; at pool: 395.92 MH/s

PhoenixMiner: If you ever have a moment of doubt about your work... get back to this post. THANKS!

After more tests, it seems auto-tuning IS working ...

But I can't make the -cvddc switch to work
If I run Claymore for a minute, it sets correct core voltage, I stop it and run Phoenix - doesn't matter if I use cvddc or not - it will use what Claymore had set. Same if set with Afterburner.

Are there some requirements for OS/Driver combo in order to use this switch? I tried on 7 and 10, relatively older drivers because I don't update what runs ok.

Moved from 2.9e to 3.0,
Version 3 is ok for my 470s, but crashed for my 1080ti's every couple of 10min with same command line. didnt disable the autotune yet
Tested with Clay 11.7 and Phoenix 2.9e with no issues

I tested v3.0c, some cards dropped 0 hashrate and restart, back to 2.9e.

Hello, im having serius issues with connecting to ethermine pool for devfee shares. Do you have any solution to this?

Hi,

Any plans for linux (hiveos) version?