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

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: PhoenixMiner on June 09, 2020, 11:20:55 PM

Quote from: UnclWish on June 09, 2020, 04:47:54 PM

So many rejected shares on 5.0x verisions... About 1-1.2% overall rejected shares (not stales or incorrect) on my RX 580 8Gb rigs...

Could you please tell us on which pools? This is normal on nicehash, as it doesn't accept stale shares and they count as rejected shares, and it seems that recently nicehash started changing the jobs more often, leading to more rejected shares.

Yes, it's on nicehash. Is there some way to correct show these stale shares?

PhoenixMiner

full member

Activity: 357

Merit: 101

PhoenixMiner 5.0e is officially released. You can find the download link and the checksums in the first post of this thread.

The changes in this release are:

Additional fixes for the problem with crashing or slowing down when switching from ETC to ETH mining

If you are already running PhoenixMiner 5.0b, 5.0c, or 5.0d, it is recommended to upgrade to 5.0e, especially if you are using pool that switches coins automatically like nicehash.

PhoenixMiner

full member

Activity: 357

Merit: 101

Quote from: boregepco on June 09, 2020, 12:56:38 AM

Not a message like this. Everything looks ok in the beginning, but when it starts to change from epoch to epoch first gpu starts to mine with a lower speed and after a while the miner crash.
P.S. My monitor is on GPU 1...

There is nothing you can do unless you connect the display to 8 GB or 6 GB card. As this isn't possible in your case, you can instead run separate instance of PhoenixMiner for just GPU1 (adding the argument -gpus 1) and use a pool that only mines ETH. The other five cards will run on another instance of PhoenixMiner (with -gpus 23456), that can mine both ETH and ETC.

Quote from: Broomey on June 09, 2020, 01:14:27 AM

Is this what you're after Phoenix? Thanks for the prompt reply too!

I can Private message you a complete "log file" if you think it will help, but other than down the bottom where is says "Agent Service Error", I don't see anything abnormal. And as I say, everything is identical to the other 4 rigs, in every way. Please ignore the Maxhash pool below.. it was a test to see if it was an Ethermine issue.. but same result. Cheers.

Code:

bin: phoenixminer
conf: phoenixminer.pcfg
[707] 2020-06-08 09:37:10Z: (CLI user) Using port 4028...
[707] 2020-06-08 09:37:10Z: (CLI user) Starting screen 'miner-4028' with: /opt/miners/phoenixminer/phoenixminer -epool stratum+ssl://eth-eu.maxhash.org:13011 -ewal 0x972e782f1a165ac661ef716a5f1fcb283a85563a.Rig4 -epsw x -mport 4028 -allpools 1 -logfile /var/log/phoenixminer.log -logsmaxsize 100MB -eworker Rig4 -fanmin 35 -tt 66 -tstop 75 -clGreen 1 -acm -amd -mclock 1960 -cclock 1040 -mvddc 800 -cvddc 800 -mode 1
[707] 2020-06-08 09:37:12Z: (CLI user) Miner screen started...
[707] 2020-06-08 09:38:38Z: (CLI user) Starting command line miner on localhost
bin: phoenixminer
conf: phoenixminer.pcfg
[707] 2020-06-08 09:38:38Z: (CLI user) Using port 4028...
[707] 2020-06-08 09:38:38Z: (CLI user) Starting screen 'miner-4028' with: /opt/miners/phoenixminer/phoenixminer -epool stratum+tcp://eth-eu.maxhash.org:8011 -ewal 0x972e782f1a165ac661ef716a5f1fcb283a85563a.Rig4 -epsw x -mport 4028 -allpools 1 -logfile /var/log/phoenixminer.log -logsmaxsize 100MB -eworker Rig4 -fanmin 35 -tt 66 -tstop 75 -clGreen 1 -acm -amd -mclock 1960 -cclock 1040 -mvddc 800 -cvddc 800 -mode 1
[707] 2020-06-08 09:38:40Z: (CLI user) Miner screen started...
[707] 2020-06-08 09:56:40Z: (CLI user) Miner stopped.
[722] 2020-06-08 09:58:19Z: (FCTRL) service started.
[722] 2020-06-08 09:58:19Z: (FCTRL) Agent Server Error:
[722] 2020-06-08 09:58:32Z: (FCTRL) local IP is 192.168.1.72.
[722] 2020-06-08 09:59:05Z: (CLI user) Starting command line miner on localhost

No, we need the log from the miner itself, which in your case appears to be in /var/log/phoenixminer.log

Quote from: alex31 on June 09, 2020, 02:20:55 AM

Hi All. please tell me can I mine Ravencoin now or at the future with PhoenixMiner?
Thanks.

Now it isn't possible as Ravencoin uses another variant of ProgPOW. We may add support in the future but there is no specific timeframe.

Quote from: delevic on June 09, 2020, 12:10:57 PM

Jutst to report that Phoenix 5.0 works fantastic on Ubuntu 18.04.4 with Amd 20.10 drivers. Much much batter than Claymore in Linux.

Nice to hear

Quote from: UnclWish on June 09, 2020, 04:47:54 PM

So many rejected shares on 5.0x verisions... About 1-1.2% overall rejected shares (not stales or incorrect) on my RX 580 8Gb rigs...

Could you please tell us on which pools? This is normal on nicehash, as it doesn't accept stale shares and they count as rejected shares, and it seems that recently nicehash started changing the jobs more often, leading to more rejected shares.

Broomey

newbie

Activity: 21

Merit: 1

Quote from: Broomey on June 08, 2020, 04:07:39 PM

Hi all. Can someone please try and point me in the right direction.
I have been running Phoenix Miner forever. I have 5 x identical mining rigs, each with MSI B360fpro MB, 8gb Ram, i3-8100 cpu and 10 x MSI RX 570 4gb gpu's, all mining ETH through Ethermine. All have been running sweet, then 1 rig stopped mining. I have checked all I can, stripped the rig back to a single gpu (and tried a few just in case).. the miner starts, but just will not hash. The miner screen shows it's trying, just looks like it's not attempting to build DAG? I've tried V5.0b, c and d. All same. I reformatted/reimaged (running PiMP, which has been/is awesome), copied and pasted the settings from one of the other stable rigs.. still same problem. I loaded "cough" claymore for testing purposes.. and it fired up right away, and has been hashing stable for the past 12hrs. It's got me puzzled, as I said, I have 4 other identical rigs running no issues? If Claymore runs, surely Phoenix should too?? The only thing left for me to do is assume its hardware and swap parts from a working rig.. 1 x 1.. painful. Sad

Any thoughts would be appreciated.
Thanks in advance.

UnclWish

sr. member

Activity: 1484

Merit: 253

So many rejected shares on 5.0x verisions... About 1-1.2% overall rejected shares (not stales or incorrect) on my RX 580 8Gb rigs...

delevic

jr. member

Activity: 30

Merit: 4

Quote from: boregepco on June 09, 2020, 05:26:05 AM

This can be bad extender very likely.

Jutst to report that Phoenix 5.0 works fantastic on Ubuntu 18.04.4 with Amd 20.10 drivers. Much much batter than Claymore in Linux.

bategojko74

member

Activity: 220

Merit: 12

Quote from: boregepco on June 09, 2020, 08:15:57 AM

Quote from: alex31 on June 09, 2020, 08:11:06 AM

Quote from: boregepco on June 09, 2020, 08:06:33 AM

Quote

I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early Roll Eyes

But maybe your monitor is connected to the motherboard video... Not on the mining card...

No, my monitor connected to the first video card because my processor no has integrated video

What and where are you mining?
I tried to mine eth in ethermine and i tried to mine in nicehash - a lot of problems and restarts... And some of mine RX480 are with a speed 7-8 MHs

You could also could have problems with overclocking and overheating. Run with -hstats 2 and show enough log just before crash.

boregepco

newbie

Activity: 26

Merit: 0

Quote from: alex31 on June 09, 2020, 08:11:06 AM

Quote from: boregepco on June 09, 2020, 08:06:33 AM

Quote

I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early Roll Eyes

But maybe your monitor is connected to the motherboard video... Not on the mining card...

No, my monitor connected to the first video card because my processor no has integrated video

What and where are you mining?
I tried to mine eth in ethermine and i tried to mine in nicehash - a lot of problems and restarts... And some of mine RX480 are with a speed 7-8 MHs

alex31

member

Activity: 93

Merit: 10

Quote from: boregepco on June 09, 2020, 08:06:33 AM

Quote

I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early Roll Eyes

But maybe your monitor is connected to the motherboard video... Not on the mining card...

No, my monitor connected to the first video card because my processor no has integrated video

another way for you is switch to another pool to mine only one coin , for example - https://ethereum.miningpoolhub.com/

boregepco

newbie

Activity: 26

Merit: 0

Quote from: alex31 on June 09, 2020, 07:54:21 AM

Quote from: bategojko74 on June 09, 2020, 07:37:22 AM

Quote from: alex31 on June 09, 2020, 07:17:21 AM

Quote from: bategojko74 on June 09, 2020, 06:45:25 AM

Code:

2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB <---------
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341

You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.

I think that you on wrong way , he has enough vram on first card

He has in theory, but the driver reserves it for the monitor. So in practice he can’t use his last 0.26GB because of the way the driver manages the VRAM when there is monitor attached. If you mine under Linux, maybe you will not have this problem for now.

I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early Roll Eyes

But maybe your monitor is connected to the motherboard video... Not on the mining card...

alex31

member

Activity: 93

Merit: 10

Quote from: bategojko74 on June 09, 2020, 07:37:22 AM

Quote from: alex31 on June 09, 2020, 07:17:21 AM

Quote from: bategojko74 on June 09, 2020, 06:45:25 AM

Code:

2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB <---------
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341

You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.

I think that you on wrong way , he has enough vram on first card

He has in theory, but the driver reserves it for the monitor. So in practice he can’t use his last 0.26GB because of the way the driver manages the VRAM when there is monitor attached. If you mine under Linux, maybe you will not have this problem for now.

I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early Roll Eyes

bategojko74

member

Activity: 220

Merit: 12

Quote from: alex31 on June 09, 2020, 07:17:21 AM

Quote from: bategojko74 on June 09, 2020, 06:45:25 AM

Code:

2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB <---------
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341

You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.

I think that you on wrong way , he has enough vram on first card

He has in theory, but the driver reserves it for the monitor. So in practice he can’t use his last 0.26GB because of the way the driver manages the VRAM when there is monitor attached. If you mine under Linux, maybe you will not have this problem for now.

alex31

member

Activity: 93

Merit: 10

Quote from: boregepco on June 09, 2020, 07:24:37 AM

When it makes a DAG for ETH and epoch #341 - yes,
but when it makes a DAG for ETC and epoch #351 the problem comes...

2020.06.09:11:43:45.258: GPU1 GPU1: Allocating DAG for epoch #351 (3.74) GB
2020.06.09:11:43:45.336: GPU1 GPU1: Generating DAG for epoch #351

I have 4Gb gpus and mined only ETC without any problems ... issue become only when you change coin on the fly (see prev posts)
so you need try to mine only one coin

boregepco

newbie

Activity: 26

Merit: 0

Quote from: alex31 on June 09, 2020, 07:17:21 AM

Quote from: bategojko74 on June 09, 2020, 06:45:25 AM

Code:

2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB <---------
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341

You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.

I think that you on wrong way , he has enough vram on first card

When it makes a DAG for ETH and epoch #341 - yes,
but when it makes a DAG for ETC and epoch #351 the problem comes...

2020.06.09:11:43:45.258: GPU1 GPU1: Allocating DAG for epoch #351 (3.74) GB
2020.06.09:11:43:45.336: GPU1 GPU1: Generating DAG for epoch #351

alex31

member

Activity: 93

Merit: 10

Quote from: bategojko74 on June 09, 2020, 06:45:25 AM

Code:

2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB <---------
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341

You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.

I think that you on wrong way , he has enough vram on first card

bategojko74

member

Activity: 220

Merit: 12

alex31

member

Activity: 93

Merit: 10

Quote from: boregepco on June 09, 2020, 05:26:05 AM

Quote from: alex31 on June 09, 2020, 04:47:33 AM

Quote from: boregepco on June 09, 2020, 04:35:20 AM

Quote from: alex31 on June 09, 2020, 03:00:25 AM

Quote from: boregepco on June 08, 2020, 11:59:45 AM

I am with a driver version: 19.4.3 and Phoenix Miner 5.0e Windows/msvc - Release build. When the miner makes a DAG for epoch #340 is ok. But the 4GB card stops when the miner starts to make a DAG for epoch #351.

Try set -rvram -1 on command line or in config, may be this can resolve your issue

I have this in my config...

please show log of startup PhoenixMiner for more information ...

In the begginig everything is ok, but after 8 min and

2020.06.09:11:43:41.083: GPU4 GPU4: Generating ethash light cache for epoch #351
2020.06.09:11:43:41.265: GPU1 GPU1: Starting up... (0)

the card with a monitor crashed:

Ok, I think that issue occurs when nicehash pool switch mining coin from ETH to ETC ...
you may try mine only ETH or ETC selecting different port on the nicehash pool ... if it is possible Cool

boregepco

newbie

Activity: 26

Merit: 0

Quote from: alex31 on June 09, 2020, 04:47:33 AM

Quote from: boregepco on June 09, 2020, 04:35:20 AM

Quote from: alex31 on June 09, 2020, 03:00:25 AM

Quote from: boregepco on June 08, 2020, 11:59:45 AM

I am with a driver version: 19.4.3 and Phoenix Miner 5.0e Windows/msvc - Release build. When the miner makes a DAG for epoch #340 is ok. But the 4GB card stops when the miner starts to make a DAG for epoch #351.

Try set -rvram -1 on command line or in config, may be this can resolve your issue

I have this in my config...

please show log of startup PhoenixMiner for more information ...

In the begginig everything is ok, but after 8 min and

2020.06.09:11:43:41.083: GPU4 GPU4: Generating ethash light cache for epoch #351
2020.06.09:11:43:41.265: GPU1 GPU1: Starting up... (0)

the card with a monitor crashed:

2020.06.09:11:44:39.570: main Eth speed: 156.337 MH/s, shares: 26/1/0, time: 0:10
2020.06.09:11:44:39.570: main GPUs: 1: 0.000 MH/s (2) 2: 31.255 MH/s (4) 3: 31.254 MH/s (4) 4: 31.266 MH/s (4) 5: 31.264 MH/s (5) 6: 31.297 MH/s ( Cool

Here is the begginig:

Code:

2020.06.09:11:34:34.411: main Phoenix Miner 5.0d Windows/msvc - Release build
2020.06.09:11:34:34.411: main Cmd line: -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal 3Q87P.Rig16 -pass x -proto 4 -stales 0 -logdir Logs -rmode 2 -cdmport 4028 -minRigSpeed 165 -dagrestart 1 -eres 0 -lidag 2 -rvram -1 -gt 25,26,27,25,25,24
2020.06.09:11:34:34.411: main No CUDA driver found
2020.06.09:11:34:37.206: main OpenCL driver version: 19.2-4
2020.06.09:11:34:37.291: main Available GPUs for mining:
2020.06.09:11:34:37.292: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
2020.06.09:11:34:37.292: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
2020.06.09:11:34:37.292: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
2020.06.09:11:34:37.292: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
2020.06.09:11:34:37.292: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
2020.06.09:11:34:37.292: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
2020.06.09:11:34:37.293: main ADL library initialized
2020.06.09:11:34:38.715: main Eth: the pool list contains 1 pool (1 from command-line)
2020.06.09:11:34:38.715: main Eth: primary pool: daggerhashimoto.eu.nicehash.com:3353
2020.06.09:11:34:38.716: main Starting GPU mining
2020.06.09:11:34:38.730: main Matched GPU1 to ADL adapter index 32 (method 1)
2020.06.09:11:34:38.767: main GPU1: AMD driver 19.4.3
2020.06.09:11:34:38.767: main GPU1: Created ADL monitor for adapter 32; overdrive version: 7 (7)
2020.06.09:11:34:38.769: main GPU1: using AMD driver ver 19.4.3
2020.06.09:11:34:38.769: main Matched GPU2 to ADL adapter index 0 (method 1)
2020.06.09:11:34:38.799: main GPU2: AMD driver 19.4.3
2020.06.09:11:34:38.799: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7 (7)
2020.06.09:11:34:38.799: main GPU2: using AMD driver ver 19.4.3
2020.06.09:11:34:38.799: main Matched GPU3 to ADL adapter index 16 (method 1)
2020.06.09:11:34:38.828: main GPU3: AMD driver 19.4.3
2020.06.09:11:34:38.828: main GPU3: Created ADL monitor for adapter 16; overdrive version: 7 (7)
2020.06.09:11:34:38.828: main GPU3: using AMD driver ver 19.4.3
2020.06.09:11:34:38.828: main Matched GPU4 to ADL adapter index 24 (method 1)
2020.06.09:11:34:38.857: main GPU4: AMD driver 19.4.3
2020.06.09:11:34:38.857: main GPU4: Created ADL monitor for adapter 24; overdrive version: 7 (7)
2020.06.09:11:34:38.857: main GPU4: using AMD driver ver 19.4.3
2020.06.09:11:34:38.857: main Matched GPU5 to ADL adapter index 8 (method 1)
2020.06.09:11:34:38.886: main GPU5: AMD driver 19.4.3
2020.06.09:11:34:38.886: main GPU5: Created ADL monitor for adapter 8; overdrive version: 7 (7)
2020.06.09:11:34:38.886: main GPU5: using AMD driver ver 19.4.3
2020.06.09:11:34:38.886: main Matched GPU6 to ADL adapter index 40 (method 1)
2020.06.09:11:34:38.914: main GPU6: AMD driver 19.4.3
2020.06.09:11:34:38.914: main GPU6: Created ADL monitor for adapter 40; overdrive version: 7 (7)
2020.06.09:11:34:38.915: main GPU6: using AMD driver ver 19.4.3
2020.06.09:11:34:39.023: wdog Starting watchdog thread
2020.06.09:11:34:39.026: main Eth: Connecting to ethash pool daggerhashimoto.eu.nicehash.com:3353 (proto: Nicehash)
2020.06.09:11:34:39.027: main GPU1: 40C 0% 10W, GPU2: 42C 0% 6W, GPU3: 39C 0% 4W, GPU4: 40C 0% 4W, GPU5: 40C 0% 6W, GPU6: 42C 0% 4W
GPUs power: 34.7 W
2020.06.09:11:34:39.076: eths Eth: Connected to ethash pool daggerhashimoto.eu.nicehash.com:3353 (172.65.200.133)
2020.06.09:11:34:39.076: eths Eth: Send: {"id":1,"method":"mining.subscribe","params":["PhoenixMiner/5.0d","EthereumStratum/1.0.0"]}

2020.06.09:11:34:39.152: eths Eth: Received: {"id":1,"error":null,"result":[["mining.notify","e47242c1ea8ae8f875d5d7f21e8b49c1","EthereumStratum/1.0.0"],"04531d"]}
2020.06.09:11:34:39.153: eths Eth: Extranonce set to 04531d
2020.06.09:11:34:39.153: eths Eth: Subscribed to ethash pool
2020.06.09:11:34:39.153: eths Eth: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["3Q87P19XpzZvBg62zzYbPqhDzk24HaivBZ.Rig16","x"]}

2020.06.09:11:34:39.189: eths Eth: Received: {"id":2,"result":true,"error":null}
2020.06.09:11:34:39.205: eths Eth: Received: {"id":3,"result":true,"error":null}
2020.06.09:11:34:39.205: eths Eth: Worker 3Q87P19XpzZvBg62zzYbPqhDzk24HaivBZ.Rig16 authorized
2020.06.09:11:34:39.205: eths Eth: Received: {"id":null,"method":"mining.set_difficulty","params":[0.8]}
2020.06.09:11:34:39.206: eths Eth: Difficulty set to 0.8
2020.06.09:11:34:39.206: eths Eth: Received: {"id":null,"method":"mining.notify","params":["000000008985e3f7","db084c0babc26227cb293196dd3ed4107a244dd20cef31b35a298c3bbaa62bb7","684c96caf6d6b299c245ce7da4ee9e80c68eb930da043680e90d78af5f2946b6",true]}
2020.06.09:11:34:39.229: main Listening for CDM remote manager at port 4028 in read-only mode
2020.06.09:11:34:39.240: eths Eth: New job #684c96ca from daggerhashimoto.eu.nicehash.com:3353; diff: 3436MH
2020.06.09:11:34:39.243: GPU1 GPU1: Starting up... (0)
2020.06.09:11:34:39.244: GPU1 GPU1: Generating ethash light cache for epoch #341
2020.06.09:11:34:39.246: GPU2 GPU2: Starting up... (0)
2020.06.09:11:34:39.247: GPU3 GPU3: Starting up... (0)
2020.06.09:11:34:39.250: GPU4 GPU4: Starting up... (0)
2020.06.09:11:34:39.251: GPU5 GPU5: Starting up... (0)
2020.06.09:11:34:39.253: GPU6 GPU6: Starting up... (0)
2020.06.09:11:34:43.134: GPU1 Light cache generated in 3.9 s (15.1 MB/s)
2020.06.09:11:34:43.499: GPU2 GPU2: Free VRAM: 3.948 GB; used: 0.052 GB
2020.06.09:11:34:43.540: GPU2 GPU2: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:43.544: GPU2 GPU2: Generating DAG for epoch #341
2020.06.09:11:34:43.905: GPU3 GPU3: Free VRAM: 3.948 GB; used: 0.052 GB
2020.06.09:11:34:43.905: GPU3 GPU3: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:43.912: GPU3 GPU3: Generating DAG for epoch #341
2020.06.09:11:34:44.079: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:34:44.080: 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)
2020.06.09:11:34:44.294: GPU4 GPU4: Free VRAM: 3.948 GB; used: 0.052 GB
2020.06.09:11:34:44.294: GPU4 GPU4: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:44.301: GPU4 GPU4: Generating DAG for epoch #341
2020.06.09:11:34:44.687: GPU5 GPU5: Free VRAM: 3.948 GB; used: 0.052 GB
2020.06.09:11:34:44.687: GPU5 GPU5: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:44.694: GPU5 GPU5: Generating DAG for epoch #341
2020.06.09:11:34:45.093: GPU6 GPU6: Free VRAM: 3.948 GB; used: 0.052 GB
2020.06.09:11:34:45.093: GPU6 GPU6: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.099: GPU6 GPU6: Generating DAG for epoch #341
2020.06.09:11:34:45.417: GPU2 GPU2: DAG 5%
2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341
2020.06.09:11:34:45.767: GPU3 GPU3: DAG 5%
2020.06.09:11:34:46.173: GPU4 GPU4: DAG 5%
2020.06.09:11:34:46.550: GPU5 GPU5: DAG 5%
2020.06.09:11:34:46.923: GPU2 GPU2: DAG 10%
2020.06.09:11:34:46.974: GPU6 GPU6: DAG 5%
2020.06.09:11:34:47.269: GPU3 GPU3: DAG 10%
2020.06.09:11:34:47.361: GPU1 GPU1: DAG 5%
2020.06.09:11:34:47.705: GPU4 GPU4: DAG 10%
2020.06.09:11:34:48.077: GPU5 GPU5: DAG 10%
2020.06.09:11:34:48.452: GPU2 GPU2: DAG 15%
2020.06.09:11:34:48.503: GPU6 GPU6: DAG 10%
2020.06.09:11:34:48.770: GPU3 GPU3: DAG 15%
2020.06.09:11:34:48.862: GPU1 GPU1: DAG 10%
2020.06.09:11:34:49.129: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:34:49.129: 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)
2020.06.09:11:34:49.205: GPU4 GPU4: DAG 15%
2020.06.09:11:34:49.607: GPU5 GPU5: DAG 15%
2020.06.09:11:34:49.981: GPU2 GPU2: DAG 21%
2020.06.09:11:34:50.005: GPU6 GPU6: DAG 16%
2020.06.09:11:34:50.299: GPU3 GPU3: DAG 20%
2020.06.09:11:34:50.362: GPU1 GPU1: DAG 15%
2020.06.09:11:34:50.733: GPU4 GPU4: DAG 21%
2020.06.09:11:34:51.107: GPU5 GPU5: DAG 21%
2020.06.09:11:34:51.507: GPU6 GPU6: DAG 21%
2020.06.09:11:34:51.510: GPU2 GPU2: DAG 26%
2020.06.09:11:34:51.827: GPU3 GPU3: DAG 26%
2020.06.09:11:34:51.878: GPU1 GPU1: DAG 20%
2020.06.09:11:34:52.260: GPU4 GPU4: DAG 26%
2020.06.09:11:34:52.634: GPU5 GPU5: DAG 26%
2020.06.09:11:34:53.034: GPU6 GPU6: DAG 26%
2020.06.09:11:34:53.038: GPU2 GPU2: DAG 31%
2020.06.09:11:34:53.356: GPU3 GPU3: DAG 31%
2020.06.09:11:34:53.408: GPU1 GPU1: DAG 26%
2020.06.09:11:34:53.787: GPU4 GPU4: DAG 31%
2020.06.09:11:34:54.156: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:34:54.156: 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)
2020.06.09:11:34:54.163: GPU5 GPU5: DAG 31%
2020.06.09:11:34:54.563: GPU6 GPU6: DAG 31%
2020.06.09:11:34:54.565: GPU2 GPU2: DAG 36%
2020.06.09:11:34:54.884: GPU3 GPU3: DAG 36%
2020.06.09:11:34:54.910: GPU1 GPU1: DAG 31%
2020.06.09:11:34:55.317: GPU4 GPU4: DAG 36%
2020.06.09:11:34:55.693: GPU5 GPU5: DAG 36%
2020.06.09:11:34:56.091: GPU6 GPU6: DAG 36%
2020.06.09:11:34:56.095: GPU2 GPU2: DAG 41%
2020.06.09:11:34:56.406: GPU3 GPU3: DAG 41%
2020.06.09:11:34:56.411: GPU1 GPU1: DAG 36%
2020.06.09:11:34:56.819: GPU4 GPU4: DAG 41%
2020.06.09:11:34:57.223: GPU5 GPU5: DAG 41%
2020.06.09:11:34:57.592: GPU6 GPU6: DAG 41%
2020.06.09:11:34:57.626: GPU2 GPU2: DAG 47%
2020.06.09:11:34:57.908: GPU3 GPU3: DAG 46%
2020.06.09:11:34:57.942: GPU1 GPU1: DAG 41%
2020.06.09:11:34:58.347: GPU4 GPU4: DAG 47%
2020.06.09:11:34:58.751: GPU5 GPU5: DAG 47%
2020.06.09:11:34:59.122: GPU6 GPU6: DAG 47%
2020.06.09:11:34:59.155: GPU2 GPU2: DAG 52%
2020.06.09:11:34:59.201: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:34:59.201: 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)
2020.06.09:11:34:59.439: GPU3 GPU3: DAG 52%
2020.06.09:11:34:59.442: GPU1 GPU1: DAG 46%
2020.06.09:11:34:59.877: GPU4 GPU4: DAG 52%
2020.06.09:11:35:00.281: GPU5 GPU5: DAG 52%
2020.06.09:11:35:00.624: GPU6 GPU6: DAG 52%
2020.06.09:11:35:00.686: GPU2 GPU2: DAG 57%
2020.06.09:11:35:00.942: GPU1 GPU1: DAG 51%
2020.06.09:11:35:00.970: GPU3 GPU3: DAG 57%
2020.06.09:11:35:01.385: GPU4 GPU4: DAG 57%
2020.06.09:11:35:01.790: GPU5 GPU5: DAG 57%
2020.06.09:11:35:02.136: GPU6 GPU6: DAG 57%
2020.06.09:11:35:02.194: GPU2 GPU2: DAG 62%
2020.06.09:11:35:02.463: GPU1 GPU1: DAG 56%
2020.06.09:11:35:02.479: GPU3 GPU3: DAG 62%
2020.06.09:11:35:02.914: GPU4 GPU4: DAG 62%
2020.06.09:11:35:03.318: GPU5 GPU5: DAG 62%
2020.06.09:11:35:03.664: GPU6 GPU6: DAG 62%
2020.06.09:11:35:03.723: GPU2 GPU2: DAG 67%
2020.06.09:11:35:03.967: GPU1 GPU1: DAG 62%
2020.06.09:11:35:04.008: GPU3 GPU3: DAG 67%
2020.06.09:11:35:04.220: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:35:04.220: 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)
2020.06.09:11:35:04.443: GPU4 GPU4: DAG 67%
2020.06.09:11:35:04.847: GPU5 GPU5: DAG 67%
2020.06.09:11:35:05.195: GPU6 GPU6: DAG 67%
2020.06.09:11:35:05.245: GPU2 GPU2: DAG 71%
2020.06.09:11:35:05.475: GPU1 GPU1: DAG 67%
2020.06.09:11:35:05.530: GPU3 GPU3: DAG 71%
2020.06.09:11:35:05.966: GPU4 GPU4: DAG 72%
2020.06.09:11:35:06.365: GPU5 GPU5: DAG 72%
2020.06.09:11:35:06.700: GPU6 GPU6: DAG 71%
2020.06.09:11:35:06.774: GPU2 GPU2: DAG 77%
2020.06.09:11:35:06.983: GPU1 GPU1: DAG 71%
2020.06.09:11:35:07.045: GPU3 GPU3: DAG 76%
2020.06.09:11:35:07.493: GPU4 GPU4: DAG 77%
2020.06.09:11:35:07.896: GPU5 GPU5: DAG 77%
2020.06.09:11:35:08.229: GPU6 GPU6: DAG 77%
2020.06.09:11:35:08.302: GPU2 GPU2: DAG 82%
2020.06.09:11:35:08.486: GPU1 GPU1: DAG 76%
2020.06.09:11:35:08.548: GPU3 GPU3: DAG 81%
2020.06.09:11:35:09.020: GPU4 GPU4: DAG 82%
2020.06.09:11:35:09.081: main GPU1: 49C 36% 52W, GPU2: 48C 36% 51W, GPU3: 48C 0% 48W, GPU4: 48C 30% 48W, GPU5: 49C 30% 49W, GPU6: 51C 50% 47W
GPUs power: 294.1 W
2020.06.09:11:35:09.283: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:35:09.283: 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)
2020.06.09:11:35:09.424: GPU5 GPU5: DAG 82%
2020.06.09:11:35:09.758: GPU6 GPU6: DAG 82%
2020.06.09:11:35:09.831: GPU2 GPU2: DAG 87%
2020.06.09:11:35:09.988: GPU1 GPU1: DAG 81%
2020.06.09:11:35:10.048: GPU3 GPU3: DAG 87%
2020.06.09:11:35:10.549: GPU4 GPU4: DAG 87%
2020.06.09:11:35:10.953: GPU5 GPU5: DAG 87%
2020.06.09:11:35:11.287: GPU6 GPU6: DAG 87%
2020.06.09:11:35:11.361: GPU2 GPU2: DAG 92%
2020.06.09:11:35:11.514: GPU1 GPU1: DAG 86%
2020.06.09:11:35:11.549: GPU3 GPU3: DAG 92%
2020.06.09:11:35:12.059: GPU4 GPU4: DAG 92%
2020.06.09:11:35:12.479: GPU5 GPU5: DAG 92%
2020.06.09:11:35:12.787: GPU6 GPU6: DAG 92%
2020.06.09:11:35:12.869: GPU2 GPU2: DAG 97%
2020.06.09:11:35:13.043: GPU1 GPU1: DAG 91%
2020.06.09:11:35:13.077: GPU3 GPU3: DAG 97%
2020.06.09:11:35:13.586: GPU4 GPU4: DAG 98%
2020.06.09:11:35:13.811: GPU2 GPU2: DAG generated in 30.3 s (124.0 MB/s)
2020.06.09:11:35:13.813: GPU2 GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
2020.06.09:11:35:14.006: GPU5 GPU5: DAG 98%
2020.06.09:11:35:14.141: GPU3 GPU3: DAG generated in 30.2 s (124.1 MB/s)
2020.06.09:11:35:14.143: GPU3 GPU3: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
2020.06.09:11:35:14.310: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:35:14.310: 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)
2020.06.09:11:35:14.319: GPU6 GPU6: DAG 97%
2020.06.09:11:35:14.475: GPU4 GPU4: DAG generated in 30.2 s (124.3 MB/s)
2020.06.09:11:35:14.478: GPU4 GPU4: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
2020.06.09:11:35:14.573: GPU1 GPU1: DAG 96%
2020.06.09:11:35:14.857: GPU5 GPU5: DAG generated in 30.2 s (124.4 MB/s)
2020.06.09:11:35:14.860: GPU5 GPU5: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
2020.06.09:11:35:15.264: GPU6 GPU6: DAG generated in 30.2 s (124.4 MB/s)
2020.06.09:11:35:15.271: GPU6 GPU6: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
2020.06.09:11:35:15.877: GPU1 GPU1: DAG generated in 30.4 s (123.6 MB/s)
2020.06.09:11:35:15.879: GPU1 GPU1: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
2020.06.09:11:35:19.330: main Eth speed: 187.068 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:35:19.330: main GPUs: 1: 30.672 MH/s (0) 2: 31.290 MH/s (0) 3: 31.300 MH/s (0) 4: 31.282 MH/s (0) 5: 31.281 MH/s (0) 6: 31.244 MH/s (0)
2020.06.09:11:35:24.149: main
2020.06.09:11:35:24.149: main *** 0:00 *** 6/9 11:35 **************************************
2020.06.09:11:35:24.189: main Eth: Mining ETH on daggerhashimoto.eu.nicehash.com:3353 for 0:00
2020.06.09:11:35:24.189: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2020.06.09:11:35:24.189: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2020.06.09:11:35:24.189: main Eth: Average speed (5 min): 0.000 MH/s
2020.06.09:11:35:24.189: main
2020.06.09:11:35:24.342: eths Eth: Received: {"id":null,"method":"mining.notify","params":["0000000089876fc2","db084c0babc26227cb293196dd3ed4107a244dd20cef31b35a298c3bbaa62bb7","b5f0689c6ad70a980c56534194e9abe12fe690518334e1908be9dea2b4815f20",true]}
2020.06.09:11:35:24.342: eths Eth: New job #b5f0689c from daggerhashimoto.eu.nicehash.com:3353; diff: 3436MH
2020.06.09:11:35:24.390: main Eth speed: 187.190 MH/s, shares: 0/0/0, time: 0:00
2020.06.09:11:35:24.390: main GPUs: 1: 30.720 MH/s (0) 2: 31.304 MH/s (0) 3: 31.267 MH/s (0) 4: 31.303 MH/s (0) 5: 31.306 MH/s (0) 6: 31.290 MH/s (0)
2020.06.09:11:35:24.658: eths Eth: Received: {"id":null,"method":"mining.notify","params":["0000000089877347","db084c0babc26227cb293196dd3ed4107a244dd20cef31b35a298c3bbaa62bb7","0a46cd1c5d640d55e030371eb71969c64e93bf7621df1d275aa4b21fb2c20468",false]}
2020.06.09:11:35:24.658: eths Eth: New job #0a46cd1c from daggerhashimoto.eu.nicehash.com:3353; diff: 3436MH

alex31

member

Activity: 93

Merit: 10

Quote from: boregepco on June 09, 2020, 04:35:20 AM

Quote from: alex31 on June 09, 2020, 03:00:25 AM

Quote from: boregepco on June 08, 2020, 11:59:45 AM

I am with a driver version: 19.4.3 and Phoenix Miner 5.0e Windows/msvc - Release build. When the miner makes a DAG for epoch #340 is ok. But the 4GB card stops when the miner starts to make a DAG for epoch #351.

Try set -rvram -1 on command line or in config, may be this can resolve your issue

I have this in my config...

please show log of startup PhoenixMiner for more information ...

boregepco

newbie

Activity: 26

Merit: 0

Quote from: alex31 on June 09, 2020, 03:00:25 AM

Quote from: boregepco on June 08, 2020, 11:59:45 AM

I am with a driver version: 19.4.3 and Phoenix Miner 5.0e Windows/msvc - Release build. When the miner makes a DAG for epoch #340 is ok. But the 4GB card stops when the miner starts to make a DAG for epoch #351.

Try set -rvram -1 on command line or in config, may be this can resolve your issue

I have this in my config...

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