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.

Hardware database is not stored in a DLL, and the layout of that database sometimes changes, so it's not a good idea to port the database between AIDA64 versions. Also, it's not just the database that changes, but the detection engine itself that is embedded in the main binary (AIDA64.EXE). So I'm afraid you cannot make an old version compatible with new hardware.

No, that's not what I meant. The only way to rule out the memory modules is to borrow some from a friend, and check out if it makes the situation better or worse.

Overheating = when your system heats up excessively under heavy load. There may be the processor that is overheating under stress, or the motherboard, or a combination of components. Failing PSU = when your power supply unit is unable to provide stable and accurate voltages on either the +5V or +12V rails. Please note that even when MemTest86+ passes, your memory module can still be failing under different workloads. MemTest86+ simulates one sort of workload, but there are many other usage scenarios where your memory module may be failing. I'm not saying it's definitely the memory module that's behind your issues, but stating that a memory module is okay just because it passes MemTest86+ is not the right approach

You need to use the /RMTREPORT and /RMTHOSTS command-line parameters in a command-line that you put amongst the Scheduled Tasks on your server. More info on the command-line facility is available in the AIDA64 Business Edition user's manual. Regards, Fiery

Some of the benchmark results may be the same on some of the systems out there. We don't revamp all benchmarks at every stable releases of course: there's no point and there's no resources to do so. But for example, at the next AIDA64 update we are planning to completely drop the current PhotoWorxx benchmark and AES benchmark, and replace them with brand new ones that produce very different scores (with even different measurement units). Same goes for the next version after that where we want to drop all current memory benchmarks and replace them with more modern, more efficient ones. Not to mention supporting new architectures where we constantly work on implementing newer and even smarter tricks to squeeze a bit more out of the system than before. E.g. if you measure an AMD Trinity system with an older version of AIDA64, you will get much lower scores than with the latest AIDA64 (v2.60). It's not easy to assure consistent benchmark results across the whole range of systems AIDA64 is capable of benchmarking (from the very first Pentium-60 and K5-75 to the latest Core i7 and FX processors). And we can only do that if you stick to the rules of comparing results only if they are obtained by the same AIDA64 release.

When you run a benchmark, AIDA64 always warns you that: "Please note that results obtained with different versions of AIDA64 cannot be compared. FinalWire constantly improves and optimizes benchmark routines and implements new technologies to provide you with the most accurate and highest benchmark scores." Hence you cannot re-use old benchmark results, simply because those old scores cannot be compared to ones you obtained with a newer AIDA64 release.

AFAIK Vertex 4 drives do not have a temperature diode. Regards, Fiery

It still leaves the other 3 options I've listed above

Many PC crashes are due to either excessive overclocking, overheating, a failing PSU (Power Supply Unit), or bad memory module(s).

Does AIDA64 stop responding when it tries to send an alert, or is it a regular issue that affects AIDA64 even when the alerting facility is not activated?

That's because if you have AI Suite installed, debug information will issue an ATKEX call for AI Suite to send the sensor info it measures to AIDA64, so AIDA64 could insert it into the debug output. When the ATKEX call is issued, AI Suite reconfigures the sensors on your motherboard.

On your motherboard AI Suite reconfigures the sensor chip, effectively altering the CPU temperature readouts. We used to have a workaround in AIDA64 for that situation, but it caused a lot of confusion amongst AIDA64 users, so we've removed it. Please note that the lower temperatures (that AIDA64 shows before running AI Suite) are the ones measured by the sensor chip, so we would treat them as the "real" ones actually... Regards, Fiery

I'm sorry, but we don't offer such license. BTW, even Windows itself has no such license Also, most anti-virus and security software have no lifetime license.

Actually, usage period is not limited in AIDA64 licenses. What's limited is the maintenance (support) period, the time until you can upgrade to newer releases of AIDA64. The regular AIDA64 license covers 1 year maintenance, so for 1 year you can benefit from updating to new AIDA64 releases, and you receive free technical support as well. After that period expires, you can still use the last AIDA64 version you could upgrade to, for an unlimited time. So for example, if you bought a 1-year license in September 2011, you got AIDA64 v1.85 with that purchase. You could then upgrade to AIDA64 v2.00, v2.20, v2.30, v2.50 and v2.60 free of charge. And you can keep using AIDA64 v2.60 for an unlimited time, but you cannot upgrade to future releases of AIDA64 v2.70, v3.00, v4.00 (etc) anymore. Please note that there're longer maintenance period licenses, for 2 years and for 3 years, with considerable discounts compared to the price of the 1-year license. It's also possible to renew (extend) an existing AIDA64 license at 70% of the new license prices. More info at: http://www.aida64.com/licensing-aida64 Regards, Fiery

Thank you for your support.

Currently it's not possible to alter the priority of AIDA64 main process. Why would you want to do that BTW? Regards, Fiery

Thank you. Can you please right-click on the "Motherboard" group in the left menu in AIDA64 --> Quick Report --> Plain Text. Copy-paste the full results into this topic.