Fiery

Thank you!

Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic, or create a screen shot of that page.

Yes.

Exporting and importing settings is easy: just backup the file called AIDA64.INI that you can find in the AIDA64 installation folder.

I'm afraid there's no debug log that could work about this particular issue. Please try to disable all External Applications features (like Shared Memory), enable SensorPanel or OSD Panel, and add those items there that you've added to your shared memory. Let it run for a few minutes, and let us know if it behaves similarly to shared memory.

Please avoid posting a single issue into multiple topics. This topic is closed.

As it is stated on the Display / GPU page, the 366.0 GFLOPS @ 953 MHz figure is the theoretical peak performance of your GPU. The actual performance is lower in most cases.

Thank you for your feedback

Great news, thank you!

Well... It's not quite as easy as I've expected As long as you move the items inside the same group -- e.g. you move CPU temperature inside the Termpeatures group one line up or down -- it works great. But, when you move an item into another group, things could get messy. Not to mention a potential scenario when you would like to rename a group to e.g. CPU, and move all CPU related items into that group. Also, it would complicate things even more if you wanted to remove (or hide) an item, and especially when you want to remove (or hide) a group or add a new group. The potential need to change the grouping logic is the most challenging task to accomplish by simple drag&drop and context menu actions... What do you think?

Thank you! Have you tried to make a report using AIDA64 v5.98?

Awesome, thank you for you feedback!

It's just a minor change, and we don't include every single small change in the changelog.

It must be something about your fans. Are they 3-wire or 4-wire fans?

It's because the Win10 1803 timer issue got mixed up with the ForceWare BSoD issue. They surfaced about the same time, and it was difficult to tell them apart from each other. We're confident that we've managed to fix the Win10 1803 timer issue in the latest AIDA64 update of v5.98, but the ForceWare issue has to be fixed by nVIDIA. We're hoping that the new generation ForceWare drivers (e.g. ForceWare 411) have that problem fixed.

We've fixed the issue in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

We've fixed the issue in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

You only need to have Asetek LC sensor support enabled in order to have H115i Pro readings.

We're already working on enabling drag & drop Stay tuned........

That motherboard info doesn't say much to be honest Do you know the actual motherboard model you've got? Please try to click through the sub-pages of ACPI, e.g. ASF!, DMAR, etc, and see if after clicking one of them, an error message is shown.

Some of the security patches are for SMT/HyperThreading enabled systems And yes, in several cases certain workloads do indeed work best without SMT/HTT.

Thank you. Make sure to close Corsair's iCUE software and Corsair's Link software before starting AIDA64. Corsair's own monitoring software is not designed to work well with 3rd party monitoring software running the same time. Also, make sure that you have Asetek LC sensor support enabled (checked) in AIDA64 / main menu / File / Preferences / Stability.

I suppose when you check AIDA64, iCUE is closed, right? Maybe iCUE changes the fan PWM settings before quitting and/or when you open it. We've checked with default settings on our H150i Pro device, and both fan RPMs and pump RPM are identical across AIDA64 and iCUE.

The VP8 reference results now depend on the Windows type, BIOS version, and the security patches you may or may not have applied on your current Windows system. Also, the VP8 benchmark doesn't scale well on 6+ core CPUs. Due to those issues, we're considering retiring the VP8 benchmark in the next AIDA64 update, along with introducing a new benchmark method. Here's the AIDA64 v5.98.4800 VP8 benchmark score we've just measured using an i7-8700K CPU, in a Gigabyte Z370 Aorus Gaming 7 motherboard and Windows 10 64-bit. The motherboard had the latest BIOS (F7) flashed, and Win10 had all patches applied to date (Win10 build number 10.0.17134.286). 6751

Thank you for your suggestions. We'll work on them in the upcoming weeks, and will send you updates via this topic.