Jump to content

Fiery

Administrators
  • Posts

    12739
  • Joined

  • Last visited

  • Days Won

    582

Posts posted by Fiery

  1. im having the same issue too, just started

    CPU reading always reads 40C until i re boot then drops back to 25c on idle

     

    i73930k at 4.5 (liquid cooled)

    Asus RE4 (liquid cooled)

     

    Aida64 CPU 24

    Aida64 CPU #1 32

    Aida64 CPU #3 27

    Aida64 CPU #4 30

    Aida64 CPU #5 35

     

    Bios Version 4002

     

    On Asus ROG motherboards, when you've got AI Suite II installed, it's best activating Asus ATKEX sensor support in AIDA64 / main menu / File / Preferences / Stability.  It may help in your case ;)  If you decide to give it a try, then first please make sure to have the latest AIDA64 beta release:

     

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

     

  2. AIDA64 reads CPU temperature from the 3rd temperature register of the sensor chip of the X79-UD5 motherboard.  What you wrote to me sounds like a BIOS issue, or a collision between AIDA64 and another monitoring software.  Try to upgrade the BIOS to the latest one, and temporarily uninstall other monitoring software that you may have installed.

  3. Same problem here. I'ts very annoying. I have tray icon disabled (it's unuseful if you have many snesor tray icons visible, they allow you to open AIDA64). Do you mean that if I enable the tray icon main window will minimize OK?

     

    Yes, that's how it works.  By having no AIDA64 tray icon and main window hidden, but sensor icons enabled, that would in theory enable you to show and hide the main window by double-clicking on one of the sensor icons.  But if you had the main window hidden, right-clicked on any of the sensor icons and choose to hide sensor icons, then you would block yourself out of using AIDA64.  Hence it would require a complicated rule if we'd involved sensor icons in that logic.

  4. Works great! I have the motherboard temp option back again. Under sensor temps there is also a measurement for PLX temp but this board does not have a PLX chip. Could this label be measuring some other temp on the board? Thanks for all your help Fiery.

     

    Thank you for the feedback.  In case the "PLX" temperature reading looks valid (not stuck, not showing anything unreal), then it must be another temperature reading.  Although we currently have no information on which temperature would it be.

  5. We do have plans about a GPGPU benchmark based on OpenCL.  However, our efforts on the benchmarks development are slowed down and somehow blocked as well by the improper quality of OpenCL compilers.  Therefore, we have to delay the release of the existing benchmarks until the compilers get more mature.  Not mentioning names, but 2 out of the 3 major GPU manufacturers have really poor OpenCL compilers, not being able to properly compile our benchmark code.  We've notified both companies in question, so they know about the issues, and they promised things will slowly improve in the upcoming months. So we expect to roll out our OpenCL GPGPU benchmarks before the end of the year.

     

    Regards,

    Fiery
     

  6. In that case then I guess it would be better if you could create a TXT report of the Devices / USB Devices page of AIDA64, and copy-paste into this topic.  We'll then find the ID in there ;)

     

    I understand that the issue may not be directly in connection with the RAID member enumeration (due to the fact that you mentioned about stick behavior), but it may still be useful to exclude the stick from the RAID member enumeration. Maybe it helps, maybe not, but sticks shouldn't be scanned anyway for RAID members ;)

  7. My only guess would be that the RAID and external drives scanning module of AIDA64 makes the stick's firmware go crazy for some reason.  The solution would be to exclude the drive from the scanning.  In order for us to add your drive to the exclusion list, we need to have its USB hardware ID.  Please go to the Device Manager, find the drive in the list, right-click on it --> Properties --> Details --> Parent.  The USB hardware ID should be in the format of "USB\VEN_xxxx&PID_yyyy".  If you could send us the ID, we can add it to the exclusion list, and send you a new AIDA64 beta to try it on your system.

     

    Thanks,

    Fiery

     

  8. I understand you need AI Suite II for your system.  What I think would worth trying is temporarily removing AI Suite II, restart the computer, then checking whether it makes a difference in the way AIDA64 blocks your system's shutdown process.  Whatever the outcome is, you can then install AI Suite II back again.

     

    An alternative solution may be activating the option Asus ATKEX sensor support (Asus ROG) in AIDA64 / main menu / File / Preferences / Stability, and restarting AIDA64 to apply the changes.  However, that solution may or may not be effective.  It worth a try though.

  9. Great program, however I am running into a small problem with custom gauges on the sensor panel.

     

    I have three different custom gauges I would like to use( 1 x temperature, 1 x fan and 1 x vcore ), but the gauges are not displaying correctly.

     

    The custom images for the gauges seem to alternate with each other and not display the correct images.

     

    Is it possible to have more than one custom gauge?

     

    Thanks.

     

    We've fixed that bug in the latest beta version of AIDA64 Extreme Edition available at:

     

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

     

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

     

    Let me know how it works ;)

×
×
  • Create New...