Fiery

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!

Your particular video card most likely requires additional tricks over regular RTX 3080 cards to make all fans to be measured. First of all, 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. Then please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. 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 --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

You can download other users' SensorPanel layout files in the following forum topic here:

Thank you for your suggestion, we'll look those APIs up and do some research on various Android devices about them.

Thank you for your feedback. It's actually absolutely normal. On many 4K devices and 4K displays, Android itself uses 1080p resolution for apps, and will only switch up to the full 4K resolution mode when you're watching a movie or looking at photos.

That's the LCDsysinfo for GOverlay device that is not supported by AIDA64 (as stated above).

Stunning!

I apologize for not being able to resolve this issue for you to date. I'll do my best to take care of you from now on. Please let me know at which page do you have AIDA64 open at where you experience that issue. Or whether you get this when you have SensorPanel, LCD or OSD Panel activated. If you've already provided a certain amount of such details to our Tech Support, please refer to your ticket number and I'll look it up.

That's quite odd then. Well... I suppose it would be best to consult overclocking enthusiasts on XtremeSystems or other similar forums about your liquid cooler setup and whether it's normal to have such high thermals with your particular setup.

AIDA64 currently does not support NZXT Smart Device v2. Do you know where can it be purchased?

I've sent you a private message about this.

The issue must be one of the Catalyst video driver interfaces that we started using between v5.99 and v6.00 at one point. Please let me know the operating system you use (and whether it's 32-bit or 64-bit OS) and we'll build a similar configuration and check the Catalyst 12.4 + HD4670 combo to find out what exact video driver call we should avoid there.

Are you using PNG or JPEG images? Are there any particular pecularity about those images? Maybe they're too large files or have special embedded data in them?

What about the other CPU related temperatures like CPU Package, CPU GT Cores, CPU IA Cores? Do all of them reflect a high temperature? Please note that laptops tend to work at much higher CPU temperatures as desktop computers, so it's not uncommon to see 70+ Celsius for laptop CPUs. I don't think you have anything to worry about. As for the "CPU" temperature vs. other thermal readings: there's a chance that in your case the laptop provides a CPU thermal reading that is more the temperature of a system component (like motherboard) than the actual thermal state of the CPU. With laptops the ACPI interface that we use to measure CPU temperature can be dodgy sometimes, so it's best to focus on the other CPU temperatures that the CPU itself measures using its on-die thermal sensing logic. Those direct CPU temperatures are the core temperatures, CPU Package, CPU GT Cores, and CPU IA Cores.

If it's possible, please send us your AIDA64.INI file in order to let us try to replicate the issue by having the same OSD configuration as yours. If you cannot attach it to a post here or you would rather send the file in email to us, please let me know in private message.

Some portion of that system load is due to Odospace. Try to turn it off and as aszc suggested, check RemoteSensor instead. Let me know if it helps to put the CPU load down considerably.

As far as we know, RTSS support is properly implemented on our end. So in case RTSS fails to provide the FPS values using the standardized method, then I'd try contacting RTSS author to find out what could be wrong on his end.