Jump to content

Fiery

Administrators
  • Posts

    12506
  • Joined

  • Last visited

  • Days Won

    559

Posts posted by Fiery

  1. It's not quite easy to measure CPU VID while building up the SensorPanel, since it takes a lot of CPU cycles to render the SensorPanel itself, and that tend to make the CPU switch to higher clock (and VID) levels meanwhile.  Anyway, we've improved on the CPU VID measurement in the latest beta version of AIDA64 Extreme Edition available at:

     

    http://www.aida64.com/downloads/aida64extremebuild2435fb9hzn7gqvzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    Let me know if it helps.

     


    Thanks,

    Fiery

  2. Thank you for the feedback.

     

    We've been trying to reproduce the No Disk issue in the past weeks on many different configurations, now with flash drives and external HDDs as well, but with no luck.  We're starting to wonder whether it may be a software or driver issue rather than a hardware issue.  Maybe you have a software installed that causes Windows to pop that message up?

     

    BTW, do you dismount the drive first and only after then you disconnect it physically from the computer?  Or you just unplug the USB cable and that's it?  Is it a USB2 or USB3 drive?  Does it have NTFS or FAT partition(s)?

  3. It seems that at least with the our setup, the motherboard CPU diode will always read approx 15C less than the CPU Package temperature. My issue is that at idle in my cool room, my CPU package temperature is often 30C or less, putting my mobo CPU temp into temperatures that just don't make sense. I wonder how GIgabyte calibrates these diodes and if the temperature sensors can't correctly read when colder than average. 

     

    In such cases when a fixed offset can be identified for a temperature reading, you can simply use the Correction feature of AIDA64 to apply the offset on the reading.  Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction to configure it.

    • Like 1
  4. As I wrote above, you should run the stability test for at least half an hour.  If your system can stand it for half an hour without overheating, than your CPU is fine.  After the first test you may also want to enable the GPU subtest to check whether your video card is overheating under heavy load.  If any visual artifacts appear on the screen while running the FPU+GPU stress test, or your video driver resets or reports an error, or the computer turns off / restarts, then there's a hardware issue.  Otherwise, I'd say it must be some sort of software or configuration problem.

  5. Such issue may be due to CPU overheating or video card overheating, or due to video driver (Catalyst) issues:

     

    http://www.anandtech.com/show/6857/amd-stuttering-issues-driver-roadmap-fraps/

     

    You can check if your CPU is overheating under heavy load if you launch AIDA64, go to main menu / Tools / System Stability Test, enable only the FPU subtest, press the Start button.  Watch the bottom graph: even after half an hour of heavy stressing, the CPU Throttling graph should still stay at 0% (means no throttling activity, means no CPU overheating).


    Regards,

    Fiery

  6. 1) Yes, there may be some background services left after AI Suite II uninstallation.  You can find more info about AI Suite issues in the following forum topic:

    http://forums.aida64.com/topic/1155-asus-maximus-v-extreme-aida64-unexpected-restartsshutdowns-at-idle-with-aida64-in-background/

     

    You can find info on how to remove the AI Suite services at:

    http://forums.aida64.com/topic/1155-asus-maximus-v-extreme-aida64-unexpected-restartsshutdowns-at-idle-with-aida64-in-background/?p=6686

     

    2) In case AIDA_CPUID.DLL wasn't replaced with the new version during the automatic upgrade process, then please try to manually upgrade to the latest AIDA64 beta by downloading the ZIP package from:

     

    http://www.aida64.com/downloads/aida64extremebuild2430wz0k3xtrlnzip
     

    Close AIDA64, extract the ZIP package to the existing installation folder.  Let it overwrite any existing files.  Both your current configuration settings and your license will be retained.

  7. 1) Are you sure you've properly performed the upgrade to Beta 2430?  Please check the file size of AIDA_CPUID.DLL, it should be 3123528 bytes (2.98 MBytes) long.  If it's correct, then please post your AIDA64.INI file so we can check it out with both the previous AIDA64 beta release and the current one.

     

    2) Even if you disable the auto-start feature in AIDA64, the Logitech LCD Manager may still auto-start AIDA64 ;)  Make sure to disable that feature in LCD Manager.

     

    3) Stability issues on Asus ROG boards are usually caused by collisions between AI Suite II and AIDA64.  We've asked Asus numerous times to implement the same industry standard synchronization techniques that would assure AI Suite II could work well with other monitoring software, but they refuse to cooperate with other software developers.  BTW, AI Suite II collides with not just AIDA64, but other monitoring and tweaking software as well, like CPU-Z, HWiNFO32/64, HWMonitor, SpeedFan, etc.

     

     

    Thanks,

    Fiery

  8. That's because you manually have to set the Type field for your gauges to either Black (Reverse) or White (Reverse).  We've chosen the manual way because for example for cooling fans some of us prefer to have the "red" region in the bottom of the scale (to indicate too slowly spinning fans), while others may prefer to have the "red" region at the end of the scale (to indicate too high RPM).

  9. @Fiery,

     

    I know you have been very busy, but I was wondering if any progress was being made regarding fixing the disk usage issue?

     

    Thanks, and keep up the excellent work.

     

    We've implemented reverse gauges in the latest beta version of AIDA64 Extreme Edition available at:

     

    http://www.aida64.com/downloads/aida64extremebuild2430wz0k3xtrlnzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    Let me know how it works ;)

  10. There seems to be a bug in Logitech Gaming Software under Windows 8 that sometimes prevents AIDA64 from detecting the connected devices.  We'll do more test runs with the latest Logitech Gaming Software, and will try to come up with a workaround until Logitech could fix it from their end.

×
×
  • Create New...