When I first installed the blockchain drivers, 4 cards were present. So it worked on all.

The next reboot, I have 3 cards detected by Windows. I change nothing and reboot again, 4 cards appear and I can mine.

It is random between 2 and 4 cards detected by windows each boot. I am not complaining because I can quickly restart until it has found four cards, but in terms of automated recovery from a shutdown, it is hard to get right

You ran out of memory. increase the size of virtual memory in Windows. you can see how in the guide below. For instance, say you have 6 Vega GPUs, they have 8 GB of mem each, so you multiply 8x6 equals 48. So you set virtual memory in Windows to 48000MB.

http://vega.miningguides.com/

I think it would be worth it to uninstall the drivers with DDU Uninstaller and see if Windows detect them all again.

Btw, based on the bat by FgTeamBr I managed to not only restart the miner but also devcon and overdrivenTool settings. Some random hash rate drops or strange behaviour from the gpu1 were driving me nuts

Miner -  Cast_XMR is only suitable for Vega or for other Reds too?

with what parameters?

Hello! I use 0.8 version cast-xmr miner with 5* his rx580 4gb (hynix+elpida) on windows 10. It shows 850 h/s per each, thats very good. But there is an issue with my system, sometimes (10 minutes from run or more) it stops show hashrates until i hit S button. When i hit S button it rapidly scroll and continue work, but all shares from that time are rejected by pool as obsolete.

I made a crutch: wrote autohotkey script which sends "S" key to miner's window every 60 seconds, but it's very inconvenient, i cannot make it to autostartup etc....

Could you make an update with new parameter to show statistics ("s" key pressed) every period of time?

It's not my case: i leave cursor in normal form, miner works and shows hashrate with scroll. When I return after some time, cursor is normal, scroolling freezes. I hit S - miner backs to mining, but all shares are rejected. I think "S" procedure re-initilialize something which cause miner to freeze in my case.

Does --forcecompute option works with Adrenaline drivers and Vegas?

This typically occurs when you have your Windows Command Prompt windows enabled for 'Quick Edit', and you click the mouse inside the window to focus; but this tells the Command Prompt window that you want to quick copy content.

To fix: While the miner is running, click the Command Prompt icon, go to Properties, and unselect Quick Edit. Then go back to that menu, select Defaults, and uncheck it there so future windows apply this setting.

Hi I had a same issue! I made a script for autohotkey to send every minute S key to miner's window and fixed it, but it's very inconvenient!! I am no alone I think developer should make an update.

Nice band-aid. What a waste of time though. You are better to figure out why the hash rate drops.

I have noticed that the hash rate drops in the following instances

1. Windows is not set to "Never Turn Monitor off" on the power settings
2. Making sure that windows never shuts off the HDD or SDD "Always on" in power settings
3. Locking the computer or sending it to the lock screen (drops hash rate instantly) Keep the computer logged in on the desktop!
4. If you can't leave a monitor hooked up to it (tuned off) then find a dummy plug.
5. Using remote desktop and logging off ( Sends computer to lock screen) Even team viewer can cause problems.
6. In some cases running miners on different pools (running multiple instances of CAST) can cause the has rate to drop, meaning its best to use a single instance and point them all at the same pool. Results differ per miner.
7. Using the onboard GPU or iGPU is recommended. Plugging displays into the VEGA mining cards directly is not really recommend but works fine for some. Find another GPU to plugin if you don't have onboard to use as a last resort.
8. Try not to mix cards, as this can cause problems as well unless you really know what you are doing.
9. For 6 Vegas you should have at a minimum of at least 49452 Virtual Memory specified in Windows. A 120GB SSD is fine and so is 4GB of ram to accomplish this, just make sure you have enough space on the drive to do this. Increase by 8GB for each additional card. Windows may display this in MB but it's fine. The math is as follows 1024*(number of vegas)*(8 megabytes/gigabytes - whatever windows)+ (300 for overhead) = 49452
You can probably get away with less but it works so who cares.
10. Boot into safe mode to remove AMD drivers using DDU or even the AMD driver removal tool.
11. Install [Suspicious link removed]pute drivers for VEGA! in normal Windows(not safe mode) Don't install anything you don't need.. like ReLive or Problem report tool... (many different opinions about Wattman. I use it and have no issues)
12. Keep your mining rig configuration simple and focused as possible and you will have few issues.
13. Device manager disable and re-enable VEGA's after every reboot before you start to mine.

Shutting down the miner all the time is a waste of time and money. Spend the time to figure out what is wrong by testing out your rig and finding out what works before using a band aid solution that is not great for mining.