Fiery

CPU utilization measurement shouldn't collide with each other, even without synchronization. What would cause a collision is the low-level hardware interrogation features, like sensor readings (temperature, voltage, fan speed measurement). But most of the software out there are synchronized together, so only those software could cause a headache that don't use synchronization. Some of the software that do use synchronization: AIDA64 (of course ) CoreTemp CPU-Z EVGA E-LEET GPU-Z HWiNFO32/64 HWMonitor Motherboard Monitor MSI Afterburner Rivatuner SIV SpeedFan One of the software that doesn't use synchronization, even though their authors were asked numerous times to do so: Asus AI Suite.

Done, thank you

I'm glad you've made progress about this issue. And yes, you can use AIDA64 v3.00 or even the latest v3.00.2529 Beta release as well.

Thank you, we'll fix that in the next AIDA64 beta release due next week

PrefetchW should be the line "AMD 3DNowPrefetch", but regular AMD 3DNow! supporting processors also support PrefetchW. It is not supported by current Intel processors, but Windows 8.1 will still work on them. I admit it's quite odd We've asked Intel, and they said PrefetchW can be executed on current Intel processors, although it is executed as NOP (no operation / no instruction). AFAIK next-generation Intel Core processors codenamed Broadwell will officially support PrefetchW. Regards, Fiery

That's very creative, thank you for posting it

Please avoid posting your issues into multiple topics. I've replied in your other topic. This topic closed.

It depends on your video driver

It looks absolutely normal. That list shows the installed video adapters, as they're managed by Windows. Windows installs one video adapter for every display outputs, so if you have a dual-output (e.g. DVI + HDMI) video card, then you will have 2 adapters listed there. Regards, Fiery

Thank you. It seems your motherboard has a few tricks up its sleeves The CPU Vcore seems to be influenced by the onboard CHL8326 VRM controller. 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. Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Thanks, Fiery

Thank you Meanwhile, we've released AIDA64 v3.00 and a few beta updates after that, and keep improving Haswell support and LGA1150 motherboards support at every updates.

I'm sorry to hear about your issues and see that you're getting frustrated Please try to give it a bit more tries, it really should work. If there's no AIDA64.INI file in the AIDA64 installation folder, then a default layout of AIDA64.INI file is created when you perform step #3. If the file isn't created, then AIDA64 may not have the necessary rights to write a file in your AIDA64 installation folder. Make sure to have administrator privileges, you need that to use AIDA64 low-level hardware features like sensors monitoring. Also, you can try moving AIDA64 files to C:\AIDA64 folder, it could make it easier to handle file permissions.

Please post a screen shot that shows AIDA64 Vcore reading against ASRock Formula Drive. It should be the definitive reference tool for sensor readings.

Thank you for posting this, it looks like a very useful tool

Thank you, the bug will be fixed in the next AIDA64 beta release.

Thank you, the bug will be fixed in the next AIDA64 beta release.

Thank you for the info. We'll add both formats for the PCI-E temperature readings to make sure AIDA64 can handle both old and new BIOSes.

In other Sabertooth Z87 logs the PCI-E #1 and PCI-E #2 temperatures are listed as "PCIE-1" and "PCIE-2". Are you sure you haven't renamed those? Or maybe between two BIOS updates Asus changed those labels? BTW, when it comes to sensor-related issues, AI Suite II = AI Suite III

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2522cfs6y7mpqjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it doesn't help, then please send us your SensorPanel configuration file.

Please note that Vcore measurement is done by the onboard sensor chip, so in case you find the measured values slightly inaccurate, it could well be because of the voltage level measurement inaccuracy of the sensor chip BTW, what motherboard do you have?

Thank you. We've fixed the Chassis Fan #4 reading. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2522cfs6y7mpqjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. As for the temperatures, on your system AIDA64 gets confused, because you've got Asus AI Suite II installed, and -- I suppose -- you've renamed the temperature labels in it. When AI Suite II is installed, AIDA64 doesn't use its low-level EC sensor functions, and relies on AI Suite II calls to gather sensor information. And that only works properly as long as you use the default labels. You can revert back to the default labels, or uninstall AI Suite II to make all temperatures appear properly in AIDA64.

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

Do you mean the local IP address of the computer, or the external IP address? Regards, Fiery

1) Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery Dump. Copy-paste the full results into this topic. 2) Then go to the Computer / Sensor page of AIDA64, and copy-paste the full page into this topic, using either the right-click menu on the Sensor page, or post a screen shot of the page. Make sure to have the battery charging (so connected to A/C power, and the battery being not fully charged) when you make those tests. Thanks, Fiery

1) 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. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. 3) Finally, right-click on the bottom status bar of AIDA64 main window --> System Debug --> Asus SPD Dump. Copy-paste the full results into this topic. Before running the 3rd test, please make sure to save your documents and close any applications you may have open, because there's a slim chance that it might cause a system lockup or BSoD. Thanks, Fiery