Fiery

The Windows scheduler explanation still applies: Windows deems it's best to run AIDA64 on the last core and probably puts more threads/processes on that core as well. It results in the core running at a higher core ratio than the other cores, which then means it has to use a higher VID step to operate properly.

Thank you for your feedback and for your kind words

As a hashing algorithm, SHA1 is obsolete. It's also redundant when you have a more modern implementation of SHA. But, to make sure not to leave it behind completely, you can still run the SHA1 benchmark from the GPGPU Benchmark panel (AIDA64 / main menu / Tools / GPGPU Benchmark / double-click on the box in the x64 column, third line from the bottom).

We've added the secondary SSD thermal reading to the Sensor page following a user request in AIDA64 v6.00.

Thank you, we'll fix the issue in the next AIDA64 beta update. I'll post a message into this topic once the new build is available for download.

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. Thanks, Fiery

Thank you for your feedback!

It's because the drive provides 2 thermal readings. It depends on the SSD controller firmware whether those are 2 distinct temperatures. You can see all the thermal readings and other readings and measurements provided by your SSD on the Storage / SMART page in AIDA64.

The latest AIDA64 update introduces SHA3-512 cryptographic hash benchmark and AVX2 optimized benchmarks for the upcoming AMD Zen 2 “Matisse” processors, adds monitoring of sensor values on BeadaPanel LCD displays, and supports the latest AMD and Intel CPU platforms as well as the new graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - SHA3-512 cryptographic hash benchmark utilizing AVX, AVX2 and AVX-512 - AVX2 and FMA accelerated 64-bit benchmarks for AMD Zen 2 “Matisse” processors - Microsoft Windows 10 May 2019 Update support - BeadaPanel LCD and SteelSeries Rival 710 OLED display support - Corsair H100i Platinum and H115i Platinum liquid cooler sensor support - Cooler Master MP750 RGB LED mousepad support - Corsair Obsidian 1000D, EVGA iCX2, Farbwerk 360, NZXT GRID+ V3 sensor support - Preliminary support for Intel “Comet Lake” CPU - GPU details for AMD Radeon VII - GPU details for nVIDIA GeForce GTX 1600 and GeForce RTX 2060 Series - Preliminary support for AMD “Navi” GPUs - Retired SHA1 and VP8 benchmarks [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v6.00 ] [ Download ]

Please check the latest update about fan RPM measurement: https://www.aida64.com/downloads/latesta64xe

We've fixed the remaining issues about Radeon VII in AIDA64 v6.00 stable update available at: https://www.aida64.com/downloads/latesta64xe

It has been rolled out in the latest AIDA64 stable update of v6.00: https://www.aida64.com/downloads/latesta64xe

The requested feature has been implemented in the latest AIDA64 update of v6.00: https://www.aida64.com/downloads/latesta64xe

After the "Cannot find DLL" message, try to open Device Manager, find the device for the Samsung frame, and try to install the Samsung SPF LibUSB driver manually.

CPU Package is a single thermal measurement provided by the CPU itself, using its on-die thermal diodes. It's not an issue at all, unless either of the CPU temperatures get above 100 Celsius.

Thank you. We're finally getting a Radeon VII video card on Monday that will allow us to dig down deeper and fix the remaining issues in the next AIDA64 update.

CPU VID on Sandy Bridge and later processors are read from a CPU register. AIDA64 doesn't specifically forces the thread that reads that register onto any cores, so it's the job of the Windows scheduler to decide which core it executes the register readout task on. Most likely Windows works the way it is because it deems AIDA64 is a performance oriented application and so whatever it does is executed on the highest performing core (also known as preferred core) which can use the highest Turbo Boost ratio. In your processor's case it seems to be the last core.

Please create and send us the following dumps: - SMART Dump - RAID Dump - Disk Controllers Dump Thank you in advance!

The content of the Apps page, Codecs page and System Files page are only included in the report when you do not submit it to us. So when you click on "Send Report In E-mail" those pages are included. However, when you click on "Send Report To Author", those pages are not included in the report.

Your system seems to have an unknown Nuvoton super I/O (sensor chip). Is there any chance you can get a peek into the chassis and find the Nuvoton chip on the motherboard PCB? It should have markings like NCT67xx (where "xx" is unkonwn to us) or NCT67xxD or such.

CPU Package is the total consumption of the whole CPU package, including the x86 CPU cores ("IA Cores") and -- if available -- the iGPU shaders/cores ("GT Cores") as well.

1) Only the first 4 cores are automatically assigned as temperature slots in the AIDA64 System Stability Test. You can use the Preferences button to change the temperature slot assignments to display the rest of the cores on the Temperature graph as well as among the thermal readings in the Statistics list. 2) TSX is not listed on any processors as part of the Instruction Set list on the AIDA64 CPUID Panel.

I know, it's a complicated issue, since the frame still works well under Windows XP... And probably under Windows Vista as well.

You can use the right-click context menu on the Computer / Sensor page --> Extended Labels to help you understand where one or more of the generic sensor readings (like Temperature #1, Fan #21, etc) comes from.

Are you sure the device cannot switch to Mini Monitor Mode? I'm just asking because when AIDA64 says it cannot find libusb0.dll, it usually means the device is ready (in Mini Monitor Mode), and the issue is on the DLL side. You can then download and install the Samsung SPF LibUSB driver from the following link: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip