Logitech G19 LCD applet irregular update frequencies

[Seyumi]

Been using Aida64 extreme for many years now.

I recently upgraded my computer top to bottom and now I'm having an issue.

I use the Logitech G19 keyboard with LCD support. I have all my computer vitals such as time, cpu usage, gpu usage, FPS, etc.

I have the update frequency every 1000ms or 1 second and I have a system time with seconds on there so I can see every second it updates. I've always done this.

Issue now is the LCD does NOT update every 1 second and it's DIFFERENT for every 3D game I play.

In normal windows usage, it only updates every 1-2 seconds
In some games, it takes 3 seconds to update
Other games, it takes 5-10 seconds to update

Ingame menus seem to run ok at 1-2 second updates but when you go in-game it will change.

This kind of makes it so I can't see my FPS and stats in real-time now so it's kind of a deal breaker. 

Some possible culprits are the new Windows 10 64bit Creator Update I installed on my system.
Another may be my new 1440p 144hz Gsync monitor but problem is still the same with Gsync on or off (was 4k 60hz)

I also went from Z170 6600k to Z720 7700k and Samsung Nvme 950pro to 960pro. Also Titan X (Pascal) to 1080Ti.

Please help out. I submitted a ticket but not sure what's going on with that. I have the problem with both the stable and the latest beta release. I'm pretty proficient with computers and this is a brand new fresh windows install. Did reinstall of logitech software, Nvidia software, Aida64, etc. Uploaded my Aida64 report below. Thanks.

EDIT: I don't think this is related to the "AIDA64 with Logitech G15 support sttutering game" topic since I'm not really seeing any stutters.

Report.htm

[Fiery]

When you have 1 second update rate configured, the actual update rate will be somewhat higher.  It's because AIDA64 waits 1 second between updates, but one update may take 50 to 500 milliseconds, depending on how many slow interface hardware (sensors mostly) you've got in your system.  So the actual update rate will be between 1050 and 1500 milliseconds.  If you want to get to exactly 1 second update rate, you need to experiment lowering the update rate from 1000 milliseconds to 900, 800, 700, etc, until you reach the exactly 1 second update rate.

As for gaming, I think it may be caused by the Game Mode feature of Win10 Creators Update.  It may allocate far less CPU cycles to background tasks -- like AIDA64 sensors polling -- than before.  You can overcome that issue by turning Game Mode off, and/or by increasing the priority level of the AIDA64 main process (AIDA64.EXE) using Task Manager.  The latter is not very convenient, but it's worth checking out.

BTW, we've checked your support ticket, but it only included an AIDA64 report snippet, without actual comment or problem description.  We can't really do anything about such tickets But we can definitely investigate this issue here, on the forums, I'm here to help you out.

[Seyumi]

17 hours ago, Fiery said:

When you have 1 second update rate configured, the actual update rate will be somewhat higher.  It's because AIDA64 waits 1 second between updates, but one update may take 50 to 500 milliseconds, depending on how many slow interface hardware (sensors mostly) you've got in your system.  So the actual update rate will be between 1050 and 1500 milliseconds.  If you want to get to exactly 1 second update rate, you need to experiment lowering the update rate from 1000 milliseconds to 900, 800, 700, etc, until you reach the exactly 1 second update rate.

As for gaming, I think it may be caused by the Game Mode feature of Win10 Creators Update.  It may allocate far less CPU cycles to background tasks -- like AIDA64 sensors polling -- than before.  You can overcome that issue by turning Game Mode off, and/or by increasing the priority level of the AIDA64 main process (AIDA64.EXE) using Task Manager.  The latter is not very convenient, but it's worth checking out.

BTW, we've checked your support ticket, but it only included an AIDA64 report snippet, without actual comment or problem description.  We can't really do anything about such tickets But we can definitely investigate this issue here, on the forums, I'm here to help you out.

Thank you I got it to work see below.

I can confirm that the Windows 10 Creators update "Game Mode" doesn't make a difference.

I also put Aida64 in the task manager on "High Priority" and it still didn't make a difference.

It was only when I put it to "Realtime Priority" on the task manager where it now updates every second as it always did before.

I also changed my update frequency to around 900ms instead of 1000ms and it now updates every second or more. I do you know if doing it even faster, like 500ms or 100ms will overburden or create any unintentional side affects or wouldn't be an issue on an expensive gaming computer like mine?

Sorry about the ticket. I copy & pasted my Aida64 report and it looks like it reached the maximum characters allowed so it bumped the actual complaint text off the ticket.

[Fiery]

6 hours ago, Seyumi said:

Thank you I got it to work see below.

I can confirm that the Windows 10 Creators update "Game Mode" doesn't make a difference.

I also put Aida64 in the task manager on "High Priority" and it still didn't make a difference.

It was only when I put it to "Realtime Priority" on the task manager where it now updates every second as it always did before.

I also changed my update frequency to around 900ms instead of 1000ms and it now updates every second or more. I do you know if doing it even faster, like 500ms or 100ms will overburden or create any unintentional side affects or wouldn't be an issue on an expensive gaming computer like mine?

Sorry about the ticket. I copy & pasted my Aida64 report and it looks like it reached the maximum characters allowed so it bumped the actual complaint text off the ticket.

I don't think 500 millisec would be an issue, but 100 millisec may cause stuttering or frame drops while gaming.  Try it, and you will see whether you can notice any difference (you will probably not )