Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12004

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    We've decided to let the Preferences / Hardware Monitoring / Update Frequency page settings go down to 500 milliseconds in 100 ms steps, so you (and other power users) will not have to deal with .INI file editing and other hurdles Please upgrade to the latest AIDA64 beta release available at: AIDA64 Extreme: http://www.aida64.com/downloads/aida64extremebuild2731phyzl2fjwbzip AIDA64 Engineer: http://www.aida64.com/downloads/aida64engineerbuild2731rvxwfcqtdhzip Let me know how it works for you
  2. Fiery
    Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2731phyzl2fjwbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  3. Fiery
    Thank you! Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2731phyzl2fjwbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works
  4. Fiery
    Can you please create a photo of the voltage, temperature and fan speed values in the BIOS Setup? It would provide us with a reference, and would help a lot to tune the voltage measurements in AIDA64. Thanks, Fiery
  5. Fiery
    Thank you for letting us know. Quite frankly, we had no idea what could have been wrong. Even with an active iGPU and no video card installed, latency scores aren't supposed to be that high as they were on your system. But I'm glad you managed to resolve it, and now you've got proper scores in AIDA64 benchmarks Regards, Fiery
  6. Fiery
    The FPU subtest of AIDA64 System Stability Test is designed to drive processors to their absolute limits. That's why it uses state-of-the-art techniques like AVX and FMA instructions. Before Haswell hit the market, we considered throttling processors (while running the Stability Test) unstable. However, with Haswell we all simply have to get used to the fact that due to the FIVR (integrated VRM) the CPU can indeed throttle under heavy load, and still work stable. So if you're okay with those high temperatures, or you believe the FPU subtest of the Stability Test is too extreme and wouldn't align with your normal, everyday usage scenario, then just ignore the throttling and use your CPU at 4.7 GHz. However, in case your system turns off due to the high temperature while e.g. running a 3D game, then you should consider improving your system cooling Regards, Fiery
  7. Fiery
    In order to use the low-level features of AIDA64 (like sensor measurements), you need administrator privileges. It is always best to run AIDA64 as the admin user. Your particular usage scenario may not be suitable to launch AIDA64 at startup via its built-in feature. You can try to disable launching AIDA64 at startup in AIDA64 Preferences, and manually create a Scheduled Task to launc AIDA64 at Windows bootup. That way you can select the Windows user to use when launching AIDA64 for example, and enter your user password as well. Regards, Fiery
  8. Fiery
    Thank you, we'll switch the fans in the next AIDA64 beta release. The new readings are: CPU temperature, +3.3V voltage, and iGPU voltage (if iGPU is enabled).
  9. 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
  10. 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
  11. 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.
  12. Fiery
    No, you shouldn't have that enabled, it may just make things worse Are you using AIDA64 Extreme v4.00.2700?
  13. Fiery
    Thank you Ganesh, it looks like a very useful app! Regards, Fiery
  14. Fiery
    Thank you. I've sent you a private message about this.
  15. Fiery
    We do have plans for more OpenCL GPGPU benchmarks, e.g. Hash, AES and ray-tracing. We'll work on them in 2014
  16. 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
  17. Fiery
    Those temperatures are normal. As for MCP, please check Q#30 at: http://www.aida64.com/support/knowledge-base
  18. 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
  19. Fiery
    No, it's not possible.
  20. Fiery
    AFAIK Marvell SATA/RAID controllers cannot pass SMART commands to Windows software like AIDA64. Regards, Fiery
  21. Fiery
    Thank you for the dumps. I've just sent you a private message about this.
  22. 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
  23. 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
  24. 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
  25. 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
×
×
  • Create New...