Squall Leonhart Posted May 18, 2011 Share Posted May 18, 2011 Just thought i'd post a heads up so you can do any tests and see if there is an issue. Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 18, 2011 Share Posted May 18, 2011 Can you please tell us more about the issue? Or maybe a link to a forum topic where users discuss it? Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted May 18, 2011 Author Share Posted May 18, 2011 sure can http://forums.guru3d.com/showpost.php?p=3986360&postcount=153 http://forums.guru3d.com/showpost.php?p=3986532&postcount=170 I saw posts elsewhere as well, i think OCUK? Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 18, 2011 Share Posted May 18, 2011 Thank you. I think it may be due to a broken I2C API of ForceWare's NVAPI module. We'll check it out. Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted May 18, 2011 Author Share Posted May 18, 2011 one of the users said he tried an older Everest build and the missing temps appeared. GPU-Z shows the temps fine however, also ironically i installed an old version of EVEREST (before it was purchased by AIDA) dated september 2010 version 5.50 and the sensors are there lol Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 18, 2011 Share Posted May 18, 2011 one of the users said he tried an older Everest build and the missing temps appeared. 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. 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. Quote Link to comment Share on other sites More sharing options...
Arctucas Posted May 18, 2011 Share Posted May 18, 2011 I am using AIDA64 1.70.1412 BETA and Forceware 275.27 BETA with two GTX460 cards in SLI and I can see both card's temperatures. Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 18, 2011 Share Posted May 18, 2011 I am using AIDA64 1.70.1412 BETA and Forceware 275.27 BETA with two GTX460 cards in SLI and I can see both card's temperatures. It's normal, since the NVAPI I2C layer issue only affects such GeForce cards that have an onboard sensor chip (e.g. ADT7473) and/or an onboard voltage regulator chip (e.g. Volterra). Anything below the top level (under GTX470/480/570/580/590) should still be fine. Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted May 19, 2011 Author Share Posted May 19, 2011 ok, that makes sense Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 30, 2011 Share Posted May 30, 2011 We've the mentioned issue in the following new beta version of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1426qv1kl8cw0czip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let us know how it works for you. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.