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

Anybody got Nicehash installed?

Can you please ZIP the entire directory: C:\Users\\AppData\Local\Programs\NiceHashMiner
Or just the miner if you can find it, and upload to MEGA, https://filebin.net or somewhere?

Let's find out what the hell NH did and what checksums they matched.
I'll also put the miner through some malware sandboxes.

Well, nicehash is drawing such drastic conclusions based on only one fact - that it got deleted from Mega. Actually very frightening how far nicehash is willing to go without any malicious evidence/proof.

I'm not a very good crisis communicator myself, so I can't really judge them on their communication skills, but c'mon, they said "maintenance" while hack was happening years ago.
Now they're saying "delete everything", just because Mega deleted a hosted file and claiming that phoenix is trying to cover their tracks.

Are they serious? Totally dysfunctional company and management.

I'm out. But will follow how this unrolls.

My phoenix working normal nothing wrong, i remember once i downloaded wrong from other source then it began working on devfee really bad. i cleaned pc till then it was good lesson. it will be very sad if phoenix also will dissapear like claymore did, and it proofs that phoenix become from claymore because phoenix itself cant do more develops since claymore is gone. there was argue between claymore and phoenix who is from whom stealing.

I agree with you. The only point I am a bit concerned is, that it is one thing to state there is a problem or a bug or some inconsistency, but a very different other thing, to advice users to reinstall their OS and consider all their data, wallets, logins compromised on PCs that ran phoenix. You know what I mean? It would be a bit insane to spread FUD on this level for marketing reasons.

The main question is who actually downloaded the phoenix miner from the unofficial sources and then included it in their nicehash software package for everyone to download? Answer: nicehash employees*

So don't blame the Phoenix now as he is not here to defend himself. So far it has proven to be stable software so I'll keep using it myself.

Also, there is no proof it is malicious so I'd advise nicehash against spreading the fud based on a single fact that it was removed from Mega. Claymore was also removed from Mega and no one panicked about it.

I know they're working on their excavator and they don't need/want phoenix anymore, but that's not the way to handle such transition. Very unprofessional, classic nicehash.

Edit: *NiceHash later confirmed that they didn't add the malware to their software package. They however still didn't confirm or explain which checksum they've compared and where.


Edit 2: Matjaž "djeZo" Škorjanc stated that NiceHash will publicly apologise to Phoenix miner team, but still insisting that I'm spreading the FUD. I'm not. But I have to explain why I've posted this.

They are trying to turn their PR failure (or whatever it was) into FUD against NH lead by me, again to demonstrate they can attack anyone they want at any time with their massive outreach. Phoenix, Trex, ... me on the personal level or anyone else, even the media.

My statement was based on their official statements and unofficial comments made by their team members.

Now, here is why I was 100% sure that NiceHash has included unofficial miner to their package:

1) NiceHash dev suggesting extreme precautious regarding Phoenix miner although the last version was released in 25th January 2021.
2) NiceHash tweet suggesting extreme precautious - suggesting that this is a press-release worthy incident and retweet is needed so the largest possible amount of people outside NH will see this as well.
3) "Control shasum from new download locations does not match the value published by the developer on his channel!" While we all know that last Phoenix release was on 25th January 2021.
4) Matjaž (original founder of NiceHash) threatened me in private here on Bitcointalk to delete all my posts or else I will see the consequences.
5) They didn't provide the key information where did they get the software from; or if that software was actually used or not; or if it they used it only for shasum comparison purposes.
6) No other mining management system reported similar incident, so it must look like it happened only to NiceHash.

All that has summed up to make it clear for me that they did actually packed the software in their release. Otherwise it wouldn't be that urgent to tell all the people to immediately stop using the software and format their drives, move crypto wallets elsewhere, ... why else would they suggest that if they didn't push the .exe to user's computers by mistake? That was my only obvious conclusion. Then threats only made it more suspicious as it looked like they wanted to cover their tracks of their failure and bring all the storm upon Phoenix miner. Which we are using it for 3 years and we trust it.

All that said - I couldn't have assumed anything else than what I wrote. The drama started about 9:40 AM CET with their Tweet.

https://www.nicehash.com/blog/post/stop-using-phoenix-miner-immediately

NH press release.
We need some dev to look into this. If it is malicious, it might impact a lot of users in a bad way that mine on their main computers.

it has been long time there is no development from Phoenix.

That sounds like nicehash downloaded a virus (the fake phoenix miner release) and included it in their packages?
I see no other reason for such panic.

I don't see anyone else except cudo and nicehash panicking about it.

Hope it's just lousy marketing stunt.

That’s what i was wondering about. I have been using it for 2 weeks now and this happens. If originally installed from this thread is there an issue? No one is making a statement about this??

mmmh what's happening here? https://twitter.com/NiceHashMining/status/1368481789325545473

Please let me know what is wrong with my Bat file?

PhoenixMiner.exe -pool ssl://us2.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xbc1q6j7qjcljxke64m4p9p3tjxffc3g4pxavlpuwus.Rig001
pause

I'm getting :pool login failed: Invalid user provided" error
from the log:
2021.03.07:00:55:05.778: main Phoenix Miner 5.5c Windows/msvc - Release build
2021.03.07:00:55:05.778: main Cmd line: -pool ssl://us2.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xbc1q6j7qjcljxke64m4p9p3tjxffc3g4pxavlpuwus.Rig001
2021.03.07:00:55:05.778: main No CUDA driver found
2021.03.07:00:55:06.209: main OpenCL driver version: 21.1.1
2021.03.07:00:55:06.213: main Available GPUs for mining:
2021.03.07:00:55:06.213: main GPU1: AMD Radeon RX 6900 XT (pcie 9), OpenCL 2.0, 16 GB VRAM, 40 CUs
2021.03.07:00:55:06.213: main ADL library initialized
2021.03.07:00:55:06.664: main Eth: Loading pools from epools.txt
2021.03.07:00:55:06.664: main Eth: the pool list contains 4 pools (2 from command-line)
2021.03.07:00:55:06.664: main Eth: primary pool: ssl://us2.ethermine.org:5555
2021.03.07:00:55:06.665: main Starting GPU mining
2021.03.07:00:55:06.665: main Matched GPU1 to ADL adapter index 0 (method 1)
2021.03.07:00:55:06.669: main GPU1: AMD driver 21.2.3
2021.03.07:00:55:06.669: main GPU1: Created ADL monitor for adapter 0; overdrive version: 8 (
2021.03.07:00:55:06.669: main GPU1: using AMD driver ver 21.2.3
2021.03.07:00:55:06.791: wdog Starting watchdog thread
2021.03.07:00:55:07.034: main Eth: Connecting to ethash pool ssl://us2.ethermine.org:5555 (proto: EthProxy)
2021.03.07:00:55:07.034: main GPU1: 25C 0% 9W
GPUs power: 9.0 W
2021.03.07:00:55:07.055: eths Eth: Connected to SSL ethash pool us2.ethermine.org:5555 (2606:4700:90:0:5f75:d2fd:8cfe:d849)
2021.03.07:00:55:07.095: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xbc1q6j7qjcljxke64m4p9p3tjxffc3g4pxavlpuwus.Rig001"]}

2021.03.07:00:55:07.135: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
2021.03.07:00:55:07.135: eths Pool login failed: Invalid user provided
https://i.imgur.com/BsSulF9.png

Hey guys,

What’s the status of Phoenix miner as of right now? Why was it dropped by nicehash? Should we stop mining on it? Is it risky? I haven’t seen anyone mention this but people are complaining about skimming andor under/over evaluating hashrate? Could someone shed a light on this

Thank you

thank you for your answer. and yes, i have it as a delta (-200 core +300 mems)
maybe should i decrease it less?

I am not running any Nvidia cards, but I just happen to look at this today and my guess would be that Phoenixminer takes offsets for NV rather than direct values, i.e. from page 1:

-cclock Set GPU core clock in MHz (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)
-cvddc Set GPU core voltage in mV (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)
-mclock Set GPU memory clock in MHz (0 for default)
-mvddc Set GPU memory voltage in mV (0 for default)

Just a guess, but thought I'd chime in....

hi guys
i am mining with some gtx 1060 6gb.
i was using claymore before, and i could set the clock mem etc.

when i try to do the same in phoenix, it gives error. it can mine, no problems, but at stock settings, and says unable to set clock delta etc.

what can i do to fix that?

also for a rig with 5 of gtx 1060 6gb, what should be the virtual memory amount on windows 10?

thanks

edit: it says error 137

Hello developers

I have a rig with 1070 and 1080Ti mixed. I have to use -straps 2 to get the correct hash from 1080Tis but when I do the rig crashes every 4 hours.

I separated the 1080tis to another machine and they work perfectly fine, no crashes in a week.

I have to out the 1080Ti back in the rig along with 1070s so I think the culprit is the -straps 2

Can -straps 2 be applied to only 2 cards out of 5?

Any help is greatly appreciated!!!

I am now, but it looks like SMOS was reporting the same number only averaged for some number of seconds so I think I have a handle on the actual clock speed being used so I am now focusing on just one GPU specifically that exhibits this behavior. So just to be clear I am now setting the clock rates and voltages using the following inputs to PM:

-cclock 1300 -mclock 900 -cvddc 800

At startup SMOS shows those exact values and a hashrate of ~52 MH/s. After about five minutes the core clock drops to between 845 and 880 and changes every few seconds but is now hashing at only ~36 MH/s.

Seems like some loop is targeting the core clock to compensate for something it perceives to be wrong or suboptimal in some way sacrificing hashrate in the process. What I don't understand is 1) which program is doing this (by process of elimination I'd guess it's the driver) and 2) if it is capable of hashing at 52 MH/s why can't I (or how can I) just force it to retain those values and either crash or start throwing HW errors or something. My best guess at this point is that the driver could just be designed to protect the card at all costs and maybe the chip in this particular one is from a lower quality bin?

I can add that the card I'm focusing on is a Msi RX 5700 XT 8GB, but as I've said before others of the same make and model are running fine in parallel on the same rig.

Hmm, one other thing I just noticed, of all the cards on this rig (14 currently) the ones showing this behavior are all MSI XTs. In contrast all the XFX XTs and MSI XLs seem to hold clock and hashrates much better so I guess it could be a problem with these particular MSI cards. Maybe the next thing to try is to reflash them but I have not done that before so....

Hey everyone! I do have a question.

     I try to test-mine with a GTX 1060 6GB GPU, I've been trying to mine in multiple pools, like PhoenixMiner(T-Rex, Gminer) and in solo, but my hash won't exceed 1.5 MH/s.
What do you guys think what may cause this problem?
The GPU driver is updated to the newest, to 641.72.
Msi afterburner's boost doesn't affect the results.

Thank you!

While the DEV resolves the MEGA issue, If someone wants the original PhoenixMiner v5.5c archives from the OP. I have uploaded the original archives. The SHA512 hash of the archive matches the hash of the original archives listed in the OP. The links will expire in a week.


https://filebin.net/d7mhuairi05x6qp2/PhoenixMiner_5.5c_Windows.zip

You can verify the file hash in Windows 10 using the Get-FileHash command in Powershell:



https://filebin.net/tvddt3ob44iz9y1b/PhoenixMiner_5.5c_Linux.tar.gz

Its unlikely the miner is lowering clock rates after startup, I doubt that's in its capabilities - it should need to restart with different settings. Starting with the 5000 series cards there aren't the old p-states (p0-p8) of set timings but an curve of timings related to clockrate, voltage, and other factors. So the "set" clock rate will vary and due to differences in each card you can get different end timings with similar initial settings. I've got one 5700 that differs quite a bit from my others so to get the desired clockrate it (the driver/card) sets a higher voltage or to get the desired voltage the clock rate is lower.

Are you running PM with the -hstats 2 option? This shows the actual current clock rates on each card in the display along with 3 temperatures (gpu, memory-junction, and memory). I would check these values after start up and then after 5min. My 5700 I usually see a sight ramp-up in clockrate from about 1240 to 1265 after about 5mins.