Quote from: teuflor on November 13, 2017, 12:14:58 PM

Quote from: R0mi on November 12, 2017, 05:43:03 PM

Quote from: Marvell2 on November 12, 2017, 02:18:26 AM

Quote from: percy_tc on November 11, 2017, 10:36:08 PM

Quote from: Marvell2 on November 11, 2017, 04:18:28 PM

Quote from: R0mi on November 11, 2017, 04:00:12 PM

Quote from: Marvell2 on November 10, 2017, 09:43:45 AM

anyone see a grey screen and crash when running more than 2 gpu on cast?

on a single gpu it works fine, but when i add more grey artifcats then crash,tried two separate motherboards
it only does thiswith the aug23 blockchain drivers , the ronbin hood ones dont crash but 1500 hs vs 1950

I hit a similar problem, but it was the same with XMR-Stak or Cast. I have a MSI X370 and could not get past three GPUs without a blue screen/crash. Changed risers, cables, Vega cards, PCIe slots, settings, on and on.

Finally solved it: Used DDU to strip everything out. Went directly to Microsoft's site and downloaded the fall creators update (takes a while). That loaded the non-blockchain drivers and for the first time I could mine with 5 Vegas on that motherboard (but slow speeds). Uninstalled the newest drivers, reinstalled blockchain drivers. It's all good now.

hmm i tried this several times, I have a window image that alrrady contsins the fall creators update included and did this with a fresh install still the same deal, Ill try it again i guess , thanks

Have you tried newest amd in compute mode? With rx 4xx/5xx there is no need of blockchain driver anymore.

I tried those drivers, had problems too

**update**
following Romis instructions i did a clean install, this time though i did not give the default driver time to install, I ran gpedit.msc and disabled the windows updates and driver updates in Immediatley rebooted the box.

I think a lot of people experience crashes with multiple Vegas because they install the driver and immediately reboot. The most important thing I found was that when you install the block chain driver, CLOSE the AMD installer at the end of the installation but don't reboot. Instead, use Regedit to go into the same directory as the SoftPowerPlay mod, and change "EnableAutoCrossfire" to "0" decimal value for every card -- e.g., folder 000, folder 001, folder 002, folder 003, folder 004. Then reboot. The pathway is listed at the top of every SoftPowerPlay mod that you download. Turn off auto cross fire in the Registry values, and also in the AMD Relive settings application as well.

Second interesting thing I found was that it's best not to get too aggressive with your basic SoftPowerPlay settings. Keep P7 in the 1401-1408/900-905 range; P3 in the 1050-1070/850-900 range (Monero settings). Too far outside those values and SoftPowerPlay causes a blue screen/crash *on startup*. Once you boot, however, you can use OverDriveNTool 0.2.1 to tweak the settings card by card and get stable performance. But you can't always write those optimal values directly into the SoftPowerPlay table and get a stable reboot. Just doesn't work, I don't know why, but that has been my experience. I see people setting 5 or 6 cards to 1100 memory across the board -- no wonder your rig is crashing. Not every air cooled Vega 56 can handle P3 at 1100. Your base settings should be dialed back. Then experiment card by card once your rig is booted.

You can save some time by taking one SoftPowerPlay Registry mod and copying that as several files -- RegMod001, RegMod002, RegMod003, RegMod004, RegMod005 -- edit each of those files for one particular card, e.g., edit the "000," "001," "002," so you don't have to manually do this each and every time.

thanks for sharing your experience! I have some problems with my 3rd rig. 6 x Vega on a Z170 Pro Gaming Board. in Windows is all ok, after installing my Blockchain driver -> Reboot. Everything ok. Use the reg keys for softplaytable -> cant boot into windows.

i will try to disable crossfire in front of using the softplay table reg

but i have only "Enable"crossFireAutoLink" in the reg keys, did you mean thad one?

apply the reg files one by one and reboot after each one. This way you will identify the card that is not accepting the settings. Make sure you do restore points before each apply, so you can easily revert it.
After you identify a problematic card - disconnect it, and continue with the rest untill you know which work with the mod and which not. After that - try a different mod, usually with lower memory settings.