Fiery

I have no idea why you cannot see any middle steps between the min and max ratios. We've just checked: on our LGA2011-v3 system (Gigabyte X99-UD4 + Core i7-5820K) clock ratio fluctuates between 12x (min) and 36x (max) with several in-between steps, like 30x, 33x, 34x, etc. What kind of system do you use? What happens if you return to default settings, so no OC? BTW, MSI Command Center, at least on the shot you've linked above, doesn't seem to be all that accurate. 100.0 x 40.0 = 4021.7 MHz? I don't think so... And when a software is obviously inaccurate, I wouldn't use it as a reference in a discussion.

Yes, the beta version is the best one for Corsair water coolers And if you prefer to use the latest beta over the latest stable version, then you can enable it in AIDA64 / main menu / File / Preferences / General / NetUpdate.

I'm sorry, but you're not right about most your points, and it's mostly because you don't understand how modern processors work, and how does CPU clock frequency measurement work. If you don't let the CPU go to sleep, then you're not measuring the clock frequency of the CPU at any given time point, but the clock frequency that your software makes the CPU to switch to, right before you measure the frequency. By inserting that pause you eliminate the effects of the workload that the preceding parts of the monitoring software. Of course if the system is running not just the monitoring software, but some other task as well (like a partial workload caused by a background virus scanning process for example), then the pause will not cause the CPU to completely go to sleep -- since it still has other work to do. If you want to do another experiment, then start a task that loads just one CPU core, like a WinRAR benchmark with the Multithreading checkbox cleared, and then check what the CPU Clock Monitor shows. After that, start a task that is not that constant about its CPU load impact, like start a background virus scanning or such. --- Based on your posts, it seems to me that you simply don't like AIDA64. In which case you can just use any of the alternatives that came up here in this topic. Noone here would force you or persuade you to pick AIDA64 over the alternative monitoring solutions. We're still 100% sure that we measure CPU core clock frequency the right way. Not because it's our way, but because it provides the accurate results.

There's an experimental CPU Clock Monitor panel in the right-click debug menu of AIDA64. To start it, just right-click on the bottom status bar of AIDA64 main window --> CPU Clock Monitor. You may need to enable status bar in AIDA64 / main menu / View first. There's no averaging. The CPU core clock frequency is measured for the first logical processor (first core), or for the selected CPU if you use the dropdown list on the CPUID Panel.

Make sure to update Corsair Link Software to its latest version too.

If we disable the pause before measuring CPU clock, the CPU would be running in a high frequency state (either max or a few steps below max) simply because it switched up because of the stuff we do in AIDA64 before measuring the CPU clock. So it would never show the idle state, even when the CPU is actually at idle. Trust me, it would be a bad idea and would yield to misleading results. Yes, it can. Try to open the AIDA64 CPUID Panel (from AIDA64 / main menu / Tools), and grab the window, and vigorously move it around the screen. Shake the window if you will. You will see that as the CPU core clock is updated in the background, the clock will fluctuate between the min and max, showing multiple states in between them.

ATI GPU Registers dump is still included the latest AIDA64 beta. But please note that it's a debug feature that is not intended for regular use. It's there to aid the development of AIDA64, and to hunt down bugs in our detection code. Regards, Fiery

You get other value than min or max when your CPU is currently operating at such a state. Like when it is under heavy load, it won't be able to sustain running at the maximum Turbo Boost clock, and will step back a few hundred MHz's. No. Why would we want to copy a built-in Windows feature? It is already done, we don't intend to re-invent the wheel again. I'm not sure what "break" feature you mean. Can you please tell me more about it? It will show the in-between states when the CPU is running at those. When the CPU is under partial load, it doesn't matter if the CPU clock measurement thread of AIDA64 provides the pause or not, the CPU won't be able to go idle and put its multiplier to the minimum state. That's when AIDA64 will measure an in-between clock. It depends on the CPU type. On modern Intel processors AIDA64 (and also CPU-Z, HWiNFO, SIV, and a lot of other monitoring software) measures BCLK (reference clock), detects the current CPU multiplier, and multiplies them to get the CPU core clock. Task Manager may just show an average clock speed measured over a period of time. We don't know what exactly it does, since we are not the developers of that tool. We are not Microsoft No. It is the current CPU core clock speed. AIDA64 does show the actual CPU clock. IMHO yes

It means either the CPU made a calculation mistake, or the memory or cache subsystem failed to load a value from your memory. It's such an issue that is impossible to track down any further, since all we can see during the stress test workload is that the calculation didn't end up with the right result. In such cases it's usually due to excessive overclocking or improper (too strict) memory timings setting. Regards, Fiery

AIDA64 lets CPUs have a bit of "break" before it measures the CPU core clock. Hence when the CPU is idle, it should measure the lowest clock rate, the sleeping state. Other software may not let the CPU go to sleep before measuring the core clock, and so the CPU may be stuck at a higher clock rate due to previous tasks ran by the same software. Regards, Fiery

What version of AIDA64 are you using? I'm just asking because we've already fixed a similar issue about Surface Pro 4 and Surface Book in AIDA64 v5.60. Thanks, Fiery

Only the high-end Asus ROG motherboards suffer from such issues about EC bank switching. AFAIK Maximus VIII Gene, Hero, Hero Alpha, Impact, and Ranger boards do not use such mechanism. PCH Core and PCH Diode temperatures are both motherboard specific. Regards, Fiery

AFAIK VTT voltage is not monitored by Rampage V Edition 10. And the other 2 voltage readings would require using an Embedded Controller bank switching mechanism which would collide with AI Suite. And such a collision could cause system instability or system lockup. We've already notified Asus about this issue. Regards, Fiery

Please send me your AIDA64 product key in private message. Also send me your email address, so I can contact you directly. Thanks, Fiery

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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Bar is already supported, albeit not with different coloured sections. We currently have no plans to expand gauges with new design options.

We've tried to replicate the issue using ForceWare 372.54, but it didn't come up on our test systems. Let me know if the issue still comes up with the latest ForceWare WHQL release of 372.70. Thanks, Fiery

No, we haven't implemented it yet, because it's not quite clear whether altering the RGB backlighting setting would write the onboard flash or not. Can you confirm it wouldn't update the flash?

1) We've checked and the Type option is still available for gauges displayed on Razer LCDs. 2) Due to the fundamental difference between the rendering engine used for RemoteSensor (and Logitech Arx), the classic gauge cannot be used for those special displays. Arc gauge is more flexible and requires less efforts on the user's part to have it customized. 3) We currently do not have a 3D game plugin that could be used to detect API/Renderer information, so such detail cannot be detected by AIDA64 at this time. Regards, Fiery

On Maximus VIII Extreme T_Sensor2 and T_Sensor3 temperature readings are only accessible via Embedded Controller bank switching. Which is a dangerous mechanism to use, since bank switching done by concurrent software (mainly AIDA64 and Asus AI Suite) could cause system lockup or stability issues. We've already notified Asus about this issue. Regards, Fiery

The only local change you may have to do -- depending on the network architecture -- is to make sure AIDA64 is auto-executed. The portable version can be used on any machine, without any sort of installation or pre-configuration procedure. There are no DLL, driver or runtime dependencies, so you don't need to install e.g. Visual C++ Redistributable Packages, .NET Framework or such.

Please read the setup guide that I've linked above

Only AIDA64 Business and AIDA64 Network Audit feature full command-line driven automation. You can read more about it in the following documents https://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-manual.pdf https://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-setupguide.pdf Regards, Fiery

Correct. Business edition is typically for a single company or organization, used to audit and monitor their full network of computers.

You need the Engineer edition for such purposes. A single Engineer license will entitle you to use AIDA64 on any client's computers for diagnostics or troubleshooting purposes. Your client however will not be able to keep using AIDA64 for his purposes. Yes, we do have a portable version for all AIDA64 editions. Regards, Fiery