Quote from: Temporel on November 29, 2017, 12:03:54 PM

Quote from: moofone on November 28, 2017, 04:56:57 PM

Completely disagree. This is dangerous way to overclock and could lead to catastrophic failure of your rig if a card dies on its own.. and they do.

Its discussed on the nvidia dev form with some python code that could be adopted to nvOC if anyone is interested:

https://devtalk.nvidia.com/default/topic/769851/multi-nvidia-gpus-and-xorg-conf-how-to-account-for-pci-bus-busid-change-/

Quote from: Bibi187 on November 28, 2017, 04:51:02 PM

Quote from: moofone on November 28, 2017, 04:42:01 PM

Hi Guys,

I discovered a serious and potentially dangerous flaw in the way nvOC handles overclocking and would like to make a suggestion for an improvement.

We really need overclocking tied to the specific pcie slot (bus id) not an index that changes every time your hardware changes.

For example, if you have a gtx1080ti in slot 2, and a gtx1060 in slot 3, and your 1080ti goes offline for some reason or you remove it, the 1080ti overclock is now applied to what it thinks is the next card in the dumb index, and applies it to your gtx1060 potentially going POOF.

Nothing to fix at all oO ...

You modified your RIG, you have to modify setting ...

top posting is disrespectful, wake up kiddo.

👍👍👍👍