Could you help me with this? I watch a lot of videos in information about the 5700XT, with Hashrate of 56/57 MHS ...
I have managed to reach that speed by modifying the timings of the BIOS, but the RIG crashes, I can only keep it stable around 54.5Mhs, if I upload OC from memory to get more speed, it hangs in a few minutes or in several hours.
Is there a way to make the 5700XT stable with 56MHS and the Rig not crash?
This is highly dependent on the concrete card. Possible tips: keep the memory temperature low (by using lower -tt), try tools like More Power Tool, and so on.
solve trouble with pool switch crashing. old bat file option -retrydelay 1 bad. change to -retrydelay 10 all ok
Good to hear! It's generally not recommended to use
-retrydelay value under the default 5, especially on rigs with many cards.
Hi there,
I've been running 5e for a couple of days, but just today, Windows Defender is saying it's detected a Trojan:
Trojan:Win32/Bomitag.D!ml
E:\PhoenixMiner_5.0e_Windows\PhoenixMiner.exe
Any comments?
This has been answered many times before - due to the way we prevent reverse engineering of our code, many AV tools freak out. In the beginning we tried to reason with them but the problem kept repeating after each new release, so now we just gave up. As long as you have verified the checksums published here against the downloaded archive, you don't have anything to worry about.
Please tell us the driver version and the Windows version, and the version of PhoenixMiner that you are running. Also, the log from the start would help much more than just the last several lines.
I use Radeon Software Crimson ReLive Edition Beta for Blockchain Compute Driver for Windows® 10 64-bit, Windows 10 Pro x64, and Version PhoenixMiner 5.0e
AMD cards with 4 GB
won't work with the blockchain BETA driver after epoch 350-353. You need to upgrade your drivers, to at least 18.x.x - see the first post of this thread for details.
Hi, about my question, tested on drivers from 18.6.1 to 18.9.3 on them the reduction in the core frequency works, on drivers above this version it does NOT work, on the latest version 20.5.1 it does not work either. Now in the summer the -tmax parameter is very relevant, please look and if possible implement it on drivers above 18.9.3
I use most of the video cards PowerColor Red Dragon/Devil RX580, but there are others 580 series (Sapphire, Gigabyte) they also do not perceive this parameter, program Phoenix 5.0e, Windows 10 LTSB/LTSC
I'm using -tmax but it's not working
I read the whole README and couldn't find any similar automatic control.
All cards are Asus RX 580 4GB
Windows 10
PhoenixMiner_5.0e
Driver Version 20.4.2
We will look into adding -ttli (or similar) functionality in the next release.
Hi
Is it possible to display blocks found in Solo Mine?
We need to display the block found
In any card
In Solo Mine
Thanks
If you are solo mining directly on a full node (not pool), then each found share is an actual block (or uncle). If you are mining on a pool, the pool determines the difficulty and we don't know if it is enough for a block solution or not. This is because the network difficulty changes all the time and is not transmitted by any pool. Even if we use the information that is gathered by -astats from third-party websites, it is out-of-date most of the time. We may add some additional information in the next release but only when
-astats is specified.
do we still need to flash mining vbios on this or does pheonix suppots vbios straps like claymore?.
We are working on general memory timing straps but they aren't ready yet. For now, you can use either VBIOS mod or thrid-party tools like AMD Mem Tweak. Another solution is the
-mt 2 option but it isn't as powerful as the VBIOS mods or AMD Mem Tweak.
Hi phoenix!!! AMD added new drivers a linux 20.20 and Windows !!!
Yes. In another driver "masterstroke" the new Windows driver is also version 20.5.1 like the last one, despite that it was released in June and should be 20.6.1 instead. Let us repeat: do not upgrade to drivers that are newer than the version of PhoenixMiner you are using. So,
do not upgrade to the new 20.5.1 (the one from June 10) or the 20.20 Linux drivers yet.