Fiery

Which sensor do you mean exactly? NICn Download Rate, NICn Upload Rate, NICn Total Download, NICn Total Upload, or NICn Connection Speed?

Thank you, we'll add those info to the next AIDA64 beta build.

Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.

We've added support for the built-in 160x32 pixel monochrome LCD screen of EVGA Z10 gaming keyboard. You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / EVGA. [/ Currently AIDA64 communicates with the LCD directly, using USB HID interface. It collides with EVGA's own software (EVGA Unleash), so it's recommended to close that software before enabling EVGA Z10 support in AIDA64. EVGA will soon develop a proper SDK/API for their keyboard, much like the LCD API of Logitech gaming keyboards, so that multiple software can put information on the LCD the same time, without collisions. You can find the new AIDA64 beta update at: https://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. Regards, Fiery

Clocks: It's normal, since the BCLK is now measured only once, to avoid collisions with the Win10 RS4 kernel. Feedback: Thank you.

Thank you

Yes, since the BCLK is now measured only once, to avoid collisions with the Win10 RS4 kernel.

My statement from 2016 is still valid today.

I'm afraid there's nothing we can do on our end, since we have to rely on nVIDIA's own API (NVAPI) to read the video memory status information. A future video driver update can get it back.

Not yet. iCUE is also affected by the same issue: Corsair decided not to use the previous synchronization mutexes in that software of theirs either. We're now pulling several strings at Corsair in an effort to try and convince them to put the mutexes back again.

The regular gauges are not available in the RemoteSensor module due to performance considerations as well as scaling issues.

Thank you for your feedback!

Then it could be 2 different issues. For the timer issue of Win10 Build 17134 the above workaround should work. We'll need to work on the ForceWare bug as well.

Thank you. It seems the video driver (ForceWare) fails to report the video memory status via the standard driver API (NVAPI) on your system. We've checked, and the same ForceWare revision does report the video memory status properly on other video cards. It could be a ForceWare bug or a certain pecularity or system property that prevents NVAPI from reporting that information to 3rd party applications. As for the GPU fan, I suppose your notebook has no GPU fan installed. The system may have one or two fans, and one of them may blow the hot air from the GPU, but those fans are not managed by the GPU, but instead the Embedded Controller logic of your notebook motherboard.

They're working on it, but progress is slow due to many occuring issues. They wouldn't want to release something half-baked. So once the non-beta BIOSes supporting the new ACPI-WMI interface is out, they will be great

You can specify the diameter, thickness and colour for arc gauges.

The LCD module doesn't support pre-drawn gauges, but only the on-the-fly generated arc gauge. That's basically the only difference between the otherwise similar SensorPanel module and the External LCD module.

EDIT: We've added the requested information.

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta

Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.