Fiery

The label System Cooler indicates any sort of coolers that aren't for CPU cooling. We use the term cooler to make sure it could be used for both cooling fans and water cooling solutions as well. What we can do is add 2 more System Cooler fields, and also a bunch of Misc Devices fields to make sure you can enter more devices in there. We'll do that in the next AIDA64 beta release due in a few days Regards, Fiery

Thank you. Do you use IXTU to adjust your memory timings, or do you only do overclocking and fine-tuning using the BIOS Setup?

Thank you for the data. There shouldn't be any collision with CPU-Z and CoreTemp, but maybe one of them (or another software) reconfigures IMC (Integrated Memory Controller) registers. Please create a new PCI Dump in case you find the timings bad again. As for the beta release, it's up to you. Your motherboard is well supported by AIDA64 v3.00 stable release as well.

We've checked it on our Intel DP55SB motherboard with Core i7-860 CPU, and couldn't reproduce the issue So it may be related to motherboard model or BIOS release. Please help us by sending us some data of your configuration: 1) When the CAS Latency is correct (before sleep), please right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results into this topic. 2) Then repeat that when the CAS Latency is wrong (after sleep). MC0 and MC1 are the two memory controllers of your processor. MC = Memory Controller. Thanks, Fiery

We've tested it on our Asus Z87-Pro motherboard, and it seems this issue is due to a BIOS bug of Asus Z87 Series boards. We've notified Asus about this issue, hopefully they will fix their BIOSes. I'm not quite sure however why only Windows 8.1 throws a BSoD when reading from the invalid memory address provided by the ACPI BIOS. It works similarly on our test systems: under Win7 and Win8 no BSoD is generated, the memory reading simply fails. Until Asus could fix the BIOS, we'll implement a workaround in AIDA64 to avoid the BSoD. It will be rolled out as a new AIDA64 beta release in a few days. Thanks, Fiery

What motherboard and processor do you have? Thanks, Fiery

Industry standard memory module temperature monitoring is called DIMM-TS (TS = Thermal Sensor). You can activate that feature in AIDA64 / main menu / File / Preferences / Stability. You don't need anything else, it can be any motherboard or CPU, as long as your memory module does have a DIMMTS compliant thermal sensing diode. In case DIMM temperature(s) do not appear on the AIDA64 Sensor page after enabling that feature (and after restarting AIDA64), then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full), and copy-paste the full results into this topic.

Great news! One of you please try it with AIDA64, and report us the results Thanks, 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

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