Fiery

Thank you! We're working on the resolution.

No, not needed, so you can let it go without it causing any issues or making a difference.

We haven't come across the same issue. If you can, please report it as a false alarm to Eset. BTW, that file is only used under 64-bit Windows Vista installations, so most likely you don't need that file anyway.

Thank you for your feedback. Please submit a report from the About page, and if possible, we will fix the reported issue in the next AIDA64 app update.

Thank you for your feedback. Please submit a report from the About page, and if possible, we will fix the reported issue in the next AIDA64 app update.

Please try the following: 1) Run AIDA64, go to main menu / Tools / Cache And Memory Benchmark 2) Press Start Benchmark button 3) Right-click on the Save button --> Save as XML 4) Attach the .XML file to your post here 5) Then right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Save the results to a file and attach the file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

Make sure to disable (uncheck) the option called SMBus access through ACPI in AIDA64 / main menu / File / Preferences / Stability.

Yes, in that case it's best to increase the TdrDelay value to avoid video driver resets.

What version of AIDA64 are you using?

Thank you, we'll implement a workaround for that issue in the next AIDA64 beta update.

Try to enable Embedded Controller (EC) bank switching in AIDA64 / main menu / File / Preferences / Stability. Let me know if it helps.

Yes, of course, our own Online Store: https://www.aida64.com/online-store

Send me your existing product key in private message, and I'll check it for you.

I've sent you a private message about this.

G2A sells illegal (pirate) product keys for AIDA64. We now actively blocking such illegal keys to push back on criminal activities.

What do you change exactly?

Can you please send us a SensorPanel file that you have issues importing?

It definitely reflects cache/memory subsystem performance much more than raw data crunching performance of the CPU cores on modern multi-core processors. Back in the day when we designed the benchmarks, when CPUs had one or two cores only, it worked as we planned You're right, we will either remove it or replace it at one point in the future. Till then, if you find it useless or too outdated, just ignore it.

The result definitely looks off. Can you please upgrade to the latest AIDA64 beta build and check if it makes a difference? https://www.aida64.com/downloads/latesta64xebeta In case it still looks off, then please check the bandwidth score with default (100MHz) BCLK, and let us know what score do you obtain that way. Also, please measure the bandwidth with 140MHz BCLK but with all E-cores (efficient/small cores) disabled if possible. Thanks, Fiery

In most cases it happens because the video card has a PCIe interface to the host (motherboard) that provides only half the bandwidth that it usually does. So either it uses e.g. PCIe 3.0 connection instead of PCIe 4.0, or PCIe x8 link width instead of PCIe x16.

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

Basically any LCD monitor that appears as a monitor under Windows would work with SensorPanel. That way you have no upper limit in dimensions.

What version+build of AIDA64 do you have installed? What motherboard do you have? (exact model) What's the actual message displayed by AIDA64? Do you have the date+time properly set in Windows?

The issue will be fixed in the next AIDA64 beta update. I will post a message into this topic once the new beta becomes available for download.

Effective clock is only available for VRAM (video memory).