[Verbum]

Zanimljiv info:

I want to tell me experience and a bug (I think) I found on new v2.1.0b1.

I have a HAWK too, and to my surprise AB 2.0.0 did not let me OC gpu core nor read gpu voltage neither, hitting "apply" did not do the trick (checked vccd with gpu-z and nvidiainspector, it always remain v0.962, and overclocking was imposible without raising gpu voltage).


That's supposed to be that way, you WILL NOT be able to monitor voltage changes with any software tool reading voltages via NVIDIA driver. Hawk uses additional voltage controller chip which is adding programmable voltage offset to output voltage of reference NVIDIA voltage control circuit. None of tools you've mentioned support that additional chip and just show you expected target voltage (which doesn't match real value in case of adding an offset via that additional chip). Furthermore, that additional chip itself also doesn't support voltage readings, it doesn't even know which voltage is on its' input, it is rather simple IC which just trying to modify the input value by specified offset. That is why there is no (and there will not be in future, I've seen rumors that I'm working on getting voltage monitoring working on Hawks and I say that's not true) voltage monitoring for Hawks when alternate voltage controller circuit is in use. The best thing that can be done to see some form of expected voltage is approximating the output by displaying summ of NVIDIA reference voltage with additional offset, but that's by far not the best solution because both components (reference circuit and additional offset circuit) add its own inaccuracy.

Izvor: http://tinyurl.com/393hb44

Post #78