Jump to content

Squall Leonhart

Members
  • Posts

    382
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Squall Leonhart

  1. Ah, something that wouldn't cause a problem for everyone then?

    you're on the ball this week Fiery, i've never had a faster response xD

    i just hope intel have fixed their uninstall script, the previous version of 11.5 installed the iastorf (Filter) as a lowerfilter and failed to remove it on uninstall leading to fun times getting windows to work if you delete the file before removing the lowerfilter value

  2. Thank you. It seems something weird is going on in the Windows 8 kernel about CPU caches. The issue can be experienced on both AMD and Intel processors, so we've contacted both companies to find out what's behind this, and whether we could fix it or get around it. I'll let you know in this topic once we have an update to this matter.

    It may be the Win8CP Ndis bug, alot of Consumer preview testers are seeing the NDIS driver consume alot of cpu and cause extremely high dpc latency which could be delaying the aida64 cache test.

  3. Thank you for the tests. We'll fix that in the next AIDA64 beta update.

    It should not require fixing

    5. Missing disk, SMART and drive temperature information on Intel RST 11.5 drivers.

    Description: Using Intel Rapid Storage Technology (RST) driver v11.5 or Enterprise RST driver will probably cause loss of disk information including SMART and temperature. This is a bug in the Intel RST driver v11.5 and Intel fixed this problem in version 11.5.0.1153 of the RST driver and Enterprise RST driver v3.2.

    Workaround: Update the RST driver to v11.5.0.1153 (or eRST to v3.2) at least.

    3.2 is not out just yet, but so far 11.5.0.1153beta tests have been positive

  4. disable the smbus via nvidia i2c/driver setting and let aida64 access it via its own method.

    see if the issue persists,

    you actually get less data from the smbus access on certain cards (in the case of my 275 i lose fan rpm's and gpu VCC)

    if you have Precision X running alongside AIDA64, its advised to close one or the other. If precision X is accessing voltage adjustment via a HWMon module, then there are known issues between HWMon access mutexs and the mutex aida64 uses. (i've seen black screens and the gpu fan stopping)

×
×
  • Create New...