Fiery

Maybe a 5-inch BeadaPanel would fit your requirements? You gotta ask the folks behind BeadaPanel about the market availability of the 5-inch version. AFAIK only the 7-inch model is on market right now, but the smaller one is coming soon.

Throttling percentage means the amount of time the CPU spends while the processing pipeline is stalled. That stalling (a.k.a. throttling) is to prevent the CPU from overheating and suffering permanent damage.

Yes, AIDA64 has an Alerting module that can do that for you. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Alerting to configure it.

What motherboard, CPU and video card(s) do you have? Are you using the latest version of AIDA64, 6.32?

That "62% zoom" only refers to the fact that the LCD preview in AIDA64 Preferences is shown as a 62% scaled-down version of the actual layout, so you shouldn't expect a pixel-to-pixel match with what you get on the actual LCD device. Also in such case don't be afraid of the images displayed slightly distorted on the LCD layout editor due to down-scaling (by the ratio of 62% in your case). Such down-scaling is necessary when there's no room on the PC monitor to display the LCD layout with 100% zoom. E.g. even on a full-HD resolution monitor you wouldn't be able to fit a 1920x1080 (full-HD) layout due to the buttons, menu and other portions of the AIDA64 Preferences window

Please show us a screenshot where the incorrect information is displayed. E.g. the Computer / Overclock page or the main menu / Tools / AIDA64 CPUID panel. As for "sleep state not supported?", what do you mean exactly? Can you see an error about that in AIDA64? Also, what motherboard do you have? Are you using the latest AIDA64 version of 6.32?

We don't manage such a database I'm afraid. AIDA64 v6.32 implements specific sensor support for Z490 motherboards made by ASRock, Asus, EVGA, Gigabyte, MSI and Supermicro. Other motherboards featuring Z490 chipset are supported via the generic sensor chip layout.

LCDsysinfo displays work with the software provided by LCDsysinfo, but the sensor readings has to be fed by a 3rd party software like AIDA64. So in case you'd like to monitor your sensor values, you need both AIDA64 and LCDsysinfo's own software to be installed and running.

What video card model do you have? Yours wasn't made by EVGA I suppose.

1) Do you have an EVGA RTX3090 card? 2) What motherboard do you have? I assume you're using AIDA64 v6.32 (latest version). If not, then please upgrade to it since it's the latest and greatest version

Yes, there's real clock that will match GPU-Z -- and there's effective clock which is 16x of the real clock and match the advertised data rate of GDDR6X memory.

Such issues may occur when the BCLK is measured too low due to virtualization or other trick that affects the CPU running mode and puts AIDA64 into a virtual environment or sandbox. Do you think that could be the case for your system?

We will fix this issue in the next AIDA64 beta update. Till then, try to restart AIDA64 to get the values back to normal. When you have the OSD Panel in justify alignment mode and you turn items on/off, the bug may occur. In which case it gets back to normal when you restart AIDA64 or when you turn the OSD Panel on/off.

It's been fixed in AIDA64 v6.32: https://www.aida64.com/downloads/latesta64xe

The new AIDA64 update introduces optimized benchmarks for AMD Ryzen 5000 Series processors, monitoring of EVGA iCX3 sensor values, and supports the latest AMD and Intel CPU platforms as well as the new graphics and GPGPU computing technologies by both AMD and nVIDIA. AIDA64 for Huawei devices AIDA64 for Android has crossed the 10 million download mark at the Play Store. It is also available now in the Huawei AppGallery, a blooming app store that offers automatic updates and various security features. New features & improvements - AVX2 and FMA accelerated 64-bit benchmarks for AMD Zen 3 based Ryzen 5000 Series processors - EVGA iCX3 sensor support - GPU details for AMD Radeon RX 6000 Series - GPU details for nVIDIA GeForce RTX 3050, GeForce RTX 3060, GeForce RTX 3060 Ti, GeForce RTX 3070 Ti, GeForce RTX 3080 Ti What's new since AIDA64 v6.00 - SHA3-512 cryptographic hash benchmark utilizing AVX, AVX2 and AVX-512 - AVX-512 accelerated benchmarks for Intel “Ice Lake”, “Rocket Lake”, “Tiger Lake” processors - AVX2 and FMA accelerated 64-bit benchmarks for AMD Zen 2 “Matisse” and “Renoir” processors - AVX accelerated 64-bit benchmarks for Zhaoxin ZX-C+, KaiXian KX-5000, KaiXian KX-6000 processors - SSE4 optimized 64-bit benchmarks for Intel "Lakefield" SoC - Further optimized SHA3-512 cryptographic hash benchmark - Art.Lebedev Optimus Popularis, BeadaPanel, El Gato Stream Deck, EVGA Z10 RGB, Matrix Orbital EVE3 LCD display support - SteelSeries Apex 7, Apex 7 TKL, Apex Pro, Apex Pro TKL, Rival 710 OLED OLED display support - Corsair H100i Platinum and H115i Platinum liquid cooler sensor support - NZXT Kraken X53, X63, X73, Z63, Z73 sensor support - Enhanced RGB LED monitoring module - Cooler Master MP750 RGB LED mousepad support - Aqua Computer Octo, Corsair Obsidian 1000D, EVGA iCX2, Farbwerk 360, NZXT GRID+ V3 sensor support - Full support for Hygon C86 “Mukti/Dhyana” CPU - Improved support for 3rd generation AMD Threadripper processors - Improved support for Intel “Comet Lake” and “Ice Lake” CPUs - Improvements for AMD A520, B550, X570 chipset based motherboards - Support for PCI Express 4.0 controllers and devices - Preliminary support for Intel "Alder Lake", “Elkhart Lake”, “Jasper Lake” CPUs - Enhanced support for LGA-1200 motherboards - Advanced support for LSI RAID controllers - NVMe 1.4 support - OpenCL 3.0 support - SMBIOS 3.4.0 support - GPU details for AMD Radeon Pro W5500, Radeon RX 590 GME, Radeon RX 5500, Radeon RX 5600 XT, Radeon RX 5700, Radeon VII Series - GPU details for nVIDIA GeForce GTX 1600, GeForce GTX 1650 Ti, GeForce MX330, GeForce MX350, GeForce MX450, GeForce RTX 2000 Super, GeForce RTX 2060 Series, GeForce RTX 3000 Series - Preliminary support for AMD “Navi” GPUs - Fixed handling of per-core HyperThreading (Intel Comet Lake-S) - Fixed lockup at startup on systems with multiple CPU groups - Retired SHA1 and VP8 benchmarks [ Press Release (English) ] [ Press Release (magyar) ] [ What's new in AIDA64 v6.32 ] [ Download ]

1) For the chipset temperature, make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta 2) As for the partitions, have you checked the Storage / Physical Drives page in AIDA64? Maybe it gives you the insight you're looking for.

It's either a hardware issue or some of the drivers acting up. Does it always shut down immediately regardless of which subtest (e.g. CPU, FPU, etc) or subtests do you have enabled in AIDA64 System Stability Test?

SensorPanel and LCD layouts can be used in (with) AIDA64 only.

Please let us know what motherboard, CPU and video card(s) you've got. Please also post a screenshot of the error message that pops up when the memory/resource error occurs.

Thank you for letting us know about the resolution.

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

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

AIDA64 memory bandwidth benchmarks use automatic calibration in order to find the trick on the actual configuration to squeeze out the highest possible performance from the system memory (and caches too, BTW). It does support both x8 and x16 DRAMs of course. Your question lacks a lot of specifics, so I can only provide a generic answer. When you compare the memory throughput scores across different configurations, make sure to use memory bound applications and benchmarks as a comparison. AFAIK neither Cinebench or 3DMark are memory bound, but much rather CPU bound. If you want to compare the memory bandwidth scores obtained by AIDA64 against another benchmark, you may want to check Sandra -- although it has a memory copy benchmark so you should compare it against AIDA64 Memory Copy benchmark scores and not the AIDA64 Memory Read or Memory Write scores. It's also very useful to track and note down AIDA64 CPU PhotoWorxx scores as well, since that's also a cache and memory bound benchmark. Another interesting benchmark to check out might be y-cruncher. For more specifics, especially if your benchmarks and evaluations affect unrelease or pre-release or Engineering Sample hardware, please contact me directly in email at tamas.miklos AT finalwire.com

Because AIDA64 doesn't have direct support for the display, but it can share the measured data with other software like the one made by LCDsysinfo. Their software then communicate with their own display and do whatever it has to in order to display the data sent by AIDA64.

Notebookok eseteben a legtobbszor nem lehet a ventilator sebesseget (RPM) kiolvasni. De mivel kivetelek mindig vannak, ranezunk a regiszterekre, hatha a Tied pont kivetel lesz. Nyomj kerlek jobb gombot az AIDA64 foablak aljan lathato allapotsoron --> Sensor Debug --> ISA Sensor Dump. Masold be a teljes eredmenyt ide a topicba. Az also allapotsort elkepzelheto, hogy elobb engedelyezned kell: AIDA64 / fomenu / Nezet / Allapotsor. Koszi elore is!