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

[miner1987]

How much increment in hashrate people getting with current version for other cards?

[bit-sokol]

How much increment in hashrate people getting with current version for other cards?

Almost not.

[miner29]

PLEASE BE CAREFUL - someone is trying to post a Phoenixminer 5.4d with "10% more hashrate for eth" and so on. The .exe inside is malware and places itself into SysWOW64 as zPhoenixminer, also into Program Files in Folder "My Program" as Phoenixminer. The exe itself is described as pain. Maybe it places some more variants in different locations. The files can be removed in safe mode if you are on windows.

I always click "Report to moderator" in this case

I also did, but unfortunately I fell for it, as I had seen it the first time.
Can you recommend anything to me what to do?

wipe your computer...cover it in gasoline and light it on fire....then nuke it from space its the only way to be sure.

Get any wallets you had and use the seed to move to new machine,..do not off load anything.  And be more careful...scammers love this place because of easy marks.  especially these day with crypto way up...they are ripe to pick you clean.

[PepsiCoin88]

Hi! Only now I noticed that my AMD RX 570 (8 Gb) began to give out not 31 MH/s, but 29 MH/s (all cards). What could be the reason? Overheating (cards suffer a little from it - all at least 74 degrees Celsius)? Or is it normal?
Thank you, sorry for my English

[Baldezh2016]

anyone tried to compare hashrate on GTX 1080 vs claymore?

[bit-sokol]

anyone tried to compare hashrate on GTX 1080 vs claymore?

About the same.

[oklickmanworld]

tell me what the problem may be
I run the miner (Phoenix) on ETH, it works stably: Ubuntu 18.04.05, h110-d3a, g4400 6 cards msi rx 588, drivers 18.20, RAM 8gb, swap file 60gb, the system is on ssd-120gb.
The problem is that the miner is constantly stopped due to a memory segmentation error (the memory stack is flushed to disk).

I tried different Ubuntu distributions, different driver versions, different versions of Phoenix miner (and other miners!!), different versions of the bios, the problem does not go away, it can work from 3 minutes to 3 days

on 1 video card, the system started, and worked stably, but after setting all 6 cards, this error was repeated, I tried to shoot some of the cards, the problem did not go away.
Tell me what to do?
 
THNX

[18-Terahash]

anyone tried to compare hashrate on GTX 1080 vs claymore?

yes, it's pretty much the same.

On AMD there's a noticeable difference (cca 1MH/s higher). Besides that I can see a much more consistent submitted share count compared to Claymore. The graph is not so choppy but almost a nice straight line. This goes for nVidia gpus as well.

[PepsiCoin88]

Hi! Only now I noticed that my AMD RX 570 (8 Gb) began to give out not 31 MH/s, but 29 MH/s (all cards). What could be the reason? Overheating (cards suffer a little from it - all at least 74 degrees Celsius)? Or is it normal?
Thank you, sorry for my English

Which driver?
Turn on calculation mode.

Most recent

[Baldezh2016]

anyone tried to compare hashrate on GTX 1080 vs claymore?

yes, it's pretty much the same.

On AMD there's a noticeable difference (cca 1MH/s higher). Besides that I can see a much more consistent submitted share count compared to Claymore. The graph is not so choppy but almost a nice straight line. This goes for nVidia gpus as well.

thank you, seems not worth to try another miner 

[batsonxl]

@Mr.Phoenix please fix issue with miner. it is consuming more power than used to be. it happened like 10 days ago. Since then my rigs are consuming more power and getting hotter. Same settings nothing changed but wattmeter shows more now. thanks

[reep74]

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG  65%
GPU5: DAG  21%
GPU4: DAG  42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG  63%
GPU2: DAG  81%
GPU6: DAG  21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG  41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG  63%
GPU3: DAG  80%
GPU7: DAG  21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

[reep74]

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG  65%
GPU5: DAG  21%
GPU4: DAG  42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG  63%
GPU2: DAG  81%
GPU6: DAG  21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG  41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG  63%
GPU3: DAG  80%
GPU7: DAG  21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

[bit-sokol]

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG  65%
GPU5: DAG  21%
GPU4: DAG  42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG  63%
GPU2: DAG  81%
GPU6: DAG  21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG  41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG  63%
GPU3: DAG  80%
GPU7: DAG  21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

[reep74]

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG  65%
GPU5: DAG  21%
GPU4: DAG  42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG  63%
GPU2: DAG  81%
GPU6: DAG  21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG  41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG  63%
GPU3: DAG  80%
GPU7: DAG  21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG  22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG  65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
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) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

[bit-sokol]

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG  65%
GPU5: DAG  21%
GPU4: DAG  42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG  63%
GPU2: DAG  81%
GPU6: DAG  21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG  41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG  63%
GPU3: DAG  80%
GPU7: DAG  21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG  22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG  65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
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) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

try to add this:

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1

[reep74]

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG  65%
GPU5: DAG  21%
GPU4: DAG  42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG  63%
GPU2: DAG  81%
GPU6: DAG  21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG  41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG  63%
GPU3: DAG  80%
GPU7: DAG  21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG  22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG  65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
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) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

try to add this:

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1

Same problem, delete all and paste what you write and same vram problem, today was working fine, i did not update nothing and stop mining

[FEKIH]

2021.01.08:17:09:48.320: GPU2 GPU2: DAG generated in 9.9 s (414.7 MB/s)
2021.01.08:17:09:48.321: GPU2 GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
2021.01.08:17:09:48.321: GPU2 GPU2: no -gt value specified, switching to auto-tune
2021.01.08:17:09:48.321: GPU2 GPU2: starting auto-tune process
2021.01.08:17:09:48.321: GPU2 GPU2: clSetKernelArg (-48)
2021.01.08:17:09:48.321: wdog Fatal error detected. Restarting.

[Xform]

Same but i saw this:

Try -eres 0 -rvram -1

[reep74]

Same but i saw this:

Try -eres 0 -rvram -1

ya lo intente, estoy instalando los drivers de nuevo a ver