The -mvddc doesnt work
If i put 800, HWiNFO64 shows me 850, and if i put 820,830,... al time HWiNFO64 shows 850.
Any idea? Im using 5.2c with AMD driver ver 19.12.2 (rig of 5700 xt)
VRM volts on Polaris must be no lower than the core volts Who said? |
|
|
|
|
@PhoenixMiner, AMD released 20.11.2 driver. PM 5.2c didn't support it. It's need update.
|
|
|
|
please fix mistake in subject "PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)". You have to delete word "Linux" at the end.
5.1c version for linux exists by the link on the 1st page. |
|
|
|
|
PM 5.2c - eres option didn't work again. Cache generates only for current DAG. On 5.2b eres worked...
|
|
|
|
I'm having a serious problem, All 8 of my RX580 8GB goes to 0.00Mh/s after an hour or so mostly when a new DAG is being created. It started happening only after I updated to Phoenix miner 5.2 (I am on Nicehash, Windows 10, AMD driver 20.7.2, also tried 20.9.2). My rig was stable from a month before updating Phoenix miner. LOL miner works perfectly and TRM also works perfectly. Please Help!
Using Windows 10 1909, AMD 20.11.1 driver, PM 5.2c, nicehash, RX 580 8Gb cards - all fine. Miner works many hours without any problem. How can you be on PM 5.2c ?, Nicehash software only updated it till 5.2b. Also, can you please give some more details about your system: like the motherboard moel, Amount of RAM, Virtual memory and settings like PCIe link speed, and if you're using Overdrive N tool or MSI or both? I'm didn't use Nicehash software. I'm use PM miner with manual settings for nicehash pool. Virtual memory is 8gb * amount of cards. I'm use modded vbioses. You can update PM in nicehash. Just find folder with PM in nicehash folder and replace files. |
|
|
|
I'm having a serious problem, All 8 of my RX580 8GB goes to 0.00Mh/s after an hour or so mostly when a new DAG is being created. It started happening only after I updated to Phoenix miner 5.2 (I am on Nicehash, Windows 10, AMD driver 20.7.2, also tried 20.9.2). My rig was stable from a month before updating Phoenix miner. LOL miner works perfectly and TRM also works perfectly. Please Help!
Using Windows 10 1909, AMD 20.11.1 driver, PM 5.2c, nicehash, RX 580 8Gb cards - all fine. Miner works many hours without any problem. |
|
|
|
No I didn't. I will try that now. If you can link me tutorial it would be great if not I will find it
Just add -acm option to PM command line and run with administrator rights. |
|
|
|
No win 10
On new drivers did you canhged your cards to compute mode? |
|
|
|
I need help. I used to mine with Claymore 15, Blokchain driver and RX570 nitro+. My speeds were 32.5 Mh/s and I switched to Phoenix miner but my speed is 31.5 and I cant change -mvddc value. If I put -mvddc it wont start mining just crashes. I can mine without that value but my power usage goes up a lot when compared to Claymore. I tried 20.8.1 drivers but only get 10 Mh/s and I can get it to work with -mvddc 900. Any ideas?
Windows 7? |
|
|
|
Where is 1.13 for Windows? On github only for linux...
Sry, I was not that quick xD Now we are even at 1.14 ... had some issues with Nvidia rigs ... but well thats fixed and some Nvidia candy added  Power consumption on Polarises with 1.14 is good! It's very close to PM miner now. Maybe the same. Speed is the same as was in previous versions... About 1.7% slower than PM. Another question: RX 580-8 rig. On 1st card of rig. When monitor connected and trying to look video on youtube or play any videofile (even in bad quality f.e. 320p) video playback goes with freezes. On all other miners (Claymore, TR, PM) video plays without problems during eth mining. |
|
|
|
|
Now testing 1.14 version on RX 580 8Gb rigs... Eth on nicehash.
|
|
|
|
Hi all !
I have some trouble with 2 Mining-Rigs. After a Windows update, Phoenix Miner (all Versions) closes directley after starting. Curios: When i turn on only Nvidia-Card, it starts correctly. It must be a problem with the AMD-Cards. I have reinstalled the AMD-Driver but that doesn't help at all ... any suggestions ?
Christian
Have the same problem. Everything worked fine until the latest rig reboot. Windows decided to update and miner stopped working. Driver 20.5.1. Tried Phoenix Miner 5.0e, 5.1c, 5.2b - all versions just closes after start without showing any errors. Maybe driver must be not so old? Try latest. |
|
|
|
Hi all !
I have some trouble with 2 Mining-Rigs. After a Windows update, Phoenix Miner (all Versions) closes directley after starting. Curios: When i turn on only Nvidia-Card, it starts correctly. It must be a problem with the AMD-Cards. I have reinstalled the AMD-Driver but that doesn't help at all ... any suggestions ?
Christian
What driver for AMD? |
|
|
|
|
Where is 1.13 for Windows? On github only for linux...
|
|
|
|
My mixed rig with 3x P106, 4x1060 6Gb, 2xNitro RX580 8gb works well with 5.2a
Drivers:
20.8.1 and 456.38
Already 5.2b exists. Us it. |
|
|
|
IMPORTANT! All owners of AMD cards with 6 GB or 8 GB RAM must either keep drivers 20.4.x or lower (do not upgrade to 20.5.1 or later), or upgrade to PhoenixMiner 5.2b or later version to continue mining after DAG epoch 384 (ETC has already passed DAG epoch 384, and ETH will pass it in less than two months).
This means that for continue mining after DAG epoch 384: 1. If you want to use PM 5.1c you must either keep drivers 20.4.x or lower (do not upgrade to 20.5.1 or later)2. If you want to upgrade your drivers to 20.5.1+ than upgrade to PhoenixMiner 5.2b or later version. Other words: PM 5.1c didn't mine DAG #384+ with new drivers, for mining with new drivers PM needs be 5.2b or later. Just try to read more carefully. |
|
|
|
win 10, adrenalin 20.4.2, 8rx578
Received: {"id":6,"jsonrpc":"2.0","result":true,"error":null}
2020.11.09:16:16:34.600: GPU4 GPU4: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:34.600: GPU4 GPU4: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:34.602: wdog Fatal error detected. Restarting.
2020.11.09:16:16:34.866: GPU3 GPU3: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:34.866: GPU3 GPU3: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.147: GPU7 GPU7: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.147: GPU7 GPU7: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.413: GPU5 GPU5: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.413: GPU5 GPU5: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.694: GPU1 GPU1: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.694: GPU1 GPU1: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.975: GPU6 GPU6: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.975: GPU6 GPU6: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:36.241: GPU8 GPU8: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:36.241: GPU8 GPU8: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:36.538: GPU2 GPU2: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:36.538: GPU2 GPU2: Allocating buffers failed with: clCreateBuffer (-61).
What can i do ?
I have exactly the same problem, I tested it on this driver and it didn't work and the BETA driver doesn't work either. Lol, wrong commandline. I donīt know why you set so much variables in commandline, most of this you donīt need. YOU SET WRONG COMMAND: -DAGLIM 1 is wrong, because it limits the dag size to 4006mb and the dag of etc is over (4010mb) this lol  Commandline variables that you donīt need: -eres 0 -rvram 0 -dagrestart 1 And by the way, update your driver AMD cards with 6 GB or 8 GB RAM must either keep drivers 20.4.x or lower (do not upgrade to 20.5.1 or later) in PM It's only for 5.1c version. For 5.2a-b drivers for 6-8Gb must be latest. |
|
|
|
|
PhoenixMiner, thanks for updates!
1. Please wrote recommended driver versions for 4Gb and 8Gb cards.
2. eres option didn't work now? Miner didn't show max DAG when building caches...
|
|
|
|
You forgot about PM uses less power than any other miner like lol or TR. So his loses in effectivity about some part of percent compensates by power economy in some percent! This test was 2 part... Mainly was about how the console hash comes is pretty much always going to be 3.5% higher than at the pool.... There will be days where you actually get it (as you can see in my test, but odds are going to be very slim) Also, TRM produced a better over hashrate, over the course of the year, that .75-1% will add up quickly. Power on both miners were so close that it was marginal. I didn't know about your system, but for me PM uses about 1-2% less power only from sensors (overall power economy from wall can be more). So 0.75-1% less efficiency but 1-2% less power. Until lol and TR didn't lower power draw by their miners for me choise is obvious. Software power draw means 0.... I have a 5700xt that's showing software power draw at 77w and 80w!!!!!! By the way; the software power draw for PM on these cards (with these settings) showed 84w. I didn't know about 5700xt. I use rx 580 8Gb rigs. On Polarises PM use less power. |
|
|
|
You forgot about PM uses less power than any other miner like lol or TR. So his loses in effectivity about some part of percent compensates by power economy in some percent! This test was 2 part... Mainly was about how the console hash comes is pretty much always going to be 3.5% higher than at the pool.... There will be days where you actually get it (as you can see in my test, but odds are going to be very slim) Also, TRM produced a better over hashrate, over the course of the year, that .75-1% will add up quickly. Power on both miners were so close that it was marginal. I didn't know about your system, but for me PM uses about 1-2% less power only from sensors (overall power economy from wall can be more). So 0.75-1% less efficiency but 1-2% less power. Until lol and TR didn't lower power draw by their miners for me choise is obvious. |
|
|
|
|
Show Posts
