I see now you have added full support for the Rx 6800 XT cards.I was having some issues with one such card Rx 6800 Xt in the 5.6b miner,as after a few hours this card hashrate was going to 0.Now I have just started 5.6d and will report back if any problems are still there.What driver do you suggest for this new miner 5.6 d?
The latest Windows drivers should be fine. Use
-hstats 2 to see the actual clocks/voltages on the card when mining. Also, either use PhoenixMiner exclusively for hardware control, or other OC program. If you use both, the problems are all but guaranteed.
@PhoenixMiner
Are you adding ZIL dag pre-allocation anytime soon?
somewhat strange behavior: I have updated some of my ETH+ZIL Polaris rigs to 20.9.1 + PM 5.6D (the performance is about 0.3-0.5% higher, with 1-3% lower power consumption) however now each time the switch is happening ALL the updated rigs go down, some random GPUs are failing to init the DAG (12GPU rigs), while 19.12.2 +PM 5.5C is working fine.
Yes, it will be included in the next release. Which switch is causing the problems? From ETH to ZIL or the reverse? In any case, it is unlikely that this has anything to do with the PhoenixMiner version, it is more likely that the newer drivers are the culprit. We would suggest trying 20.4.x as the latest drivers that limit the DAG size to 4 GB if you have stability issues with 20.5.1 and later versions.
I have had this several times with my GitHub repositories with miners forks.
So, GitHub blocks accounts for five reasons:
1. Someone has complained
2. Automatically by mistake
3. Someone forked the repository from a "dirty" account (When a fraudulent account is created and it starts to fork normal accounts, good chain accounts are sometimes also blocked.
4. The presence of two accounts.
5. Someone spammed the issues branch (sometimes GitHub blocks the account itself)
What I used to do and always got amnesty:
1. Write to support (
https://support.github.com/contact/account) and ask the reason for blocking. In a response letter (2-3 days), they always write the reason for blocking the account. They will also ask you to describe your files and what they do.
After they receive this information, then in 99% of cases the unlocking takes place, if you do not drag out for a long time.
I always wrote that this is a cryptocurrency miner such as NiceHash and asked why then NiceHash is not blocked? After all, this is essentially the same miner. After that I was always unblocked
Then the account never gets the Suspended status again.
Try to write support, I think it will help.
We appreciate the suggestions but for the time being we are done with github. If they at least had warned us, we would have taken measures to avoid this disruption (however short) but to terminate our account without even an e-mail message is just unacceptable. About what you can expect from Microsoft owned company.
When a GPU crashes, is there any indication in the log of which card crashed? I normally look to see which one is stuck at 0 MH/s but sometimes the card crashes and then resumes mining normally. Is there an event logged anywhere?
If the GPU doesn't bring down the whole rig, you should see something like "GPUx is not responding" towards the end of the log.
That was fast.
It certainly looks like you guys were anticipating something like this was going to happen. Kudos for getting your own repo ready quickly.
We learned some lessons from the MEGA fiasco a couple of months ago. Hopefully this would be the last time something like this happens.
is @Phonexminer hacked
I dont remmeber they ever gave a d version out, it was either beta like 5.5b
or the release 5.5c
5.5d has been usually malware
checked the HASH of 5.5C on the new website and old file and they match but hte 5.5D is a new file so if phonexminers account on here is hacked and their github is hacked... ummm
5.6d is a legitimate version (if you download it from the link in the first post, and compare the checksums for a good measure). It replaced the 5.6c, which contains a regression bug (not showing the Nvidia GPU temperatures unless
-hstats 2 is used). The problem was annoying enough and easy to fix, so we decided to just release 5.6d instead of waiting about a month or more before releasing the fix with the next PhoenixMiner version.
The above post (from the forum user
stef_stef)
probably contains malware! Do not download anything from the links in his post!
Our GitHub account was terminated (not a big surprise after they deleted some other mining software repos but we kind of liked the functionality there). Again, no explanation was given - they just don't want to host popular mining software it seems.
Our new host is up and running. You can find the latest version of PhoenixMiner (as well as older releases and beta versions) here:
https://phoenixminer.info/downloads/As always, make sure to compare the checksums of the downloaded files with these from the first post of this thread. This is a good idea for any download and takes mere seconds to do.
It very much did contain malware as I woke up and found I had been TeamViewer?(not sure) hacked and they transferred out 2.34 BTC (but left 0.27, wonder why?) among other coins. Don't be dumb like me, just thought I'd share, sad day for me. There isn't anything that can be done about it I'm guessing?
All in all I am grateful they didn't take everything but it does hurt quite a bit... the shock is wearing off and now feeling a bit sickly.
That is really bad! The best thing you can do is try to check the destination address and if it is in some of the big exchanges, you try writing them to at least block the account of the scammers.
The malicious post was deleted by the admins without 30 minutes or so, and we reported it as soon as we noticed it. The github account that it linked was created just yesterday. Please, please, do
not download anything PhoenixMIner-releated from posts that are not from our account! And always compare the checksums - it is quite easy to do and can spare you a lot of trouble. Additional good security practice is to always keep your private keys encrypted, and not on the same machine from which you are making the transactions.
Hi. Can someone give a good guide to what I should compare the checksums(the first post no longer has checksums for 5.6c) I have been running PhoenixMiner_5.6c. But I no checksums I can find match my zip or my exe.
I got it from github several days ago. which seems down now. Yhis whole situation with nicehash and multiple compromised versions seems odd.
Here is our post with the checksums of 5.6c:
https://bitcointalksearch.org/topic/m.56968316An incident with our share validation engine caused shares to be rejected for ~30 minutes. As compensation, the mining and MEV fees on Ethermine will be lowered to 0% for 48 hours starting from the 12th of May 2021 15:30 UTC. Please accept our appologies for this incident & thank you for mining with us.
what is this?
There was a problem with ethermine pool, causing a lot valid shares to be rejected as invalid. They will compensate the miners as explained in their tweet.
Has anyone figured out the low hashrate problem on Windows 7 when using NVIDIA GTX10xx series cards, RTX cards work fine on Win7 and hash at full speed, I tried diff versions of PM and still only get about half the speed, I got 14 total rigs, 6 rigs on Win7 that work great with no problems but had to switch to GMINER for the time being, and 8 rigs on Win10 using PM with no problems.
Any ideas, I think the last version that worked ok with Win7 if I remember was 5.2 or earlier.
We will try to reproduce the problem on Windows 7 rig. Is this also happening with older drivers?
@Phonexminer
Noticed some nasty bugs:
* Win10, 1060 6GB cards, when GPUs clocks are applied via miner with command line parameters, clocks/voltages/memory,
miner start reporting wrong power consumption.. [unreal low one],
you can check that by comparing the power consumption reported by miner with other tools like GPU-Z and similar.
When all those options are removed, (and miner no longer control the GPU parameters like clocks/voltages)
the miner start reporting the correct power consumption.
* Win10, for 3080 GPU when using command line option "-tmaxmem xx",
it cause brutal share staling for all GPUs (with regardless of GPU's models used in the same rig)
lag of 2888ms, 3000ms, 300ms in that range randomly vary between 300ms - 3000ms.
When this option is removed, all found shares return to normal latency of 38ms for all GPUs[/color]
We will need logs to reproduce these problems, as we haven't seen anything similar on our test rigs.
