Upgraded to the latest beta driver with mining fix while coming from 17.5.2. Like others, I'm having some issues with voltages returning to default. Running Windows 10, mix 470/480/580.
I've read various posts relating to voltages not staying set, and I figured I'd add my own experiences in hopes of finding a workaround/solution.
What I see happening is that AMD drivers are not correctly storing voltage settings. The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
Once the voltages are reset, all tools (wattman, overdriventool) still display the voltages as the user defined settings. To get the voltages back down, I must either increase, or decrease mV slightly, then return back to preferred setting.
A possible solution could be to have claymore dual miner check every minute or so, and if needed automatically re-apply cvddc and mvddc with a +/- 1 mV. My past experience using cvddc is that it sets only once when the miner is first launched and never tries to re-apply if settings have changed.
Yes same bug here. As i wrote ~4 posts earlier. The clocks suddenly become unstable (and apparently also the voltages, as the WATT consumption from the wall spikes when this bug occurs). I get this bug only with newer driver than 17.5.2.
The drivers seem to re-apply the default voltages when switching between power states, when primary display is turned off, resolution is changed, and potentially going in and out of exclusive fullscreen.
This all is absolutely true. I first encountered the bug when I went to fullscreen video playback in ZoomPlayer. Oddly this only happens with "EVR" as renderer, when i switch to MADVR as renderer, the bug does not appear.
Thanks to your hint, I can at least leave the computer run when I am gone, after I disabled the screen "power saving mode" in Windows to NEVER. So the clocks/vcore stay stable and I dont have to reapply settings in Wattman to fix the bug.
However, this is not the place to discuss the bug, IMO. I guess it is another DXVA hardware acceleration bug. We had many of these bugs in the past on the POLARIS architecture. Its AMDs fault and hopefully they will fix it in a driver update.
What i want to know is how to use just the driver files in the Claymore folder. If that is even possible or if Claymore could implement such a feature. This would be great. thx
