if it mostly happens in turbo mode it's most likely a thermal issue rather than drivers. I use custom mode and undervolt and have had no issues. try tweaking in custom mode rather than using turbo.
yes, and no. Vega is a different beast all together on how it controls it's core speeds etc. Voltage and thermal controls the clock speed more than the actual core speeds you have set in the P6 and P7 states.
As you would expect, if the Vega gets to hot, the card will start to throttle. However, if the card is running nice and cool, the card will increase the clock until it hits the voltage limit of what the p6/p7 voltage is set at +power limit. The core speeds set in those states are just low limits, meaning it will clock much higher than what you have set, if the temps are good and it has not hit the voltage limit.
I learned this when I added the second radiator to my Vega cooling. It brought down the temperatures, which introduced instability (specially in rainbow six siege). I was baffled, because It was running cooler, so why would it cause instability since I changed no settings.
Turns out, that because it was running cooler, it would increase the clock speeds higher than before because it now had a better thermal ceiling and still had voltage available. It was spiking to 1785 Mhz in Siege. I already knew my Air cooled card that I put under water, was only stable to about 1720 Mhz.
So I had to start undervolting to keep it from spiking. (this was running the LC bios). If I had left the bios on the stock air cooled, it would have ran at 1610 all day long. With LC bios and undervolting and reduction in the p7 core speeds (can't do the 1750 it defaults at) my card happily runs at 1660 to 1700, and no crashes in any game.
Basically, it was the spikes that was causing the crashing, all because I gave it a better thermal ceiling and allowed it to have the voltage to push the core speeds beyond what MY silicon is able to sustain.
The irony is I updated to the latest drivers the same time I added the extra radiator. At first, I to thought it was driver related, until I rolled back, and had the same problem.
