Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11214

  • Joined

  • Last visited

  • Days Won

    475

 Content Type 

Posts posted by Fiery

    LCD and Program Temperature Readings are frozen (and impossible) after sleep.

    in Bug reports

    Posted

    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.

    Stress test help

    in Benchmarking, system performance

    Posted

    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

    Using PC during AIDA 64 stability test?

    in Benchmarking, system performance

    Posted

    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

    Multiple Display Sensor Panel

    in Bug reports

    Posted

    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

    Network traffic

    in Brainstorming

    Posted

    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

    Submit Report To FinalWire

    in Bug reports

    Posted

    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

    eVGA Classified 3 voltages?

    in Hardware monitoring

    Posted

    I believe not all voltages you see in E-LEET can really be monitored. That screen is used to set values only, for values really monitored check the "Monitoring" tab.

    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 ;)

    HP Microserver AMD 785E chipset

    in Hardware monitoring

    Posted

    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

    Read test suite error

    in Bug reports

    Posted

    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.

    DDR3 - Sandy Bridge Multiplier (Asus P8Z68-V)

    in Hardware monitoring

    Posted

    32:3 means 1066 MHz memory clock, since the base clock of Sandy Bridge processors is nominal at 100 MHz. So 100 x 32 / 3 = 1066.66 MHz, which is the clock speed of DDR3-2133 memory modules.

    We are not in a position to comment on values you obtain (the "8:1") using other software, since we're not behind those software in any ways. You can however contact the author of CPU-Z for clarification though.

    As for the voltages, make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at:

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

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

    Let me know if you find any further issues in AIDA64 about your computer.

    Regards,

    Fiery

    ... without a windows server domain

    in Network audit, change tracking, SQL databases

    Posted

    In case your workstation computers do not log into a server, then the easiest way probably is to create a Scheduled Task on all computers, to launch AIDA64 Business Edition from a central location (e.g. a shared folder on your file server).

    Storing AIDA64 files in a central location is recommended because then it's easier to re-configure AIDA64, or to update to a newer version.

    Regards,

    Fiery

    LCD and Program Temperature Readings are frozen (and impossible) after sleep.

    in Bug reports

    Posted

    Please let us know more about your system configuration:

    1) Motherboard model, CPU type?

    2) Video card (or video cards) model?

    3) Do you have any external disk drives connected? (e.g. USB, FireWire, eSATA)

    4) Which version of Logitech gaming keyboard drivers do you have installed?

    Also, make sure to be running the very latest beta release of AIDA64 available at:

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

    Thanks,

    Fiery

×
×
  • Create New...