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

[toynn]

Hi,

I've been mining successfully for about 2 month now - no reboots. PhoenixMiner has been working perfectly.

All of a sudden about 2 hours ago, I'm getting every share rejected.

I've tried switching to Nanopool but I get the same.

Any ideas?  

Do you use latest version? 5.3 has problems.

My rigs are fine but seems like a few similar issues suddenly got reported right about when the dag epoch changed from 389 to 390. Since ETH passed the 4GB dag size these new epoch seem a possible cause of crashes/issues depending on your GPUs, drivers, and PM version. Its happened to me a few times and always fixed by rebooting the rig and restarting the miner.

[Deafran]

Is hashrate really fluctuating with Phoenix Miner?  My radeon 7 and rx5700 hashrates are very inconsistent. GT on autotune, driver 20.12.1. I tried Team Red Miner and it was consistent.

it might coz epoch/dagsize change

i can say that coz my 4gb gpu decrease hashrate

[CGS_CC]

Any way to configure miner to start a new log file for each new day?  if I pause miner and restart will it create a new log file? or will it just continue on the current log file?

[Hacksawblade]

I just started having the same problem.......mining on Nanopool and every share started to be rejected. I have been running all week with no issues........

I am also have this problem. I have six rigs that were all mining since November when 4 gig opened back up and I switched from claymore to Phoenixminer. Although the hashrates have been decreasing over the past month, starting this morning they all skyrocketed back to their maximums I’ve ever seen. About 30 per card. However nanopool shows them all off-line and rejects transactions. I have been using Ethos with Phoenixminer 5.4b. I upgraded 1 machine to 5.4c with the same issue.  I looked at the miner log and it looks like there’s something going on with the Epoch 390. I get the error “not enough vram for dag Epoch 390”. Is this the end of mining ETC with 4 gig cards?

Thanks in advance to anyone who can offer me advice,

Ken

[earlybird36]

Is hashrate really fluctuating with Phoenix Miner?  My radeon 7 and rx5700 hashrates are very inconsistent. GT on autotune, driver 20.12.1. I tried Team Red Miner and it was consistent.

Yes, it happens because of overclocking. Don't overclock your memory too much...

Memory is not overclocked that much. I noticed the fluctuation started when we switched to epoch 384

[Deafran]

I just started having the same problem.......mining on Nanopool and every share started to be rejected. I have been running all week with no issues........

I am also have this problem. I have six rigs that were all mining since November when 4 gig opened back up and I switched from claymore to Phoenixminer. Although the hashrates have been decreasing over the past month, starting this morning they all skyrocketed back to their maximums I’ve ever seen. About 30 per card. However nanopool shows them all off-line and rejects transactions. I have been using Ethos with Phoenixminer 5.4b. I upgraded 1 machine to 5.4c with the same issue.  I looked at the miner log and it looks like there’s something going on with the Epoch 390. I get the error “not enough vram for dag Epoch 390”. Is this the end of mining ETC with 4 gig cards?

Thanks in advance to anyone who can offer me advice,

Ken

here my 4 gb :

71°C  Fan: 2.8    Hash: 14.59    01 Ellesmere RX 570 115-D009PI0-100 SK Hynix
57°C  Fan: 2.7    Hash: 14.79    03 Ellesmere RX 470 113-WE353FU-M73 Samsung
70°C  Fan: 2.8    Hash: 14.56    04 Ellesmere RX 570 115-D009PI0-100 SK Hynix
64°C  Fan: 2.8    Hash: 14.60    05 Ellesmere RX 570 115-D009PI0-100 SK Hynix
77°C  Fan: 2.6    Hash: 14.59    06 Ellesmere RX 570 115-D009PI0-100 SK Hynix

about last 2 days i am using other miner, miner for amd only, with ethos

[bokel1]

Hi, I was trying to run my old rx580 on the same win machine I am running 3x RX 5700 and it was mining with 8MH/s and it was not stable. Any ideas? thanks!

[grazzyman]

Hi, I was trying to run my old rx580 on the same win machine I am running 3x RX 5700 and it was mining with 8MH/s and it was not stable. Any ideas? thanks!

I Have the same issue 4x RX580's and 2x GTX1070s. ***all 8GB CARDS***
All perfectly stable for months then all of a sudden approx. 4pm UK time yesterday, nothing will work.   Also went back and took a look if claymore worked...it did not.

Is this anything to do with the minor pools trying to go against the bigger ones?

I'm hoping someone with more experience can help on this forum.

[j2james]

Hi, I was trying to run my old rx580 on the same win machine I am running 3x RX 5700 and it was mining with 8MH/s and it was not stable. Any ideas? thanks!

I Have the same issue 4x RX580's and 2x GTX1070s.
All perfectly stable for months then all of a sudden approx. 4pm UK time yesterday, nothing will work.  Also went back and took a look if claymore worked...it did not.

Is this anything to do with the minor pools trying to go against the bigger ones?

I'm hoping someone with more experience can help on this forum.

Which OS do you use? I had problems in Win 7. 6 * gtx-1070. After switch to Win 10 all works.

[grazzyman]

Which OS do you use? I had problems in Win 7. 6 * gtx-1070. After switch to Win 10 all works.

Im on Windows 10 Pro.

[tuchubby]

Would it be possible to reload the config.txt with "c" key forcefully? 

For example:
1.  I press "c" and my config loads up hardware parameters.
2.  I go into a different application and adjust GPU power/clock/fan.
3.  If I press "c" again on the miner, it doesn't reload my settings. 

It doesn't know that hardware parameters were changed elsewhere.  My theory is pressing the "c" key reloads config.txt, compares it with the current set of parameters, then only applies parameters that have been updated.  It does not forcefully reload the entire config.txt. 

[grazzyman]

Some extra info... all my cards are 8GB, so I don't think this is a 4GB card issue.

It seems as time goes on, more and more miners are getting this issue and it does not seem to resolve by changing pool.

As I had my rig running the most sable it has ever been (moved from claymore), I'm reluctant to change drivers/bios etc. as it seems a 'sudden' change has caused this... I just can't figure out what.

[thorbob]

I have a couple of miners setup for RDP. Phoenix Miner will not generate a new DAG unless you are connected via RDP. The program is running as admin. Generating the DAG is not an issue, as I used the -bench to test multiple times in different configurations. I just verified this was the issue as I watched during the recent DAG iteration.

Any help is much appreciated! Thanks!

[manosqq]

Hello,
i tried the beta version 5.5b using the same command line from 5.4c and everything was looking fine.
My rig seemed to be mining normally and finding shares so i left it to mine using the beta version.
When i checked the pool (cruxpool)to see how the new miner was going i saw that the miner was offline from the moment i stopped the 5.4c miner.almost 10 hours.
I stopped the new version and start again the 5.4c the shares was shown at the pool normally again.
I wonder where the shares was going...

Im using windows 10 and 2rx 570 with 20.11.1 drivers

[bit-sokol]

The new beta version is ready. You can download PhoenixMiner 5.5b from here:

https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.5b_Windows.zip
    ===================================
   SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
 SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
 SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957

    File: PhoenixMiner_5.5b_Linux.tar.gz
    ====================================
   SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
 SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
 SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The new features in this release are:

• Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
• Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
• The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
• Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
• Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating

If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to  keep the temperature below 65-66 C.

Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.

This version looks stable

[madpapa]

The ver 5.5b is not stable for me. My rig was freezing sometimes. That is why I changed back to the earlier version of Phoenix. It is stable and there is no any freezing.

[skablast]

I am lost, a little help please.

A rig with
1070  8gb , GPU 1
580  8 gb  GPU 2
570  4 GB  GPU3

In order to mine only with GPU1 and  GPU2

 the command sintax is -gpus 12 in the config  in the Batch file or ?

[manosqq]

The truth is that 5.5b was very stable for me to... slightly better performance and 2-3 watts less energy,
but what to do it if shares are not showing in then pool?

[madpapa]

I am lost, a little help please.

A rig with
1070  8gb , GPU 1
580  8 gb  GPU 2
570  4 GB  GPU3

In order to mine only with GPU1 and  GPU2

 the command sintax is -gpus 12 in the config  in the Batch file or ?

comma separated -gpus 1,2,3

[grazzyman]

Hi,

So far I don't think anyone has explained why so many of us suddenly can't mine...

Code:

21.01.21:19:56:04.818: GPU3 Eth: GPU3: ETH share found!
2021.01.21:19:56:04.818: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":
line removed
2021.01.21:19:56:04.818: eths Eth: Share actual difficulty: 6734 MH
2021.01.21:19:56:04.839: eths Eth: Received: {"id":4,"jsonrpc": "2.0","result": false,"error": "Provided PoW solution is invalid!"}
2021.01.21:19:56:04.839: eths Eth: Share rejected in 21 ms

My rig has sat idle for 36 hours now. I've tried multiple versions of PhoenixMiner / Claymore and nothing works. But, the miner is happy hashing and finding shares...just 100% rejected.