SSL works. cool.
@PM suggestion: show the SSL in the console.
Yes, we realized that there is only one message that indicates a secure connection. We will fix this in the next release.
hi
i'm getting "CUDART error in CudaProgram.cu:172 : unspecified launch failure" every 10 or 15 minutes.
what could be possible reasons and how to solve it?
This is part of the DAG-generation kernel. What coin you are mining? Try to specify the coin you are mining with the
-coin xxx command-line argument (xxx could be one of: eth, etc, exp, music, ubq, pirl, ella, etp, pgc, akroma, whale, or vic; see the Readme.txt or the first post for details) to avoid unnecessary DAG generation during devfee periods.
Does SSL give more stale shares?
No, it doesn't affect the stale shares or effective hashrate in any way. It just encrypts and authenticates the connection between the miner and the pool, making the man-in-the-middle attacks impossible.
i'm getting error FATAL ERROR: debugger detected
Gigabyte rx570
-amd option key doesn't help
Sorry about that. We will make some changes in this code in the next release of PhoenixMiner to lower the probability of this thing happening. So far we have determined that tool old or non-official drivers may be one of the reasons for the problem.
The best thing to compare is the number of found shares for given time period. Obviously this requires a significantly longer test period but even in your example you can see 43 shares from PhoenixMiner for 26 minutes and 42 shares from Claymore for 28 minutes. Also, you can compare the 5 min average hashrate on PhoenixMiner, which is 278.578 MH/s in your case, and 1 min average hashrate on Claymore, which is 278.149 MH/s in the second screenshot.
Also, if you want to increase the hashrate of PhoenixMiner "to the max", specify the
-mi 12 command-line option but keep an eye on the stale shares. Finally, you should lower the overclock on your GPU3 (the third GPU) because it is giving more incorrect shares than correct ones - anything over 0.1-0.5% incorrect shares on given GPU is just not worth it.
had a weird problem today. windows performed some updates and detected the phoenix miner exe as a trojan (i know it's false) and deleted the file, which killed the miner. turned off windows active protection, re-extracted 2.7b, then restarted it. after a couple hours it stopped again. upon restarting it it would give me an error about not having the proper priviledges. run as admin (wasnt needed before), and then it says it cant find the phoenix miner exe despite still being there in the same directory as my .bat file.
downloaded 2.7c and the problem seems to have gone away.
The best way to fix the problem is to add the folder(s) where you keep the miner software to the Windows Defender exceptions as specified here:
https://support.microsoft.com/en-us/help/4028485/windows-10-add-an-exclusion-to-windows-defender-antivirus. Otherwise, it can delete the executable again in the most inconvenient time, even while the miner is running.
Whats the best tunning for RX580 8G ? I've got lower rates than at 11.2
Claymore monitoring at port 3333 doesnt work. Sayed failed.
As we stated above, printed momentary hashrate is not the best way to compare miners. Compare the number of shares over exactly the same time period (at least 1-2 days). As for the remote monitoring, the port 3333 must be free. If you are running PhoenixMiner and Claymore at the same time, use the
-cdmport option of PhoenixMiner to change the port to something else (e.g. 3334) and use the same port when trying to connect to PhoenixMiner from the remote manager.
author=PhoenixMiner
I have a problem with the connection to ethereum.miningpoolhub.com
at the address specified by us-east.ethash-hub.miningpoolhub.com:20535 the miner does not connect.
you have an entirely different address in the example us-east1.ethereum.miningpoolhub.com:20536. Where does this address come from?
at this address connects but the number of rejects exceeds 50%
how to make the miner work concretely with asia.ethash-hub.miningpoolhub.com:20535?
Hmm, sorry about that, this is obviously a typo on our part. We will fix it. As for the connection problems, make sure to specify the
-proto 1 command line option when connecting to the ethash pools of miningpoolhub:
PhoenixMiner.exe -pool asia.ethash-hub.miningpoolhub.com:20535 -wal YourLoginName.WorkerName -pass x -proto 1
