Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12166

  • Joined

  • Last visited

  • Days Won

    535

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you. It seems your fans are connected to the IPMI BMC chip, instead of the onboard Nuvoton Super IO & sensor chip, so you can see the measured fan RPM values on the Computer / IPMI page instead of the Computer / Sensor page.
  2. Fiery
    Thank you for the feedback
  3. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2656b7hl0kzgtszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If the problems persists, then 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. 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.
  4. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2656b7hl0kzgtszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  5. Fiery
    Currently it's not supported in AIDA64. For each process running, what property (or properties) would you like to see on the SensorPanel? CPU utilization? Memory utilization? Handles count? Threads count? Something else than those? Thanks, Fiery
  6. Fiery
    It may happen when the stress test process crashes, without providing any feedback to the System Stability Test window. Is your computer overclocked or specially tuned?
  7. Fiery
    Maintaining a list of reference systems could be problemous, because unlike classic x86/x64 CPU and FPU benchmarks, results of OpenCL benchmarks heavily depend on the software environment. OpenCL benchmark results may vary between video driver updates, may change when you go from Windows 8 to Windows 8.1, etc.
  8. Fiery
    Only Gigabyte knows the answer to that
  9. Fiery
    Thank you, the issue will be fixed in the next AIDA64 beta release.
  10. Fiery
    In Windows 8.1 DPI scaling has been revamped one more time (after revamping it in Vista, and then again in Win8). It seems the new interface doesn't provide meaningful values, or at least we haven't yet figured out which API call to use to detect the native resolution of the display. We'll do our best, but we eventually may be forced to simply drop the idea of detecting native resolution, and simply use the logical resolution setting Windows provides via standard API calls. You can always check the native resolution of your monitors on the Display / Monitor page
  11. Fiery
    Here's another new AIDA64 beta update that further improves the new GPGPU Benchmark Panel layout and handling: http://www.aida64.com/downloads/aida64extremebuild2656b7hl0kzgtszip
  12. Fiery
    No, I'm afraid AIDA64 is designed in a way that it shouldn't leave any files behind, except for its configuration files (like AIDA64.INI, AIDA64.SST.INI). It doesn't automatically save a report of your system configuration. Regards, Fiery
  13. Fiery
    The easiest way is to backup the file called AIDA64.INI that you can find in the installation folder of AIDA64. Alternatively, you can export your SensorPanel settings into a SensorPanel configuration file by right-clicking on the SensorPanel --> SensorPanel Manager --> Export (button). Please note that only AIDA64 v3.20 is fully compatible with Windows 8.1. If you use AIDA64 v3.00 or older versions under Windows 8.1, not all features will be available due to Windows 8.1 blocking the kernel driver of older AIDA64 releases due to compatibility issues. Regards, Fiery
  14. Fiery
    I'm afraid that information is only available under Windows XP. You can see that on the Storage / Windows Storage page there. Regards, Fiery
  15. Fiery
    Here's a new AIDA64 beta update that further improves the new GPGPU Benchmark Panel layout and handling: http://www.aida64.com/downloads/aida64extremebuild2651ztbq8cv4pfzip
  16. Fiery
    If you don't have AI Suite installed, and you're sure all its remaining components (services) are removed properly, then you should disable ATKEX support. But please note that AI Suite tends to leave its components installed and running in the background, even after you've uninstalled it
  17. Fiery
    I meant to write RAID or AHCI
  18. Fiery
    CPU#1 is the CPU Diode temperature sensor. DIMM temperature sensing has to be activate in AIDA64 / main menu / File / Preferences / Stability, by enabling DIMM TS sensor support. You need to restart AIDA64 after altering that option. North Bridge temperature should be correct. You can compare the measured value against Gigabyte EasyTune to verify.
  19. Fiery
    In case you can only see 2 temperature readings in the BIOS Setup's H/W Monitor or PC Health Status screen, and Gigabyte's own EasyTune utility also shows only 2 temperature readings, then it's safe to assume your motherboard is only capable of measuring those 2 temperatures. The third one could be anything, even a bogus value. Regards, Fiery
  20. Fiery
    Thank you for the data. What exactly is the problem with the sensor readings?
  21. Fiery
    Thank you for the feedback. Please note that AIDA64 uses standard synchronization mutexes to synchronize its low-level hardware access functions with other software. AFAIK SpeedFan uses the same mutexes (so as CPU-Z, HWiNFO, HWMonitor, SIV, etc), but maybe it isn't implemented there properly
  22. Fiery
    Thank you for the sensor dump. It looks like AIDA64 has difficulties reading motherboard temperature on your board. Somehow the sensor chip doesn't provide a stable and reliable motherboard temperature reading. It could be because the low-level sensor module of AIDA64 collides with another monitoring application. Do you have any such applications installed, either made by MSI or another company? Thanks, Fiery
  23. Fiery
    On modern AMD processors the core temperature diode may provide incorrect, very low readings when the processor is idle. When we've asked AMD about this, they said that the diode will only provide reliable readings when the CPU is under load. It's a hardware issue that we cannot fix from AIDA64. As for the HDD issue, that usually happens when you have multiple drives connected to an AMD SATA controller configured as RAID controller. AMD's RAID drivers do not provide the necessary ATA passthrough interface to access all drives of the RAID array, but instead it only allows access to the first drive. Regards, Fiery
  24. Fiery
    Those spikes could be because of unstable measurement of APIC clock -- which equals to BCLK on Sandy Bridge, Ivy Bridge and Haswell. Please let me know what motherboard do you have, what operating system do you have installed, and which software do you use to encode video, and we'll try to reproduce the issue on our test systems. Thanks, Fiery
  25. Fiery

    Virtu MVP

    Fiery replied to P.J's topic in General Discussion

    On Intel GPUs GPU-Z measures GPU utilization via Direct3D calls. Such Direct3D calls are not used by AIDA64 simply because they aren't fully reliable. Limitation #1: they only measure Direct3D load, and not the actual GPU load. Hence, if you start a computing task (via OpenCL), the Direct3D "GPU utilization" value will not show the actual GPU utilization, but a much lower value. Limitation #2: those Direct3D calls only works properly on single-GPU systems, due to the fact that Direct3D doesn't properly support multiple GPU devices. Regards, Fiery
×
×
  • Create New...