Fiery

But until then you should be able to upgrade to a X58 board, or some AMD stuff

Thank you. On our own test systems the latest AIDA64 beta combined with the previous Intel RST release already didn't produce any "hickups" or lags, so we have to rely on you guys to provide us feedbacks on this RST update

We've asked our contact at Intel, and he reckons due to the nature of the problem (which is very deep, at the silicon level) there's no scientific way to measure or even estimate the level of degradation. There's of course a number of diagnostic features of AIDA64 that you can use to find out whether your hardware is still working at the expected level of performance. E.g. you can check if the SMART attributes look okay -- if there're multiple critical values reported, it most likely means the controller is failing. Or you can use the AIDA64 Disk Benchmark to measure the bandwidth of the controller. And you can use the AIDA64 System Stability Test to stress the disk drives while also stressing the whole system. But if you ask me, I would either just connect the drives to the SATA 6.0gbps ports (port#0 and port#1), or better still, return the board under warranty for a replacement. There's really no point relying on an unreliable hardware, and then check how unreliable it is right now

That may be due to the revamped hot-plug drive support in AIDA64. Now when you add or remove a disk drive (e.g. a USB HDD), the order of drives may change. We'll try to further improve it to avoid such hassles that you described. Meanwhile, please make sure to use the latest beta release of AIDA64: http://www.aida64.com/downloads/aida64extremebuild1243bw4ylkfd0mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Thanks, Fiery

On most motherboards the "Motherboard" temperature is the surface temperature of the sensor chip (that is mounted on the motherboard PCB). In other words, the sensor chip measures its own temperature, and reports it as "Motherboard" temperature.

Thank you for the suggestion. We'll work on it, and hopefully will be able to add it to the next AIDA64 release. Thanks, Fiery

How many tabs would you like to have?

You can basically extract the files to any folder. If you have an older AIDA64 already installed, you can overwrite its files. If you have no AIDA64 installed, you can extract the ZIP content to any folder, even if you place that folder on a USB flash drive

You're right, normally you should issue a Windows restart everytime you upgrade or downgrade AIDA64 But in this case, restarting Windows would reset the counters, so it's not a good idea

When you restart your system, those counters are all resetted to zero (by Windows itself, since Windows manages those counters). You should not restart Windows between making screen shots about this matter.

That's a 4th issue then Please let us know which AIDA64 Hardware Monitoring features do you have enabled. E.g. Sidebar, LCD, OSD, or a combination of those?

Thanks. I'm sorry to be a pain in the back, but can you please do another test run, by creating 3 screen shots: 1) First, with the latest AIDA64 beta 2) Then, with the old AIDA64 version (v1.20) 3) Then, with the latest AIDA64 beta again I'm just asking that, because there's a noticable difference between swap space usage on the 2 screen shots you created, and I suspect between the time the first shot was captured and the time the second shot was captured, Windows simply started to use up the swap space, and hence started using the paging file. We've double-checked everything about the paging file utilization, and found no issues or anomalies at all. I still reckon you have no problems on your system, or at least nothing that would be related to AIDA64.

Thank you for the feedback

Existing Logitech LCD settings can be found in AIDA64.INI file in \Program Files\FinalWire\AIDA64 folder.

nForce chips implement an integrated PLL that is well-documented. Hence it's relatively easy to read PLL settings on any nForce-based motherboards in AIDA64. However, other chipsets (e.g. AMD 7-series and 8-series) has no integrated PLL, hence PLL settings readout method depends on the PLL chip mounted on the motherboard. And motherboard manufacturers don't give out documentation for the PLL chip used, and so it's not possible for us to implement PLL settings readout in AIDA64

1) Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 2) Also copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. Thanks, Fiery

Thank you for the feedback

What I was trying to explain above is: there're 3 separate issues there, and one out of them is not related to AIDA64: 1) The first one, reported by Squall Leonhart was about the duplicate lines appearing after a while. We've already fixed that. 2) The second one, reported by you was about the missing utilization lines. It was due to AIDA64 did not bother displaying 0 MB / 0 MB and 0% lines. We've already changed that approach to displaying every lines even when they display no meaningful information. So even zero utilization is displayed now. We consider this issue fixed too. 3) The third one, reported by you was about zero paging file utilization reported by AIDA64 while using Adobe Premiere Pro. I've pointed to the fact that AIDA64 reports paging file information using standard Windows API calls. It's a kind of information that comes from Windows itself, and not processed or measured or computed or altered by AIDA64. If you don't like those values, or in case you simply don't believe in those values, then you have to find the error in the way Windows reports pagefile usage, and not try to find a bug in AIDA64 In case you're adament that previous betas reported "better" values, then please try to downgrade to an older beta, and show us on a screen shot what values did it report. But if you do so, then please also create a screen shot right after that, using the latest beta, for comparison. However, apart from issue#1 and issue#2, I'm 100% sure every previous AIDA64 beta and stable releases will report the very same values that the latest AIDA64 beta does.

Then I'm afraid we cannot do more to avoid the lagging issues We've done extensive tests in the past 2 weeks, and apparently the issue does not come up with Version 8 of Intel RAID drivers, but it does come up on certain configurations with Version 10 of Intel RAID drivers. The actual slowdown seems to be occuring inside Intel RAID drivers, so we hope Intel will eventually fix that and make us all happy.

We've implemented a completely new method to measure CPU core clock on Intel Core i3/i5/i7 processors. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1243bw4ylkfd0mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've implemented a completely new method to measure CPU core clock on Intel Core i3/i5/i7 processors. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1243bw4ylkfd0mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've fixed the texture fillrate calculation in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1243bw4ylkfd0mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. As for the memory sizes, they can be confusing, but that's how Windows manages swap space and paging files. Even if you disable paging files completely, Windows will still manage some swap space. Quite hard to follow that logic, but that's just how Windows works

Thanks for the feedback! Quite frankly, we have to do a lot of tweaks on the AIDA64 SMART handling module, and some of the issues now seem to be gone, fortunately. However, other issues related to Intel RAID drivers cannot be fixed from AIDA64, so we have to wait for Intel to update their drivers.

Are you using AIDA64 latest beta release? http://www.aida64.com/downloads/aida64extremebuild1241ow5ief2yskzip

AIDA64 collects pagefile info using standard Windows API call NtQuerySystemInformation (1st parameter = SystemPageFileInformation). In case it reports unexpected values on your system, it's not the fault of AIDA64. The previous issue (when pagefile utilization lines did not display for a while) was because AIDA64 didn't bother to display "0 MB / 0 MB" lines. As soon as the utilization climbed up from zero, it displayed those lines. Now it is changed, so even zero utilization is shown.