Fiery

Single-threaded memory benchmarking is obsolete, and retaining them next to the multi-threaded ones would just cause more confusion. You can still compare i7-4770K against Core 2 using the new multi-threaded benchmarks. You can still use the old single-threaded AIDA64 cache & memory benchmarks if you keep a copy of AIDA64 v2.85.

Thank you for the feedback

1) Even if you divide the L1 cache bandwidth scores by the number of cores, it's not really possible to compare Haswell AIDA64 v3.00 L1 cache results against results obtained by previous releases, mostly because only AIDA64 v3.00 utilizes AVX instructions. Without AVX it's not possible to properly measure Haswell L1 cache bandwidth. 2) 5400 vs. 4699 MB/s: you need to use XMM or YMM registers to properly utilize the cache and memory subsystem capabilities of modern Intel processors. 3) According to Intel's optimization guide, the bank conflict issue of Sandy Bridge and Ivy Bridge has been eliminated in Haswell. 4) "I hate the fact that cannot play with new toys myself" -- In order to develop kick-ass benchmark methods, you simply need to get the hardware you optimize for Without letting you to try every combinations on an actual CPU, it's very tough to come up with extreme optimizations. Hope this helps to let you dig deeper into Haswell

We may implement per-core clock frequency and multiplier measurement in the future, but it's not on our short-term roadmap. Regards, Fiery

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

I'm sorry to hear about your difficulties. Please note that AMD RAID controller drivers have RAID member enumeration improperly implemented, so in most cases only the first member drive can be detected. Hence it's best to disable the RAID member enumeration on AMD controllers. Regards, Fiery

In HWMonitor Uncore power is calculated as: UncorePower = PackagePower - IACoresPower - GTCoresPower (if applicable) We're not 100% certain such calculation is valid, that's why we didn't implement it. As for offset voltages, we don't have any information on how to detect/measure such values

Please try to disable the Master Volume item, and let us know if it helps.

Thank you for the feedback. AIDA64 and its Desktop Gadget uses the Registry to pass values between them. The gadget is supposed to detect if AIDA64 is running, but maybe on your system it cannot do that. Does the gadget always freeze when you close AIDA64?

I've sent you your product key in private message.

On certain ASRock motherboards we've added CPU VRM voltage reporting using the onboard CHL8328 VRM chip. Even though the VRM is not inside the CPU package, it is still useful to check out its voltages.

Thank you! Please give us a few days to figure out the exact sensor layout for your motherboard. I'll let you know in this topic once we have a new AIDA64 beta release that you can try

Are those voltage rails measured by Gigabyte EasyTune or the HW Monitor page in the BIOS Setup? Please post an ISA Sensor Dump, a SMBus Dump (Full) dump, and a screen shot of all measured values in Gigabyte EasyTune. Thank you for your help

Both "CPU" and "Aux" temperature readings are invalid, so you don't need to worry about them. We'll adjust sensor readings for your system in the next AIDA64 beta release due in a few days.

We'll add VBAT voltage for Asus 6-Series and 7-Series motherboards in the next AIDA64 beta release.

1) Reading SMART values (incl. drive temperature) out of HDDs and SSDs make them keep going to sleep. This is a firmware limitation that is still not addressed after so many years What you can do is increase the Disk temperature polling frequency value in AIDA64 / main menu / File / Preferences / Hardware Monitoring. 2) Fraps is the only external software that AIDA64 supports to import values from. Regards, Fiery

We haven't dropped the VBAT Voltage reading, it is still available.

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

That's great news, thank you for the feedback

Thank you for the feedback

Please send me your full name, email address and the approx. purchase date in private message, and I'll send you your product key. Regards, Fiery

We've implemented a workaround for the tCAS issue after resuming from sleep. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2536f5mtnpwq1lzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Please note that now AIDA64 implements 3 different methods to read tCAS on Intel Lynnfield, Bloomfield, Gulftown and Westmere processors, but none of them is perfect Somehow Intel forgot to implement a proper tCAS detection register in the mentioned CPUs. It should work fine on your particular motherboard from now on though

We've implemented the mentioned workaround in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2536f5mtnpwq1lzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

We've implemented support for the onboard CHL8328 VRM chip of your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2536f5mtnpwq1lzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. With this beta you'll see new items on the Sensor page. The most important one would be the CPU VRM voltage, which hopefully would indicate the right Vcore voltage you're looking for. Let me know how it works.

It's two memory channels per processor node. A 12-core Magny-Cours processor has 2 nodes, so a single processor package supports 4 memory channels. It effectively works as two 6-core processors (each supporting 2 memory channels) put into a single CPU package.