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

Nicehash now sponsoring LinusTechTips for restore their lost reputation:
https://www.youtube.com/watch?v=swOj0wvuCO8

But really why would someone want to work with Nicehash and mining ETH but receive BTC with those super high fees instead?
I used Nicehash a few years ago for 2 weeks but not only BTC fees not worth it but also their pool always make less profits than ethermine.org even in exacts same situations.

I have 6*5700xts on my rig and this sometimes happens to me also but not too much. thanks for the description. hope the phoenix team solves this issue soon.

Hello Dev,

I started mining a month ago and used PhoenixMiner most of the time.

Every 2 or so days all my cards start getting about 30% invalid shares on my 12x 3070 rig on HiveOS. At first I thought I had an issue on the rig, maybe the mobo since it was all cards at once. But everything seemed normal and even cards at 39c had the issue. Restarting the miner always solved it.

A few weeks later I made a 2 new rigs on a different city, 3000km away (2x 12x 3070). The issue happened again, on all 3 rigs at once. This ruled out local issues.

I changed one of the rigs to a different miner just to troubleshoot if it was an issue with PhoenixMiner, and apparently is. The two rigs on PhoenixMiner exhibited the same issue a couple times, while the rig on the other miner didn't.

I searched a bit and found a post on reddit with someone with the same issue, he didn't name PhoenixMiner but said many miners are experiencing the same issue on 3060 and 3070: https://www.reddit.com/r/EtherMining/comments/lz7a3f/best_mining_software_and_how_to_choose_it/gq0s4my/?utm_source=reddit&utm_medium=web2x&context=3

Apparently it has something to do with epoch changes, I researched a bit and an epoch change occurs in eth between 8 and 48 hours, which is in line of the issue happening every few days. If a new DAG needs to be generated, the issue is likely the same when we start the miner with overclocking and get tons of invalid shares. That's why HiveOS have a config option to overclock only X seconds after miner start.

If I correctly diagnosed the issue, the solution will likely be to either restart the miner on a new epoch or send some message to HiveOS to bring the cards to default settings during epoch changes, or some other software change that makes the cards be in a stable state when loading DAGs while overclocked.

I will happily change back to PhoenixMiner when there is a solution for this issue, keep up the great work!

Thanks!

  Yes, there will be several options to control the junction temperatures and memory temperatures with the fan speed in the new version but only for AMD cards that report these temperatures. We are working on the same feature for Nvidia 3080/3090 but we are not sure it will make it for the next release.


  Everyone used it for hosting mining software when we started, and we usually don't try to fix things that aren't broken. Of course, after terminating our account, we had no choice but move elsewhere. It is encouraging that other miner software survives fine on github, so hopefully it will be our new hosting solution.



   Not that weird  - the TLB cache is part of the core, and its speed is the limiting factor of the hashrate of GTX1070 with the current DAG sizes. We could add it but not in the next release.



  It's hard to tell - could be anything. We know that the (non-fake) releases of PhoenixMiner are clean but we can't speculate for the rest. It could even be some kind of vulnerability at a browser, or OS level. We would recommend using firewall that is blocking outgoing connections (in the default state Windows firewall only asks for permission for incoming connections and allows all outgoing connections). With such firewall even if something is compromised, at least it won't be able to "phone home". These firewalls are a bit of pain in the ass to configure though, as a lot of things connect to the Internet all the time.



  The commands look fine but you need to check how the cards are listed by the miner when you run ./PhoenixMiner -list. Some cards may be named differently and won't match the selector in the commands. You should also check the log for applying the clocks and voltages for all cards. For example:

Situation:

We are no experts miners..
First we used 6 Radeon RX 580  GPU's (mixed brands) with Ubuntu as OS and Phoenixminer 5.5c as miner for a while.. Then we added a 7th 580 which came available and with no hussle we got it running. I have been busy to get the best settings for each card and got decent hashrates..

Now we wanted to up the hashrates by replacing the 580's GPU's with RX 5700 XT's one by one.
But for some reason we do not get the first one to be recognized in Phoenixminer.
It shows in the PCI list of Linux..

To make sure the 580's would run kind of optimized and since I do not know yet at what GPU number the 5700 would be set by phoenixminer, I wrote following lines in the config file:

-cclock RX*580:1150
-cvddc RX*580:850

-mclock RX*850:2175
-mvddc RX*580:860

As I understood from the help for the config file this should set the core/mem clock and voltage for all GPU's that are named RX AND 580 with the specified numbers.. all other cards (the RX 5700 XT) should use their default.
But when the miner is started the settings are not used and the RX 5700 is not displayed and we start mining with only 6 iso 7 cards.

I tried to look for any sollutions already but came without any..

Any help, ideas are highly appreciated.

Hello all,

Want to mention first that I am not here to blame anyone, probably the only one to blame is just me for not enabling 2FA.


I got hacked and here is the story.
Been using NH for about two weeks, I was like, let me jump on the train with the rest.
At the beginning I used Phoenix miner, that was the default miner in which NH was going but I noticed that after 10+ hours was getting many errors so after about 4/5 days I decided to go on Excavator.
In the whole time I managed to mine till last night about £50 worth when the account got hacked.

The hacker got full access on my PC (Main rig, because the one that I was planning to use for mining was keep crashing), used chrome and  he went in to nice hash, he enabled 2fa on his phone and goodbye account. Went on my email and deleted the emails from nice hash.
This happened last night at 00:29. At 00:52 I woke up and checked my phone and saw notifications that I enabled 2FA on my NH account, straight away I could not log in as he was receiving the notifications for 2FA, and went for forgot password on NH.

Started sending them emails and look after anyone available from NH on Twitter, Discord.
Amazingly no one answered so there are almost 24H now passed and no one bothered to answer to my account hacking emails.

As I said, not blaming anyone, already did another account and enabled 2FA, I enabled 2FA for all my email sessions and other crap like this, fixing the second rig that was supposed to be used for mining so I segregate everything that has to do with NH and all the rigs to Linux.

This is just more of a heads up for everyone, the shit is real, something did happened  and we have the below scenarios:
1) Pheonix got hacked
2) NiceHash got hacked and someone changed the binaries for Phoenix and they are trying now to blame them.
3)Excavator got hacked
4)All the above )

Seeing the Phoenix posts here he seems a legit guy/group so I am starting to discard scenario 1.
The fact that NiceHash can`t be bothered to answer my emails and don`t have any Customer Support in weekend makes me to go for Scenario two. I have emailed them on both the CS email and the 2FA one, you would imagine that they would considering the money that they spin.





LE:
Looking thru my hard drives I noticed a file created last night at 00:31, text file.
15PWpx4vXagY5cGDEvaKV2ZcW6kq8RfDNX
This is the wallet that he used, he even named it Trazor.

Phoenix mentioned about a windows bug so I will post the session from event viewer from my hacked pc.
http://

Stay safe all

An account was successfully logged on.

Subject:
   Security ID:      SYSTEM
   Account Name:      DESKTOP-XXXX
   Account Domain:      WORKGROUP
   Logon ID:      0x3E7

Logon Information:
   Logon Type:      5
   Restricted Admin Mode:   -
   Virtual Account:      No
   Elevated Token:      Yes

Impersonation Level:      Impersonation

New Logon:
   Security ID:      SYSTEM
   Account Name:      SYSTEM
   Account Domain:      NT AUTHORITY
   Logon ID:      0x3E7
   Linked Logon ID:      0x0
   Network Account Name:   -
   Network Account Domain:   -
   Logon GUID:      {00000000-0000-0000-0000-000000000000}

Process Information:
   Process ID:      0x3d4
   Process Name:      C:\Windows\System32\services.exe

Network Information:
   Workstation Name:   -
   Source Network Address:   -
   Source Port:      -

Detailed Authentication Information:
   Logon Process:      Advapi  
   Authentication Package:   Negotiate
   Transited Services:   -
   Package Name (NTLM only):   -
   Key Length:      0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The impersonation level field indicates the extent to which a process in the logon session can impersonate.

The authentication information fields provide detailed information about this specific logon request.
   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
   - Transited services indicate which intermediate services have participated in this logon request.
   - Package name indicates which sub-protocol was used among the NTLM protocols.
   - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

There are many reasons why MEGA would take mining software links down that aren't as straightforward, from hosting servers in China where there is currently a crackdown, to deciding they can't be bothered to check the safety every upload to see if it's legit when so many more of them are re-uploaded altered versions with malware versus only a handful of legit ones.

Cheers to that! I also fired up a cup of coffee and sat down to read the unfolding drama. This is the best sitcom since Trump.

Wikipedia article for more info : 

https://en.wikipedia.org/wiki/Mariposa_botnet

Very last line is important.....

Oh great, another stellar djeZo post. If only every Redditor would see the posts here instead of the ones that get censored/locked/deleted on r/NiceHash.

i have tried -lidag already. Same issue

Have you tried using -lidag 3

or 2 or 1.  0 is default but it slows down dag creation and may solve your issue.