All Activity

Fantastic idea! Thanks for the update and the notification. Cheers!

Font Helvetica Compressed Res 320x480 TUF 320x480.axlcd

I had the same problam. Try to found program that can use this disk. I had a program OpenHardwareMonitor that monitoring all devices on PC. After I off it, test started.

Actually both happens in the same time. First the clock is reduced, and in case the overheating situation persists, the pipeline gets stalled.

Your video driver doesn't expose the necessary interface that AIDA64 would require to interface with your video card. In most cases it's because the video driver needs to be reinstalled.

Intel says that when thermal throttling happens, clock speed of the CPU decreases. Is it the same as stalling CPU execution pipeline as you said?

------[ Versions ]------ Program Version : AIDA64 Extreme v7.50.7200 LLKD Version : 2 BenchDLL Version: 4.7.911.8-x64 Windows Version : Microsoft Windows 10 Home 10.0.19045.5371 (64-bit) GetProductInfo : 0x00000065 ------[ Video Adapters ]------ PowerColor RX 6800 XT Red Devil [1002-73BF / 148C-2406 / Rev C1] ------[ Video Driver ]------ atiadlxx: 32.0.12019.1028 - AMD Adrenalin 24.10.1 WHQL amdxc64|||amdxc32|||amdxn64|||amdxx64|||amdxn32|||amdxx32|||atiumdva|||atiumd6a ------[ ATI GPU #1 @ mem FCC00000 ]------ Video Adapter = PowerColor RX 6800 XT Red Devil GPU Code Name = Navi 21 XT PCI Device = 1002-73BF / 148C-2406 [Rev C1] GPU Clock = 0 MHz Memory Clock = 0 MHz GPU Base Clock = 27000 kHz Memory Base Clock = 30720 kHz ati-$034BC = 01005800 ati-$0378C = 00003FF0 ati-$098F0 = 00000001 ati-$098F4 = 00000001 ati-$098F8 = 00000444 ati-$098FC = 00000000 ati-$09B7C = 00000000 ati-$30800 = 00000000 ati-$50100 = 80000106 ati-$50200 = FFFFFFFF ati-$50300 = FFFFFFFF ati-$50400 = FFFFFFFF ati-$50500 = FFFFFFFF ati-$52100 = FFFFFFFF ati-$52200 = FFFFFFFF ati-$54100 = FFFFFFFF ati-$54200 = FFFFFFFF ati-$56100 = FFFFFFFF ati-$56200 = FFFFFFFF ati-$59954 = 00000000 ati-$59958 = 00000000 ati-$5995C = 00000000 ati-$59960 = 00000000 ati-$59968 = 00000000 ati-$59988 = 311827D2 ati-$5998C = 00000000 ati-$59990 = 00000000 ati-$59994 = 00000000 ati-$59998 = 00000000 ati-$5999C = 01813300 ati-$599A0 = 96091A7D ati-$599A4 = 51FF0C30 ati-$599A8 = 00008001 ati-$599AC = 00000000 ati-$599B0 = 00000000 ati-$599B4 = 0000642C ati-$599B8 = 961E1F7D ati-$599BC = 02BF0228 ati-$599C0 = 00008005 ati-$599C4 = 00000000 ati-$599C8 = 0000FA00 ati-$599CC = 00000000 ati-$599D0 = 00000000 ati-$599D4 = 00000060 ati-$599D8 = 00000348 ati-$599DC = 00000016 ati-$599E0 = 00000318 ati-$599E4 = 00000000 ati-$599E8 = 00000000 ati-$599EC = 00000000 ati-$5A00C = 0160001E ati-$5A010 = 016F0001 ati-$5A014 = 0168000E ati-$5A04C = 00000000 ati-$5A050 = 6F000000 ati-$5A054 = 68000000 ati-$5A078 = 80000002 ati-$5B084 = 00000000 ati-$5B088 = 40840000 ati-$5B08C = 00000009 ati-$5B0A0 = 64000000 ati-$5B0A4 = 00080100 ati-$5B0A8 = 00030000 ati-$5B0AC = 00000000 ati-$5B0B0 = 00000000 ati-$5B0B4 = 00000000 ati-$5B0B8 = 00000000 ati-$5B0BC = 00000000 ------[ ATIDriver Calls ]------ ATIDriver Performance Switching: Not Supported ATIDriver MultiVPU: Not Supported

There are multiple ways/methods to measure GPU utilization. Most likely Task Manager uses a different method like Direct3D based measurement while AIDA64 measures GPU utilization using direct AMD or nVIDIA video driver calls.

Hey all, I'm currently using a SensorPanel via Aida64, and as you can see here on the panel, my GPU Utilization is 26%, yet the Performance tab on Task Manager is reporting 4%. Quite a big difference, and the reason for my post is that there is always such a big disparity between the 2 GPU readings. Screenshot: https://imgur.com/a/oMeVBDh My sensor panel is currently displaying the GPU1 Utilization datapoint. There are other options for GPU1 (GPU1 MC Utilization, VE Utilization & BI Utilization) but they are also - and somewhat expected - not in line with what Task Manager is showing, but did test them to see if they matched. So, my question is... Which data point are you using to reflect an accurate (or acceptable) read here?; and\or is there currently a known issue with the GPU readings with AIDA64? I'm also willing to play devil's advocate to my own question and acknowledge the fact that Task Manager itself could be wrong, but again... just curious what people do for an accurate (or acceptable) read for GPU util here with Aida64. Thank you. To add: Here is a link to the sensor panel I am using: https://moderno.freire.ca/bianco/

Here are a few https://forums.aida64.com/search/?q="320x480"&quick=1&type=forums_topic&item=13296

In AIDA64 please press Ctrl+D --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Thank you for your feedback!

Thank you for your help in diagnosing this issue. The issue occurs when you use resizing on your image but the desired dimensions of the image matches the actual dimensions of your image, and so there's no actual need to resize it. So in your particular case you use a PNG file with 515x1920 pixels resolution, and you have a resize setting to 515x1920 configured. Once you disable resizing, the SensorPanel will start working for you again. In the next AIDA64 beta update we will implement a proper bug fix for this issue of course.

Works like a charm thank you for the quick fix!

So, I'm having issues with the sensor panel not showing an option for the GPU clock or temp to be displayed, it seems like they just aren't available to be displayed. I've updated my GPU drivers and Aida64 to the most current version but they are still not appearing.

In the latest AIDA64 beta update we've added Ctrl+M keyboard shortcut on the SensorPanel to let you open the SensorPanel Manager without using the right-click context menu. https://www.aida64.com/downloads/latesta64xebeta

In the latest AIDA64 beta update we've added Ctrl+M keyboard shortcut on the SensorPanel to let you open the SensorPanel Manager without using the right-click context menu. https://www.aida64.com/downloads/latesta64xebeta

We've fixed the issue in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

We've implemented support for HX1200i 2023 PSU in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Yes, you can use my explanation of the issue.

Thank you so much. Actually, I asked this from chatgpt and it gave me the same answer but I thought it was wrong😊 Can you please give me an authoritative reference to the definition ofthe percentage of throttling?

They came back and informed us that the project was put on hold. I suppose they have to focus on other matters that are more pressing than dealing with AIDA64

No, 1% throttling means that 1% of the time the CPU execution pipeline gets stalled due to overheating. So in a period of one second (which equals to 1000 milliseconds) the CPU only operated for 990 milliseconds and stood idle for 10 milliseconds.

No, it won't damage your CPU, you're safe.

I'm not quite sure the issue is with the motherboard. As long as it's consistently the same memory module (the 3rd one out of four), it looks like more of an issue with the SPD chip that's on that single memory module that fails to switch the SPD bank.