Jump to content

Fiery

Administrators
  • Posts

    11188
  • Joined

  • Last visited

  • Days Won

    475

Everything posted by Fiery

  1. The main temperature is the GPU Diode, which is measured by the GPU itself, using its on-die temperature sensing logic. GPU VRM1 and GPU VRM2 are the two rails of the onboard power regulator chip (e.g. CHL8328). Catalyst Control Center should display the same temperature that AIDA64 shows as GPU Diode.
  2. That shouldn't make any difference. The self-installing EXE package contains the very same files as the ZIP (portable) package.
  3. Thank you, we've added Oland and Kalindi from the 2nd source. I wouldn't consider the 1st one 100% reliable, especially since the Kaveri codenames do not match
  4. Thank you for the list. In order to verify the list, could you please provide the source you got it from? I'm just asking, because I'm not entirely sure about the accuracy of your list. For example, the APUs of Kaveri should rather be codenamed Spectre and Spooky. Regards, Fiery
  5. Then please copy-paste the full content of the following pages of AIDA64 into this topic, so we can check out what's wrong. - Display / Monitor - Display / Desktop - Display / Multi-Monitor Thanks, Fiery
  6. AIDA64 reports the current desktop resolution setting, which may or may not match the native resolution of the display. You can adjust the desktop resolution by right-clicking on the Windows desktop --> Screen Resolution. Regards, Fiery
  7. We'll add your storage device to the filter list to make sure AIDA64 can get through the SMART scanning. But in order to do that, we need to have the USB device ID for your device. In the Device Properties window please select "Parent" as Property, and send us a new screen shot. It should show the USB device ID in a format of e.g. "USB\VID_xxxx&PID_yyyy". Thanks, Fiery
  8. First, please try to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2559vf5d6rhmlkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it doesn't solve the issue, then try to completely uninstall Asus AI Suite II. If that doesn't help, then please let us know, and we'll investigate the issue further. In most cases however, it's the improper synchronization (or better said, the complete lack of synchronization) of AI Suite II that causes such issues
  9. Try to disable the "Load AIDA64 at Windows startup" option, close AIDA64, open the Windows Task Scheduler, and remove any AIDA64-related tasks you may find there left. Then start AIDA64 again, and enable the "Load AIDA64 at Windows startup" option. BTW, make sure to have the option AIDA64 Preferences / Layout / "Hide icon and bubble in Notification Area" disabled (unchecked), since using both "Load AIDA64 at Windows startup" and that option is not possible.
  10. We've tried it on a Win7 64-bit SP1 configuration, and it worked flawlessly for us. Are you sure your Windows user have permissions to write to C:\ folder? Try to change C:\ to a folder where you definitely have write permissions. If it doesn't help, then AIDA64 may crash at one of the report pages, so try to limit the report profile to e.g. Audit-related pages, using the following command-line: aida64 /R C:\Report.html /HTML /SHOWPCANCEL /AUDIT Regards, Fiery
  11. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2559vf5d6rhmlkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Please note that when the GT Cores are not utilized, their power measurement indicates 0 (zero) Watts, and then AIDA64 may hide the value from the Sensor page. Regards, Fiery
  12. You can set any image file as background, just make sure to move the image file to the top of the list using the SensorPanel Manager. The order of the items there determines the placement order on the panel's Z axis (depth).
  13. Please avoid posting your questions into multpiple forum topics. I've replied you in your other topic.
  14. When you open the Preferences, do you have the option Layout / Hide icon and bubble in Notification Area disabled (unchecked), and the option General / Hide main window (minimize to System Tray) enabled? Please note that you cannot hide the System Tray icon and have AIDA64 minimized to System Tray in the same time.
  15. Due to product segmentation it's not really possible to build a database for such features. And most companies tend to keep information on detecting such features private
  16. "FPU" subtest uses AVX acceleration on certain AVX capable processors. It's not possible to disable AVX acceleration, unless of course you switch to Windows 7 SP0 or Windows XP -- where AVX is not available due to Windows kernel restrictions.
  17. We currently have no information on how to measure such GPU load on either architectures. Do you know of a software that can do that? Thanks, Fiery
  18. If you use only the "FPU" subtest in AIDA64 System Stability Test, then you can try the worst case scenario for your processor: an AVX accelerated heavy stress test that will put the most demanding load on the CPU. With the "FPU" subtest your CPU will reach the highest power draw and the highest temperatures as well. If you don't want to put so much stress on the CPU, to test the "without AVX" scenario, then in the AIDA64 System Stability Test just enable all tests except for the "FPU" subtest. Regards, Fiery
  19. I'm afraid I don't understand your question. Can you please explain it more detailed, or maybe post it in your native language and we can use Google Translate to figure it out. Thanks, Fiery
  20. Please let us know more detailed what the issue is.
  21. Thank you for the dumps. Please check it with GPU-Z 0.7.2 as well, and let us know if it shows similar value to AIDA64 or not. Thanks, Fiery
  22. 1) Custom PNG images can only be used for gauges. 2) The seconds issue is due to the fact that the update frequency of the panel is 1 second, but it could be more when detecting certain items take a long time. We'll try to come up with a workaround soon. 3) You can use the auto-scaling option for your graph to avoid the clipping issues. The auto-scaling feature is implemented specifically for the network traffic items
  23. CPU VRM means VR Input voltage for Haswell processors. I'm afraid we still have no information on IT8790E, hence we cannot figure out where the missing voltage and fan values come from
×
×
  • Create New...