Fiery

What's the value reported by AIDA64, what do you reckon the accurate value should be, and what version+build of AIDA64 are you using?

What motherboard and CPU do you have, and which version of AIDA64 are you using?

You're right, it doesn't cause any issues, but of course we will fix this in the PCI database of AIDA64 in the next AIDA64 beta update.

The mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta

It's implemented in the latest AIDA64 beta update available for download at: https://www.aida64.com/downloads/latesta64xebeta

We're not quite sure why it happens and at what point of Windows 10 development this was introduced, but when you right-click on the Windows Desktop or on a Desktop icon, Windows takes away the always on top setting from the SensorPanel window, and it wouldn't give it back after the right-click context menu gets hidden. The SensorPanel however detects that it no longer has the always on top setting (even though you have it configured in the AIDA64 Preferences for it), and it reconfigures its own window to have it back. It then causes the right-click context menu shown by Windows on the Desktop to vanish. Very weird, but so far we haven't found a perfect solution to get around this. Because if the SensorPanel window doesn't detect its own always on top state change, the always on top behavior will stop working after you press a right-click on the Windows Desktop or on a Desktop icon

Rendering the LCD layout could well cause power consumption spikes, since it consumes system resources to render the LCD layout.

Do you find a pattern across those different systems you've mentioned, like a common hardware component? Maybe they both have the same Radeon video card?

If you deem it's an incorrect reading, then just ignore it and focus on the other thermal readings.

It's not written in stone yet. We're planning to do a release before September, but we'll see how it turns out.

Thank you. Do you think the EK Loop Connect device appears as YiMing 1840 as a connected USB device?

Yes, either Odospace is the solution or the RemoteSensor feature:

I'm afraid I have no idea what could be going wrong in those instances My best guess would be a collision with another software, but it's just a guess.

As for CPU temperature, your motherboard cannot measure that. But you can re-assign the missing reading to another CPU thermal reading like CPU Package by right-clicking on the CPU temperature bar --> Modify. As for GPU temperature, I suppose you use the integrated Intel GPU and not have a video card. In which case you can re-assign the missing reading to another GPU thermal reading like CPU GT Cores or iGPU by right-clicking on the GPU temperature bar --> Modify.

Please try to close CAM and right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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

What motherboard do you have?

Thank you for your feedback!

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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

Do you have AIDA64 loaded at Windows bootup?

1) Do you try to add the image to the SensorPanel layout, or to an external LCD layout? 2) Is the image in PNG or JPEG format? 3) Would it be possible for you to send a sample image to us in email that fails to work on your system? Make sure to remove any sensitive information or details from the image beforehand though

I suppose what happened is that the AIDA64 kernel driver got stuck inside the Windows driver cache. Try to uninstall AIDA64, scan for your HDD/SSD for any of its remaining executable files (AIDA64.EXE) and remove them in case there're some left over. Restart Windows, and scan the HDD/SSD for KERNELD.X64 file, and remove them if there're any left over. When you're done with it, everything should be back to normal and you should be able to reinstall AIDA64 properly.

It looks great, good job there!

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it fails to fix the issues.

It's in the system menu of the AIDA64 app.

On processors that have a large L3 cache that serves a lot of CPU cores, it's very tough to avoid some background process or service to write something into the L3 cache. There's no real solution to this issue other than re-running the L3 read bandwidth benchmark 10 times or until you get the highest score possible. Just double-click on the box that is in the row of "L3 Cache" and in the column of "Read" to re-run just the L3 cache read benchmark.