Jump to content

Fiery

Administrators
  • Posts

    12599
  • Joined

  • Last visited

  • Days Won

    565

Posts posted by Fiery

  1. As I've explained above, such issues may happen when under heavy load the CPU intermittently provides invalid core temperature readings to AIDA64.  Such readings should be ignored.  As for GPU, I'm not sure what may cause that, but since the GPU TDP% reading is measured via nVIDIA driver calls, it depends on the driver whether it provides reliable and stable readings.

  2. What we need is those feature bits to appear in the ATA/ATAPI Command Set specifications.  But as it seems, it's not been propagated for ACS-3 (latest revision), so I guess we would need to wait for ACS-4 to be drafted.

  3. 1) Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump.  Copy-paste the full results into this topic.

     

    2) Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full).  Copy-paste the full results into this topic.

     

    3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump.  Copy-paste the full results into this topic.

     

     

    Thanks,

    Fiery

  4. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump.  Copy-paste the full results into this topic.

     

    Using that data we may be able to calibrate the AIDA64 sensor module to better support your motherboard.  But please note that the core temperatures are measured via the on-die temperature diode of your processor.  And most FM1, FM2 and AM3+ socket based AMD processors feature a hardware issue in their temperature diodes that yields to very low temperature readouts at idle -- usually way below ambient (room) temperature.  The measured core temperatures only make sense when the CPU is under load.

     


    Thanks,

    Fiery
     

  5. Thank you, but we haven't found the actual method to detect the Device Sleep capability and status in any of the documents we've got.  It is possible via the IDENTIFY DEVICE command, but even the latest ACS doc doesn't mention Device Sleep, DEVSLP or DevSleep.  So we don't know which register to use.

  6. This may or may not be related here, but I get an access violation on each startup using beta 2505.  I usually have to retart 4 or 5 times before it loads properly.  Attached is a picture of the fault.

     

    ASUS Z87-PRO EFI/BIOS 1007

    i7-4770K

     

    Try to reinstall AIDA64 using the latest ZIP package:

     

    http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip

    It looks like one or more of the main DLL files are either missing or got corrupted.

  7. We've made several modules of AIDA64 more solid by improving exception handling.  We've also disabled CPU throttling measurement by default.  Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

     

    http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    Let me know if it helps.

     

     

    Thanks,

    Fiery
     

  8. We've made several modules of AIDA64 more solid by improving exception handling.  We've also disabled CPU throttling measurement by default.  Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

     

    http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    Let me know if it helps.

     

     

    Thanks,

    Fiery
     

  9. We've made several modules of AIDA64 more solid by improving exception handling.  We've also disabled CPU throttling measurement by default.  Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

     

    http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    Let me know if it helps.

     

     

    Thanks,

    Fiery

     

  10. Update frequency per item: We don't have plans on making such customizations possible.  The SensorPanel is already too complicated for many AIDA64 users, so we wouldn't add such a layer that would make it even more complicated without actual benefits to most users.

     

    Adding shapes: We may add those sometime in the future, but it's not high priority, since most SensorPanels feature a background image anyway.  And on the background image it's quite easy to draw any shapes using Paint, Photoshop or any other image editing software.

     


    Regards,

    Fiery

    • Like 1
  11. This thread perfectly describes what we would like to do.  I don't understand why you'd split the features that businesses would want into two license types, and then make it impossible to purchase both.  I am holding out hope that this oversight has been addressed in recent years, as this thread is a few years old.  Can I purchase an engineer license with temperature logging and command line options?

     

    Not yet. But we have plans on introducing a "Super Business Edition" that will be based on the current AIDA64 Business Edition, but would also implement the missing features from AIDA64 Extreme Engineer, like benchmarks and overclock information.

  12. You can try uninstalling AI Suite II to see if it causes any lags, but most of the lags during benchmarking and stressing your system are simply caused by the benchmark module of AIDA64 that really and actually uses up 100% of system resources.  So there's very little system resource left for the Windows management subsystem and the rest of the operating system functions.

     

  13. AIDA64 Disk Benchmark handles physical drives, as they are managed by Windows.  In case you have a RAID array defined, the RAID array will appear as a single physical drive in Windows, hence AIDA64 will treat it as a single drive, and will benchmark it as a single drive.  In such case e.g. for a RAID0 array of 2 drives, both drives will be benchmarked in the same time, and their theoretical performance will be added up (aggregated).

     

    If you have a RAID array defined, there's no way to benchmark the individual drives (member drives) separately.  AIDA64 also doesn't have file system benchmarks, so for example you cannot benchmark C: drive or D: drive separately, if they're 2 partitions of a physical drive.

     


    Regards,

    Fiery

     

×
×
  • Create New...