Jump to content

Fiery

Administrators
  • Posts

    11546
  • Joined

  • Last visited

  • Days Won

    489

Everything posted by Fiery

  1. That's another issue that we have to fix. It will be resolved in the next AIDA64 beta release due next week
  2. Thank you for the feedback
  3. Yes, it is still on our roadmap
  4. Updating your video driver may well have caused the difference. I suppose the old driver didn't enable (didn't activate) the Optimus feature.
  5. What motherboard, CPU and video card(s) do you have in your system? Thanks, Fiery
  6. Thank you for the data. I suppose the issue is caused by the nVIDIA Optimus technology that completely switches off the GeForce GPU when the computer is not running a 3D scene (like a game). And when the GeForce GPU is "sleeping", AIDA64 and other software can only access the onboard IGP graphics provided by your Intel Ivy Bridge CPU.
  7. You can open a new topic for that in the Hardware Monitoring forum: http://forums.aida64.com/forum/9-hardware-monitoring/ Name it e.g. "Show off your LCD setups"
  8. 1) The area graph issue is a bug related to monochrome LCDs. It will be fixed in the next AIDA64 beta release due next week. 2) For line graphs and area graphs the graph step is the pixel distance between two graph measurement points on the X axis. Try to raise it to see what does it make to the graph design. For histograms step is the pixel distance between histogram bars. 3) I'm sorry, but it's not possible to format the network download/upload rates value
  9. Thank you for the data. I'm afraid we haven't found anything unusual in it. Can you please try running the benchmarks using AIDA64 v3.20 (latest version) at both stock (default) clock speeds, and also at overclocked speed, and post both results?
  10. 1) Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. 2) Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery
  11. CPU Fan1 and CPU Fan2 are muxed together on many ASRock motherboards, using such a mux solution that cannot be handled by AIDA64 properly. In default AIDA64 should be able to measure CPU Fan2, so you may want to move the fan to that fan header to make it better work with AIDA64. Regards, Fiery
  12. Please avoid posting a single issue into multiple forum topics. I've replied your question in your other topic
  13. You can change the LCD update frequency in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency. Regards, Fiery
  14. For laptop, notebook and tablet computers it is absolutely normal to have only a CPU temperature reading. As for 86 Celsius, yes, it is also normal for mobile computers that do not have a large chassis that would help to draw the heat away from the CPU area. Mobile processors are designed to operate at temperatures up to 100-110 Celsius.
  15. In case you want to test your system's overall stability, then having every subtests enabled is the way to go. However, if you're looking for maximum CPU thermal stress, to check whether you system cooling is adequate, then you should only have the FPU subtest enabled. The FPU subtest uses a special code path with AVX/FMA/SSE optimizations that is capable of putting maximum power and thermal load on the processor. Regards, Fiery
  16. Thank you for the data, we've fixed the sensor readings on your motherboard. Please upgrade to the latest version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/a64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.
  17. You need to enable the SensorPanel (AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel). Then right-click on the SensorPanel --> SensorPanel Manager --> push the Import button --> open the .sensorpanel file.
  18. I'm not sure which feature of the mentioned software do you mean, but we currently have no cloud-based feature in AIDA64.
  19. The screen shot shows a sample SensorPanel layout that you can download from: http://download.aida64.com/sensorpanel/320release_sample.sensorpanel You can import that layout using the SensorPanel Manager.
  20. Thank you for the feedback
  21. When starting a previous (v3.00 or older) AIDA64 release under Windows 8.1 or Windows Server 2012 R2, the Program Compatibility Assistant may show a warning message about compatibility issues regarding the AIDA64Driver.sys file. Please note that under these operating systems only AIDA64 v3.20 and later versions can be used.
  22. Please note that modern Intel processors use a combination of EIST (SpeedStep), C1E (Enhanced Halt State) and C3/C6 to reduce their power draw when the CPU is idle. Once C1E or C3/C6 kicks in, the clock is lowered to 1.60 GHz.
  23. We have the 10 temperatures/voltages/fans limit in the System Stability Test simply because by using too many items, your graphs would look too crowded and hard to read. You can however put all 12 core temperatures to e.g. the AIDA64 OSD Panel or SensorPanel. What exactly is the issue with the CPU clock measurement? What is the actual speed you've configured in the BIOS Setup, and what is the wrong clock speed AIDA64 measures?
  24. We haven't changed EVGA W555 sensor support since AIDA64 v2.70, so upgrading to v3.00 or v3.20 most likely wouldn't help. Can you see the fan RPM speeds in the BIOS Setup, on either the HW Monitor or PC Health Status page? As for the core temperatures, you can put them to the System Stability Test graphs if you press the Preferences button at the bottom of the System Stability Test window --> Temperatures. Regards, Fiery
  25. Windows 8.1 RTM and Windows Server 2012 R2 RTM support has been implemented in AIDA64 v3.20: http://forums.aida64.com/topic/1490-aida64-v320-is-out/
×
×
  • Create New...