Hey all,
I identified a serious conflict between HWMonitor 1.16 and MSI Afterburner, which I communicated to the author of CPUid's HWMonitor. It seems to be a conflict that occurs when both programs are trying to access voltage information (i.e. when you're monitoring voltage). It caused my HD5850 to suffer an enormous voltage spike to 1.6v and an immediate crash on several occasions before rolling back to HWMonitor 1.15.
I have been on the e-mail exchange between HWMonitor's author and the author of MSI Afterburner (Alexey Nicolaychuk), and they are trying to work out a solution. It turns out that the problem affects Nvidia too, as shown in this thread: http://www.overclock.net/nvidia/789107-warning-gtx-470-fan-issues-w.html. In Nvidia's case, it shuts off the fan (!).
An easy solution is to roll back to HWMonitor 1.15, which did not include GPU voltage monitoring. Unfortunately, it's not on the CPUid website anymore.
Just thought everyone should know, as this could potentially damage your shiny new cards.
I identified a serious conflict between HWMonitor 1.16 and MSI Afterburner, which I communicated to the author of CPUid's HWMonitor. It seems to be a conflict that occurs when both programs are trying to access voltage information (i.e. when you're monitoring voltage). It caused my HD5850 to suffer an enormous voltage spike to 1.6v and an immediate crash on several occasions before rolling back to HWMonitor 1.15.
I have been on the e-mail exchange between HWMonitor's author and the author of MSI Afterburner (Alexey Nicolaychuk), and they are trying to work out a solution. It turns out that the problem affects Nvidia too, as shown in this thread: http://www.overclock.net/nvidia/789107-warning-gtx-470-fan-issues-w.html. In Nvidia's case, it shuts off the fan (!).
An easy solution is to roll back to HWMonitor 1.15, which did not include GPU voltage monitoring. Unfortunately, it's not on the CPUid website anymore.
Just thought everyone should know, as this could potentially damage your shiny new cards.