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

BeretvaJanos

newbie

Activity: 3

Merit: 0

Quote from: BeretvaJanos on May 19, 2018, 06:30:17 AM

At DAG update [so every 5 days and a few hours] I'm running into the issue as per the screenshot:

https://pasteboard.co/HlSWewG.png

I tried to find in readme file whether there's a fix for this; I already have 16 GB of virtual memory allocated so that shouldn't be the issue.

The cards in question are all nvidia, so the codes suggested won't work [as it says in title only for AMD].

Any help is appreciated!

Cheers,

Greg

This is more overclocking and/or PSU releated. If your cards are overclocked, during the DAG generation they may fail as DAG generation is more computationally intensive than the normal ethash computation. Another possible reason is a PSU(s) that are at the limit. During the DAG generation the cards will draw more power and if the PSU is near it's limit, the voltages may drop too much and the cards will crash. We will add the -gser option to serialize the DAG generation to solve the second problem in the next release.
[/quote]

Hi PM,

First of all thanks for the advice; thought I'd give some feedback on the above.
Just to put into context, the cards I'm mining with are 1x1080Ti and 3x1050ti; power usage normally is 410W at the wall; the PSU is good up to 750W so this shouldn't be the issue.
I have however reset to 0 the Core and Mem clock settings in Afterburner[from +150Core and +1000Mem, effectively going back to 80MH/s from 105.5MH/s] prior to the DAG update this evening and can confirm that the miner hasn't crashed.
During the next few weeks I'll endevour to see which overclock settings would not cause any problems during DAG update; will start with 140/900; at the moment performance is @ 103.5MH/s so will see in about 5 days how it goes.

Cheers,
Greg

pinamalina

jr. member

Activity: 47

Merit: 1

A hint for nvidia GTX 1070 overclocking.

Currently running with the following OC settings:

On most GPUs with: core: -200, mem:+900, fixed fan speed, fixed power target as per next cmd OC tool:

start nvidiaInspector.exe -setBaseClockOffset:0,0,-200 -setMemoryClockOffset:0,0,880 -setPowerTarget:0,60 -setTempTarget:0,1,65 -setFanSpeed:0,45
start nvidiaInspector.exe -setBaseClockOffset:1,0,-200 -setMemoryClockOffset:1,0,880 -setPowerTarget:1,60 -setTempTarget:1,1,65 -setFanSpeed:1,60
start nvidiaInspector.exe -setBaseClockOffset:2,0,-200 -setMemoryClockOffset:2,0,900 -setPowerTarget:2,60 -setTempTarget:2,1,65 -setFanSpeed:2,45
start nvidiaInspector.exe -setBaseClockOffset:3,0,-200 -setMemoryClockOffset:3,0,625 -setPowerTarget:3,55 -setTempTarget:3,1,65 -setFanSpeed:3,40
start nvidiaInspector.exe -setBaseClockOffset:4,0,-200 -setMemoryClockOffset:4,0,900 -setPowerTarget:4,60 -setTempTarget:4,1,65 -setFanSpeed:4,45
start nvidiaInspector.exe -setBaseClockOffset:5,0,-200 -setMemoryClockOffset:5,0,900 -setPowerTarget:5,60 -setTempTarget:5,1,65 -setFanSpeed:5,60
start nvidiaInspector.exe -setBaseClockOffset:6,0,-200 -setMemoryClockOffset:6,0,900 -setPowerTarget:6,60 -setTempTarget:6,1,65 -setFanSpeed:6,45

When atempting to start the miner, it will fail during the DAG when using the above settings.
So this is what I do:
Step 1: Setup the OC with core: -200, mem +800 as per above.
Step 2: Start the PhoenixMiner and wait for hashing to start (after loading the DAGs).
Step 3: After few minutes apply the OC settings with -200, mem +900.

These are current results:
Eth speed: 417.699 MH/s, shares: 335/0/0, time: 0:58
GPUs: 1: 33.641 MH/s (25) 2: 33.642 MH/s (21) 3: 33.804 MH/s (30) 4: 31.308 MH/s (28) 5: 30.930 MH/s (24) 6: 33.826 MH/s (27) 7: 33.844 MH/s (30) 8: 30.963 MH/s (22) 9: 30.462 MH/s (26) 10: 30.885 MH/s (20) 11: 30.837 MH/s (24) 12: 33.808 MH/s (28) 13: 29.749 MH/s (30)

The GPUs 5,8,9,10,11 and 13 are AMD RX580.

Still in process of increasing the mem clocks but leaving a system for 24h observation between each change to confirm stability.

Happy mining!

Digital_Seytan

jr. member

Activity: 222

Merit: 2

[email protected]

Quote from: sidaliroy on May 21, 2018, 07:04:08 PM

Hi, You've told us that you will release 3.0 it this end of month and we're already one week away from the end, Any news Phoenix? We're so excited for the new version

Yes come on with the release 3.0 beta ,before I go on vacation I would like to test and of course curious about the new features that have been added. Huh

Digital_Seytan

jr. member

Activity: 222

Merit: 2

[email protected]

Quote from: haliy-2017 on May 21, 2018, 07:26:50 AM

The most stable driver for Nvidia 1060 6g?

The most stable driver for Nvidia 1060 6g i tested most nvidia driver in my case best is 390.65
works verry good and stable.

--------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH

MaxMidnite

newbie

Activity: 143

Merit: 0

Any news, its been a while?

rboer

newbie

Activity: 16

Merit: 0

Please add -coin support for ETHO.

thanks

lesjokolat

jr. member

Activity: 117

Merit: 3

Quote from: nongkrong on May 22, 2018, 05:43:11 PM

Even with 2.5d now I'm unable to run the miner, though I'm starting to think it's something on my end. After further investigation once GPUs are identified in the console the error message: "FATAL ERROR: Debugger detected" is shown immediately before it crashes. So there's some update please ? Or maybe i will back to use my last miner software. Anyway thank you for trying make more chipper dev fee mining.

id recommend 2.8 or 2.9 if not useing vega 64. also will help to see your bat files configr as well. what driver versions also and may as well spec out gpus you are using.

nongkrong

newbie

Activity: 45

Merit: 0

Even with 2.5d now I'm unable to run the miner, though I'm starting to think it's something on my end. After further investigation once GPUs are identified in the console the error message: "FATAL ERROR: Debugger detected" is shown immediately before it crashes. So there's some update please ? Or maybe i will back to use my last miner software. Anyway thank you for trying make more chipper dev fee mining.

ikyo

newbie

Activity: 18

Merit: 0

j2james

newbie

Activity: 80

Merit: 0

Hi PM developers. Can you add an additional hot key and corresponded functionality to show in console all parameters used by miner (even if they are not defined in command line and have default values). For example in this way:

param1: value1
param2: value2 (default)
param3: value3
param4: value4
param5: value5 (default)

Thank you

lesjokolat

jr. member

Activity: 117

Merit: 3

jendabenda

newbie

Activity: 11

Merit: 0

Reddit232

newbie

Activity: 3

Merit: 0

Hi comunity !

First at all let me thank you for youre miner, a great job.
Until now I was using PhoenixMiner_2.6 and everything works perfectly.
Yesterday I decided to upgrade to a newer version PhoenixMiner_2.9e.
He works even better 2.6, but, usually my hashrate and only on GPU0 drop to 19-18 and then go back to 30.
May i kindly ask youre help with this problem.

Thank You in advance.

https://i.imgur.com/T3nYzZb.jpg

ikyo

newbie

Activity: 18

Merit: 0

I am having some issues upgrading to 2.9e. When I use 2.8C on my Vega rigs (Beta Blockchain drivers), I have no issues. If I try 2.9e, I run into this issue:

Code:

2018.05.21:22:58:46.662: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.21:22:58:46.662: main Cmd line: -amd -pool us1.ethermine.org:4444 -wal 0x61cab7e0c6cefc6bb9FC6005ef9850764fe4C561.vega1 -coin ETH -pass X
2018.05.21:22:58:47.804: main Available GPUs for mining:
2018.05.21:22:58:47.805: main GPU1: 687F:C1 (pcie 3), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU2: 687F:C1 (pcie 7), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU3: 687F:C1 (pcie 10), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU4: 687F:C1 (pcie 13), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU5: 687F:C1 (pcie 18), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU6: 687F:C1 (pcie 21), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.828: main ADL library initialized
2018.05.21:22:58:48.186: main Listening for CDM remote manager at port 3333 in read-only mode
2018.05.21:22:58:48.187: main Eth: the pool list contains 3 pools
2018.05.21:22:58:48.187: main Eth: primary pool: us1.ethermine.org:4444
2018.05.21:22:58:48.187: main Starting GPU mining
2018.05.21:22:58:48.187: main Matched GPU1 to ADL adapter index 24 (method 1)
2018.05.21:22:58:48.214: main GPU1: Using the X2 ODN API
2018.05.21:22:58:48.214: main GPU1: Created ADL monitor for adapter 24; overdrive version: 7
2018.05.21:22:58:48.218: main GPU1: using the blockchain beta driver
2018.05.21:22:58:48.218: main Matched GPU2 to ADL adapter index 30 (method 1)
2018.05.21:22:58:48.241: main GPU2: Using the X2 ODN API
2018.05.21:22:58:48.241: main GPU2: Created ADL monitor for adapter 30; overdrive version: 7
2018.05.21:22:58:48.241: main GPU2: using the blockchain beta driver
2018.05.21:22:58:48.241: main Matched GPU3 to ADL adapter index 12 (method 1)
2018.05.21:22:58:48.264: main GPU3: Using the X2 ODN API
2018.05.21:22:58:48.264: main GPU3: Created ADL monitor for adapter 12; overdrive version: 7
2018.05.21:22:58:48.264: main GPU3: using the blockchain beta driver
2018.05.21:22:58:48.264: main Matched GPU4 to ADL adapter index 18 (method 1)
2018.05.21:22:58:48.291: main GPU4: Using the X2 ODN API
2018.05.21:22:58:48.291: main GPU4: Created ADL monitor for adapter 18; overdrive version: 7
2018.05.21:22:58:48.291: main GPU4: using the blockchain beta driver
2018.05.21:22:58:48.291: main Matched GPU5 to ADL adapter index 6 (method 1)
2018.05.21:22:58:48.318: main GPU5: Using the X2 ODN API
2018.05.21:22:58:48.318: main GPU5: Created ADL monitor for adapter 6; overdrive version: 7
2018.05.21:22:58:48.318: main GPU5: using the blockchain beta driver
2018.05.21:22:58:48.318: main Matched GPU6 to ADL adapter index 0 (method 1)
2018.05.21:22:58:48.344: main GPU6: Using the X2 ODN API
2018.05.21:22:58:48.344: main GPU6: Created ADL monitor for adapter 0; overdrive version: 7
2018.05.21:22:58:48.344: main GPU6: using the blockchain beta driver
2018.05.21:22:58:48.344: wdog Starting watchdog thread
2018.05.21:22:58:48.345: main Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.05.21:22:58:48.480: eths Eth: Connected to ethash pool us1.ethermine.org:4444 (18.219.59.155)
2018.05.21:22:58:48.480: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x61cab7e0c6cefc6bb9FC6005ef9850764fe4C561.vega1","5tarwar5"]}

2018.05.21:22:58:48.546: main GPU1: 30C 58%, GPU2: 29C 58%, GPU3: 32C 58%, GPU4: 28C 58%, GPU5: 30C 58%, GPU6: 30C 59%
2018.05.21:22:58:48.564: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.05.21:22:58:48.565: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.05.21:22:58:48.639: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xacb4fe231378097ab12add466b810ebdda1b1095c501cc06d1ecc25a704b2d9b","0xc16796d9b504e2ac0305bf673638b84a7d0278ba389d82377cde63edcca1a1bb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x564bc8"]}
2018.05.21:22:58:48.639: eths Eth: New job #acb4fe23 from us1.ethermine.org:4444; diff: 4000MH
2018.05.21:22:58:48.640: GPU1 GPU1: Starting up... (0)
2018.05.21:22:58:48.640: GPU1 Eth: Generating light cache for epoch #188
2018.05.21:22:58:48.641: GPU2 GPU2: Starting up... (0)
2018.05.21:22:58:48.643: GPU3 GPU3: Starting up... (0)
2018.05.21:22:58:48.645: GPU4 GPU4: Starting up... (0)
2018.05.21:22:58:48.647: GPU5 GPU5: Starting up... (0)
2018.05.21:22:58:48.649: GPU6 GPU6: Starting up... (0)
2018.05.21:22:58:50.737: GPU1 build: Failed to GPU1 program: clBuildProgram (-11)
2018.05.21:22:58:50.738: GPU1 GPU1: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:50.933: GPU2 build: Failed to GPU2 program: clBuildProgram (-11)
2018.05.21:22:58:50.933: GPU2 GPU2: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.125: GPU3 build: Failed to GPU3 program: clBuildProgram (-11)
2018.05.21:22:58:51.125: GPU3 GPU3: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.314: GPU4 build: Failed to GPU4 program: clBuildProgram (-11)
2018.05.21:22:58:51.314: GPU4 GPU4: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.346: wdog Thread(s) not responding. Restarting.
2018.05.21:22:58:51.513: GPU5 build: Failed to GPU5 program: clBuildProgram (-11)
2018.05.21:22:58:51.513: GPU5 GPU5: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.708: GPU6 build: Failed to GPU6 program: clBuildProgram (-11)
2018.05.21:22:58:51.708: GPU6 GPU6: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:53.360: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.21:22:58:53.360: 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)

sidaliroy

newbie

Activity: 23

Merit: 0

Hi, You've told us that you will release 3.0 it this end of month and we're already one week away from the end, Any news Phoenix? We're so excited for the new version

Mathero11

jr. member

Activity: 36

Merit: 12

Quote from: Soliqesh on May 21, 2018, 04:47:55 PM

Someone has problems with the hashrate drops on amd cards? My 2 rigs have the same problem, by random some cards is reset to 25-26mhs and after 10-30 seconds it returns to 30-32mh as it should be Undecided

. On Claymore there is no such problem.

I've got that too but im not bothering the 30-45 secs. Phoenix is more stable then claymore to me & less devfee.

lesjokolat

jr. member

Activity: 117

Merit: 3

Quote from: Iamtutut on May 21, 2018, 05:42:26 PM

Quote from: skinnyfalcon on May 21, 2018, 11:42:50 AM

Just to report in, the latest Windows 10 update pushed out (yesterday) is not compatible and miner will hang. I rolled back the update to get the miner working again.

I mine with windows 10 build 1803 and 18.3.4 drivers (AMD), no issue with Phoenix 2.9e.

This week i'll try the very last drivers (Q2) that unify Radeon IGP with discrete Radeon GPU drivers.

@Soliqesh:
I had this issue with #2 GPU (dropping from 31.2-31.4MH/s to 24-26MH/s), had to change my afterburner OC voltage settings. Stable for hours now.

beware if you use it with vegas 64, PM has issues with that combo. WINDOWS 1803 AND AMD 18.4.1

Iamtutut

full member

Activity: 1120

Merit: 131

Quote from: skinnyfalcon on May 21, 2018, 11:42:50 AM

Just to report in, the latest Windows 10 update pushed out (yesterday) is not compatible and miner will hang. I rolled back the update to get the miner working again.

I mine with windows 10 build 1803 and 18.3.4 drivers (AMD), no issue with Phoenix 2.9e.

This week i'll try the very last drivers (Q2) that unify Radeon IGP with discrete Radeon GPU drivers.

@Soliqesh:
I had this issue with #2 GPU (dropping from 31.2-31.4MH/s to 24-26MH/s), had to change my afterburner OC voltage settings. Stable for hours now.

Soliqesh

newbie

Activity: 48

Merit: 0

Someone has problems with the hashrate drops on amd cards? My 2 rigs have the same problem, by random some cards is reset to 25-26mhs and after 10-30 seconds it returns to 30-32mh as it should be Undecided

. On Claymore there is no such problem.

Stihlus

newbie

Activity: 31

Merit: 0

Hi, someone know why there is a big drop hasrate on the pool? :/ It's a little bit strange. My hashrate it's ok ...
https://ibb.co/kV4mmT
And still going down. Strange. I'm on Ethermine but I will change to Nanopool ....

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