Quote from: sreetglide2011 on Today at 05:47:05 PM

Quote from: volig on Today at 04:58:31 PM

Quote from: batsonxl on Today at 06:45:42 AM

Quote from: volig on Today at 06:25:44 AM

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

yes im having that problem too. it looks like 5.2a 5.2b 5.2c has that problem, also developer do not recommend 20.9.1 driver

I haven't tried all the other drivers. The 20.9.1 driver is recommended for Phoenix version 5.2 . The first page says that we recommend drivers from 19.12.2 to 20.11.1 (inclusive). Maybe someone checked on which drivers there is no such problem?

19.12.2 to 20.8.1 (inclusive).

Page 293, post 5843, author of the Phoenix Miner. Quote:Here are some additional notes:

With PhoenixMiner 5.2c either remove the -daglim option entirely, or set it to -daglim 4023, which should work on all 470/480/570/580/590 cards with "good" drivers (see bellow)
The -daglim option works only on Polaris cards (RX470, RX480, RX570, RX580, RX590). It limits the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 374 on Windows (or after 380-383 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit), or 1 (automatic DAG limit size, usually around 4023 MB under Windows; this is the default option). Note that the hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example -daglim 3990
It is also important to use auto-tune (do not specify -gt values in the command line) because the optimal -gt value may change with each new epoch, and will definitely be different than before.
If you cards doesn't work with the default DAG limit of 4023 and require substantial decrease to 4006 or 3990, you need to update to one of the "good" AMD drivers for Windows: from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.11.1 (inclusive)
Using -rxboost, -vmr, or -straps on AMD cards requires running as administrator (or as root under Linux), so you need to run PhoenixMiner as administrator for the VRAM timing options to work. Note that the -mt option will still work without running as administrator/root.
The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.
Please let us know if you have any problems or questions related to PhoenixMiner 5.2c.

Where is my mistake?