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

[DrG]

Anyone have an idea why my rx480 rigs always have lower current hash values to reported on ethermine pool while my 1070 rigs always report more current than reported?  They both have been running for a week or more consistently.

It all comes down to share submission. It's not like the pool is discriminating against AMD cards versus nVidia cards. If you left the miners running for the same amount of time, just compare the amount of shares submitted between the 2 rigs (assuming same difficulty). The ratio should be within 5% of that ration that is showing on your local machine. Anything more that 5% deviance you can start suspecting things. Maybe one rig has more latency.

[bategojko74]

8x580
phoenix 238mhs, clay 243mhs
why such difference? long time ago mined eth and phoenix was faster.

With Phoenix it's need to use AMD memory tweak tool to set REF parameter. Claymore can do this by -rxboost option. Phoenix not.

Yet. Hope the developer will soon add this feature.

[UnclWish]

8x580
phoenix 238mhs, clay 243mhs
why such difference? long time ago mined eth and phoenix was faster.

With Phoenix it's need to use AMD memory tweak tool to set REF parameter. Claymore can do this by -rxboost option. Phoenix not.

Yet. Hope the developer will soon add this feature.

I hope too. But dev several years didn't add this feature... Hope slowly dies...

[rdbase]

8x580
phoenix 238mhs, clay 243mhs
why such difference? long time ago mined eth and phoenix was faster.

With Phoenix it's need to use AMD memory tweak tool to set REF parameter. Claymore can do this by -rxboost option. Phoenix not.

Yet. Hope the developer will soon add this feature.

I hope too. But dev several years didn't add this feature... Hope slowly dies...

AMD mem tweak is there!
You just need to set the value to 30.
Even though it states 20 is default I've found 30 works better according to some researching about it.

Now they just need to release version 5.2 already to fix the 4gb mining problem where the current release states those cards don't have enough vram to start mining. The warning in bright yellow is at the beginning of the process for detecting the cards you have installed in your rig.
And yes, the program has been like this for the past month from the beginning of October.
It is a problem Phoenix Miner Devs!
Look: https://bitcointalk.org/index.php?topic=5281830

Lolminer has already addressed the problem with their last release several weeks ago.

[UnclWish]

AMD mem tweak is there!
You just need to set the value to 30.
Even though it states 20 is default I've found 30 works better according to some researching about it.

What program on screenshot? AMD mem tweak looks different for me...

[rdbase]

^^
This is hiveos. If it's not there (it wasn't there for me until I did the following), then you just need to update or use the latest version of their os.
They released memtweak for phoenix miner since earlier this year.

[NCarter84]

Anyone have an idea why my rx480 rigs always have lower current hash values to reported on ethermine pool while my 1070 rigs always report more current than reported?  They both have been running for a week or more consistently.

What percentage difference are we talking about here?

You are probably experiencing variance. Meaning that the speed you see per GPU says 30MH/s is just an estimate of what hashrate you should get in the long run. However it depends on how many shares you actually found. This number can be higher or lower than your actual hashrate. Most likely always lower since you got dev free mining, stales and might get internet connection problems.

Eventually as time -> infinity you will find its more and more close to your true hashing rate.

Your pool side average should be within a few % at any given time, you are correct. But, when your poolside average is always 3-4% lower, day after day after day then something is wrong with the miner.

Sneak Peak on a project I'm working on.

 

• Expected Hashrate   57.26
• Average Hash   55.19
• Days At or Above 57.26 | 5
• Days Below 57.26 | 42
• % off from Expected   -3.62%
• Average Daily Shares   1192.28

[zeef]

IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.0e or later version to continue mining after DAG epoch 350 (both ETH and ETC has already passed DAG epoch 350). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0e and later:

Just moved to lolminer because today on this epoch (371) my 4gb cards stops hashing, cant realoce VRAM
Any future release to solve this problem?
I got all good configurated and switch from claysmore 2 months ago to PM and worked flawless until today.
I got too one 8gb card on the system and one vega. (This two i use PM)

Thanks

[Crash95]

IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.0e or later version to continue mining after DAG epoch 350 (both ETH and ETC has already passed DAG epoch 350). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0e and later:

Just moved to lolminer because today on this epoch (371) my 4gb cards stops hashing, cant realoce VRAM
Any future release to solve this problem?
I got all good configurated and switch from claysmore 2 months ago to PM and worked flawless until today.
I got too one 8gb card on the system and one vega. (This two i use PM)

Thanks

Same here !

[fanis77]

hi
my rx580 8gb stop mining ETC at #379 epoch (4GB DAG size) in win10 & PhoenixMiner 5.1c
but still work ETH at #368 epoch.
my driver is Crimson Beta for Blockchain.
i dont have any problem in linux but some rigs work in win10.
any suggestion?
 

Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.8.1 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).

Your 8GB RX580 should be able to mine ETC without issues though, even with Blockchain drivers.

but my 8gb rx580 stop mining ETC...
the problem is PhoenixMiner 5.1c!!!
this miner dosen't support after #379 epoch (4GB DAG size) in win10.
any one can mine ETC in win10 with 8gb gpus on PhoenixMiner or claymore now???

I had the same problem bro on blockchain drivers. Try last Adrenaline drivers version 20.10.1

[zeef]

hi
my rx580 8gb stop mining ETC at #379 epoch (4GB DAG size) in win10 & PhoenixMiner 5.1c
but still work ETH at #368 epoch.
my driver is Crimson Beta for Blockchain.
i dont have any problem in linux but some rigs work in win10.
any suggestion?
 

Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.8.1 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).

Your 8GB RX580 should be able to mine ETC without issues though, even with Blockchain drivers.

but my 8gb rx580 stop mining ETC...
the problem is PhoenixMiner 5.1c!!!
this miner dosen't support after #379 epoch (4GB DAG size) in win10.
any one can mine ETC in win10 with 8gb gpus on PhoenixMiner or claymore now???

I had the same problem bro on blockchain drivers. Try last Adrenaline drivers version 20.10.1

Blockchain drivers are deprecated
I use 19.5.2 that should work.
 

First post says:

"

    Do not upgrade to a new AMD driver unless it is explicitly supported by PhoenixMiner. With 4 GB AMD cards, this will not only lower your hashrate but it will make impossible to mine when the DAG epoch is above 350.
    After the DAG epoch becomes more than 350, the optimal -gt value for the 4 GB AMD cards may change. So, we recommend to run auto-tune again after DAG epoch 350 to find the best GT values for the cards.


After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers:

    Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.8.1 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.

"
 

[zeef]

Should the -gt value from an card from an algo be used to mine another algo, or we should should use auto-tune when switch to other algo and after the best value achieved we should fix it in .config file?

For example my -gt values from ETH can be used to mine UBIQ?

Thanks

[melpheos]

What's going on again ?
I switched from Ethermine to Niceshash (with daggerhashimoto) with my 8gb 1070Ti rig (motherboard has 8Gb of ram) and I see the same issue I had when my motherboard had only 2gb or ram !
The only difference I see between Nicehash and Ethermine is that nicehash request a 4Gb DAG while ethermine starts with 3.8Gb
The speed is halfed and the power usage is reduced by 25% (going from 100w to 75w)
Any ideas ?

[jgonzi]

Anyone have an idea why my rx480 rigs always have lower current hash values to reported on ethermine pool while my 1070 rigs always report more current than reported?  They both have been running for a week or more consistently.

What percentage difference are we talking about here?

You are probably experiencing variance. Meaning that the speed you see per GPU says 30MH/s is just an estimate of what hashrate you should get in the long run. However it depends on how many shares you actually found. This number can be higher or lower than your actual hashrate. Most likely always lower since you got dev free mining, stales and might get internet connection problems.

Eventually as time -> infinity you will find its more and more close to your true hashing rate.

Your pool side average should be within a few % at any given time, you are correct. But, when your poolside average is always 3-4% lower, day after day after day then something is wrong with the miner.

Sneak Peak on a project I'm working on.

 

• Expected Hashrate   57.26
• Average Hash   55.19
• Days At or Above 57.26 | 5
• Days Below 57.26 | 42
• % off from Expected   -3.62%
• Average Daily Shares   1192.28

Nice stats… you should try with another miner and give ups the information that Phoenix has the Mhs up that the reallity

[NCarter84]

Anyone have an idea why my rx480 rigs always have lower current hash values to reported on ethermine pool while my 1070 rigs always report more current than reported?  They both have been running for a week or more consistently.

What percentage difference are we talking about here?

You are probably experiencing variance. Meaning that the speed you see per GPU says 30MH/s is just an estimate of what hashrate you should get in the long run. However it depends on how many shares you actually found. This number can be higher or lower than your actual hashrate. Most likely always lower since you got dev free mining, stales and might get internet connection problems.

Eventually as time -> infinity you will find its more and more close to your true hashing rate.

Your pool side average should be within a few % at any given time, you are correct. But, when your poolside average is always 3-4% lower, day after day after day then something is wrong with the miner.

Sneak Peak on a project I'm working on.

 

• Expected Hashrate   57.26
• Average Hash   55.19
• Days At or Above 57.26 | 5
• Days Below 57.26 | 42
• % off from Expected   -3.62%
• Average Daily Shares   1192.28

Nice stats… you should try with another miner and give ups the information that Phoenix has the Mhs up that the reallity

I have those other stats for the miners too... Will be releasing all info next month once the test is done.

[fapar]

Should the -gt value from an card from an algo be used to mine another algo, or we should should use auto-tune when switch to other algo and after the best value achieved we should fix it in .config file?

For example my -gt values from ETH can be used to mine UBIQ?

Thanks

In your case, it is better to use auto-tuning -gt 0. Because the previously found best value for ETH may be worse for CLO or UBIQ.

[Ursul0]

some weirdness for you:

[UnclWish]

some weirdness for you:

In Windows device manager list GPU's didn't go in order of PCI bus number. They're in alphabetical order there.

[BogdanCo]

some weirdness for you:

In Windows device manager list GPU's didn't go in order of PCI bus number. They're in alphabetical order there.

Still.... he has 4 Vega and 4 Rx 5700 according to PM )

[Ursul0]

some weirdness for you:

In Windows device manager list GPU's didn't go in order of PCI bus number. They're in alphabetical order there.

Still.... he has 4 Vega and 4 Rx 5700 according to PM )

still the same fuckery. the dev manager is the correct, as it is also apparent from the hash.
also I run 12gpu rigs on asrock 14nm btc since 2017, I know all about enumeration of busses devices and win registry.

...not even trying to fix it now. it has other issues, more critical.