Fiery

GT Cores power measurement is only available when your CPU has an active iGPU. DRAM power measurement is only available for certain Intel processors too. We cannot add those just like that when the measurements are not available. Uncore power is calculated and shown even when GT Cores or DRAM power cannot be measured.

It's only a guess.

You can do that, but first you need to enable Enable CPU throttling measurement in AIDA64 / main menu / File / Preferences / Hardware Monitoring.

I'm afraid we still cannot reproduce the issue and so we have no way to fix it up.

Thank you! Can you please try the ATI SMBus Dump again, but this time make a photo that would show the bottom status bar of AIDA64 window as well? Where it says "Trying ATI I2C Device GPU #1 / B..."

In /SAFE mode AIDA64 will not enumerate PCI devices, SMBus devices and sensors using low-level hardware access. In /SAFEST mode AIDA64 will not load its kernel driver and not read SMART information from HDDs and SSDs. It's the safest way since then AIDA64 will work like any other user-mode software. Only you can decide whether the consequence of using those parameters (ie. the lack of information that will be missing from the reports) is fine with you, or you'd rather let AIDA64 use its full detection capabilities and interrogate hardware more thoroughly by omitting to use of /SAFE and/or /SAFEST.

I'm not sure, since we don't deal with such matters. Probably someone at forums like XtremeSystems could help you about that.

It is called Huawei Mobile Services. We haven't invented or made up the term from HMS. And why are you so upset about detecting an optional Android component in an app?

That's our conclusion based on the methodology we need to use to measure those two thermal readings (PCH and PCH Diode).

It's not easy to guess, but in such cases that's the best we can do. I'd try to borrow a PSU from a friend and try it with that. Although these times that's a tall order...

I don't think such a flag ("GPU is throttling at this moment") exists in GPUs.

AIDA64 does that, but in many cases it would be a negative value due to the pecularities of the power measurement logic of your CPU. It's because the CPU can measure the following power values: CPU Package, IA Cores, GT Cores, DRAM. Uncore power however can be calculated by substracting the last 3 values from the first one. And due to the pecularities of the power measurement logic, the last 3 could be higher than the overall power draw of the package, leaving no room to calculate a meaningful uncore power value.

On your motherboard "PCH" temperature is measured by the onboard sensor chip, and so it's not a direct reading coming from the PCH. While "PCH Diode" is measured using the internal registers of the PCH, and it should represent the most accurate thermal measurement for the PCH.

What processor and motherboard do you have?

Does AIDA64 load its kernel drivers when you run it using the SYSTEM account? Do you use the /SAFE or /SAFEST command-line options?

Version 9.02.65.

I suppose it's because AIDA64 has no access to its kernel driver or has no administrator privileges that would be required to load its kernel driver. Check if you have all AIDA64 files in the AIDA64 folder, and restart Windows to make sure the Windows driver stack gets re-initialized as well.

Thank you! Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI 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 --> ATI SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

I used Logitech Gaming Software. Quite frankly, I never even tried G Hub.

Well... yes Close AIDA64, start Registry Editor (REGEDIT.EXE), navigate to: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 And alter the following values to modify the SensorPanel placement on the Windows Desktop: SensorPanelPosX SensorPanelPosY However, what I meant to suggest is to modify the SensorPanel monitor position in Windows Settings first rather than to fiddle with the SensorPanel position itself.

We've checked it with an iPad 2 and it works fine for us. In the Arx Control app (on the iPad) you need to swipe up on the bottom of the screen (where a tiny "up" arrow or upside-down "v" is shown) to get to the list of applets. In that list you should be able to find AIDA64.

1) Are you running the latest version of AIDA64, v6.20? 2) Do you have the latest drivers installed for your video card? 3) Does AIDA64 freeze when you go to the Computer / Sensor page? 4) Does AIDA64 freeze when you go to the Display / GPU page?

You can only change that in case the manufacturer of your device updates the firmware with an Android platform that has a 64-bit kernel.

Thank you for your feedback!

Date and time formatting conforms to the current locale/region settings of Windows.