Jump to content

Fiery

Administrators
  • Posts

    12179
  • Joined

  • Last visited

  • Days Won

    536

Everything posted by Fiery

  1. Please try updating your RAID drivers to the latest Intel RST Enterprise WHQL driver.
  2. Please try to remove KERNELD.* files from AIDA64 folder.
  3. We've recently fixed a few major issues about Radeon HD 7xxx cards in AIDA64. So make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery
  4. It's actually easy to identify drives with a GPT partition table. Go to AIDA64 / Storage / Physical Drives, and check the Partition Type column. If any of the partitions are FAT, FAT32 or NTFS, then it's a classic MBR. If it's one of these, then it's GPT: Basic Data (this is the most common one) EFI System LDM Metadata LDM Data MS Recovery MS Reserved Unused Regards, Fiery
  5. I wouldn't worry too much about those idle temperatures. Of course there may be a bit of room for improvement if you could improve the air flow of your system case. E.g. install a rear exhaust fan, and/or have a CPU cooler that blows air straight into the rear exhaust. I personally am not a huge fan of side mounted CPU fans
  6. Please try to replace /SAFE with /SAFEST. Let me know if it helps. Thanks, Fiery
  7. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.
  8. Thank you for the info, we've added those O&O software licenses to AIDA64, and fixed the 64-bit Windows issues. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery
  9. We've implemented the changes you requested. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery
  10. Cca. 70 Celsius is a bit high for core temperature, but not critical. You can check the maximum working temperature (TJMax) on the Motherboard / CPUID page in AIDA64. Regards, Fiery
  11. Thank you for the feedback
  12. What GTX670 and GTX680 cards can measure is not an absolute Wattage value, but rather a "Percentage of TDP" value that is not really easy to fit into the existing hardware monitoring module of AIDA64. We'll work on it though
  13. First of all, please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2029bcq0xs8flwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Then please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Thanks, Fiery
  14. I'm sorry, but having a very small gauge size plus a different style where red colour would be at the low end of the scale is not something we'd want to do at this time -- unless we get more user requests on the same idea
  15. 100 MB/sec is very low difference on modern processors.
  16. I think we've figured out what the reason behind the C-State anomaly. Apparently Intel Turbo Boost only considers a core sleeping (inactive) when it enters either the C3 or C6 state: http://download.inte...nots/320354.pdf (Check 3.3 and 3.4 in the PDF) Hence, if you disable C-States (C3 and C6), Turbo Boost will work less efficiently. And that effectively means that single-threaded performance will suffer when you disable C-States. It is reflected by AIDA64 memory benchmarks which are single-threaded benchmarks. It will not be reflected by multi-threaded benchmarks like AIDA64 CPU and FPU benchmarks -- or Sandra memory benchmarks for that matter. BTW, if you check the measured core clock on the Cache & Memory Benchmark Panel, you may see that with C-States enabled your processor will work at a higher core clock level. On our test system (Core i7-2600 + Gigabyte Z68XP-UD3-iSSD) Turbo Boost could push the CPU up to 3.70 GHz during the memory benchmarks when C-States were enabled, but it managed to push the CPU up to only 3.50 GHz with C-States disabled.
  17. What I meant to say was: the Gadget feature requires the Registry to pass on sensor values between AIDA64 (main application) and the Gadget. Without using the Registry it cannot work at all.
  18. It's a false alarm. But if you're unsure, just let it remove the file, it's mostly not utilized. Regards, Fiery
  19. Yes, it looks fine.
  20. You can check the L3 cache performance using AIDA64 Cache & Memory Benchmark (AIDA64 / main menu / Tools / Cache & Memory Benchmark). In case your processor have L3 cache enabled, you will see it evaluated there
  21. Please check Q#10 at: http://www.aida64.com/support/knowledge-base Regards, Fiery
  22. Thank you for confirming the bug fix. Hopefully Roblion would also find it stable now
  23. Thank you for the feedback
  24. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2029bcq0xs8flwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery
×
×
  • Create New...