Fiery

Please send us a link to a picture frame that supports such interface an can receive bitmaps via the wireless connection.

As long as free exceeds total, it's nothing we can do about it We need the video driver to report memory usage properly.

Thank you! That looks like a ForceWare driver bug. Via the standard nVIDIA video driver API (called NVAPI) ForceWare reports the following values when things go south: Total / Free Video Memory = 8388608 KB / 9376044 KB Obviously "free" should never exceed "total"

Please go to AIDA64 installation folder, and create new file there called ENABLE_HWMONINIT_LOG.TXT. Then start AIDA64, go to the Computer / Sensor page, and wait 1 minute. Then close AIDA64 (if Windows allows it), or restart your computer. You should be able to find then a new file on your Windows Desktop called LowLevelLog.txt. Please copy-paste the full file into this topic, or attach it as a file to your post. After that test is done, please make sure to remove the file ENABLE_HWMONINIT_LOG.TXT from the AIDA64 installation folder to disable logging. Thanks, Fiery

GX Typhoon RGB backlighting control will be implemented in the next AIDA64 beta update due in a few days from now. It will add 2 more sliders next to the current Brightness slider. The old slider will be responsible for controlling the intensity of the red backlighting component, and the 2 new sliders will be for blue and green.

We would love to support any photo frames, but most of them simply do not support passing bitmap data over the USB connection, so we cannot support them.

I'm afraid we have no plans to separate the configuration of those features. You need to further filter down the values exported, in order to get the list you need in your other software. Regards, Fiery

Can you please create and submit a nVIDIA GPU Registers dump before and after the anomaly occurs? You can create such dumps by right-clicking on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. 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

Yes, it is a false positive. Just let it submit the file to Malwarebytes. AIDA64 files got considerably bigger because we're in the process of implementing DPI scaling (DPI awareness) in AIDA64. And it requires adding high-resolution versions of the existing graphical content (e.g. splash screen, report wizard theme image, About box logo, CPUID Panel background, icons, etc). And since we need to prepare AIDA64 to scale to 400% and even beyond that, we need to add quite large images to the resources of the main module (AIDA64.EXE) as well as to existing DLL resource modules. But don't worry, it doesn't mean AIDA64 would load those images to RAM all the time They are only used when such high DPI setting is actually in use, and even so only one of the high-resolution images is loaded, not all of them.

AIDA64 supports up to 16 Aquacomputer devices. It can be any kind of a mix of Aquaero 4, Aquaero 5, Aquaduct, Aquastream XT/Ultimate, MPS, PowerAdjust, or Farbwerk. Regards, Fiery

Thank you. TBM 3.0 is only supported by Core i7-6800 and 6900 Series, so we can skip that. On your particular setup the best explanation may be that EIST is disabled for some reason, and what you can see the CPU alternating between the min and max multiplier is due to C1E activity. Another explanation might be that due some BIOS pecularity the EIST states (like 14x, 16x, etc) are not properly configured in the ACPI BIOS, and Windows fails to read the in-between states. In which case even though EIST is active, Windows may not be able to fully utilize its clock speed steps granularity.

One feature that may influence the way the CPU switches between various power states is Turbo Boost Max 3.0: http://www.anandtech.com/show/10337/the-intel-broadwell-e-review-core-i7-6950x-6900k-6850k-and-6800k-tested-up-to-10-cores/2 I'm not sure however what CPU you've got, and whether you have TBM 3.0 enabled or not. Also, when a CPU is overclocked, it may behave completely different to a similar CPU running at stock settings. So it would be very important to find out what CPU you've got, and also whether it works different without OC and special settings, so in its factory default state. It would also be interesting to see the list of PStates the BIOS Setup configures for your CPU. Also, if you disable SpeedStep (EIST), the CPU may fall back to using C1E (Enhanced Halt State), to save power. C1E only alternates between the min and max ratio, no middle steps. Same thing could happen if you (or a software) alters the Windows CPU power management settings by forcing the CPU to work at the highest ratio all the same, effectively disable SpeedStep. In which case C1E may still work, so the min and max ratios may be used, just no middle steps. BTW, you can check and modify the Windows CPU power management settings, enable/disable C1E, enable/disable Turbo Boost using the CPU Tweakings panel of AIDA64. Which you can launch from the same right-click context menu that you use for CPU Clock Monitor.

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