ronzino

I mean both, neither screensaver (the windows default ones, the only i have installed) nor monitor energy save work. As soon as I disable the shared memory in aida64, both start to work again.

Hi, i have windows 10 x64 and aida64 5.70.3879 beta when aida64 is started, the windows screensaver does not run. I have found that the problem is the related to the shared memory option: when it is enabled = no screen saver when it is disabled = screensaver is ok PLEASE NOTE 1) the problem manifests even if the other application that uses the shared memory is disabled. I mean even if there is any application that is using the shared memory, the option activation in aida64 reproduce the bug. 2) I have tried to enable shared memory and disable the whole list of sensors shared, the no screensaver problem is still there 3) i have the corsair link module enabled. disabling it does not fix the problem suggestions ?

Hello, windows 10 introduced a brand new way to managing the screen resolution, windows, apps and text zooming and this run into confusion the user and aida64 too. (quick explanation of new windows 10 high res managing) --- Previous windows 10, the user has the ability to modify the DPI size of texts in order to increase their physical dimension when high resolutions are activated, but this most of the time broke the application functionality as enlarging the texts and reducing the application windows sizes, due to increased resolution, always lead text out of application windows areas. Of course the user can manually modify the applied autozoom, even disabling, but infact is damn useful and work pretty well --- The problem is this if I use a resolution of 1920x1080, aida64 reports it correclty BUT if i rise the desktop resolution to 4k (i.e. 3840 x 2160, and of course i have a 4k monitor) suddenly windows detect this and triger the zooming function, enlargin everything to 225%. so even if my monitor report on the OSD 3840x2160 60hz resolution, aida shows 1707 x 960 and if you make the calculation... 1707 / 100 x 225% = 3840 and 960 / 100 x 225% = 2160 that is exactly the 4k resolution that I had defined. Aida64 infact is right, it is deceived by windows.... MY FIRST REQUEST IS: Is it possibile to insert a new function in aida64 in order to show BOTH resolutions ? suggestion "windows desktop resolution" and "monitor resolution" SECOND REQUEST / PROBLEM In the situation described above, if i start a full screen application, like a game and the game run in 4k, Aida64 continues to show the desktop resolution 1707x960 no the new full screen resolution imposed by the game. can this be fixed, or a new parameter inserted in the aide64 ? suggestion "full screen application resolution" Thanks for your help

problem solved. I had selected the italian version language for aida64 on a windows 10 (in italian too). In the poll rate menu is reported 5,000 ms that means (in italian numeric notation) 5ms as for us the "," is decimal separator, not thousand. instead the software means 5,000 ms i.e. 5 sec, also when the italian language is select. I figured out later that the italian language is just a quick translation of some text menu, not the whole software and not numeric notation. thanks for your help

i have 5 ms for all update frequencies. i have the same problem on OSD Sensor Panel external reading g19 lcdhost

mmm there's something wrong ... 1) there is no update frequency in aida64 menu for hdd polling 2) windows polls the hdd write/read speeds every second, according to windows performance monitor 3) HWiNFO64 is able to poll the hdd write/read speeds every second like windows is it possible that you have wrongly connect the TEMPERATURE HDD POLLING (minimum allowed value = 10 sec) to the HDD PERFORMANCE polling ?

The disk sensors like "Disk Activity" "Disk read speed" "Disk write speed" have an update rate of amout 7 seconds. how can i reduce the pooling time for those sensor ?