|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
gameboy366
Jr. Member
 Offline
Activity: 252
Merit: 8
|
 |
May 25, 2018, 06:19:44 PM |
|
Please devs, you are losing a lot of money by not capitalising on linux users. I mine on HiveOS and I have tested Pheonixminer on Win10 and there is no doubt that it is the best ethash miner. There's not much time left for ethash GPU mining, so come up with somethig fast.
|
|
|
|
|
Jbodz83
Newbie
Offline
Activity: 124
Merit: 0
|
|
May 26, 2018, 07:39:24 AM |
|
any plans on doing dual?.
|
|
|
|
|
okiesmokie
Newbie
Offline
Activity: 5
Merit: 0
|
|
May 26, 2018, 01:49:22 PM |
|
Any news on beta?Thx  |
|
|
|
|
sidaliroy
Newbie
Offline
Activity: 23
Merit: 0
|
|
May 26, 2018, 02:46:19 PM |
|
Any news on beta?Thx Yeah it's already the end of the month and the 3.0 beta is not out yet :/ Any info PhoenixMiner? |
|
|
|
|
|
UnclWish
|
|
May 26, 2018, 08:42:21 PM |
|
I think author must make Windows 10 1803 April Update compatibility with new drivers.
AMD Adrenalin 18.5.1 driver normal works with Claymrore's miners...
|
|
|
|
|
|
Iamtutut
|
|
May 27, 2018, 06:25:26 AM |
|
any plans on doing dual?.
Dual mining is dead. XVG just got attacked again. Sia and decred are owned by ASICs...For dual mining, there is claymore. I hope Phoenix won't do the mistake to implement dual mining. |
|
|
|
|
rboer
Newbie
Offline
Activity: 16
Merit: 0
|
|
May 27, 2018, 09:11:22 AM |
|
Got a weird error today after windows update. See below out of mem error. Mining Win10 with 6x 1060 6GB and 16GB PageFile. Resolve it finally by increasing the page file to 24GB. Hope this helps others. 2018.05.27:10:37:56.494: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.27:10:37:56.494: main Cmd line: -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal XXX -proto 3
2018.05.27:10:37:59.271: main Available GPUs for mining:
2018.05.27:10:37:59.272: main GPU1: GeForce GTX 1060 6GB (pcie 1), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU2: GeForce GTX 1060 6GB (pcie 2), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU3: GeForce GTX 1060 6GB (pcie 4), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU4: GeForce GTX 1060 6GB (pcie 6), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU5: GeForce GTX 1060 6GB (pcie 8), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU6: GeForce GTX 1060 6GB (pcie 9), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.283: main NVML library initialized
2018.05.27:10:37:59.506: main Listening for CDM remote manager at port 3333 in read-only mode
2018.05.27:10:37:59.508: main Eth: the pool list contains 4 pools
2018.05.27:10:37:59.508: main Eth: primary pool: eu1.ethermine.org:4444
2018.05.27:10:37:59.508: main Starting GPU mining
2018.05.27:10:37:59.509: wdog Starting watchdog thread
2018.05.27:10:37:59.509: main Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: QtMiner)
2018.05.27:10:37:59.544: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (94.23.36.128)
2018.05.27:10:37:59.544: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["XXX"]}
2018.05.27:10:37:59.573: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.05.27:10:37:59.573: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.05.27:10:37:59.591: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":2018.05.27:10:37:59.591: eths Eth: New job #7d15954f from eu1.ethermine.org:4444; diff: 4000MH
2018.05.27:10:37:59.592: GPU1 GPU1: Starting up... (0)
2018.05.27:10:37:59.592: GPU1 Eth: Generating light cache for epoch #189
2018.05.27:10:37:59.594: GPU2 GPU2: Starting up... (0)
2018.05.27:10:37:59.595: GPU3 GPU3: Starting up... (0)
2018.05.27:10:37:59.598: GPU4 GPU4: Starting up... (0)
2018.05.27:10:37:59.601: GPU5 GPU5: Starting up... (0)
2018.05.27:10:37:59.602: GPU6 GPU6: Starting up... (0)
2018.05.27:10:37:59.711: main GPU1: 38C 0%, GPU2: 35C 0%, GPU3: 37C 0%, GPU4: 46C 0%, GPU5: 42C 0%, GPU6: 42C 0%
2018.05.27:10:38:00.985: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":
2018.05.27:10:38:00.985: eths Eth: New job #992bc07d from eu1.ethermine.org:4444; diff: 4000MH
2018.05.27:10:38:02.597: GPU6 GPU6: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.625: GPU5 GPU5: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.625: GPU1 GPU1: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.662: GPU2 GPU2: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.666: GPU4 GPU4: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.681: GPU6 GPU6: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.715: GPU1 GPU1: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.756: GPU5 GPU5: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.780: GPU4 GPU4: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.805: GPU2 GPU2: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.895: GPU6 GPU6: Generating DAG for epoch #189
2018.05.27:10:38:02.906: GPU3 GPU3: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.941: GPU1 GPU1: Generating DAG for epoch #189
2018.05.27:10:38:02.969: GPU5 GPU5: Generating DAG for epoch #189
2018.05.27:10:38:02.992: GPU4 GPU4: Generating DAG for epoch #189
2018.05.27:10:38:03.020: GPU2 GPU2: Generating DAG for epoch #189
[color=red]2018.05.27:10:38:03.099: GPU3 CUDA error in CudaProgram.cu:377 : out of memory (2)
2018.05.27:10:38:03.103: GPU3 GPU3: CUDA memory: 6.00 GB total, 4.97 GB free
2018.05.27:10:38:03.103: GPU3 GPU3 initMiner error: out of memory
2018.05.27:10:38:03.597: wdog Thread(s) not responding. Restarting.[/color]
2018.05.27:10:38:04.557: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.27:10:38:04.557: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
2018.05.27:10:38:04.592: GPU6 GPU6: DAG 13%
2018.05.27:10:38:04.650: GPU5 GPU5: DAG 13%
2018.05.27:10:38:04.686: GPU4 GPU4: DAG 13%
2018.05.27:10:38:04.703: GPU2 GPU2: DAG 13%
2018.05.27:10:38:04.744: GPU1 GPU1: DAG 13%
|
|
|
|
|
human75
Newbie
Offline
Activity: 51
Merit: 0
|
|
May 27, 2018, 12:11:47 PM |
|
Hi.
i am. using latest phoinex miner.
i have no stale and no incorrect shares but i have around 15 rejected shares in 36hours.
how do reduce rejected shares to minimum? Many thx in advance for your advices...
|
|
|
|
|
Lunga Chung
Member
Offline
Activity: 277
Merit: 23
|
|
May 27, 2018, 12:22:41 PM |
|
Hi.
i am. using latest phoinex miner.
i have no stale and no incorrect shares but i have around 15 rejected shares in 36hours.
how do reduce rejected shares to minimum? Many thx in advance for your advices...
lower OC |
|
|
|
|
lncm
Member
Offline
Activity: 388
Merit: 13
|
|
May 27, 2018, 01:23:02 PM |
|
I think author must make Windows 10 1803 April Update compatibility with new drivers.
AMD Adrenalin 18.5.1 driver normal works with Claymrore's miners...
I have 1083 update in one rig, installed 18.5.1 drivers yesterday to try them out, and Phoenix miner worked just fine. |
|
|
|
|
gameboy366
Jr. Member
Offline
Activity: 252
Merit: 8
|
|
May 27, 2018, 03:10:59 PM |
|
Hello, today i first time switched from HiveOS and ethminer to Win10 and Phoenoxminer.
I have one problem, the gpu temp. Is high compared to ethminer in hiveos. 10C high !
|
|
|
|
|
human75
Newbie
Offline
Activity: 51
Merit: 0
|
|
May 27, 2018, 03:36:58 PM |
|
Hi.
i am. using latest phoinex miner.
i have no stale and no incorrect shares but i have around 15 rejected shares in 36hours.
how do reduce rejected shares to minimum? Many thx in advance for your advices...
lower OC Thanks mate. will. do |
|
|
|
|
lesjokolat
Jr. Member
Offline
Activity: 117
Merit: 3
|
|
May 27, 2018, 06:11:07 PM |
|
Got a weird error today after windows update. See below out of mem error. Mining Win10 with 6x 1060 6GB and 16GB PageFile. Resolve it finally by increasing the page file to 24GB. Hope this helps others. 2018.05.27:10:37:56.494: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.27:10:37:56.494: main Cmd line: -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal XXX -proto 3
2018.05.27:10:37:59.271: main Available GPUs for mining:
2018.05.27:10:37:59.272: main GPU1: GeForce GTX 1060 6GB (pcie 1), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU2: GeForce GTX 1060 6GB (pcie 2), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU3: GeForce GTX 1060 6GB (pcie 4), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU4: GeForce GTX 1060 6GB (pcie 6), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU5: GeForce GTX 1060 6GB (pcie 8), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU6: GeForce GTX 1060 6GB (pcie 9), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.283: main NVML library initialized
2018.05.27:10:37:59.506: main Listening for CDM remote manager at port 3333 in read-only mode
2018.05.27:10:37:59.508: main Eth: the pool list contains 4 pools
2018.05.27:10:37:59.508: main Eth: primary pool: eu1.ethermine.org:4444
2018.05.27:10:37:59.508: main Starting GPU mining
2018.05.27:10:37:59.509: wdog Starting watchdog thread
2018.05.27:10:37:59.509: main Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: QtMiner)
2018.05.27:10:37:59.544: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (94.23.36.128)
2018.05.27:10:37:59.544: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["XXX"]}
2018.05.27:10:37:59.573: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.05.27:10:37:59.573: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.05.27:10:37:59.591: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":2018.05.27:10:37:59.591: eths Eth: New job #7d15954f from eu1.ethermine.org:4444; diff: 4000MH
2018.05.27:10:37:59.592: GPU1 GPU1: Starting up... (0)
2018.05.27:10:37:59.592: GPU1 Eth: Generating light cache for epoch #189
2018.05.27:10:37:59.594: GPU2 GPU2: Starting up... (0)
2018.05.27:10:37:59.595: GPU3 GPU3: Starting up... (0)
2018.05.27:10:37:59.598: GPU4 GPU4: Starting up... (0)
2018.05.27:10:37:59.601: GPU5 GPU5: Starting up... (0)
2018.05.27:10:37:59.602: GPU6 GPU6: Starting up... (0)
2018.05.27:10:37:59.711: main GPU1: 38C 0%, GPU2: 35C 0%, GPU3: 37C 0%, GPU4: 46C 0%, GPU5: 42C 0%, GPU6: 42C 0%
2018.05.27:10:38:00.985: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":
2018.05.27:10:38:00.985: eths Eth: New job #992bc07d from eu1.ethermine.org:4444; diff: 4000MH
2018.05.27:10:38:02.597: GPU6 GPU6: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.625: GPU5 GPU5: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.625: GPU1 GPU1: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.662: GPU2 GPU2: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.666: GPU4 GPU4: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.681: GPU6 GPU6: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.715: GPU1 GPU1: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.756: GPU5 GPU5: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.780: GPU4 GPU4: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.805: GPU2 GPU2: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.895: GPU6 GPU6: Generating DAG for epoch #189
2018.05.27:10:38:02.906: GPU3 GPU3: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.941: GPU1 GPU1: Generating DAG for epoch #189
2018.05.27:10:38:02.969: GPU5 GPU5: Generating DAG for epoch #189
2018.05.27:10:38:02.992: GPU4 GPU4: Generating DAG for epoch #189
2018.05.27:10:38:03.020: GPU2 GPU2: Generating DAG for epoch #189
[color=red]2018.05.27:10:38:03.099: GPU3 CUDA error in CudaProgram.cu:377 : out of memory (2)
2018.05.27:10:38:03.103: GPU3 GPU3: CUDA memory: 6.00 GB total, 4.97 GB free
2018.05.27:10:38:03.103: GPU3 GPU3 initMiner error: out of memory
2018.05.27:10:38:03.597: wdog Thread(s) not responding. Restarting.[/color]
2018.05.27:10:38:04.557: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.27:10:38:04.557: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
2018.05.27:10:38:04.592: GPU6 GPU6: DAG 13%
2018.05.27:10:38:04.650: GPU5 GPU5: DAG 13%
2018.05.27:10:38:04.686: GPU4 GPU4: DAG 13%
2018.05.27:10:38:04.703: GPU2 GPU2: DAG 13%
2018.05.27:10:38:04.744: GPU1 GPU1: DAG 13%
possible you need to increase pagedile memory? what is it at now? try doubling it to see if it cures error if under 16 gig. |
|
|
|
|
lesjokolat
Jr. Member
Offline
Activity: 117
Merit: 3
|
|
May 27, 2018, 06:48:16 PM |
|
Hi.
i am. using latest phoinex miner.
i have no stale and no incorrect shares but i have around 15 rejected shares in 36hours.
how do reduce rejected shares to minimum? Many thx in advance for your advices...
lower OC Thanks mate. will. do Hey guys just an FYI not sure what pool you guys are using but i recently found a pool with no fees. Works great with PM and i can say my avg eth pay has increased by20% they are smaller and find less frequent but been better for me. ethertrench.com |
|
|
|
|
human75
Newbie
Offline
Activity: 51
Merit: 0
|
|
May 27, 2018, 08:53:41 PM |
|
Hi.
i am. using latest phoinex miner.
i have no stale and no incorrect shares but i have around 15 rejected shares in 36hours.
how do reduce rejected shares to minimum? Many thx in advance for your advices...
lower OC Thanks mate. will. do Hey guys just an FYI not sure what pool you guys are using but i recently found a pool with no fees. Works great with PM and i can say my avg eth pay has increased by20% they are smaller and find less frequent but been better for me. ethertrench.com yes. small pool pays more at initial and when starts cant find block then they wont pay you... i lost almost 2 week at xminer.net.electricy is expensive so i couldn't wait very long. so bigger pool pays everyday and regularly. i would prefer regular payments. |
|
|
|
|
j2james
Newbie
Offline
Activity: 80
Merit: 0
|
|
May 28, 2018, 02:45:50 PM
Last edit: May 28, 2018, 03:01:35 PM by j2james |
|
I have this error regularly beginning from 2018.04.22:18:14. I do not remove logs, so I have full history. Sometime I have other errors. My error history is the following:
error 719 - 5 times (the 1st of them was 2018.04.22:18:14)
error 999 - 1 time
error 719 - 1 time
error 719 and error 999 after 719 - 1 time
error 719 - 1 time
error 4 - 1 time
error 719 - 7 times
error 999 - 1 time
error 719 - 1 time (this one was 2018.05.11:15:24)
Also I had some restarts during this period w\o errors in log files.
All these errors in PM 2.9e. Before that I used 2.7c and 2.8c. And only one time I had only one error 999 in 2.7c. So looks like something wrong in 2.9e.
Hi PM developers. I have found the problem of 999 and 719 errors in my case. It was too big overclocking. I have decreased my MC from +670 to +650 and I forget about any errors during 10 days after this change. So it was not bug of PM. Moreover, my hashrate was decreased on 1 Mh/s, but I have better average mining result and w\o any restarts. |
|
|
|
|
gameboy366
Jr. Member
Offline
Activity: 252
Merit: 8
|
|
May 28, 2018, 07:06:23 PM |
|
Asking again- My temperature is more when mining with Phoenixminer and Win10 then they are with HiveOS and ethminer or claymore(on HiveOS). Temp increased by 7-10C. Is this normal or is this some settings problem.
|
|
|
|
|
Stihlus
Newbie
Offline
Activity: 31
Merit: 0
|
|
May 28, 2018, 07:38:09 PM |
|
I have this error regularly beginning from 2018.04.22:18:14. I do not remove logs, so I have full history. Sometime I have other errors. My error history is the following:
error 719 - 5 times (the 1st of them was 2018.04.22:18:14)
error 999 - 1 time
error 719 - 1 time
error 719 and error 999 after 719 - 1 time
error 719 - 1 time
error 4 - 1 time
error 719 - 7 times
error 999 - 1 time
error 719 - 1 time (this one was 2018.05.11:15:24)
Also I had some restarts during this period w\o errors in log files.
All these errors in PM 2.9e. Before that I used 2.7c and 2.8c. And only one time I had only one error 999 in 2.7c. So looks like something wrong in 2.9e.
Hi PM developers. I have found the problem of 999 and 719 errors in my case. It was too big overclocking. I have decreased my MC from +670 to +650 and I forget about any errors during 10 days after this change. So it was not bug of PM. Moreover, my hashrate was decreased on 1 Mh/s, but I have better average mining result and w\o any restarts. Hello, I have 1070 G1 Gaming (Micron memory) and I keep them at 60% TDP, -150 CC and +780 Memory on 2.9e (with MSI Afterburner, I've tried also Nvidia Inspector but now I have a custom fan curve) and it's working fine maybe for few days and after that a restart but I don't care (with 230.2 MH/s for 7 GPU's). On Claymore 11.6 on 60%, 0 CC and +800 Memory no errors for weeks and working very good but with 226 MH/s. Now I'm trying on 1 RIG with 2.8C with 60% TDP, -150 CC and +800 to see how long they will run. (I have 231 MH/s for 7 GPU). I'm still with Windows 10 1709 and Nvidia driver 391.35. I'm waiting the new version to see how will be. And yes, I have that error 999 - unable to get fan speed and only for GPU 1 and only on one RIG...:/ That little breackdown it's when I've changed the miner 2.9e with 2.8c. NanoPoolRegards |
|
|
|
|
faizmubarok
Newbie
Offline
Activity: 2
Merit: 0
|
|
May 29, 2018, 11:07:24 AM |
|
Hey dev, first of all. Phoenix miner is the best miner I've ever used. My RX570 was 29.1 MH/s now it's 30.6 MH/s.
I have 3 miner running.
I want to ask something,
From 1 of my 18 cards (RX 570). After running about a day, the hashrate dropped from 30,6 to 8.0 MH/s (miner is still running fine). Anyone know why?
This problem can be solved by just restarting the rig.
Is there a command that will restart the rig (not just the miner) if the hashrate drop on a certain value? I tried -minrigspeed but it's just restart the miner, not the rig.
Much appreciation.
|
|
|
|
|
|
