rick11

Wouldn´t it be a solution to add an offset possibility for cpu-utilization in settings/corrections?

This fix to set roundedFSB=1 in AIDA64.INI seems not to work anymore in current versions. edit: Issue disappeared with 7.40

I appreciate his work very much for years and love the hardware panel, sadly there are only two options for cpu values, that doesn´t work for me: 1. without fix AIDA64 shows constantly 0 in idle, whereas taskmanager shows 3-4 % 2. with fix AIDA64 shows values in idele that are twice that high ~ 7 %

@Fiery Is there no way to implement it so that the CPU load values are displayed exactly in sync with the Windows 11 Task Manager values, like HW-Monitor or HW-Info do?

Did some further testing and the actual versions of HWInfo as well as HWMonitor get the job correctly done in idle too.

Hi, for a long time and even with latest version 7.35 CPU load value of my 8700K on idle is compared to win11 taskmanager is 1. approx 4 times higher compared to task manager with activated stability/ win11 CPU util. measurement wokaround 1. approx 4 times lower compared to task manager with deactivated stability/ win11 CPU util. measurement wokaround will there ever be a working fix or can´t this issue be solved?

The license expires 12.19.2025, so I shoul be fine. Since Sunday no further crashes. I will try v7.00 after next time I see a blue screen closing AIDA64. Otherwise excellent work, I enjoy every day 👍 Thank you!

Good morning Fiery, do I need a liscense upgrade from AIDA v.6.32.5600 to v.7.00?

Hello, today I got 2 bluescreens with Win 11 build 22631.3155 exactly in the moment when I was closing Aida64 v.6.32.5600. I attached the two minidumps related to the crashes. BugCheck String: PAGE_FAULT_IN_NONPAGED_AREA Caused by Driver: ntoskrnl.exe Caused by Adress: ntoskrnl.exe+416c30 021824-5156-01.dmp 021824-5406-01.dmp

Maybe I was wrong and it´s somehow different now. It seems that the problem only exists after playing with nVidia 4x Downsampling, not in general...

Hi Fiery, now I have a new GTX1070 with actual driver built 430.86 and still I got the same issue after quitting a game... AIDA64 (6.00.5100) Windows 10 pro 64 (1809) MB ASUS Z370-F (1412) CPU 8700K GPU ASUS GTX1070 Strix with latest Driver (430.86) Best regards Rick

That´s great. Thank you! Feedback: "Works perfect, exactly what I desired!"

Thank you for your answer, Fiery. Maybe I didn´t express well, because of my insufficient english skills. I didn´t wanted to say, that this behaviour is a bug of Aida64 and so far as I know Aida64 measures BCLK only one time at startup.' My BCLK is set to 100 MHz but varies between 99.9 and 100 MHz, due to default activated VRM-Spreading. Most of the time BCLK shows exactly 100, but even then, the clocks often are somewhat like 799-4798 MHz etc. (I suppose of not shown decimal places like 100,03). Is there a way to configure Aida64 in a config.file, so that I can define a static BCLK of 100 MHz?

Hi, Ii there a way to fix BLCK in Aida64 at 100, so I can see more rounded numbers in my senson panel?

OK. Thank you for your fast response and have a nice weekend!

Hi, in the last weeks I got irregularely 4 BSOD´s (WHEA 124) about 30s after I closed a game, in idle, while running the AIDA64 Sensor Panel or immeadetely starting it after playing. AIDA64 (5.98.4800) Windows 10 pro 64 (1809) MB ASUS Z370-F (1412) CPU 8700K GPU ASUS GTX560TI with latest Driver (391.35) All BSOD reports had in common, that they showed up the aida64.exe process. Could this be a GPU driver related Bug, as I read about in formar posts, or might this have other reasons? Is there anything I can do about it, to avoid crashing? Best regards Rick