Its definitely difficult to get 12+ GPUs working which is why most don't try but I think 13 should be possible. You say you increased the swap file without being specific - how big is the swap file? I would have it at 90GB-100GB for 13GPUS. I run 11 on a ASROCK H110 pro btc+ and recall going from 10 to 11 gpus and eventually got it working after increasing the swap file from 64GB to 80GB. If you already have a huge swap file you might check that your swapfile disk isn't running out of space (did that to myself once too).

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.

suntrip23  - From your screenshot its seems clear that your pool/wallet info isn't being accepted from the command-line settings during miner startup so that PhoenixMiner next tries to use what is in the epools.txt file which are just examples so they don't work either. I would try to run your command-line settings from command prompt yourself (not from the bat file) and see if the same error happens or you may see other errors to help tbshoot. Alternatively get your settings in to the config.txt file and don't use the command-line settings, just launch the miner.

Sorry no help for the specific errors but if you moved your rigs and they aren't stable I would first look at thermal issues. For me this is the #1 cause of rigs crashing/issues. Monitor your gpus temps and see if any are getting higher than expected, if so deal with it. If not thermals then I see if your rig updated the cuda drivers since it was last stable. Best of luck in your mining.

Is the wallet address associated with a mining pool? You can't mine directly to an offline wallet unless you've set up a solo mining node and it would likely take years or decades before you got lucky enough to solve a block. You need to join a mining pool which allows you to participate just by submitting shares and then share in the blocks solved by the pool. Find a pool, setup an account there, and follow the instructions for how to connect. The PM Readme.txt has information on the different mining pools and how to connect. There are a lot of choices, I'm personally at miningpoolhub.com

Overclocking memory higher depends mostly on the quality of your silicon, that means being lucky to get a card that will overclock that much. You may also have to increase voltages to push higher too usually resulting in more watts burned than hash improvement gained. I've had some 570s that could to 2250 2 years ago but now, perhaps due to the dag size increases those gpus only do 2100 now. I run mine 2100@800v,1065clock@800mv getting 29.5mhs but they never crash - running 170hrs+. If you've got a stable setup at 30mhs that's a lot better than one that you've pushed only to crash every 2 hrs.

I haven't tried the -eres setting before (thought that was for 4GB issues but I'm wrong). I'll give it a try. Thank you. 

I agree this is a good setting to try. I've used -lidag 3 and it does seem to help with the crashes during dag changes and also helped with crashing at startup I was having on an 11 gpu rig. But I still get crashes on some rigs during the dag change even with the lidag setting.

Unless it was the crossing 4GB threshold I haven't. For my gpus I personally haven't found the autotune GT value to change much even when I've changed AMD drivers or PM versions or DAG epoch changes. But doing autotune is still important after a major change and depending on the gpu and how its set the best GT value does vary.

In my experiences now with the >4GB dag what worked before may not work now. Mining software like PM has to do things to keep hash rate up and wattage down that can make previous settings/card unstable.

You don't mention if this is Windows or Linux or what AMD drivers you are using -  that might help. In Windows I have no issues using the 20.8.1 driver. What voltage are you using at 1150 and what is the memory OC? The voltage and memory OC are kind of more important than cclock on card stability. I could run HWiNFO64 when mining to monitor the gpus for reported errors. This helped me find cards I needed to lower the memory OC.

Just sharing how I've setup my 570's with OverdriveNTool at 1065/800 and 2000-2100/800 depending on the card and they run very stable at about 29.2-29.5mhs drawing ~112watts at the wall. I tested higher, like 1130 cclock the voltage need to be 850mv and I could get to 30.5mhs but that found the +1mh could make the cards more unstable, generate more heat, and draw as much as 10watts more - that wasn't worth it so I'm staying with the lower hashrate.

My rigs are fine but seems like a few similar issues suddenly got reported right about when the dag epoch changed from 389 to 390. Since ETH passed the 4GB dag size these new epoch seem a possible cause of crashes/issues depending on your GPUs, drivers, and PM version. Its happened to me a few times and always fixed by rebooting the rig and restarting the miner.

Hi all and PM,

Long time watcher here but thought I would give some feedback on 5.5b - I'm running it on 2 rigs which are quite stable (uptime approx 92hrs) but on a third rig it wasn't stable so I reverted to 5.4c. Overall 5.5b is better - with wattage draw similar to 5.2e and hashrate similar to 5.4c. For my 7 GPU rig that runs stable with 5.5b it means 10-15W less vs 5.4c with a similar hashrate of 3mhs more vs 5.2e.

Unfortunately running 5.5b on my 11 GPU rig shows a lot of hashrate fluctuation on each GPU and a lower total hashrate than either 5.2e or 5.4c. Then crashes after a few hours. With 5.4c it runs quite stable.

OS:Windows 10
Driver: 20.8.1

Rig 1 (3 GPU): Vega56, RX580 x2
Rig 2 (7 GPU): RX570 x3, RX580 x2, RX5600XT, RX5700
Rig 3 (11 GPU): Vega56 x2, RX570 x4, RX580 x2, RX5600XT x2, RX5700

Seems to be already sold out on AMD and Newegg

Looks like the things are adjusting with Monero algo change fork. MPH might have had some issue post fork but from my understanding after the fork yesterday the net hash rate was still very high, around 1140MH, since its averaged over a few days. This kept the difficulty high too - around 119 billion. But the actual hash rate was much lower so blocks were taking a very long time yesterday. The net hash rate is now reported as about 645MH and difficult dropped to 78 billion. I expect we'll see the net hash rate drop further over the next 24 hours and the difficultly also adjust as things settle down with the Monero network post algo change fork.

Note the MPH Monero pool hash rate for the days before the change was 22MH - 31MH and then fell down to 4MH post fork and now at about 7.7MH. The drop in hash rate definitely shows the impact of ASICs and of course those who haven't updated their miners (or can't).