stillwater Posted January 16, 2019 Share Posted January 16, 2019 Hi, I've used Aida64 for the Sensor Panel for many years. But after upgrading my PC*, I've noticed that Aida64 uses a relatively high amount of CPU (often hovering around 5%, sometimes hitting 10+%. Perhaps it always used so much but I've only noticed now. Anyway, the CPU usage seems unrelated to what's actually on the sensor panel: it behaves the same whether it has 0 items on it or 100. Though it does improve if I set transparency to 0%. And it does dip below 1% if the sensor panel is turned off completely by unchecking "show sensor panel" (as opposed to just hidden by setting all items to "hide"). It also seems to be pretty much unaffected by whether the polling rate is 100ms or 2000ms. So I have 2 questions: 1. Are there certain settings I can change in Aida64 that would reduce CPU usage? I only use the sensor panel and logitech g510s lcd panel (I don't even use the main aida64 window). So I'd be happy to disable anything that doesn't relate to those. Could I disable something in the stability section perhaps? 2. Is the 5-10% cpu usage actually a problem if I don't max out my CPU to 100%? I'm a photoshop power-user, which frequently works my CPU and RAM hard, but it usually only maxes out one or two cores (my CPU has 8 physical cores). My understanding is that, in theory at least, if Photoshop maxes out, say, cores 1 and 2, then the CPU will just shift Aida64's workload to core 3, and Photoshop's performance would remain unharmed. Is this how it works in reality? Thanks * Asus Prime z390-a; core i7-9700k; 64gb ram; two gtx980ti in SLI; two m.2 drives; six sata drives Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 17, 2019 Share Posted January 17, 2019 13 hours ago, stillwater said: Hi, I've used Aida64 for the Sensor Panel for many years. But after upgrading my PC*, I've noticed that Aida64 uses a relatively high amount of CPU (often hovering around 5%, sometimes hitting 10+%. Perhaps it always used so much but I've only noticed now. Anyway, the CPU usage seems unrelated to what's actually on the sensor panel: it behaves the same whether it has 0 items on it or 100. Though it does improve if I set transparency to 0%. And it does dip below 1% if the sensor panel is turned off completely by unchecking "show sensor panel" (as opposed to just hidden by setting all items to "hide"). It also seems to be pretty much unaffected by whether the polling rate is 100ms or 2000ms. So I have 2 questions: 1. Are there certain settings I can change in Aida64 that would reduce CPU usage? I only use the sensor panel and logitech g510s lcd panel (I don't even use the main aida64 window). So I'd be happy to disable anything that doesn't relate to those. Could I disable something in the stability section perhaps? 2. Is the 5-10% cpu usage actually a problem if I don't max out my CPU to 100%? I'm a photoshop power-user, which frequently works my CPU and RAM hard, but it usually only maxes out one or two cores (my CPU has 8 physical cores). My understanding is that, in theory at least, if Photoshop maxes out, say, cores 1 and 2, then the CPU will just shift Aida64's workload to core 3, and Photoshop's performance would remain unharmed. Is this how it works in reality? Thanks * Asus Prime z390-a; core i7-9700k; 64gb ram; two gtx980ti in SLI; two m.2 drives; six sata drives 1) It would be best to first check what might cause the high CPU usage. Try to right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. 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 --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Generally speaking, certain Asus motherboards could operate with a very high EC (Embedded Controller) latency that would cause AIDA64 sensor module to load the CPU for several milliseconds. You can check if your motherboard is affected by that anomaly by disabling EC support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. Also note that by disabling EC support you will lose a few sensor readings like CPU OPT fan RPM. 2) It's not really a huge issue, especially if you almost never max out the CPU usage across all cores. If you only load the first 2 or 3 CPU cores using Photoshop, Windows will automatically switch AIDA64 to use one of the other cores to update the sensor readings and the SensorPanel. Quote Link to comment Share on other sites More sharing options...
stillwater Posted January 17, 2019 Author Share Posted January 17, 2019 Thanks for your attention, Fiery. Here's the Sensor ProfilingDump. Looks like GPU and LM78 are the main culprits? ------[ Versions ]------ Program Version : AIDA64 Extreme v5.99.4900 BenchDLL Version: 4.3.793-x64 Windows Version : Microsoft Windows 10 Pro 10.0.17763.253 (64-bit) ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : Asus Prime Z390-A Motherboard Chipset : Intel Cannon Point Z390, Intel Coffee Lake-S DMI MB Manufacturer : ASUSTeK COMPUTER INC. DMI MB Product : PRIME Z390-A DMI MB Version : Rev 1.xx DMI MB Serial : 181037805502187 DMI SYS Manufacturer: System manufacturer DMI SYS Product : System Product Name DMI SYS Version : System Version DMI SYS Serial : System Serial Number DMI BIOS Version : 0702 ------[ Video Adapters ]------ MSI GTX 980 Ti (MS-V323) [10DE-17C8 / 1462-3232] MSI GTX 980 Ti (MS-V323) [10DE-17C8 / 1462-3232] ------[ Video Driver ]------ nvapi.dll: 25.21.14.1735 - nVIDIA ForceWare 417.35 C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumd.dll ------[ Sensor Profiling (Init) ]------ SensorInfo : 81.204 ms GPUSensorInfo : 15.719 ms GPU01 / NV Diode : 0.004 ms GPU01 / NV Fan PWM: 0.655 ms GPU02 / NV Diode : 0.004 ms GPU02 / NV Fan PWM: 0.563 ms HDD : 0.135 ms SPD : 0.732 ms AMB : 0.001 ms Asus EPU2 : 0.000 ms Asus EPU1 : 0.000 ms nVIDIA SPP : 0.000 ms nVIDIA MCP : 0.000 ms Intel GMCH : 0.000 ms Intel PCH : 0.000 ms Intel SNB : 0.026 ms Zambezi : 0.000 ms Kaveri : 0.000 ms Zen : 0.000 ms AMD SVI2 : 0.000 ms MTC0303 : 0.000 ms Smart Battery : 0.000 ms HID UPS : 0.000 ms TVALZ : 0.000 ms T-Balancer : 0.000 ms Asetek LC : 0.000 ms Kraken X42 : 0.000 ms Riing+ : 0.000 ms LM78 : 7.808 ms TT DPS : 0.000 ms Digifanless : 0.000 ms Corsair RMi : 0.000 ms Corsair AXi : 0.000 ms Odin : 0.000 ms Aquaero : 0.000 ms ------[ Sensor Profiling (Last) ]------ SensorInfo : 81.756 ms GPUSensorInfo : 16.498 ms GPU01 / NV Diode : 0.004 ms GPU01 / NV Fan PWM: 0.693 ms GPU02 / NV Diode : 0.004 ms GPU02 / NV Fan PWM: 0.812 ms HDD : 0.129 ms SPD : 0.716 ms AMB : 0.001 ms Asus EPU2 : 0.000 ms Asus EPU1 : 0.000 ms nVIDIA SPP : 0.000 ms nVIDIA MCP : 0.000 ms Intel GMCH : 0.000 ms Intel PCH : 0.000 ms Intel SNB : 0.025 ms Zambezi : 0.000 ms Kaveri : 0.000 ms Zen : 0.001 ms AMD SVI2 : 0.000 ms MTC0303 : 0.000 ms Smart Battery : 0.000 ms HID UPS : 0.000 ms TVALZ : 0.000 ms T-Balancer : 0.000 ms Asetek LC : 0.000 ms Kraken X42 : 0.000 ms Riing+ : 0.000 ms LM78 : 7.987 ms TT DPS : 0.000 ms Digifanless : 0.000 ms Corsair RMi : 0.000 ms Corsair AXi : 0.000 ms Odin : 0.000 ms Aquaero : 0.000 ms Quote Link to comment Share on other sites More sharing options...
stillwater Posted January 17, 2019 Author Share Posted January 17, 2019 Embedded Controller dump: ------[ Versions ]------ Program Version : AIDA64 Extreme v5.99.4900 BenchDLL Version: 4.3.793-x64 Windows Version : Microsoft Windows 10 Pro 10.0.17763.253 (64-bit) ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : Asus Prime Z390-A Motherboard Chipset : Intel Cannon Point Z390, Intel Coffee Lake-S DMI MB Manufacturer : ASUSTeK COMPUTER INC. DMI MB Product : PRIME Z390-A DMI MB Version : Rev 1.xx DMI MB Serial : 181037805502187 DMI SYS Manufacturer: System manufacturer DMI SYS Product : System Product Name DMI SYS Version : System Version DMI SYS Serial : System Serial Number DMI BIOS Version : 0702 ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #0 ]------ 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 46 29 20 D8 28 00 ..........F) .(. 0040 7C 00 00 0C 00 00 00 00 00 00 00 00 00 00 00 00 |............... 0050 00 00 00 00 00 0A 0A 00 00 00 00 00 00 00 00 00 ................ 0060 80 80 80 22 20 00 00 00 07 00 00 00 00 00 00 00 ..." ........... 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 02 7F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ............... 00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00D0 40 00 10 41 00 00 00 00 33 33 44 43 00 00 04 01 @..A....33DC.... 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 CC 0C 08 0F 00 00 00 00 00 00 00 00 DD 08 00 ................ ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #1 ]------ 0000 0A 15 1B 1E 00 00 00 00 47 D8 20 1D 00 00 00 00 ........G. ..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 02 08 62 78 03 18 1E 1F ..........bx.... 0040 03 20 02 A8 00 06 00 00 00 3F 04 E7 00 70 00 17 . .......?...p.. 0050 00 42 00 00 00 00 00 00 01 29 25 ED 01 08 00 00 .B.......)%..... 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 00 00 00 00 00 01 54 00 78 00 D2 01 54 00 78 .......T.x...T.x 00C0 00 00 01 90 00 C8 00 F0 01 90 00 C8 00 F0 00 00 ................ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 0F 00 00 00 00 00 00 00 EC 00 00 00 00 00 00 01 ................ ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #2 ]------ 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 ................ 0050 09 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................ 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 ................ 00C0 00 15 00 43 E8 02 00 00 00 00 00 00 00 00 00 00 ...C............ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 ................ ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #3 ]------ 0000 03 60 02 CD 02 A7 02 8C 02 84 01 52 01 F8 FF FF .`.........R.... 0010 01 47 03 FD 02 86 02 87 FF FF FF FF FF FF 02 89 .G.............. 0020 02 89 02 8A 02 87 02 86 00 98 00 A8 00 98 00 60 ...............` 0030 00 C0 00 00 00 A8 00 00 00 00 00 00 01 20 01 20 ............. . 0040 01 30 00 D0 01 40 01 FF 01 80 01 FF 01 FF 01 FF .0...@.......... 0050 00 90 00 70 00 30 00 50 00 A0 00 00 00 70 00 00 ...p.0.P.....p.. 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070 00 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 01 FF 01 FF 01 FF 01 FF 01 FF 01 FF ................ 0090 01 FF 01 FF 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .p.............. 00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 ................ ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #4 ]------ 0000 03 2A 02 CC 02 A0 02 8E 02 85 01 52 01 E1 FF FF .*.........R.... 0010 01 47 03 FD 02 BA 02 97 FF FF FF FF FF FF 02 88 .G.............. 0020 02 88 02 88 02 88 02 86 00 98 00 A8 00 98 00 60 ...............` 0030 00 C0 00 00 00 A8 00 00 00 00 00 00 01 20 01 20 ............. . 0040 01 30 00 0C 01 40 01 FF 01 80 01 FF 01 FF 01 FF .0...@.......... 0050 00 90 00 70 00 30 00 50 00 A0 00 00 00 70 00 00 ...p.0.P.....p.. 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070 00 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 01 FF 01 FF 01 FF 01 FF 01 FF 01 FF ................ 0090 01 FF 01 FF 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .p.............. 00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 ................ ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #5 ]------ 0000 03 2B 02 DE 02 A7 02 8D 02 84 01 52 01 F7 FF FF .+.........R.... 0010 01 47 03 FD 02 4A 02 96 FF FF FF FF FF FF 02 8B .G...J.......... 0020 02 8A 02 88 02 87 02 87 00 98 00 A8 00 98 00 60 ...............` 0030 00 C0 00 00 00 A8 00 00 00 00 00 00 01 20 01 20 ............. . 0040 01 30 00 0C 01 40 01 FF 01 80 01 FF 01 FF 01 FF .0...@.......... 0050 00 90 00 70 00 30 00 50 00 A0 00 00 00 70 00 00 ...p.0.P.....p.. 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070 00 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 01 FF 01 FF 01 FF 01 FF 01 FF 01 FF ................ 0090 01 FF 01 FF 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .p.............. 00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 ................ ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #6 ]------ 0000 03 5F 02 CC 02 A0 02 8C 02 86 01 52 01 F8 FF FF ._.........R.... 0010 01 47 03 FD 02 B8 02 96 FF FF FF FF FF FF 02 8F .G.............. 0020 02 8B 02 88 02 88 02 86 00 98 00 A8 00 98 00 60 ...............` 0030 00 C0 00 00 00 A8 00 00 00 00 00 00 01 20 01 20 ............. . 0040 01 30 00 0C 01 40 01 FF 01 80 01 FF 01 FF 01 FF .0...@.......... 0050 00 90 00 70 00 30 00 50 00 A0 00 00 00 70 00 00 ...p.0.P.....p.. 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070 00 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 01 FF 01 FF 01 FF 01 FF 01 FF 01 FF ................ 0090 01 FF 01 FF 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .p.............. 00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 ................ ------[ Embedded Controller at 0066/0062 via Port I/O / Bank #7 ]------ 0000 03 61 02 DF 02 A8 02 8C 02 86 01 52 01 F7 FF FF .a.........R.... 0010 01 47 03 FD 02 86 02 86 FF FF FF FF FF FF 02 8B .G.............. 0020 02 8B 02 89 02 87 02 86 00 98 00 A8 00 98 00 60 ...............` 0030 00 C0 00 00 00 A8 00 00 00 00 00 00 01 20 01 20 ............. . 0040 01 30 00 0C 01 40 01 FF 01 80 01 FF 01 FF 01 FF .0...@.......... 0050 00 90 00 70 00 30 00 50 00 A0 00 00 00 70 00 00 ...p.0.P.....p.. 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070 00 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 01 FF 01 FF 01 FF 01 FF 01 FF 01 FF ................ 0090 01 FF 01 FF 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .p.............. 00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 ................ Time #1 = 5922 msec Time #3 = 0.281 / 0.276 / 0.285 / 0.252 / 407.217 / 0.256 / 0.248 / 0.278 / 0.249 / 408.921 / 0.255 / 0.268 / 0.293 / 0.263 / 413.320 / 0.267 msec Quote Link to comment Share on other sites More sharing options...
stillwater Posted January 17, 2019 Author Share Posted January 17, 2019 16 hours ago, Fiery said: Asus motherboards could operate with a very high EC (Embedded Controller) latency that would cause AIDA64 sensor module to load the CPU for several milliseconds. You can check if your motherboard is affected by that anomaly by disabling EC support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. Also note that by disabling EC support you will lose a few sensor readings like CPU OPT fan RPM. Yep, that seems to have done the trick! As soon as I disable that option (even before restarting Aida), the CPU usage goes way down. It now hovers at <1% and very occasionally peaks at ~1.5%. When I rerun the Sensor Profiling Dump, GPUSensorInfo is still high, but LM78 is now about 50 times lower (0.148 instead of 7.9). My sensor panel did have CPU Opt RPM on it, which has now stopped working as you said (it's no big deal). I can't see any other changes in the sensor panel. Can I assume that, apart from CPU Opt RPM, disabling EC support will have negligible impact for me in AIDA64? Also, is this high EC latency something that I should be concerned about? Is it likely to impact my general PC performance? Is it a sign of a faulty motherboard? Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 18, 2019 Share Posted January 18, 2019 16 hours ago, stillwater said: Yep, that seems to have done the trick! As soon as I disable that option (even before restarting Aida), the CPU usage goes way down. It now hovers at <1% and very occasionally peaks at ~1.5%. When I rerun the Sensor Profiling Dump, GPUSensorInfo is still high, but LM78 is now about 50 times lower (0.148 instead of 7.9). My sensor panel did have CPU Opt RPM on it, which has now stopped working as you said (it's no big deal). I can't see any other changes in the sensor panel. Can I assume that, apart from CPU Opt RPM, disabling EC support will have negligible impact for me in AIDA64? Also, is this high EC latency something that I should be concerned about? Is it likely to impact my general PC performance? Is it a sign of a faulty motherboard? Apart from losing a few sensor readings, you don't lose any functionality in AIDA64 by disabling EC support. EC latency is only a problem if you're running a software that polls EC registers. And those are typically hardware monitoring tools like HWiNFO, HWMonitor, SIV, SpeedFan, etc. Other kind of software would never go as deep as to talk to the EC, since they have no information to gather from the EC at all. Quote Link to comment Share on other sites More sharing options...
willem Posted December 16, 2019 Share Posted December 16, 2019 (edited) FYI: Asus Prime Z390-A/H10 + Intel i9-9900KS Same problem, same solution. Also losing CPU OPT reading. No big deal. Edited December 16, 2019 by willem Typo Quote Link to comment Share on other sites More sharing options...
Dridd Posted October 22, 2021 Share Posted October 22, 2021 Since I found this topic through a Google search for AIDA high CPU usage, I thought I would tack on additional info for future people with a similar problem. In my case, AIDA64 was constantly using about 1.5% CPU (hard to do, since this is a 32 core, 64 thread system). This after slowing down the update frequency quite a bit. Changing the EC support did not change anything at all, but I then started experimenting with the other stability selections. One by one, quick to do since the running AIDA64 reacts immediately when you click Apply after changing the selections. In my case, the culprit was the selection for RAID SMART Support. 30+ drives, a good portion of them controlled by an Adaptec RAID card. Apparently asking them all for SMART info every few seconds (which my sensor panel does not use anyway) is not a good idea. RAID Member enumeration, and Adaptec Card support turned on/off made no/little difference, but RAID SMART support apparently takes a lot out of it. After turning off SMART support, AIDA64 consistently runs at only 0.1-0.2%. Now I can raise the update frequency again. Hurray.. Not necessary anyway, since the system runs HDSentinel to keep track of the drives over time. Don't need that support in AIDA64. So, if EC Support turned off does not help, try the others. What is hogging the CPU might be different for each installation. In reality there is no need to have sensor support turned on for something you are not planning to want to use anyway. Quote Link to comment Share on other sites More sharing options...
Gnusmas Posted April 8 Share Posted April 8 On 1/18/2019 at 5:43 PM, Fiery said: Apart from losing a few sensor readings, you don't lose any functionality in AIDA64 by disabling EC support. EC latency is only a problem if you're running a software that polls EC registers. And those are typically hardware monitoring tools like HWiNFO, HWMonitor, SIV, SpeedFan, etc. Other kind of software would never go as deep as to talk to the EC, since they have no information to gather from the EC at all. Hello, sorry to revive and old thread but i had the same problem, CPU usage was 4%-5%, after disabling EC CPU usage went down between 0.1% and 06%, thats good but i want to ask something as i didnt understood what you meant in the post i quoted. Will my HWiNFO and HWMonitor apps be affected because disabling that option in Aida64? Is that option just for Aida64 or something globally on my PC? Thank you for your information! Quote Link to comment Share on other sites More sharing options...
Agrias Posted August 1 Share Posted August 1 welp, sorry to revive this thread, I've looked around in stability options and tried turning things on and off and see what might've caused it and I got nothing. CPU is bouncing between 2-8% usage, which is pretty significant and affecting my idle temps. ------[ Versions ]------ Program Version : AIDA64 Extreme v7.35.7000 LLKD Version : 2 BenchDLL Version: 4.6.900.8-x64 Windows Version : Microsoft Windows 11 Pro 10.0.22631.3958 (64-bit) GetProductInfo : 0x00000030 ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : MSI MAG X670E Tomahawk WiFi (MS-7E12) Motherboard Chipset : AMD X670E, AMD K19.6 FCH, AMD K19.6 IMC DMI MB Manufacturer : Micro-Star International Co., Ltd. DMI MB Product : MAG X670E TOMAHAWK WIFI (MS-7E12) DMI MB Version : 1.0 DMI MB Serial : 07E1211_N31E484210 DMI SYS Manufacturer: Micro-Star International Co., Ltd. DMI SYS Product : MS-7E12 DMI SYS Version : 1.0 DMI SYS Serial : To be filled by O.E.M. DMI BIOS Version : 1.E2 ------[ Video Adapters ]------ Asus TUF-RX7900XTX-O24G-Gaming [1002-744C / 1043-0506 / Rev C8] ------[ Video Driver ]------ atiadlxx: 32.0.11029.1008 - AMD Adrenalin 24.7.1 WHQL amdxc64|||amdxc32|||amdxn64|||amdxx64|||amdxn32|||amdxx32|||atiumdva|||atiumd6a ------[ Sensor Profiling (Init) ]------ SensorInfo : 367.344 ms GPUSensorInfo : 0.858 ms GPU01 / AMD PMLOG: 0.855 ms HDD : 0.066 ms SPD : 0.002 ms AMB : 0.001 ms DIMMTS : 1.728 ms Asus EPU2 : 0.000 ms Asus EPU1 : 0.000 ms nVIDIA SPP : 0.000 ms nVIDIA MCP : 0.000 ms Intel GMCH : 0.000 ms Bixby : 0.000 ms PROM21 : 0.018 ms Intel PCH : 0.000 ms Intel SNB : 0.001 ms Zambezi : 0.000 ms Kaveri : 0.000 ms Zen : 0.004 ms AMD SVI2 : 0.000 ms MTC0303 : 0.000 ms Smart Battery : 0.000 ms HID UPS : 0.000 ms TVALZ : 0.000 ms Asetek LC : 0.000 ms Kraken X-2 : 0.000 ms Razer PWM : 0.000 ms Riing+ : 0.000 ms Hydro Pt : 0.000 ms LM78 : 353.206 ms TT DPS : 0.000 ms Digifanless : 0.000 ms Corsair RMi : 0.000 ms Corsair AXi : 0.000 ms Odin : 0.000 ms Aorus PSU : 0.000 ms MSI Ai PSU : 0.000 ms Aquaero : 0.000 ms ------[ Sensor Profiling (Last) ]------ SensorInfo : 507.481 ms GPUSensorInfo : 1.124 ms GPU01 / AMD PMLOG: 1.110 ms HDD : 0.086 ms SPD : 0.002 ms AMB : 0.001 ms DIMMTS : 1.150 ms Asus EPU2 : 0.000 ms Asus EPU1 : 0.000 ms nVIDIA SPP : 0.000 ms nVIDIA MCP : 0.000 ms Intel GMCH : 0.000 ms Bixby : 0.000 ms PROM21 : 0.016 ms Intel PCH : 0.000 ms Intel SNB : 0.001 ms Zambezi : 0.000 ms Kaveri : 0.000 ms Zen : 0.003 ms AMD SVI2 : 0.000 ms MTC0303 : 0.000 ms Smart Battery : 0.000 ms HID UPS : 0.001 ms TVALZ : 0.000 ms Asetek LC : 0.000 ms Kraken X-2 : 0.000 ms Razer PWM : 0.000 ms Riing+ : 0.000 ms Hydro Pt : 0.000 ms LM78 : 493.497 ms TT DPS : 0.000 ms Digifanless : 0.000 ms Corsair RMi : 0.000 ms Corsair AXi : 0.000 ms Odin : 0.000 ms Aorus PSU : 0.000 ms MSI Ai PSU : 0.000 ms Aquaero : 0.000 ms Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 4 Share Posted August 4 On 8/1/2024 at 2:07 PM, Agrias said: welp, sorry to revive this thread, I've looked around in stability options and tried turning things on and off and see what might've caused it and I got nothing. CPU is bouncing between 2-8% usage, which is pretty significant and affecting my idle temps. I suppose the slow sensor polling is caused by slow access to the MSI MCU where some of the sensor readings (VDD Misc, +1.8V and Chipset voltages) are polled from. Quote Link to comment Share on other sites More sharing options...
Agrias Posted September 19 Share Posted September 19 On 8/4/2024 at 9:29 AM, Fiery said: I suppose the slow sensor polling is caused by slow access to the MSI MCU where some of the sensor readings (VDD Misc, +1.8V and Chipset voltages) are polled from. I was without my computer for a while and came back to an update. Don't know what you did, but CPU usage seems fixed. Thank you! Quote Link to comment Share on other sites More sharing options...
Fiery Posted September 19 Share Posted September 19 30 minutes ago, Agrias said: I was without my computer for a while and came back to an update. Don't know what you did, but CPU usage seems fixed. Thank you! We haven't done anything actually So this could have been a Windows related issue. Quote Link to comment Share on other sites More sharing options...
Agrias Posted September 19 Share Posted September 19 2 hours ago, Fiery said: We haven't done anything actually So this could have been a Windows related issue. actually not at all surprised that it was. windows has been less than consistent for a while now... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.