Fiery

Those temperatures look normal. I cannot comment on the warranty issue since I have no idea what you can or cannot claim at Samsung service centers about damages done or happening to your devices. You need to ask them and see if they can do something about it.

The above mentioned new AIDA64 beta build is now available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

Thank you, we will implement sensor support for your motherboard in the next AIDA64 beta update. I will post a message into this topic once the new build becomes available for download.

Yes, you can use custom gauges that you design. You can load them into the SensorPanel by using the Gauge item type and then selecting Custom as Type.

Such issues may occur when WIndows manages disk drives in a different order than how you manage them.

You can simply load the image you want to have as a background and move it to the first position in the list of SensorPanel items to make sure every other item is placed on top of the background image. In most cases the dimensions (width and height in pixels) of the background image matches the SensorPanel dimensions.

Thank you. The PKEY.TXT you've been supplied is indeed an illegal (pirate) product key for AIDA64. If you received that file from Lamptron, it means they're supplying illegal AIDA64 licenses with their hardware.

Let me know if you know a 100% reliable method to detect Bluetooth 5.x capability on Android devices. So far we've only found a method to detect Bluetooth 4.x/5x capability that we show as 4+. It means "4.0 or higher".

In private message please send me the product key Lamptron provided with their hardware for your purchase.

I think it's because of certain scenarios and system state parameters having to fall into the right places in the same time to enable your video card to increase the memory clock to a very high level. So the actual memory clock boost clock depends on the actual task that your GPU is working on.

It usually happens when AIDA64 has no access to its kernel driver. Either because it has no administrator privileges or the user who started AIDA64 has no administrator privileges in the first place.

Settings (incl. LCD layout and sensor icons settings, etc) are still stored in the file called AIDA64.INI in the AIDA64 installation folder as long as AIDA64 has permissions to write to that folder. When it has no permission to save the settings file there, it will put it into the local appdata folder, for example C:\Users\<YourUserName>\AppData\Local\FinalWire\AIDA64\AIDA64.INI

Make sure to use a 64-bit operating system for such a high core count system, and disable Hyper-V and Memory Integrity to prevent sandboxing environments to affect AIDA64 benchmarks.

In the memory stress test, AIDA64 allocates 95% of the physical memory by default. It may be excessive in case you have many background processes and makes Windows to panic about running out of memory. Try to lower 95% to 90% in AIDA64 / System Stability Test / Preferences / General / Memory allocation.

We haven't changed the memory subtest of the AIDA64 System Stability Test recently, so this issue is not related to your upgrading to the latest AIDA64 version.

Please try the latest version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Please note that the first battery capacity value (labelled as "Capacity (Reported by Android)") comes from the Android profile of your device. It was encoded to the profile by the manufacturer of your device, and may or may not reflect an accurate value. The second value (labelled as "Capacity (From Database)") comes from the built-in AIDA64 hardware database, and should reflect the correct value.

I've sent you a private message about this issue.

Try to run only the Memory Copy GPGPU benchmark to make sure the VRAM is under heavy stress too. During the FLOPS and IOPS tests the GPU itself crunching data, but the VRAM is not really under heavy load.

What motherboard do you have? If it's an Asus motherboard, then you may want to try to disable the following 2 options in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Embedded Controller (EC) support Embedded Controller (EC) bank switching Without EC (Embedded Controller) register access AIDA64 will lose a few sensor readings, but it should help to get rid of the stuttering.

I suppose the memory bandwidth is lower at idle than under load. Try to put some load on the GPU, e.g. open the GPGPU Benchmark Panel of AIDA64 (from main menu / Tools) and start the Memory Copy benchmark by clicking on the box next to "Memory Copy" in the left column.

Do you have Hyper-V or Memory Integrity enabled? They could influence benchmark results and so it's recommended to have them both disabled.

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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

I've just sent you an email about this issue.

That's an illegal (pirate) product key. They are not affiliated with us, and they are not our reseller. Make sure to report the website where you purchased that license that they are involved in criminal activities. I also recommend you to ask for a refund or start a chargeback procedure at your bank.