Thread: Issues with latest AIDA64 and multi-GPU temperatures with ForceWare 275.27

That's normal, since Everest uses direct I2C communications. However, nVIDIA strongly advises against using direct I/O on GeForce 400 and GeForce 500 Series, so with AIDA64 we've switched to using the driver-level I2C I/O by default, via ForceWare's NVAPI layer. You can still switch back to the direct I/O with AIDA64 if you want --> AIDA64 / main menu / File / Preferences / Stability / disable the option called "nVIDIA GPU SMBus access through nVIDIA ForceWare", and restart AIDA64.

SMBus access through ACPI (Asus motherboards). Asus owners only, hehe :P

We've already started performing test runs using ForceWare 275.xx drivers. The new drivers seem to have a broken NVAPI I2C interface. We'll need a bit more time to find out more about the root of the problem, and to possibly implement a workaround.

Moved to the PC Hardware forum. This is more appropriate.

Originally Posted by stuntmanSLim

That's normal, since Everest uses direct I2C communications. However, nVIDIA strongly advises against using direct I/O on GeForce 400 and GeForce 500 Series, so with AIDA64 we've switched to using the driver-level I2C I/O by default, via ForceWare's NVAPI layer. You can still switch back to the direct I/O with AIDA64 if you want --> AIDA64 / main menu / File / Preferences / Stability / disable the option called "nVIDIA GPU SMBus access through nVIDIA ForceWare", and restart AIDA64.

SMBus access through ACPI (Asus motherboards). Asus owners only, hehe :P

We've already started performing test runs using ForceWare 275.xx drivers. The new drivers seem to have a broken NVAPI I2C interface. We'll need a bit more time to find out more about the root of the problem, and to possibly implement a workaround.

Where is this from? What is the context?

Sounds like part of an article or thread. If so, where's the attribution?

Aida64 giving a false cpu temperature reading. Start up Asus Probe 2 > exit Asus probe 2 & it corrects the issue.