@PhoenixMiner
During the process of optimizing the OC settings I discovered the following bug:
After mining stable for a while the miner was stopped,
in the process of changing the memory clock setting from
-mclock 2150,2150,2150,2200,2125,2200,2150,2150
to
-mclock 2150,2150,2150,2200,2150,2200,2150,2150
and restarting the miner, the hash rate for GPU5 showed no change as a result of the clock increase. However, when the rig was rebooted, the hash rate now reflected the clock change.
It would appear that restarting the miner after setting changes (in this case the miner clock, may be true for other parameters as well) does not apply these changes (write to the hardware). Only rebooting Windows affected the change.
I am running:
Windows 10 1709
AMD 18.3.1
8 x RX580 8 GB
During the process of optimizing the OC settings I discovered the following bug:
After mining stable for a while the miner was stopped,
in the process of changing the memory clock setting from
-mclock 2150,2150,2150,2200,2125,2200,2150,2150
to
-mclock 2150,2150,2150,2200,2150,2200,2150,2150
and restarting the miner, the hash rate for GPU5 showed no change as a result of the clock increase. However, when the rig was rebooted, the hash rate now reflected the clock change.
It would appear that restarting the miner after setting changes (in this case the miner clock, may be true for other parameters as well) does not apply these changes (write to the hardware). Only rebooting Windows affected the change.
I am running:
Windows 10 1709
AMD 18.3.1
8 x RX580 8 GB
Try OverdriveNTool to wipe the profiles and memory settings before starting your miner, it works quite well
