Fiery

Since it's quite hard to debug this issue (due to the BSoD takes at least several hours typically to come up), the best way is to try downgrading to an older RSTe release, in a hope that they're more stable...

Because in such case no calls are made for the ATA layer of Intel RSTe drivers. But the bug is still in the RSTe drivers.

When both RAID options are disabled, AIDA64 will use standard Windows API calls to detect ATA devices and to acquire SMART attributes list incl. disk temperature (if available). It means, if that causes a BSoD, it is caused by the storage controller driver, so it should be the fault of Intel RSTe drivers rather than AIDA64's.

AIDA64 v2.60.2153 (latest beta release) should be fine for your motherboard. Please try to uninstall AIDA64 completely, restart Windows, install v2.60.2153 Beta, restart Windows again, and try AIDA64. If it still doesn't work, then please let us know exactly what happens after clicking on the AIDA64 icon, and also let us know if you've got any Asus software or other hardware monitoring, tweaking, overclocking or stress testing software installed. Thanks, Fiery

There's no clear formula, especially since there are command delays, data throughput, data latency and a lot of other factors involved.

Since there're several other factors (like memory controller's own latency), it's not possible to directly translate clocks+CL/RCD/RP/RAS timings into memory latency. Please note that clocks and CL/RCD/RP/RAS latency values are detected, while memory latency is measured.

That's normal, and it is caused by the low-level EC (Embedded Controller) access features of AIDA64. You can simply ignore those warnings, they're just notifications by the ACPI EC driver of Windows. Regards, Fiery

When you've got a Logitech LCD keyboard, there're two methods of starting AIDA64 at Windows bootup. First is the classic method of using the option in AIDA64 Preferences / General page, which starts AIDA64 from either the Registry's relevant Run section (under Win2000/XP), or using the Task Scheduler (of Vista/Win7/Win8). Using this startup method may cause issues when bootup order of software and drivers get mixed up. Second method is using the Logitech LCD Manager to launch AIDA64 when it starts up the applets. I suppose in your case this option should be used, and the classic startup method in AIDA64 Preferences should be disabled. That way LCD Manager will launch AIDA64 when it initializes the LCD applets. Regards, Fiery

I'm afraid it's not possible, since the underlying hardware monitoring module has such parts that take 200 to 500 milliseconds to complete, hence a sub-second refresh rate would mean a constant polling of sensors that would put high load on the system and may cause unexpected issues Regards, Fiery

I'm afraid not yet We haven't been able to reproduce the issue on our test systems. We'll do more test runs soon, but first we need to get more test boards, more specifically one that is identical to yours

Actually, using custom gauge states is already supported by the latest AIDA64 Extreme Edition beta. So you can use Photoshop to design your own gauge states, and add them to the SensorPanel.

Scripting in AIDA64 Business Edition is available only for reporting and network audit purposes. The Disk Benchmark and System Stability Test modules are not automatized in either editions. With HDDs you can use any tests in AIDA64, they will not shorten the lifespan of the drives. Solution a) is a good one to stress multiple HDDs, but it can also be used to stress all local disk drives in parallel, incl. any SSD+HDD combinations.

666 MHz means your memory cycle time is 1.5 ns, which equals to 1T. The memory chips are made of a matrix of cells, where there are a certain number of columns and rows. The 4 timing values represent the time your memory chips will take to access a row, a column, and then finally the actual data. The first 9 means CAS Latency = 9T = 9 x 1.5 ns in your case. The second 9 is for RCD, the third 9 is for RP, and the 24 is for RAS. It's quite a complex method, but you can read more about it at: http://en.wikipedia.org/wiki/Memory_timings Regards, Fiery

1) System Stability Test stresses all local disks simulatenously, but only as long as they contain a partition table and they have files on them. This is because that test is a file system test, so it relies on the existence of files on the tested drive(s). 2) It's not recommended to use the write tests on SSD drives, due to them wearing out SSD flash memory cells. You can however use the new Linear Write + Verify test (of AIDA64 Disk Benchmark) once on each new drive to see if it has proper data integrity. That will only consume 1 write cycle for each cell, so it's not excessive in terms of wearing the memory cells out. 3) Another alternative is using the read tests of AIDA64 Disk Benchmark in a loop to drive them all night long. The only limitation is that you can only stress a single drive at once, so you need 3 nights to test 3 drives. I'm afraid AIDA64 has no more advanced features than the ones above. No offense, but your application scenario is quite unique It's not everyday an AIDA64 user buys 3 new drives that he/she wants to burn-test simultaneously and quickly. Regards, Fiery

Go to AIDA64 / main menu / Tools / System Stability Test, and enable only the "FPU" and "GPU" subtests there. That should put both all CPU cores and the video card at 100% load. Regards, Fiery

If it's possible, please go to the BIOS Setup, navigate to the PC Health Status or HW Monitor page, and note down all temperature, voltage and fan speed values your motherboard is monitoring, including their current value. Those values would help us to figure out the necessary sensor register values and ratios to make sure AIDA64 provides accurate readings. Thanks, Fiery

A while ago AMD made a decision to not release their Catalyst drivers with APP (OpenCL) support for pre-HD5000 cards. AIDA64 System Stability Test requires an OpenCL capable GPU device to stress the video adapter(s). Hence this is a video driver limitation, and not the fault of AIDA64. If you decide to upgrade your card in the future to a HD5000 or later card, then you will be able to use the GPU stress test in AIDA64. Regards, Fiery

No, it's not possible. But if you have the SensorPanel enabled in AIDA64, then when you start AIDA64, it will automatically show the SensorPanel.

Wow, that one looks cooool!

It's not possible using a single graph. But, you can make a graph with no background and no grid lines to make it transparent, and then you can place it above any other graph

There's a very slim chance that more than 1 memory module is failing, and an even slimmer chance that more than two. So yes, it's pure statisics And quite frankly, I personally am not fond of using more than two memory modules in a mainstream desktop motherboard (ie. one that has 4 DIMM slots and uses a dual-channel memory controller). So if there's any possibility of switching to just 2 identical memory modules, that alone could fix the issues in many cases. I'm not saying in your particular case that it is definitely the solution, but if you could just remove 2 memory modules, it's a test that worth the extra time and efforts. Removing two of them for a test doesn't cost any $$ at least Before you continue spending more $$ on your system, make sure to try the "remove half of the memory modules" test run. Also, you may want to try playing around with memory timings as well, _if_ your BIOS Setup allows altering timings. Upping the Command Rate (CR or tCMD) from 1T to 2T might help as well to stabilize the memory controller. I'm afraid software issue, operating system issue and configuration issue are always a possibility. A wrong device driver, a wrong service could cause all sorts of issues, not to mention potential malware that has already infected the computer. And then there's the slim chance that an installed software or driver getting "freaked out" when AIDA64 puts extreme stress on the system. Please note that the "FPU" subtest in AIDA64 System Stability Test puts such a heavy workload on the system that is quite unusual, and many systems fail to run that test for more than a few minutes. The "FPU" subtest is definitely the worst case scenario a computer could go through, but a properly built and properly configured PC has to pass that test to be considered a stable system So if you could save all your data, documents and settings, and have the possibility to completely reinstall Windows and all software from scratch, then it would definitely worth a try. Having a clean Windows installation could improve the response time of the system as well.

Thank you. If you have a chance to borrow two identical DDR3-1333 modules from a friend, then it would worth checking out whether it makes a difference. If you cannot do that, then it may worth playing around with the memory modules, because there may be one or two weak ones amongst the 4 modules you've got installed. Try removing two, and check out if it changes anything. If not, then try replacing the two installed modules with the ones you removed previously, etc. Make sure to have the 2 modules always placed in the DIMM slots that makes the chipset operate optimally (dual-channel; first DIMM slots usually). I apologize for not being able to provide better ideas on troubleshooting. Remotely it's usually quite difficult But what you did so far (installing a better CPU cooler and a new PSU) were both good steps in trying to hunt down the cause of the hardware issue.

Please send me your full name and email address in private message, and I'll try to find your license in our customers database. Thanks, Fiery

Please keep posting to this forum only about AIDA64-related matters. Regards, Fiery

I've never seen such error message before. Maybe other forum users can help you out.