Bitcoin Forum
August 21, 2018, 02:52:17 PM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 [29] 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 ... 121 »
  Print  
Author Topic: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)  (Read 82297 times)
Tranzius
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
February 17, 2018, 10:04:05 AM
 #561

Currently running 2.7a on two rigs - 1xNividia and 1x AMD without a single crash. 64hours nonstop and running very well.

Speed is better and stale shares lower than Claymore. So far very good.

Keep up the good work guys!
1534863137
Hero Member
*
Offline Offline

Posts: 1534863137

View Profile Personal Message (Offline)

Ignore
1534863137
Reply with quote  #2

1534863137
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
flatounet
Jr. Member
*
Offline Offline

Activity: 54
Merit: 0


View Profile
February 17, 2018, 01:27:34 PM
 #562

Currently running 2.7a on two rigs - 1xNividia and 1x AMD without a single crash. 64hours nonstop and running very well.

Speed is better and stale shares lower than Claymore. So far very good.

Keep up the good work guys!

yup , watchdog work fine ,phoenix 2.7a working fine , ( i desactivated a gpu in windows/hardware )
phoenix found a probleme and restart , good.

but i dont have see security about T°c  limit ,when a card reach 90°C
stop made it minnning for 5 minutes for cold down & restart it ?

im a bit crazy but i will leave rig 3 weeks .....

got usb watchdog key working fine , phoenix have watchdog for GPU ....
sonoff for restart rig when probleme

just "need" GPU T° check for security / dont burn/kill it ....
Reckle55
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 17, 2018, 03:32:08 PM
 #563

Where can I download 2.6 without WIN10 Defender Trojan alerts, please advise.
flatounet
Jr. Member
*
Offline Offline

Activity: 54
Merit: 0


View Profile
February 17, 2018, 04:04:52 PM
 #564

Where can I download 2.6 without WIN10 Defender Trojan alerts, please advise.

disable AV ,download + install miner , exclude folder of miner ,start AV ...

or exclude signature ...
KougarLOB
Member
**
Offline Offline

Activity: 120
Merit: 15


View Profile
February 17, 2018, 06:02:00 PM
 #565

I have seen a small 1.5-2% speed improvement poolside over Claymore 11.0 on my Nvidia 1060 rig.  Thank you.

My RX-480 cards are also 2-5% faster but not enough improvement to keep them on Ethash.  Their MH/s output has dropped 33% in the last few months.  Flashed a few BIOs and tweeked with Afterburner.  Is there a magic bullet to regain old speeds to 480s or is this the new norm for ETH algo?

1ER7JwEjpjQfm4qaTxy6EaNdNy8MqzP1pt  Smiley
themurph2k
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
February 17, 2018, 06:59:40 PM
 #566

Getting "debugger detected" crash no matter what settings I try.

AMD aug23 blockchain drivers
All AMD cards (2x rx580, 4x rx570)
I tried using the -amd switch.

Tried Phoenix Miner v2.6 and v2.5d

Please help. I'd really like to use your miner.

All software installed on my system:
https://image.ibb.co/cD0mbS/software.png

Update: I uninstalled Python. Still getting error.
Sandal_Hat
Full Member
***
Offline Offline

Activity: 420
Merit: 118


View Profile
February 17, 2018, 07:00:54 PM
 #567

Currently running 2.7a on two rigs - 1xNividia and 1x AMD without a single crash. 64hours nonstop and running very well.

Speed is better and stale shares lower than Claymore. So far very good.

Keep up the good work guys!

How much faster are we talking about?

Selling 100 dollar coupons (8units expire 11th June, 14 units expire 1st july) and 125 dollar coupon (2 unit exp 30th June). Selling at 20% of value
BennyT
Full Member
***
Offline Offline

Activity: 269
Merit: 108


View Profile
February 17, 2018, 07:52:20 PM
 #568

Currently running 2.7a on two rigs - 1xNividia and 1x AMD without a single crash. 64hours nonstop and running very well.

Speed is better and stale shares lower than Claymore. So far very good.

Keep up the good work guys!

How much faster are we talking about?

1-1.5% faster with a lower dev fee. Temps also 1 degree cooler vs claymore
junkstory
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
February 17, 2018, 07:55:58 PM
 #569

I take back my doubts from my previous posts. After 36 hours of running Phoenix with several rigs and looking at charts on ethermine, I can say with great certainty that Phoenix is indeed better than Claymore:

1) With Phoenix, the Effective Hashrate zig zags across the Reported Hashrate very closely (which by the way, is already slightly higher than Claymore's Reported Hashrate).
2) With Claymore, the Effective Hashrate line would be underneath the Reported Hashrate more often than not. It also fluctuates a lot.
3) With some cards, Phoenix run about 1 degree Celsius cooler.
4) The lower dev fee is very welcoming

I'm a developer myself, and I can understand/appreciate why the Phoenix Miner is better from an engineering perspective. Simply put, the Claymore Miner has grown to become a big messy code base with many features. It supports many alt coins not just for one, but two platforms (Windows + Linux). With Phoenix, the developers can dedicate their time on optimizing Ethereum mining. No gimmicks. I truly hope that Phoenix will continue to improve on the speed optimizations, and not worry about dual mining, Linux, etc.

Keep up the great work Phoenix Developers.
BennyT
Full Member
***
Offline Offline

Activity: 269
Merit: 108


View Profile
February 17, 2018, 08:17:08 PM
 #570

^ great post junk story!

Still respect for Claymore, they’ve been huge for the mining community. Although they kept the 2.0% fee active for too long. They finally dropped the dual mining fee but it was too late and 1% given the scale of how large the mining community is now, is still too much. Good job for Phoenix for introducing a better product with a lower fee.
Lebaaaron
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
February 18, 2018, 12:12:00 AM
 #571

Where's the 2.7?
Lebaaaron
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
February 18, 2018, 02:38:42 AM
 #572

Where's the 2.7?

We all thought you were writing it.
What's the hold up.

 Huh

some people seems to test it already 2.7a
tenmoi
Jr. Member
*
Offline Offline

Activity: 54
Merit: 0


View Profile
February 18, 2018, 04:24:46 AM
 #573

Running 2.7a for 20 minutes now without crashing. Previously it BSODed windows less than a minute after starting. Had to add the command mi 8. Hash rate is lower at 173. Claymore registers 175. Anyway Phoenix reports much higher hashrate at the pool: greater than 190 so I’m happy. Why is effective hashrate higher than local one?

My specs: Windows 10 pro, 6 x msi rx 570 gaming x 4G.
janding
Jr. Member
*
Offline Offline

Activity: 136
Merit: 0


View Profile
February 18, 2018, 04:37:11 AM
 #574

Running 2.7a for 20 minutes now without crashing. Previously it BSODed windows less than a minute after starting. Had to add the command mi 8. Hash rate is lower at 173. Claymore registers 175. Anyway Phoenix reports much higher hashrate at the pool: greater than 190 so I’m happy. Why is effective hashrate higher than local one?

My specs: Windows 10 pro, 6 x msi rx 570 gaming x 4G.

20 minutes does not reflect an accurate hash rate at the pool.
It will level out after a few hours. Give it 24 at least.
Your pool hash rate will not be higher than the local hash rate over time.
You're simply getting lucky at the moment.
axe0911
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
February 18, 2018, 04:51:45 AM
 #575

Truly a great miner.

I have been facing a challenge when one of the GPU hangs, the miner does not restart.

It gives an error that reboot.bat couldn't be located.

Also, why is the GPU hanging ?

Code:
17580:04:04:52.516: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:04:52.516: eths Eth: New job #289abbab from asia1.ethermine.org:4444; diff: 4000MH
17580:04:04:52.990: main Eth speed: 57.131 MH/s, shares: 284/0/0, time: 5:16
17580:04:04:52.990: main GPUs: 1: 28.367 MH/s (142) 2: 28.763 MH/s (142)
17580:04:04:59.633: main Eth speed: 56.980 MH/s, shares: 284/0/0, time: 5:16
17580:04:04:59.633: main GPUs: 1: 28.374 MH/s (142) 2: 28.606 MH/s (142)
17580:04:04:59.677: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x36496db","0xdf1e1ca4401117200633d5a343be0ae9c05e3d9e630c497b76f2409afb2b402e"]}

17580:04:04:59.772: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17580:04:05:04.687: main Eth speed: 22.871 MH/s, shares: 284/0/0, time: 5:16
17580:04:05:04.687: main GPUs: 1: 0.000 MH/s (142) 2: 22.871 MH/s (142)
17580:04:05:08.344: main GPU1: 59C 17%, GPU2: 67C 17%
17580:04:05:09.686: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:09.766: main Eth speed: 28.610 MH/s, shares: 284/0/0, time: 5:16
17580:04:05:09.766: main GPUs: 1: 0.000 MH/s (142) 2: 28.610 MH/s (142)
17580:04:05:09.778: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:14.845: main Eth speed: 28.609 MH/s, shares: 284/0/0, time: 5:16
17580:04:05:14.845: main GPUs: 1: 0.000 MH/s (142) 2: 28.609 MH/s (142)
17580:04:05:19.687: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:19.687: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x34c999c","0xdf1e1ca4401117200633d5a343be0ae9c05e3d9e630c497b76f2409afb2b402e"]}

17580:04:05:19.781: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:19.873: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:19.873: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17580:04:05:19.923: main  
17580:04:05:19.923: main Eth: Mining ETH on asia1.ethermine.org:4444
17580:04:05:19.923: main Eth speed: 28.607 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:19.923: main GPUs: 1: 0.000 MH/s (142) 2: 28.607 MH/s (142)
17580:04:05:19.923: main Eth: Accepted shares 284 (8 stales), rejected shares 0 (0 stales)
17580:04:05:19.923: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 2.82%
17580:04:05:19.923: main Eth: Maximum difficulty of found share: 1274.3 GH (!)
17580:04:05:19.923: main Eth: Average speed (5 min): 54.926 MH/s
17580:04:05:19.923: main Eth: Effective speed: 59.71 MH/s; at pool: 59.71 MH/s
17580:04:05:19.923: main  
17580:04:05:25.002: main Eth speed: 28.243 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:25.002: main GPUs: 1: 0.000 MH/s (142) 2: 28.243 MH/s (142)
17580:04:05:29.688: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:29.782: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:30.096: main Eth speed: 28.617 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:30.096: main GPUs: 1: 0.000 MH/s (142) 2: 28.617 MH/s (142)
17580:04:05:35.175: main Eth speed: 28.605 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:35.175: main GPUs: 1: 0.000 MH/s (142) 2: 28.605 MH/s (142)
17580:04:05:36.394: main GPU1: 54C 17%, GPU2: 67C 17%
17580:04:05:39.689: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:39.689: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x32eb4a9","0xdf1e1ca4401117200633d5a343be0ae9c05e3d9e630c497b76f2409afb2b402e"]}

17580:04:05:39.783: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:39.876: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:39.876: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17580:04:05:40.285: main Eth speed: 28.604 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:40.285: main GPUs: 1: 0.000 MH/s (142) 2: 28.604 MH/s (142)
17580:04:05:45.364: main Eth speed: 28.601 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:45.364: main GPUs: 1: 0.000 MH/s (142) 2: 28.601 MH/s (142)
17580:04:05:49.690: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:49.783: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:50.442: main Eth speed: 28.606 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:50.442: main GPUs: 1: 0.000 MH/s (142) 2: 28.606 MH/s (142)
17580:04:05:54.128: wdog GPU1 not responding
17580:04:05:54.128: wdog Thread(s) not responding. Restarting.
17580:04:05:55.552: main Eth speed: 28.604 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:55.552: main GPUs: 1: 0.000 MH/s (142) 2: 28.604 MH/s (142)
PhoenixMiner
Jr. Member
*
Offline Offline

Activity: 133
Merit: 6


View Profile
February 18, 2018, 05:19:24 AM
 #576

i think im in error ,but i see miner restard because low hash....
i removed -minRigSpeed 129  after , and now ,no anymore probleme .....
  The -minRigSpeed option works with 5 minutes average hashrate. It doesn't care about the effective hashrate, because it can be quite random. So if the 5 min average hashrate speed drops under 129 MH/s in your case, the miner will be restarted. To avoid unnecessary restarting, put this option to your normal hashrate minus about half of one card's hasrate. I.e. if your normal hashrate is 132 MH/s with 5 GPUs, set -minRigSpeed 119

This will be work  (-cclock 1150 -mclock 2170 -cvddc 850 -mvddc 850)  with this minner??? Or how to set the clocks?Huh
  There is no support for these options yet. We are working on it and it will be released in version 2.7b.

2.7 has almost 2x more stales then 2.6
  There is no reason for that - should be the same or slightly lower. We have seen some wild variations on stales because of luck (when the average block time drops and a few blocks are found in quick succession there are a lot more stale shares). We will include pool stats in a later version to show the average round time, latencly, etc.

yup , watchdog work fine ,phoenix 2.7a working fine , ( i desactivated a gpu in windows/hardware )
phoenix found a probleme and restart , good.

but i dont have see security about T°c  limit ,when a card reach 90°C
stop made it minnning for 5 minutes for cold down & restart it ?

im a bit crazy but i will leave rig 3 weeks .....

got usb watchdog key working fine , phoenix have watchdog for GPU ....
sonoff for restart rig when probleme

just "need" GPU T° check for security / dont burn/kill it ....
  You mean like -tstop and -tstart options of Claymore? We will try to include these in 2.7.

I have seen a small 1.5-2% speed improvement poolside over Claymore 11.0 on my Nvidia 1060 rig.  Thank you.

My RX-480 cards are also 2-5% faster but not enough improvement to keep them on Ethash.  Their MH/s output has dropped 33% in the last few months.  Flashed a few BIOs and tweeked with Afterburner.  Is there a magic bullet to regain old speeds to 480s or is this the new norm for ETH algo?
  33% drop in hashrates? It looks like you are not using the blockchain driver (or the newest AMD drivers switched to COMPUTE mode). Please google AMD blockchain driver and install it (after removing the current driver with DDU).

Huh
some people seems to test it already 2.7a
  You can find 2.7a in this post: https://bitcointalk.org/index.php?topic=2647654.msg30259176#msg30259176 but please note that it is a beta release - do not try it on a large scale (i.e. multple rigs). We test each beta version for at least 12-24 hours on about a dozen testing rigs with various GPUs but the configurations in the field are much more diverse than our test rigs so some errors can't be found in this testing.


Truly a great miner.

I have been facing a challenge when one of the GPU hangs, the miner does not restart.

It gives an error that reboot.bat couldn't be located.

Also, why is the GPU hanging ?

Code:
17580:04:04:52.516: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:04:52.516: eths Eth: New job #289abbab from asia1.ethermine.org:4444; diff: 4000MH
17580:04:04:52.990: main Eth speed: 57.131 MH/s, shares: 284/0/0, time: 5:16
17580:04:04:52.990: main GPUs: 1: 28.367 MH/s (142) 2: 28.763 MH/s (142)
17580:04:04:59.633: main Eth speed: 56.980 MH/s, shares: 284/0/0, time: 5:16
17580:04:04:59.633: main GPUs: 1: 28.374 MH/s (142) 2: 28.606 MH/s (142)
17580:04:04:59.677: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x36496db","0xdf1e1ca4401117200633d5a343be0ae9c05e3d9e630c497b76f2409afb2b402e"]}

17580:04:04:59.772: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17580:04:05:04.687: main Eth speed: 22.871 MH/s, shares: 284/0/0, time: 5:16
17580:04:05:04.687: main GPUs: 1: 0.000 MH/s (142) 2: 22.871 MH/s (142)
17580:04:05:08.344: main GPU1: 59C 17%, GPU2: 67C 17%
17580:04:05:09.686: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:09.766: main Eth speed: 28.610 MH/s, shares: 284/0/0, time: 5:16
17580:04:05:09.766: main GPUs: 1: 0.000 MH/s (142) 2: 28.610 MH/s (142)
17580:04:05:09.778: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:14.845: main Eth speed: 28.609 MH/s, shares: 284/0/0, time: 5:16
17580:04:05:14.845: main GPUs: 1: 0.000 MH/s (142) 2: 28.609 MH/s (142)
17580:04:05:19.687: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:19.687: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x34c999c","0xdf1e1ca4401117200633d5a343be0ae9c05e3d9e630c497b76f2409afb2b402e"]}

17580:04:05:19.781: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:19.873: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:19.873: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17580:04:05:19.923: main  
17580:04:05:19.923: main Eth: Mining ETH on asia1.ethermine.org:4444
17580:04:05:19.923: main Eth speed: 28.607 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:19.923: main GPUs: 1: 0.000 MH/s (142) 2: 28.607 MH/s (142)
17580:04:05:19.923: main Eth: Accepted shares 284 (8 stales), rejected shares 0 (0 stales)
17580:04:05:19.923: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 2.82%
17580:04:05:19.923: main Eth: Maximum difficulty of found share: 1274.3 GH (!)
17580:04:05:19.923: main Eth: Average speed (5 min): 54.926 MH/s
17580:04:05:19.923: main Eth: Effective speed: 59.71 MH/s; at pool: 59.71 MH/s
17580:04:05:19.923: main  
17580:04:05:25.002: main Eth speed: 28.243 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:25.002: main GPUs: 1: 0.000 MH/s (142) 2: 28.243 MH/s (142)
17580:04:05:29.688: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:29.782: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:30.096: main Eth speed: 28.617 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:30.096: main GPUs: 1: 0.000 MH/s (142) 2: 28.617 MH/s (142)
17580:04:05:35.175: main Eth speed: 28.605 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:35.175: main GPUs: 1: 0.000 MH/s (142) 2: 28.605 MH/s (142)
17580:04:05:36.394: main GPU1: 54C 17%, GPU2: 67C 17%
17580:04:05:39.689: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:39.689: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x32eb4a9","0xdf1e1ca4401117200633d5a343be0ae9c05e3d9e630c497b76f2409afb2b402e"]}

17580:04:05:39.783: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:39.876: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:39.876: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17580:04:05:40.285: main Eth speed: 28.604 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:40.285: main GPUs: 1: 0.000 MH/s (142) 2: 28.604 MH/s (142)
17580:04:05:45.364: main Eth speed: 28.601 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:45.364: main GPUs: 1: 0.000 MH/s (142) 2: 28.601 MH/s (142)
17580:04:05:49.690: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17580:04:05:49.783: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x289abbab48807a4927ff272c8d39ff2d1460bd952c7228c4c98536ca6a554c44","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4df57e"]}
17580:04:05:50.442: main Eth speed: 28.606 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:50.442: main GPUs: 1: 0.000 MH/s (142) 2: 28.606 MH/s (142)
17580:04:05:54.128: wdog GPU1 not responding
17580:04:05:54.128: wdog Thread(s) not responding. Restarting.
17580:04:05:55.552: main Eth speed: 28.604 MH/s, shares: 284/0/0, time: 5:17
17580:04:05:55.552: main GPUs: 1: 0.000 MH/s (142) 2: 28.604 MH/s (142)
  Please check your command-line options: if you have -rmode 2 (or -r 1), remove it as it forces the miner to try and run the reboot.bat file in the same folder as the miner instead of just restarting the PhoenixMiner.exe with the same options. As for the reason for freezing of GPU1, it is either too high clocks or too low voltage (or combination of both). Please note the the current version of PhoenixMiner doesn't support the hardware control options (-cvddc, -mvddc, etc.). They will be added in the upcoming 2.7b and for now you have to rely on third-party program for controlling the clocks and voltages of the GPUs.

tenmoi
Jr. Member
*
Offline Offline

Activity: 54
Merit: 0


View Profile
February 18, 2018, 06:42:42 AM
 #577

Phoenixminer,
My rig config: win 10 pro, 6 x msi 570 gaming x 4G, mining at Nanopool, mclock 2030, vcddc 870, cclock 1100, vcore 950, fan 80%.

Miners 2.6 and 2.7a both crash win, BSOD. Claymore doesn’t, but it resets the voltages and clocks after sometime after the decree sessions I guess. Now I’m running 2.7a with -mi 8. This reduces the local hashrate to around 173 from 175 of claymore.

Please look into this issue.

Thank you.

After 4 hours and a half it stopped: error debugger detected. Running claymore again now.
yyyam2
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
February 18, 2018, 07:28:46 AM
 #578

Phoenixminer,
My rig config: win 10 pro, 6 x msi 570 gaming x 4G, mining at Nanopool, mclock 2030, vcddc 870, cclock 1100, vcore 950, fan 80%.

Miners 2.6 and 2.7a both crash win, BSOD. Claymore doesn’t, but it resets the voltages and clocks after sometime after the decree sessions I guess. Now I’m running 2.7a with -mi 8. This reduces the local hashrate to around 173 from 175 of claymore.

Please look into this issue.

Thank you.

Try give them more voltage and test the miner first. If you can run for 24hrs stable, try decrease the voltage. For my experience, the claymore hardware control is not so stable. I am now using overdrivetools to control. It 's easy to use.
xinomahc
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
February 18, 2018, 07:35:06 AM
 #579

...

Hi, im trying to make a simple script to get stats from Phoenix's API... but unlike claymore or others... When i make the SAME TCP CALL to Pheonix as I do on other miners... the call just hangs forever... and does not come back with any info... whats up with that?


Code:
using (var socket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp))
            {
                socket.Connect("localhost", 3333);
                socket.Send(Encoding.ASCII.GetBytes("{\"id\":0,\"jsonrpc\":\"2.0\",\"method\":\"miner_getstat1\"}"));
                socket.Receive(receiveBytes, receiveBytes.Length, SocketFlags.None);
            }
            var resp = Encoding.ASCII.GetString(receiveBytes);

My small sample to pull claymore's stats

... in Phoenix the socket.Receive just hangs forever

Regards and thanks for the miner software Smiley
tenmoi
Jr. Member
*
Offline Offline

Activity: 54
Merit: 0


View Profile
February 18, 2018, 07:38:00 AM
 #580

Phoenixminer,
My rig config: win 10 pro, 6 x msi 570 gaming x 4G, mining at Nanopool, mclock 2030, vcddc 870, cclock 1100, vcore 950, fan 80%.

Miners 2.6 and 2.7a both crash win, BSOD. Claymore doesn’t, but it resets the voltages and clocks after sometime after the decree sessions I guess. Now I’m running 2.7a with -mi 8. This reduces the local hashrate to around 173 from 175 of claymore.

Please look into this issue.

Thank you.

Try give them more voltage and test the miner first. If you can run for 24hrs stable, try decrease the voltage. For my experience, the claymore hardware control is not so stable. I am now using overdrivetools to control. It 's easy to use.

Then Phoenix draws more power than claymore with reduced hashrate. I’ll wait. Thanks for the tip.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 [29] 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 ... 121 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!