Fiery

The current multiplier the CPU is running at may be difficult to measure ot detect. For example, at idle it may be running at 45x, under partial load (like running a game) it may be working at 42x, while under full load it may switch down to 40x or so because of power (TDP) limits. Turbo Boost is a very complicated technology in modern Intel processors BTW, between BIOS updates such settings like max. Turbo Boost multiplier or power limits may change.

Haswell processors tend to reach very high temperatures under heavy load, and in many cases they start to throttle. It's a drawback that comes from the combination of the FIVR (integrated voltage regulator) and the inadequate heat dissipation from the CPU core to the heatspreader. In case you want to test your CPU for maximum thermal stress, then only enable the FPU subtest in the AIDA64 System Stability Test, and disable the rest of the subtests.

Thank you for the feedback We'll roll out a new update for Business Edition soon

1) What version of AIDA64 are you using? 2) Are you sure your CPU isn't throttling (slowing itself down) while running the benchmarks, due to overheating?

91 Celsius is quite high for a CPU, and throttling activity (be it 0% or more) is never good. BTW, 0% throttling means "sub-1%" throttling, so it's still a bit amount of throttling. If it's possible, you should definitely try to improve the cooling of your system. Regards, Fiery

In that case the lag you're experiencing is just the usual lag because of the heavy load AIDA64 System Stability Test puts on the computer. The stress test module uses up all available system resources, that's normal.

The Windows UI elements lagging is caused by ForceWare video drivers. ForceWare slows down quite a bit once you put a heavy load on the GPU via OpenCL GPGPU code. So what you are experiencing on your system is absolutely normal. I suppose the work computer you mentioned has no nVIDIA GPU. Regards, Fiery

1) & 2) On which page of AIDA64 do you miss those information? 3) On your system it's not possible to measure Vcore via direct CPU VID detection or via a classic sensor chip register readout. As for DMI, please check Q#10 at: http://www.aida64.com/support/knowledge-base 4) It's because there's no classic sensor chip in your system. IPMI Sensor is not supported by the AIDA64 hardware monitoring module. 5) Thank you, we'll fix that. 6) Changing between IPMI subdevices causes that. It comes from the logic how AIDA64 hardware detection engine works, but we'll check if it's possible to improve on it. Thanks, Fiery

During benchmarks the CPU may or may not be able to use its maximum Turbo frequency. I guess in your case the CPU is only able to switch up to 4200 MHz during the benchmarks.

In case the graph exceeds the configured limits, then you need to either set the limits to higher/lower values, or enable the auto-scaling feature.

I've just sent you your product key in email. Regards, Fiery

We've implemented area graphs and histograms for the SensorPanel in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2590hs6vgtb9xyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. As for the adaptable bar limits, we believe it would be too much (too many colors) to track for most users, so we prefer not to implement that.

We've implemented area graphs and histograms for the SensorPanel in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2590hs6vgtb9xyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

We've fixed the GTX770/GTX780 fan duty cycle issue. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2590hs6vgtb9xyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you, we've added your flash drive to the filter list. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2590hs6vgtb9xyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

AIDA64 reads voltages directly, from the sensor chip. However, your motherboard doesn't monitor +5V and -12V rails, so AIDA64 cannot monitor them either.

Can you see those voltage readings in the BIOS Setup, under PC Health Status or H/W Monitor?

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2584py2mftr4szzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it still doesn't work as expected, then please try to disable SMBus access in AIDA64 / main menu / File / Preferences / Stability, and let us know if it makes a difference. After altering the SMBus option, make sure to restart Windows. Thanks, Fiery

You can try reinstalling Windows, updating drivers, updating BIOS, but I'm not sure if those would help at all in your case. It worth a try though.

Then you can try downgrading to a previous AIDA64 release. Although, I'm pretty sure it won't be able to measure SSD temperature, since it is a hardware limitation.

Only Corsair knows about the firmware patches schedule, so please ask them about their SSD capabilities

When the temperature sensing logic is missing or inoperational, we cannot fix that from AIDA64.

AFAIK Corsair Force 3 SSDs do not feature a temperature sensing logic. Regards, Fiery

1) It's possible that sometimes the iGPU reading shows 0 Celsius or above 200 Celsius, and AIDA64 filters out such invalid readings. 3) I'm afraid it's only possible via a BIOS update or BIOS hack. You need to consult Dell to find out what can be done.

1) Does the issue affect both drives? 2) While you have both USB drives connected, please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Let me know if it causes any of the drives to disconnect. Thanks, Fiery