Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    It's not easy to diagnose such issues remotely Your temperatures seem to be quite high for your processor, so I would definitely try to improve the cooling of the CPU, and also improve the ventilation of the system case. That alone may just help to stabilize the system. The other issue may be the memory timings configuration: if it is currently running at Command Rate (tCR) = 1T, then try to increase it to 2T. On many systems that makes things a lot more stable. Regards, Fiery
  2. Fiery
    It may not cause too much troubles on your particular machine, or some other machines out there, but on some configurations it wouldn't work well. We try to make a tool that works alright on any systems, so it has to be prepared for the worst situations "out of the box". For example, if you've got an iGPU, 100 millisec may work fine, but if you add 4 dGPUs to the system (like two HD7990 cards), you will have a much higher CPU impact at each updates -- so keeping the update rate higher would be the best idea. One thing that might work is enabling sub-1sec update frequency only via editing the AIDA64.INI configuration file. That way power users can see what rate is acceptable for their particular usage scenario. We'll do that in the next AIDA64 beta release (due in a few days), and I will post a message in this topic once the new beta is available
  3. Fiery
    Update frequency is limited that way, because collecting all sensor values AIDA64 supports (CPU DTS, motherboard sensor chip(s), chipset sensors, sensor and VRM chips for all GPUs, HDD and SSD sensors, DIMM TS sensors, fan controllers, various sensor devices, etc) may take 200-300 or sometimes even 600-800 milliseconds combined. Not to mention that you may also enable measuring a lot of other system values that can be even slower to measure, like clock speeds, memory/CPU/GPU utilization, etc. etc. So configuring a sub-1sec update frequency is potentially dangerous and would result in a constant polling of sensors and a high CPU utilization.
  4. Fiery
    No, you shouldn't have that enabled, it may just make things worse Are you using AIDA64 Extreme v4.00.2700?
  5. Fiery
    Thank you Ganesh, it looks like a very useful app! Regards, Fiery
  6. Fiery
    Thank you. I've sent you a private message about this.
  7. Fiery
    We do have plans for more OpenCL GPGPU benchmarks, e.g. Hash, AES and ray-tracing. We'll work on them in 2014
  8. Fiery
    Please note that old user results will not be shown when you upgrade to a newer AIDA64 version, because results obtained with previous AIDA64 versions cannot be compared to the current version results. A warning about that fact is displayed every time you run a benchmark Regards, Fiery
  9. Fiery
    Those temperatures are normal. As for MCP, please check Q#30 at: http://www.aida64.com/support/knowledge-base
  10. Fiery
    Thank you for the feedback. It seems we have to keep looking for Vdimm Can you please do the following: 1) Set 1.50V in the BIOS, and create an ISA Sensor Dump. Please also create a SMBus Dump (Full). 2) Set 1.60V in the BIOS, and create another ISA Sensor Dump + a SMBus Dump (Full). Hopefully we'll be able to find the register responsible for Vdimm in there this time Thanks, Fiery
  11. Fiery
    No, it's not possible.
  12. Fiery
    AFAIK Marvell SATA/RAID controllers cannot pass SMART commands to Windows software like AIDA64. Regards, Fiery
  13. Fiery
    Thank you for the dumps. I've just sent you a private message about this.
  14. Fiery
    Changing labels for External Applications is not possible at this time -- but you can hide the labels if you want. We may add the labels configuration feature sometime next year. Regards, Fiery
  15. Fiery
    Thank you for the data, and I'm sorry for the delays. Can you please post 2 another ISA Sensor Dumps, both made before sleep, when DIMM voltage is shown as 2V? One dump at default 1.50V DIMM voltage, and the other at a slightly different one, like 1.55V or 1.60V. That way we can check which register is responsible for holding the DIMM voltage value. Thanks, Fiery
  16. Fiery
    If you have the option Enable CPU throttling measurement (in AIDA64 / main menu / File / Preferences / Hardware Monitoring) enabled, then try to disable that option and see if it fixes the issues. Regards, Fiery
  17. Fiery
    ACPI Tool was never a public or official feature of AIDA64, but more a debugging tool to help us find issues in AIDA64 related to certain ACPI BIOS bugs. It has been removed from AIDA64 at v4.00. Regards, Fiery
  18. Fiery

    eDrive support

    Fiery replied to dann23's topic in Brainstorming

    We can add eDrive detection once it gets included in the ATA specification. Unless of course there's an alternative method of detecting that capability -- but we have no information on that at this time. Regards, Fiery
  19. Fiery
    There's no logging in the AIDA64 System Stability Test simply because the elapsed time doesn't change the fact that the system is either stable or unstable If the computer can't stand the stress test for 5 seconds, it is considered unstable -- but it's also unstable if it can run it for 5 hours and only after then it fails But, you can activate the Logging facility of AIDA64 (main menu / File / Preferences / Hardware Monitoring / Logging) to track various system parameters while running the Stability Test. Regards, Fiery
  20. Fiery
    I'm sorry for the delays. We've done quite a few test runs on similar configurations in our test labs, but couldn't reproduce the issues The only thing "suspicious" about your system configuration is the Rampage IV Extreme mobo, which has support for AI Suite II. Do you have that software installed? Or, if not, then do you happen to have the AI Suite services still installed and running? Please note that since Asus refuses to implement the necessary synchronization techniques in AI Suite, it may collide with AIDA64 sensor measurement code and cause all sorts of issues that may lead to sensor values dropout. If possible, please uninstall AI Suite, and verify if it has any services left after its uninstallation. FYI, for unknown reason even after uninstalling AI Suite it leaves a few services installed and running, that will still keep polling sensors and collide with other monitoring applications like AIDA64
  21. Fiery
    We've done a lot of improvements to the CHiL and ONSemi sensor chip functions, and revamped many generic communication functions around there to make GPU sensor measurements more stable, and make the initial scanning of GPU sensor chips quicker. I'm glad that -- as a side effect -- it solved the issues you've experienced
  22. Fiery
    Thank you for the update on this issue. Please note that when you enable stressing GPU(s), it's normal that during the AIDA64 System Stability Test the whole system consumes more power and runs at higher temperatures than while running a game or another stress test. You've got a very powerful configuration, but a game like Battlefield will only drive your GPUs do high levels, but not the CPU. While with the AIDA64 System Stability Test you can push all components to their limits simultaneously. Regards, Fiery
  23. Fiery
    Nice 1st post, thank you And you've got quite a fleet of PCs
  24. Fiery
    Yes, we do have plans about that, but unfortunately the current software stack for Corsair Link architecture doesn't allow multiple applications access the Link hardware simultaneously. Corsair said they will roll out a brand new software stack with 3rd party applications support sometime next year. As soon as their new software stack is ready, we'll get back to implementing Corsair Link support in AIDA64. Regards, Fiery
  25. Fiery
    The latest beta version of AIDA64 Extreme implements full support for Radeon R5, R7 and R9 Series: http://www.aida64.com/downloads/aida64extremebuild2714szdhb5yw8gzip Regards, Fiery
×
×
  • Create New...