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

[Anknownlolz]

Im running the 5.5b version with my RX 6800XT however I'm getting only around 20 MHs. I tried different settings (even gaming profile) but still the same low Hashrate. Card temps are around 45C. Same problem on 5.4c. Somehow phoenix miner detect my card only with 36CU instead of 72CU, can I somehow correct this? Core at 1500, memory 2150.

[PhoenixMiner]

PhoenixMiner 5.5c (release candidate) is ready. You can download PhoenixMiner 5.5c from here (both Windows and Linux versions):

https://github.com/PhoenixMinerDevTeam/PhoenixMiner/releases/tag/5.5c  (github.com, MEGA link is no longer active)

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 Nvidia cards under Windows):

Code:

   File: PhoenixMiner_5.5c_Windows.zip
    ===================================
   SHA-1: 9a3efe6130ba21ab2ade9df38ff9d52a539d9693
 SHA-256: 0bb20989cd107c6b65d08da30f014df0b3cb94f8124253e2caee1dfa99431c2d
 SHA-512: 2e1aa259f6519d6759ccf679bf1b989c36fe504c9066cc3ba79537bf34129fb168b2956e385a4cf593e45c3a22e89590319870fb502ff13a371932aad441b250

    File: PhoenixMiner_5.5c_Linux.tar.gz
    ====================================
   SHA-1: 43bc9221582c8e90188fb1b416df14a8259d5b4e
 SHA-256: 66914e1b5011c35cf6af3f0d3e7540f5fa1bbe1563105fd242a67a96437b8e69
 SHA-512: 1088fcfd06b1bf63a3ab0d92089504b37e634bc138290c432797594ed25d37f8e5a658cf4124b6bb4495592b2b90f89bf0a68d03f51ce97e61b69efbe0667943

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

The changes in this release (since 5.5b) include the following:

• Added support for the latest AMD Windows driver 21.1.1 (still, we don't recommend using the 21.1.1 driver yet - we had some instability issues with it even when just idling on the desktop!)
• Added new -mcdag parameter to reset the memory overclock on Nvidia cards during DAG generation. This may allow you to set higher memory overclock on your Nvidia cards without risking corrupt DAG buffer, which can lead to excessive number of incorrect shares. Use -mcdag 1 (by default the value is 0, which means turned off) to use this new feature.
  Under Linux -mcdag 1 will execute a shell script named daggen.sh (if present in the current directory) for each Nvidia GPU, passing the GPU index as the first argument, and PCIE bus ID as second argument. The miner will then wait for about 7 seconds before starting DAG generation to allow the script enough time to reset the memory overclock.
  
• The -tt parameter is now strictly for controlling the fan behavior. E.g. -tt 60 sets auto-fan speed with target temperature 60C; -tt -70 sets fixed fan speed 70%; and -tt 0 turns off the fan control. All these can be specified per GPU.
• There is a new -hwm parameter that allows controlling the frequency of the hardware monitoring, which was also done by -tt in the previous versions of PhoenixMiner
• Other small improvements and fixes

The changes of the previous beta (5.5b) since the last version (5.4c) 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 won't 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

Please let us know if you have any problems or questions related to PhoenixMiner 5.4c

[PhoenixMiner]

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.

  We need more information in order find out what exactly is happening. As a general rule we can't do anything to help you unless we have the following information: Windows (or Linux) version, driver version, how many and what cards are in the rig, and a log file, that contains not only the last few lines but also the first several minutes after the miner is started, as there are a lot of technical clues there. To avoid privacy issues, you may PM us with this information (and/or scrub your wallet address by search-and-replace operation in any text editor).

   Our best guess is that Windows may have updated your drivers to 21.1.1, which aren't supported by any version of PhoenixMiner before the just released 5.5c. But this is based on hand waving, we just need more information in order to help. Please note that this goes to everyone that wants our help.

Im running the 5.5b version with my RX 6800XT however I'm getting only around 20 MHs. I tried different settings (even gaming profile) but still the same low Hashrate. Card temps are around 45C. Same problem on 5.4c. Somehow phoenix miner detect my card only with 36CU instead of 72CU, can I somehow correct this? Core at 1500, memory 2150.

  The number of the CUs is not a problem (actually they are reported by OpenCL as 36). Something else is going on in your case. Make sure that all hardware control options of PhoenixMiner are turned off (i.e. remove all -cclock, -mclock, -tt, -cvddc, -mvdcc, etc. parameters), and set the clocks, voltages, and fans via the AMD control center software. You may also add the -hstats 2 parameter to see the actual clocks of the card when mining.

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?

  There are only a few possible answers:

• The command line (or config.txt, or epools.txt file) is not actually the same and you are mining on other wallet.
• Your version of PM 5.5b is not authentic and may be tampered with by someone if you have downloaded from anywhere else except the official MEGA github.com download link given in our posts. Please note that any "mirror", including the phoenixminer.org site, github accounts other than our official PhoenixMinerDevTeam account, etc. have nothing to do with us and we can't guarantee that the files there are not altered. If you can't download from our github.com account for any reason, at least use the checksums listed here to check if the files you have downloaded are authentic or not.
• Finally, there is a possibility of an IP MITM attack on ISP level, which redirects your connection to another pool. These aren't as rare as it seems and we personally have observed such attacks in real time. Use only SSL-enabled pools to make sure that this attack is impossible.

[nik-qz]

PhoenixMiner 5.5c (release candidate) is ready. You can download PhoenixMiner 5.5c from here (both Windows and Linux versions):
Please let us know if you have any problems or questions related to PhoenixMiner 5.4c

In the Teamredminer 8.0 program implemented a good reduction in the power supply for Polaris almost to the level of 4GB DAG, implement this in Phoenix

[alikait]

PhoenixMiner 5.5c (release candidate) is ready. You can download PhoenixMiner 5.5c from here (both Windows and Linux versions):

https://mega.nz/folder/HQ9EyYBD#qIGApl7-ZB1mLq3rjM1XOg  (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 Nvidia cards under Windows):

Code:

    File: PhoenixMiner_5.5c_Windows.zip
    ===================================
   SHA-1: 9a3efe6130ba21ab2ade9df38ff9d52a539d9693
 SHA-256: 0bb20989cd107c6b65d08da30f014df0b3cb94f8124253e2caee1dfa99431c2d
 SHA-512: 2e1aa259f6519d6759ccf679bf1b989c36fe504c9066cc3ba79537bf34129fb168b2956e385a4cf593e45c3a22e89590319870fb502ff13a371932aad441b250

    File: PhoenixMiner_5.5c_Linux.tar.gz
    ====================================
   SHA-1: 43bc9221582c8e90188fb1b416df14a8259d5b4e
 SHA-256: 66914e1b5011c35cf6af3f0d3e7540f5fa1bbe1563105fd242a67a96437b8e69
 SHA-512: 1088fcfd06b1bf63a3ab0d92089504b37e634bc138290c432797594ed25d37f8e5a658cf4124b6bb4495592b2b90f89bf0a68d03f51ce97e61b69efbe0667943

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

The changes in this release (since 5.5b) include the following:

• Added support for the latest AMD Windows driver 21.1.1 (still, we don't recommend using the 21.1.1 driver yet - we had some instability issues with it even when just idling on the desktop!)
• Added new -mcdag parameter to reset the memory overclock on Nvidia cards during DAG generation. This may allow you to set higher memory overclock on your Nvidia cards without risking corrupt DAG buffer, which can lead to excessive number of incorrect shares. Use -mcdag 1 (by default the value is 0, which means turned off) to use this new feature.
  Under Linux -mcdag 1 will execute a shell script named daggen.sh (if present in the current directory) for each Nvidia GPU, passing the GPU index as the first argument, and PCIE bus ID as second argument. The miner will then wait for about 7 seconds before starting DAG generation to allow the script enough time to reset the memory overclock.
  
• The -tt parameter is now strictly for controlling the fan behavior. E.g. -tt 60 sets auto-fan speed with target temperature 60C; -tt -70 sets fixed fan speed 70%; and -tt 0 turns off the fan control. All these can be specified per GPU.
• There is a new -hwm parameter that allows controlling the frequency of the hardware monitoring, which was also done by -tt in the previous versions of PhoenixMiner
• Other small improvements and fixes

The changes of the previous beta (5.5b) since the last version (5.4c) 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 won't 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

Please let us know if you have any problems or questions related to PhoenixMiner 5.4c

Hey Phoenix,

Any chance you guys can get the VII hashrate up like TRM? Apparently you have to use a modified kernel under linux but there are reports of 100-120mh/s, don't know how doable this would be on windows but for the few of us that have these cards it could be quite awesome.  Thanks!

[batsonxl]

@Phoenix what about straps. you said not before January well now soon it is february. please give us this feature. thanks

[Anknownlolz]

  The number of the CUs is not a problem (actually they are reported by OpenCL as 36). Something else is going on in your case. Make sure that all hardware control options of PhoenixMiner are turned off (i.e. remove all -cclock, -mclock, -tt, -cvddc, -mvdcc, etc. parameters), and set the clocks, voltages, and fans via the AMD control center software. You may also add the -hstats 2 parameter to see the actual clocks of the card when mining.

Thanks for the reply. I have everything set in AMD Radeon software. The -hstats 2 parameter is reporting same values as are set in Radeon software. Im running driver version 20.12.1. Any other ideas where could be the problem?

[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.

  We need more information in order find out what exactly is happening. As a general rule we can't do anything to help you unless we have the following information: Windows (or Linux) version, driver version, how many and what cards are in the rig, and a log file, that contains not only the last few lines but also the first several minutes after the miner is started, as there are a lot of technical clues there. To avoid privacy issues, you may PM us with this information (and/or scrub your wallet address by search-and-replace operation in any text editor).

   Our best guess is that Windows may have updated your drivers to 21.1.1, which aren't supported by any version of PhoenixMiner before the just released 5.5c. But this is based on hand waving, we just need more information in order to help. Please note that this goes to everyone that wants our help.

I've PM'd you with the requested info... hope you can help!

[bit-sokol]

PhoenixMiner 5.5c (release candidate) is ready. You can download PhoenixMiner 5.5c from here (both Windows and Linux versions):

https://mega.nz/folder/HQ9EyYBD#qIGApl7-ZB1mLq3rjM1XOg  (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 Nvidia cards under Windows):

Code:

    File: PhoenixMiner_5.5c_Windows.zip
    ===================================
   SHA-1: 9a3efe6130ba21ab2ade9df38ff9d52a539d9693
 SHA-256: 0bb20989cd107c6b65d08da30f014df0b3cb94f8124253e2caee1dfa99431c2d
 SHA-512: 2e1aa259f6519d6759ccf679bf1b989c36fe504c9066cc3ba79537bf34129fb168b2956e385a4cf593e45c3a22e89590319870fb502ff13a371932aad441b250

    File: PhoenixMiner_5.5c_Linux.tar.gz
    ====================================
   SHA-1: 43bc9221582c8e90188fb1b416df14a8259d5b4e
 SHA-256: 66914e1b5011c35cf6af3f0d3e7540f5fa1bbe1563105fd242a67a96437b8e69
 SHA-512: 1088fcfd06b1bf63a3ab0d92089504b37e634bc138290c432797594ed25d37f8e5a658cf4124b6bb4495592b2b90f89bf0a68d03f51ce97e61b69efbe0667943

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

The changes in this release (since 5.5b) include the following:

• Added support for the latest AMD Windows driver 21.1.1 (still, we don't recommend using the 21.1.1 driver yet - we had some instability issues with it even when just idling on the desktop!)
• Added new -mcdag parameter to reset the memory overclock on Nvidia cards during DAG generation. This may allow you to set higher memory overclock on your Nvidia cards without risking corrupt DAG buffer, which can lead to excessive number of incorrect shares. Use -mcdag 1 (by default the value is 0, which means turned off) to use this new feature.
  Under Linux -mcdag 1 will execute a shell script named daggen.sh (if present in the current directory) for each Nvidia GPU, passing the GPU index as the first argument, and PCIE bus ID as second argument. The miner will then wait for about 7 seconds before starting DAG generation to allow the script enough time to reset the memory overclock.
  
• The -tt parameter is now strictly for controlling the fan behavior. E.g. -tt 60 sets auto-fan speed with target temperature 60C; -tt -70 sets fixed fan speed 70%; and -tt 0 turns off the fan control. All these can be specified per GPU.
• There is a new -hwm parameter that allows controlling the frequency of the hardware monitoring, which was also done by -tt in the previous versions of PhoenixMiner
• Other small improvements and fixes

The changes of the previous beta (5.5b) since the last version (5.4c) 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 won't 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

Please let us know if you have any problems or questions related to PhoenixMiner 5.4c

Should I upgrade if I have an Nvidia 3060 TI?

[miner1987]

PhoenixMiner 5.5c (release candidate) is ready. You can download PhoenixMiner 5.5c from here (both Windows and Linux versions):

https://mega.nz/folder/HQ9EyYBD#qIGApl7-ZB1mLq3rjM1XOg  (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 Nvidia cards under Windows):

Code:

    File: PhoenixMiner_5.5c_Windows.zip
    ===================================
   SHA-1: 9a3efe6130ba21ab2ade9df38ff9d52a539d9693
 SHA-256: 0bb20989cd107c6b65d08da30f014df0b3cb94f8124253e2caee1dfa99431c2d
 SHA-512: 2e1aa259f6519d6759ccf679bf1b989c36fe504c9066cc3ba79537bf34129fb168b2956e385a4cf593e45c3a22e89590319870fb502ff13a371932aad441b250

    File: PhoenixMiner_5.5c_Linux.tar.gz
    ====================================
   SHA-1: 43bc9221582c8e90188fb1b416df14a8259d5b4e
 SHA-256: 66914e1b5011c35cf6af3f0d3e7540f5fa1bbe1563105fd242a67a96437b8e69
 SHA-512: 1088fcfd06b1bf63a3ab0d92089504b37e634bc138290c432797594ed25d37f8e5a658cf4124b6bb4495592b2b90f89bf0a68d03f51ce97e61b69efbe0667943

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

The changes in this release (since 5.5b) include the following:

• Added support for the latest AMD Windows driver 21.1.1 (still, we don't recommend using the 21.1.1 driver yet - we had some instability issues with it even when just idling on the desktop!)
• Added new -mcdag parameter to reset the memory overclock on Nvidia cards during DAG generation. This may allow you to set higher memory overclock on your Nvidia cards without risking corrupt DAG buffer, which can lead to excessive number of incorrect shares. Use -mcdag 1 (by default the value is 0, which means turned off) to use this new feature.
  Under Linux -mcdag 1 will execute a shell script named daggen.sh (if present in the current directory) for each Nvidia GPU, passing the GPU index as the first argument, and PCIE bus ID as second argument. The miner will then wait for about 7 seconds before starting DAG generation to allow the script enough time to reset the memory overclock.
  
• The -tt parameter is now strictly for controlling the fan behavior. E.g. -tt 60 sets auto-fan speed with target temperature 60C; -tt -70 sets fixed fan speed 70%; and -tt 0 turns off the fan control. All these can be specified per GPU.
• There is a new -hwm parameter that allows controlling the frequency of the hardware monitoring, which was also done by -tt in the previous versions of PhoenixMiner
• Other small improvements and fixes

The changes of the previous beta (5.5b) since the last version (5.4c) 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 won't 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

Please let us know if you have any problems or questions related to PhoenixMiner 5.4c

Thanks for the new version. It will need to be tested over the weekend.

[18-Terahash]

I do like that this miner displays my best share to the pool 

[KiparisD]

Waiting for bandwagon of "hotfix" versions aka 5.5d with +100500 improved hashrate  

[Anknownlolz]

  The number of the CUs is not a problem (actually they are reported by OpenCL as 36). Something else is going on in your case. Make sure that all hardware control options of PhoenixMiner are turned off (i.e. remove all -cclock, -mclock, -tt, -cvddc, -mvdcc, etc. parameters), and set the clocks, voltages, and fans via the AMD control center software. You may also add the -hstats 2 parameter to see the actual clocks of the card when mining.

Thanks for the reply. I have everything set in AMD Radeon software. The -hstats 2 parameter is reporting same values as are set in Radeon software. Im running driver version 20.12.1. Any other ideas where could be the problem?

So I experimented with the settings a little bit and I found out that if I set my Memory speed to 2150 (MAX) my hash rate is around 20. But if i lower it to 2100 my hash rate goes to 62. Any reason why it's behaving so weird? The card is stable, temps under 50.

[Pizacompany]

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

I have the same problem.
My rig with 5xRX580 works fine with a total has of 151Mh/s
Suddenly i saw at the https://ethermine.org that my reported has rate haw gone to 0 like my miner stop working
This is happening over three to four times a day
If anybody helps me how can i post an image i'l do it and you will see what i mean.
I logged in through internet because its far away and saw that its steal working and mining and the internet its online

Whats happening ?
Anybody has that problem ?
All the share wile I'm off the pool where are going ?
This is the pic from the pool
https://mega.nz/file/hvxGRIAa#ZKLMj-6gcfGOtFCITKb-Tc23aSTHwZ59y8Q3AIZRHW0

[grazzyman]

I have the same problem.
My rig with 5xRX580 works fine with a total has of 151Mh/s
Suddenly i saw at the https://ethermine.org that my reported has rate haw gone to 0 like my miner stop working
This is happening over three to four times a day
If anybody helps me how can i post an image i'l do it and you will see what i mean.
I logged in through internet because its far away and saw that its steal working and mining and the internet its online

Whats happening ?
Anybody has that problem ?
All the share wile I'm off the pool where are going ?
This is the pic from the pool
https://mega.nz/file/hvxGRIAa#ZKLMj-6gcfGOtFCITKb-Tc23aSTHwZ59y8Q3AIZRHW0

Hi, this is exactly the issue I posted a day or so ago...but on my rig all shares are rejected...I don’t even get small amounts of uptime. It’s very frustrating as I had a super stable rig which would run for months. The log says proof of work invalid. I’ve sent the log files to phoenixminer earlier today so hopefully someone with more experience can resolve it.

[soda37]

straps option does not work for me at all, miner simply ignore this option. I'm using 3x Vega56 cards with 20.12.1 driver with Win 10 64bit. Is it a bug?

[magicxs]

hello,
the new Feature -mcdag 1 doesn't work on my Gigabyte 3070.  using v.5.5c under win10. When i oc using afterburner before starting the miner, i will get only rejected shares after dag generation. If i dont oc befor starting the miner, the shares works fine even i oc after dag generation.
even when using -lidag 3

[grazzyman]

This is not phoenixminer problem
İ saw this problem on Ethermine pool

This problem occurs whenever I set my miner for ethermine
same system working perfect on nanopool
also same system working perfect on 2miners

I also tried Nanopool with no luck... I'll try 2miners as you suggested and see what happens...

***UPDATE: Tried 2miners, same thing 100% rejection of all shares ***

[PhoenixMiner]

This is not phoenixminer problem
İ saw this problem on Ethermine pool

This problem occurs whenever I set my miner for ethermine
same system working perfect on nanopool
also same system working perfect on 2miners

I also tried Nanopool with no luck... I'll try 2miners as you suggested and see what happens...

***UPDATE: Tried 2miners, same thing 100% rejection of all shares ***

Mystery solved! Thanks for posting the logs, they definitely helped to see what the issue is. It's very simple: you have -coin etc on your command-line (or bat file), which forces the miner to mine ETC, and this logically leads to 100% incorrect shares when trying to mine ETH. Just remove -coin etc from your bat files (or config.txt if you are using config.txt file) and everything will be back to normal!

For everybody else with 100% incorrect shares problem - check if the miner is reporting Mining ETC on instead of Mining ETH on. If this is the case, find and remove the -coin etc  parameter from your bat file, or config.txt file.

hello,
the new Feature -mcdag 1 doesn't work on my Gigabyte 3070.  using v.5.5c under win10. When i oc using afterburner before starting the miner, i will get only rejected shares after dag generation. If i dont oc befor starting the miner, the shares works fine even i oc after dag generation.
even when using -lidag 3

  If you are using external program to overclock the memory (MSI Afterburner in your case), there is no way for PhoenixMiner to control that program's behavior. So, in order to use -mcdag 1, you need to let PhoenixMiner to set your memory overclock (and turn off Afterburner). You can set the same settings that you were using in Aftrburner (e.g. -powlim -30 -mclock +800 -mcdag 1 will set power limit to 70%, will overclock the memory by 800 MHz, and will remove the memory overclock during the DAG generation to avoid corrupted DAG buffer.

   Note that the recent Nvidia drivers require PhoenixMiner.exe to be run as administrator in order to control the memory clocks.

straps option does not work for me at all, miner simply ignore this option. I'm using 3x Vega56 cards with 20.12.1 driver with Win 10 64bit. Is it a bug?

  Check the logs for any error messages related to straps, or memory timings. Most probably you are not running PhoenixMiner.exe as administrator, which is required for the straps to work.

So I experimented with the settings a little bit and I found out that if I set my Memory speed to 2150 (MAX) my hash rate is around 20. But if i lower it to 2100 my hash rate goes to 62. Any reason why it's behaving so weird? The card is stable, temps under 50.

  It is possible that the higher memory clocks are on another memory timing strap with higher latencies, which are crucial for the ethash algorithm with its random memory access pattern. You may try to switch the "Memory timing" to the "Fast timing" in the "VRAM Tuning" section of the AMD control center.

I have the same problem.
My rig with 5xRX580 works fine with a total has of 151Mh/s
Suddenly i saw at the https://ethermine.org that my reported has rate haw gone to 0 like my miner stop working
This is happening over three to four times a day
If anybody helps me how can i post an image i'l do it and you will see what i mean.
I logged in through internet because its far away and saw that its steal working and mining and the internet its online

Whats happening ?
Anybody has that problem ?
All the share wile I'm off the pool where are going ?
This is the pic from the pool
https://mega.nz/file/hvxGRIAa#ZKLMj-6gcfGOtFCITKb-Tc23aSTHwZ59y8Q3AIZRHW0

We quote ourselves: There are only a few possible reasons for this problem:

• Check the command line (or config.txt, or epools.txt file) and miner logs, and see if you are mining on the correct pool and with the correct wallet address.
• If you are seeing 100% incorrect shares, upgrade to the latest version of PhoenixMiner, and make sure that you do not have -coin XXX on your command line, bat file, or config.txt file if you are mining Ethereum. The -coin XXX parameter is only needed for other coins like ETC, UBQ, and so on.
• Your version of PhoenixMiner is not authentic and may be tampered with by someone if you have downloaded from anywhere else except the official MEGA github.com download link given in our posts. Please note that any "mirror", including the phoenixminer.org site, github accounts other than our official PhoenixMinerDevTeam account, etc. have nothing to do with us and we can't guarantee that the files there are not altered. If you can't download from MEGA for any reason, at least use the checksums listed in our posts here to check if the files you have downloaded are authentic or not.
• Finally, there is a possibility of an IP MITM attack on ISP level, which redirects your connection to another pool. These aren't as rare as it seems and we personally have observed such attacks in real time. Use only SSL-enabled pools to make sure that this attack is impossible.

[Hacksawblade]

Mystery solved! Thanks for posting the logs, they definitely helped to see what the issue is. It's very simple: you have -coin etc on your command-line (or bat file), which forces the miner to mine ETC, and this logically leads to 100% incorrect shares when trying to mine ETH. Just remove -coin etc from your bat files (or config.txt if you are using config.txt file) and everything will be back to normal!

For everybody else with 100% incorrect shares problem - check if the miner is reporting Mining ETC on instead of Mining ETH on. If this is the case, find and remove the -coin etc  parameter from your bat file, or config.txt file.


I am a bit confused. In late November with the Thanos Hardfork upgrade this brought the size of the DAG well below 4 gig so that 3 and 4 Gig cards could mine again.  The documentation I read said that we could use phoenix miner and use -coin ETC. I did this and successfully mind for about two months.  Nanopool reflected that I was mining ETH even though I used -coin ETC flag in my config file.  I never really thought about it, but now that I think about it it seems strange I mined ETC see but nanopool was reflecting ETH shares. I was thinking some sort of conversion was taking place behind the scenes.  Starting last Tuesday is when all of my minors hash rates seem normal but Nanopool reflected zero shares being mine. I tried removing the -coin ETC flag with 5.4b as you suggest but my rig show no hashing.  If I leave the -coin ETC flag the rig will hash but nanopool will not reflect this hashing. I did download Phoenixminer 5.4b from github that was running successfully with -coin ETC.  as I remember it with the hardfork we could only mine ETC with 4 Gig cards. Isn’t this true? What changed last Tuesday to make of my rigs stop (Maybe next epoch?) And why when I remove the -coin ETC does my rig stop Hashing? Any information or advice would be appreciated.


UPDATE - i’m an idiot. I just realized I was mining ETC (using Flag coin - ETC) to an ETH Nanopool. For some reason Nanopool allowed this for a couple of months and accepted the shares (they must’ve just been doing some conversion on their side). Nanopool changed something last Tuesday to Start rejecting shares of ETC going to ETH. That’s why I was getting all shares rejected.  I am now mining ETC to Nanopool (https://etc.nanopool.org/account####### also had to change pool address to etc from eth and port from 9999 to 19999). What I don’t know is why I can’t mine ETH using Phoenixminer on EthOS. Seems like an I can only get 5.4c to run on this. I couldn’t figure out how to manually update my Phoenixminer to the latest 5.5c on ethos. I got all the files to the machine but I don’t know how to run the installer on Ethos if it’s possible.

UPDATE 2 I switched everything back to the original in my config file pointing at ETH 9999 and removed -coin ETC flag. It is now working as before last Tuesday. Something in Nanopool changed for 1 week. I’m back to my original configuration running 5.4b with no problem. I did upgrade to 5.5c just for fun and see the same speeds. They are not the original 180 Hash like I was seeing a month ago. I’m down to about 75 hash but I think that’s understood due to increased difficulty.

Thanks
Ken