Fiery

Yes, gauges and graphs are definitely on our list of improvements for "SensorPanel v2.0"

I guess it could be due to AIDA64 detecting SSD SMART attributes (including SSD temperature readings, if available) for your RAID array. Please try to increase or decrease the Disk temperature polling frequency value in AIDA64 / main menu / File / Preferences / Hardware Monitoring, and verify if the frequency of the blips follow the polling frequency change. Regards, Fiery

Please try to disable as many options on the Stability page in Preferences as possible. As a start, please disable the following options there: - RAID SMART support - SMBus access through ACPI - Apple SMC sensor support - Dell SMI sensor support - Koolance TMS-200 sensor support - T-Balancer sensor support - DIMM thermal sensor support - Toshiba TVALZ sensor support - Volterra VT11xx sensor support - GPU fan speed measurement After altering the Stability page options, make sure to restart AIDA64 to apply the changes. Please let me know if it helps. If not, then please try to disable one more option on the Stability page: - Fan divisor reconfiguration If none of those helps, let me know, and we'll create you a special AIDA64 build with enhanced debugging features to pinpoint the code segment where the AIDA64 sensor module halts on your system. Please use AIDA64 latest beta (Build 1720) for those tests. Thanks, Fiery

According to our own Sandy Bridge test runs -- albeit at slightly lower core clocks -- the mentioned AIDA64 benchmarks get memory bandwidth limited at high core clocks. You may want to use higher clocked DDR3 modules to squeeze out more performance from your system.

Do you use Turbo Boost? If yes, then can you please tell us all ratios you use? Max. Non-Turbo ratio, 1-core Turbo ratio, etc? Thanks, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. That data will help us to investigate this issue. Thanks, Fiery

That's why I said "most chipsets". AIDA64 latest beta already includes reference results for Sandy Bridge-E with Quad Channel DDR3-1600, and Bulldozer with Dual Channel DDR3-1866. When a chipset or CPU doesn't support a memory grade officially, raising the memory ratio still makes it overclocking. If you raise the CPU core multiplier on an unlocked CPU (e.g. Core i7 Extreme Edition), it is still overclocking

It is due to a BIOS bug about building DMI information. Please check Q#10 at: http://www.aida64.co.../knowledge-base I'm pretty sure the L3 cache isn't actually disabled. You can check the L3 cache size on the Motherboard / CPU page in AIDA64. If it shows a non-zero value there, your L3 cache is enabled. You can also try to run the Cache & Memory Benchmark (AIDA64 / main menu / Tools / Cache & Memory Benchmark) -- you should see a L3 cache read score somewhere between the L2 cache score and the Memory score. Since the L3 cache is a slower buffer than the L2 cache, but faster than the system memory. And BTW, such DMI issues do not affect system performance or stability at all. Regards, Fiery

Different core temperature on Intel processors before the Core i3/i5/i7 era could be due to different TJMax value used. If you believe AIDA64 measures 10 Celsius more than what it should, then try to set a lower TJMax value in AIDA64 / main menu / File / Preferences / Hardware Monitoring.

1) Do you simply disconnect the drive without ejecting it from the System Tray icon? 2) Is it a USB, FireWire or eSATA drive? Thanks, Fiery

Thank you for the dump. We've verified the registers content, and also the relevant part of AIDA64, and everything looks fine. The only thing that may cause such issue would be the proprietary fan muxing feature that ASRock uses on your motherboard (and a number of other motherboards as well). It effectively muxes the RPM measurement signals of the CPU fan1 and the CPU fan2 headers into the same fan register of the Nuvoton sensor chip. When another software (for example ASRock's own monitoring software called Extreme Tuner) alters the GPIO setting for the fan mux, then the sensor chip will reflect the fan RPM for the CPU fan2 header. I'm afraid we don't have a solution for such issues ASRock should simply stop using that weird GPIO fan muxing on their boards.

1) On mobile systems you may need to alter the default setting of power management features (like SpeedStep) to make sure your computer will be running at HFM (High Frequency Mode) under heavy load. With certain settings that some manufacturers call "Battery saving mode" the computer will always work at LFM (Low Frequency Mode), no matter if the computer is running from AC or DC power. You have to make sure to check the current power management settings, although in most cases to get a mobile computer to work at HFM is easy: just connect it to AC power 2) The FPU stress test usually heats up all system components in 15-20 minutes. 3) AIDA64 System Stability Test is a lot more sophisticated and is better optimized to the latest processors than what EVEREST used to offer -- that's why with AIDA64 it's normal to reach higher temperatures due to the heavier workload it puts on the system. EVEREST is an obsolete and discontinued product that e.g. doesn't support any processors released in 2011 (e.g. Sandy Bridge, Bulldozer, Llano). 4) The FPU stress test uses a heavy workload, based on floating-point calculations, to fill up all the floating-point processing units of the processor with calculation threads. It stresses all available CPU cores and CPU threads, and it utilizes every relevant modern x86 extensions such as SSE, FMA4 and AVX. Modern processors can be heated up to the highest level by running exactly the type of worload that AIDA64 uses in the FPU stress test. 5) Most mobile computers cannot measure their own fan speed, but only able to control the fan speed based on the measured CPU temperature. Unfortunately most mobile computers are not equipped with a sophisticated sensor chip (due to size constraints on the motherboard PCB). 6) I42IL1 is most likely produced by Elitegroup, which manufactures a lot of different motherboard and notebook brands, e.g. ECS, PCChips, Uniwill, etc., and their products are rebranded by an even bigger number of computer assembly companies. Elitegroup a huge company, but since we're not sure which brand the notebook product called "I42IL1" belongs to, we show what DMI reflects. And DMI holds the manufacturer name as "OEM" on your system. Regards, Fiery

Mobile computers implement serious constraints on case space and fan sizes to make sure they are portable. Hence you cannot expect the same cooling performance from a mobile computer than from a desktop computer. Generally speaking, hard disk drives should be the same in mobile and desktop computers, but the mobile motherboards and mobile processors can stand a bit more than their desktop counterparts. So as long as your CPU isn't overheating, you should be fine. You can check CPU overheating in the AIDA64 System Stability Test by enabling only the FPU test, and pressing the Start button. Watch the bottom graph where Throttling should never show any non-zero percentage activity. When your CPU is throttling, it means it is overheating. A properly designed computer should be able to run such a heavy workload like AIDA64 FPU stress test without the processor overheating. Regards, Fiery

Temperatures in AIDA64 may be missing and then re-appear because the temperature readout is unstable due to sensor device issues. GMCH sensors of Intel chipsets are notorious of providing unstable temperature readings When AIDA64 reads an invalid temperature (e.g. 200 Celsius), it removes it from the Sensor page, to avoid displaying bogus/invalid/meaningless values. While HWiNFO doesn't seem to have such tricks, and so it displays bogus values too.

Yes, it utilizes the general data crunching capabilities of modern GPUs rather than their ability to render high-resolution 3D images. When you "just" process a huge amount of data with the GPU, the whole video card is stressed in a different way than when running e.g. a 3D game. We picked the GPGPU way to let AIDA64 users stress their GPUs without the need to switch to full-screen mode.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Make sure to use the latest AIDA64 Extreme Edition beta release: http://www.aida64.com/downloads/aida64extremebuild1714gcn7wyrhdzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Thanks, Fiery

Thank you. Due to the fundamental difference between a full-screen 3D app and a GPGPU application (AIDA64 SST), the GPU won't be loaded or stressed the same way with those apps. On our test systems it took 15-30 minutes to make the video adapter heat up with GPGPU to the same levels that a full-screen 3D app could reach in a few minutes. It's definitely a slight issue, but since we generally recommend our users to run AIDA64 System Stability Test for at least a couple of hours, I don't think this is a show-stopper issue.

1) You can activate the DIMM temperature measurement in AIDA64 / main menu / File / Preferences / Stability. After altering that option you need to restart AIDA64. 2) As for the HP ENVY EC access, I'm not entirely sure if it's relevant on your system. Based on the measured values in HWiNFO, the values seem to show a huge fluctuation. And that usually means the readings are invalid (bogus). Regards, Fiery

Thank you. Have you tried to check it with GPU + FPU test both enabled? I wonder how would that affect the overall system temperature and the GPU temperatures too.

DDR3-1600 is an out of spec (overclocked) memory grade on most chipsets, and our reference results database do not feature any overclocked results due to our internal policy. We may include a DDR3-1600 or DDR3-1866 system featuring an AMD FX-8150 processor -- when that CPU becomes widely available. As for Z68, it's not much different to the P67 which we already have in our reference database. We may add a Z68 system to the database, featuring a Celeron G440 CPU.

Thank you for the feedback

They aren't outdated at all. What are your concerns about the reference results?

Thank you for the feedback Regards, Fiery

Thank you for the feedback Regards, Fiery

Maybe the fact that you have multiple monitors makes a difference... As for the 5-digit bar limits issue and the bar frame colour adjustment bug, we've just rolled out a new AIDA64 beta that should solve both of them: http://www.aida64.co...14gcn7wyrhdzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.