What settings do you have for the VEGA?

As far as I know, you can mine two coins with PHI2 algo: LUX and AGM.
Both are falling in price (especially AGM), so I do not know if it will be very profitable to mine them.
My goal is to get enough coins to mount an AGM MN. I still far away ... 
I do not have pools at hand. Let me get home and I'll confirm it.

Btw, what are you mining?

Really expecting new release.
Results of PHI2 with my RX580's are spectacular.
Each new algo that is added will be welcome! 

Update listing of Intensecoin (ITNS). Intensecoin is changed name to Lethean (LTHN).

Other crypto sites updated to Lethean.

Hmm, this is actually an interesting point.  As is the miner can get hung if the output is blocked, like when you go into that editing mode in windows.  We'll change it in the next version so that the inability to print will not have an effect on mining.

You might possibly have clicked into the miner with your mouse, leaving the cursor there and blocking it from working (known issue). If you press a key or click the cursor away mining resumes.

You can lock your window and prevent this from happening if you right-click on the top bar, then "properties" and uncheck "quick edit mode".

Faced a problem. The miner just stops working. It does not hang and can be closed.

The miner has a quite aggressive style. When you lose a gpu after a few hours or even days there’s no bug per se in the miner, it’s the opencl api and/or driver that stops responding. The only solution (except you lowering clocks) is a redesign of the kernels, although it’s probable this is also more about your psus rather than the gpu clocks. We have the next-level design ready though, we’ll attack it in the near future.

1 particular miner 4x rx570 starts at  3500hs at 450W   I start on 1200/1700
Then reset in Overdriventool  and clocks are 1284/1700  and 980mv  it goes to 4100 at 520W.

I am not sure whats happening here but it doesn't matter what memory clock I start the miner on it is the same result. So if it is as I person said the memory clocks aren't applying underload. I would love to see the hashrate if they did change then. Although I have checked with hwinfo and the memory clocks are changing.
Something wierd going on with my rx570/580 cards with this miner.

As others have pointed out, this stuff doesn't really belong in the miner, and is incredibly easy to add to your startup script...

Apply settings w/ overdriventool:
"<Installation path>\OverdriveNTool.exe" -consoleonly -r<gpu_index> -p<gpu_index><gpu_profile_name>

Restart gpus w/ devcon (vegas):
"<Installation path>\devcon.exe" disable "PCI\VEN_1002&DEV_687F"
timeout /t 3
"<Installation path>\devcon.exe" enable "PCI\VEN_1002&DEV_687F"

For example:

Btw, restarting w/ devcon shouldn't be necessary w/ any recent driver version.

We'll detect the state where the miner thread(s) for a gpu is stuck in an OpenCL API call, and there has been zero new hashes reported for the gpu for ~20 secs. At that point we (1) attempt to shut down the miner, like if you'd press ctrl-c and (2) execute a user .bat/shell script in a forked process, i.e. in parallel with the shutdown.

Now, what you choose to do in that .bat/shell script is entirely up to you. If you're sure you'll get an ok miner shutdown, then wait 20 secs + reset cards + apply clocks + start miner, in your .bat file. For others, it's more likely they'll do a "shutdown /r now". I mean, on my testing workstation I'm even having a hard time to get a clean reboot when I mistreat my Vega too badly, I need a manual power cycle. So, in the general case the guarantees we can provide are very weak. We'll let you run a .bat file, that's pretty much it.

For examples, sure, we can whip up some restart.bat examples, or other people can post theirs here. I have the devcon Vega restart snippets somewhere, been a while since I last used them...

Yes, this miner desperately needs an error handler. An option to shutdown/reboot would be nice to stop GPU from consuming power with zero hashes.

are you sure? that you were not a bit confused?
 give me SS your HR 5min and your option- 1850 in tube ?
H and S work fine in 1.7.0

I'am reverted back all rigs to 18.3.4, because, the newest drivers has a bug - some cards are detected as RX580, but they actually are RX570. And in my IMHO, 18.3.4 is more stable.

I:58 T:2 W:16 F:4