Jump to content

Fiery

Administrators
  • Posts

    11611
  • Joined

  • Last visited

  • Days Won

    494

Everything posted by Fiery

  1. We've fixed that issue in the AIDA64 v1.85 stable release that we've just rolled out: http://www.aida64.com/downloads After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery
  2. The new AIDA64 release revamps the Logitech LCD module to support multiple LCD devices with enhanced configuration options, and adds preliminary AMD “Trinity” CPU optimizations as well as OpenGL 4.2 graphics device support. New features & improvements - Advanced multi-device Logitech LCD support - Preliminary support for AMD Trinity processors - Improved support for Socket FM1 motherboards - Temperature, fan speed, voltage correction - GPU details for nVIDIA GeForce 510, GeForce GTX 580M - OpenGL 4.2 support [ Press Release ] [ What's new in AIDA64 v1.85 ] [ Download ]
  3. The AIDA64 LCD feature only works with a LCD-equipped Logitech gaming device: G13, G15, G19.
  4. Do you have a Logitech G13, G15 or G19 gaming device with a built-in LCD screen? If so, then do you have the necessary Logitech drivers installed? Regards, Fiery
  5. Here you go: http://www.aida64.com/product/aida64-extreme-edition/features SQL database support and reporting to CSV and XML files are only supported by AIDA64 Business Edition. Regards, Fiery
  6. FYI, in the latest AIDA64 beta releases we've completely revamped the Logitech LCD support, so you have to recalibrate all items, especially their placement. We've basically applied the same improvements that we introduced as the SensorPanel feature on the Logitech LCD feature. It enables you to display bars and to use a more precise items placement -- but on the other hand it requires a bit more efforts to recalibrate your old settings.
  7. 1) If you would like to stress your system to reveal a potential hardware flaw or instability, then enable all tests in the System Stability Test window, and press Start. Let it run for a few hours. If it doesn't display any error messages, Windows also runs fine, and your computer doesn't reboot, doesn't lockup and doesn't shut down, then your computer is considered very stable. 2) If you rather want to stress your system from a thermal point of view, to reveal potential cooling issues, then only enable the FPU test in the System Stability Test window, and press Start. Let it run for a few hours. Watch the temperature graphs, where the motherboard temperature should stay below 55-60 Celsius, and your CPU temperature should stay below 80 Celsius. In case you have an Intel processor, then should also watch the bottom graph where the Throttling activity should stay at 0% all the time. If the Throttling graph shows any non-zero activity, it means your processor is overheating. In case your computer restarts, shuts down, locks up or throws a BSoD while running the thermal stress test, then your computer is overheating. Regards, Fiery
  8. 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. Make sure to use the latest beta of Build 1498. Thanks, Fiery
  9. Thank you for the feedback
  10. Have you tried to lower the LCD update frequency to 1 second? (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency)
  11. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1498pxwc5m0ygbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery
  12. We generally recommend not to use any other software or process while running the AIDA64 System Stability Test, since it may mean AIDA64 cannot stress all cores equally hard at all times. So we can only guarantee the maximum reliablilty of our test if you don't use your computer for other purposes. If you can't afford to not use your computer for several hours during the day, then you can also let it run by night while you're away from your computer. 2GB RAM is more than enough for our test to run properly. Regards, Fiery
  13. Do you mean you have a secondary or tertiary monitor, e.g. a LCD TV connected via DVI or HDMI that you sometimes disconnect from your computer? If that's the case, then please let us know more about your system configuration. What video card do you have? Do you have your Windows Desktop extended to join all displays to a single wide desktop? Thanks, Fiery
  14. Do you mean a new column in the Remote Monitor window of AIDA64 Business Edition to show not the current network traffic, but the average traffic since the Remote Monitor window was opened? Thanks, Fiery
  15. Do you mean CPU-Z is right and AIDA64 shows the wrong BCLK (FSB) and DRAM clock?
  16. A small bug has slipped into the OpenGL 4.1 and 4.2 compliancy test of AIDA64. We'll fix it in the next beta release. Have a great weekend
  17. Can you please try it with the latest AIDA64 beta release? http://www.aida64.com/downloads/aida64extremebuild1498pxwc5m0ygbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. BTW, what video card do you have? Do you have Windows 7 64-bit installed? Thanks, Fiery
  18. Usually a report submit is only necessary once or twice on a computer, so that's why AIDA64 doesn't remember your name and email address. You can however set those bits in AIDA64 / main menu / File / Preferences / Report. As for the connection issue, I suppose it's due to a firewall. If you have a software firewall on your computer, then make sure to let AIDA64 through it. If you have a company firewall, then you may not be able to use AIDA64 report submit function. BTW, the report submit facility uses HTTP protocol to submit reports directly to our web server. Regards, Fiery
  19. Yes, you need to have AIDA64 running on all your computers that you want to monitor or control remotely. Regards, Fiery
  20. That's normal. On the Motherboard / CPU page you can see that the total L2 cache size for your CPU package is 2x 3MB. On the AIDA64 CPUID Panel you can see the L2 cache size that belongs to the selected CPU core. Regards, Fiery
  21. Please contact our Sales Department at: sales AT aida64.com (replace AT with @) Make sure to explain the issue with AIDA64 more detailed. Thanks, Fiery
  22. VBAT should the battery, but apparently your motherboard does not monitor the battery. You can verify that in the BIOS Setup. We'll remove the VBAT reading on your motherboard in the next AIDA64 beta release. Thank you for the feedback
  23. Exactly. The values listed in E-LEET are read using manufacturer-specific calls, usually some sort of SMI calls, directly from the BIOS. The actual calling method to retrieve those values is not only manufacturer dependant, but also custom to actual motherboard models, so such interface cannot be implemented in 3rd party diagnostic software like AIDA64. There're certain motherboards (e.g. Asus, Intel, some Gigabyte) that support standard interfaces like Asus ATK and Intel XTU, and so the BIOS settings can be read and displayed on the Motherboard / BIOS page in AIDA64. Unfortunately most motherboard manufacturers do not support standard interfaces
  24. AIDA64 reads sensor information from sensor chips directly, except for the hard drives (and SSDs) It's not safe to communicate with disk drives directly, so AIDA64 uses standard Windows API calls to read SMART information and disk temperature. However, there are some SATA controllers that has such drivers that don't expose the standard Windows API interface necessary to read SMART information and disk temperature. In such cases AIDA64 will try to access the drives with alternative, manufacturer-specific SATA driver methods, but it won't work in every cases. In other words, reading SMART information and disk temperature is very much driver dependant, and that explains the differences you can see across various Windows versions and installations. BTW, SMBus has nothing to do with reading SMART information or disk temperature Regards, Fiery
  25. Please note that certain SSD controllers may skip actually reading SSD sectors _if_ those sectors are still in their factory default state. In other words, if you don't fill (write) the drive completely with *some* data first (to initialize every flash chip blocks), the drive will know that those sectors are empty (not-yet-initalized, never written before), and it will simply give back zero values for all data in virtually no time at all. And that will effectively mean the drive will be able to "read" data at the throughput speed of the controller itself, which in the case of SATA 6.0Gbps (SATA3) controllers would be around 500 to 540 MegaBytes/sec. With SATA2 SSD drives that issue usually wasn't revealed, since the sequential read performance for many controllers almost matched the throughput of the SATA2 channel anyway Solution: before testing any SSD drives, make sure to create a maximum-size partition, and copy large files on it until it's completely full. Once the drive is filled, you can remove the partition, and start benchmarking the drive.
×
×
  • Create New...