Fiery

As I've explained above, we believe AIDA64 reports both values (VID and actual Vcore) properly, it's only a matter of which value do you look at. So IMHO there's no need to fix anything in AIDA64.

We've checked it, and it would require D3D hooking, which is also required for full-screen OSD and FPS measurement BTW. We currently have no plans to deal with D3D hooking I'm afraid

VRM is the Voltage Regulator Module, so its power draw shows the power going through that component of your video card. Regards, Fiery

We've tried it with two SSDs in a RAID0 array on a Z77-based motherboard, but it worked flawlessly for us. Can you please tell us more about your configuration? Do you have any RAID arrays defined? Is your SATA controller configured to IDE, AHCI or RAID mode?

Voltage measurement on LGA1150 boards is quite a special thing, since most boards will measure CPU VRM voltage (nominal 1.8V) in the classic CPU Vcore register. AIDA64 -- and so as other hardware monitoring software -- will have to be adjusted to each board to make sure it shows both the CPU Vcore (if it's possible to measure it) and CPU VRM voltage properly. Haswell support is still not 100% in the latest AIDA64 beta, but we keep improving it at every new beta updates. Full support for Haswell, including AVX2 and FMA optimized benchmarks, is scheduled for late May. Regards, Fiery

DLL is not suitable for us I'm afraid What we'd need is explanation on the usage of the USB HID interface, so we could communicate with the device directly, without any external modules.

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. Thanks, Fiery

Have you tried it with the latest beta version of AIDA64 Extreme Edition? http://www.aida64.com/downloads/aida64extremebuild2440kn0rzpwgflzip

We've fixed the No Disk error in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2440kn0rzpwgflzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let us know how it works.

AIDA64 does not currently support USB temperature sensors. If there's a programming manual (datasheet, SDK, etc) available for the mentioned device, and we can purchase the hardware online or in a local store, then we may be able to add it to AIDA64.

AFAIK = As far as I know

AFAIK Crucial M4 SSDs do not feature a temperature diode.

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2435fb9hzn7gqvzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

There's something wrong with RST 12.6, since it works on several systems with AIDA64, but not on some other systems. Whereas RST 12.5 seems to be more reliable and more consistent. We'll need to wait for a new 12.6 update to see if anything needs to be done on our end.

For such UEFI systems video BIOS version and release date are displayed on the Display / GPU page.

Thank you for the feedback, glad it works better

It's not quite easy to measure CPU VID while building up the SensorPanel, since it takes a lot of CPU cycles to render the SensorPanel itself, and that tend to make the CPU switch to higher clock (and VID) levels meanwhile. Anyway, we've improved on the CPU VID measurement in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2435fb9hzn7gqvzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

The mentioned new AIDA64 beta release is available for download at: http://www.aida64.com/downloads/aida64extremebuild2435fb9hzn7gqvzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you for the feedback. We've been trying to reproduce the No Disk issue in the past weeks on many different configurations, now with flash drives and external HDDs as well, but with no luck. We're starting to wonder whether it may be a software or driver issue rather than a hardware issue. Maybe you have a software installed that causes Windows to pop that message up? BTW, do you dismount the drive first and only after then you disconnect it physically from the computer? Or you just unplug the USB cable and that's it? Is it a USB2 or USB3 drive? Does it have NTFS or FAT partition(s)?

In such cases when a fixed offset can be identified for a temperature reading, you can simply use the Correction feature of AIDA64 to apply the offset on the reading. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction to configure it.

1) It works on some systems with AIDA64, while on other systems it intermittently fails. 2) We'll implement BIOS release date detection for nVIDIA GPUs in the next AIDA64 beta release due in a few days.

As I wrote above, you should run the stability test for at least half an hour. If your system can stand it for half an hour without overheating, than your CPU is fine. After the first test you may also want to enable the GPU subtest to check whether your video card is overheating under heavy load. If any visual artifacts appear on the screen while running the FPU+GPU stress test, or your video driver resets or reports an error, or the computer turns off / restarts, then there's a hardware issue. Otherwise, I'd say it must be some sort of software or configuration problem.

Such issue may be due to CPU overheating or video card overheating, or due to video driver (Catalyst) issues: http://www.anandtech.com/show/6857/amd-stuttering-issues-driver-roadmap-fraps/ You can check if your CPU is overheating under heavy load if you launch AIDA64, go to main menu / Tools / System Stability Test, enable only the FPU subtest, press the Start button. Watch the bottom graph: even after half an hour of heavy stressing, the CPU Throttling graph should still stay at 0% (means no throttling activity, means no CPU overheating). Regards, Fiery

Thank you for your message, I'm glad you managed to resolve it. We'll fine-tune the DLL handling at automatic updates from the next AIDA64 beta release, to make sure such issues wouldn't happen again. Regards, Fiery

Thank you for the feedback!