Jump to content

Fiery

Administrators
  • Posts

    11202
  • Joined

  • Last visited

  • Days Won

    475

Everything posted by Fiery

  1. Thank you. I'm afraid something is going wrong with the sensor adjustments layer of AIDA64 on your motherboard. Even the voltages are off, but they all should be in line with PC Probe II, since your motherboard has already received "special treatment" in AIDA64. Maybe it doesn't work for some reason, or maybe your motherboard cannot be properly identified by AIDA64. Please do the following: 1) Copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Using that data we can continue investigating this issue. Thanks, Fiery
  2. As I've stated above: In order to let us come up with our own AIDA64 plugin for AlphaCool, we would need either: 1) The source code or the uncompressed DLL image for acEverest.dll, or 2) Guidelines (SDK, programming documentation) on how to develop a new AlphaCool plugin from scratch
  3. Then please try to close it, run REGEDIT.EXE again, and now try to change both the WindowPosX and WindowPosY values to zero (0). Hopefully that will make the window to appear in the top-left corner of either one of your monitors
  4. Please try to close AIDA64, and start REGEDIT.EXE (Registry Editor). In REGEDIT navigate to the following path ... HKEY_CURRENT_USER\Software\FinalWire\AIDA64 ... and remove the following entries inside that path: WindowPosX WindowPosY WindowSizeX WindowSizeY WindowState Let me know if it helps. Thanks, Fiery
  5. Most SSDs are equipped with a controller that is not capable of temperature monitoring. Even when a temperature readout is provided, in many cases it's stuck and shows a fixed value, no matter how cool or hot the SSD actually is.
  6. Can you see a different "CPU" and "Motherboard" temperature in Asus' own monitoring software called Asus PC Probe II?
  7. Fiery

    HDD cache

    Due to limitations of ATA spec, most drives with 64MB cache cannot report their cache size in the ATA autodetect block. So what you see there is normal, unfortunately.
  8. You seem to have posted an empty post with just a quote from me
  9. 1) What version of AIDA64 are you using? 2) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 3) Also copy-paste the full content of the Motherboard / CPU page of AIDA64 into this topic. Thanks, Fiery
  10. AIDA64 supports up to 16 GPUs, and its hardware monitoring module supports up to 8 GPUs. What kind of GPUs do you have? Do you have Multi-GPU support enabled in AIDA64 / main menu / File / Preferences / Stability?
  11. That may be not the Vcore (Core Voltage) measured by the sensor, but the VID value configured by EIST. It is not a measured value, but a register setting. It may or may not be the same as the actual Vcore.
  12. Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1484y5asv0gmnczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery
  13. Thank you for the report. We've adjusted sensor readings to suit your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1484y5asv0gmnczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery
  14. As I've stated above: The AIDA64 gadget requires AIDA64 (the main application) to be running. That's the normal behavior of the AIDA64 gadget when AIDA64 is not running.
  15. That's fine, but it effectively disables the sensor functions of CPU-Z. It then won't be able to measure CPU Vcore for example. I hope Franck will be able to deliver a real fix for this issue soon
  16. 1) First of all, make sure to have the latest AIDA64 beta release: http://www.aida64.com/downloads/aida64extremebuild1481xz1wg0rpkvzip 2) Do you get a lockup with the OSD Panel feature as well? Or on the Computer / Sensor page? 3) You can reset the SensorPanel feature into its default state by editing the AIDA64.INI file that you can find in the AIDA64 installation folder. From the AIDA64.INI file make sure to remove any lines starting with HWMonSP Or you can even remove the AIDA64.INI file completely, if you don't have any other AIDA64 settings you want to retain. Regards, Fiery
  17. The AIDA64 gadget requires AIDA64 (the main application) to be running. The resetting to a default setting may be due to some Registry entries left in the Registry by a previous AIDA64 session. If you want to make sure the gadget resets to the proper state when AIDA64 is closed, you need to close AIDA64 first, then start REGEDIT.EXE, and remove the following keys including all its sub-entries: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\VistaSidebar HKEY_LOCAL_MACHINE\Software\FinalWire\AIDA64\VistaSidebar HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FinalWire\AIDA64\VistaSidebar Then you can start AIDA64 again, and the gadget should reset to the proper state after you close it again.
  18. On the second link you wrote, focus on the blue chart The first line is the latest beta. Click on the "Download" in the first line of the blue chart, and then you're at the beta download page where you can click the "Click for release notes".
  19. On the AIDA64 beta download page on our website you need to click on the "Click for release notes" line to expand the list of changes in that particular beta release. If you want a history of AIDA64 beta releases with all the changes in them, there's a great thread in another forum: http://www.techpowerup.com/forums/showthread.php?t=132926&goto=newpost Regards, Fiery
  20. 1) Do you have a nVIDIA RAID array? 2) Which motherboard do you have? 3) What version of RAID controller driver do you have installed? 4) Do you use a 64-bit Windows 7? Thanks, Fiery
  21. You need to manually add the Sidebar Gadget to your Windows Desktop. If it still doesn't work, then try to turn off the option "Use HKLM in Registry" in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Vista Sidebar.
×
×
  • Create New...