Just to prevent possible misinterpretations I'll clarify once again: beta 18 WON'T fix jumping monitored GPU usage on 290 series, it is bad AMD driver's coding issue and it can be fixed by AMD driver team only. In beta 18 GPU usage artifacts (spikes/gaps) will be smoothed a bit due to adding special math filtering algorithm aimed special to correct erroneous AMD driver's readings on Hawaii. But the artifacts still will be visible and usage will go up and down, just not that rapidly as before due to post-processing data. Some users with no expect knowledge in this area tend to insist that it is still broken in AB simply because they don't see that pattern in GPU-Z. Which is not true at all and I'll repeat once again that GPU-Z is simply displaying different performance counter under "GPU Load" name for Hawaii, what you see there is D3DKMT performace counter and not a hardware GPU load sensor reading coming from AMD ADL API. It doesn't (and not supposed to) match with values which you see in AB, CCC or any other vendor's tool working with AMD driver. Those who understand that and still wish to see D3D GPU usage perf counter instead of AMD GPU usage perf counter will be able to edit CFG and force AB to display DX perf counter instead of AMD's one.