Fiery

I'm pretty sure the new AIDA64 beta will work fine

If you are connected via Remote System Information, then your messages will be sent via the TCP/IP port for Remote System Information. If you are connected via Remote Monitor, then your messages will be sent via the TCP/IP port for Remote Monitor. BTW, are you using AIDA64 Business Edition v2.50? (latest version)

Generally speaking, we recommend to let the stess test run for at least a couple of hours. If you have time to leave it running, then give it 12 to 24 hours. Regards, Fiery

It could be a port or firewall issue. You can configure the TCP/IP port for each AIDA64 remote feature in AIDA64 / main menu / File / Preferences / Remote Features.

Make sure to improve the cooling of your system. If you don't have a rear exhaust fan, installing one may be a huge help in driving out the hot air from the system case.

If you want to stress your system to check if it is overheating under heavy load, then go to AIDA64 / main menu / Tools / System Stability Test. Only enable the "FPU" subtest, and disable the rest. Press the Start button, and watch the bottom graph for any throttling activity. If the green graph stays at 0% all the time, even after running the FPU test for cca. 30 minutes, then your system can stand heavy load without overheating. If the green graph turns red and shows any non-zero activity, then your CPU is overheating.

Most BIOS will not show the core diode readings at all. If you're unsure about the core temperature accuracy in AIDA64, then you can adjust the TJMax value in AIDA64 / main menu / File / Preferences / Hardware Monitoring.

Please try updating your RAID drivers to the latest Intel RST Enterprise WHQL driver.

Please try to remove KERNELD.* files from AIDA64 folder.

We've recently fixed a few major issues about Radeon HD 7xxx cards in AIDA64. So make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery

It's actually easy to identify drives with a GPT partition table. Go to AIDA64 / Storage / Physical Drives, and check the Partition Type column. If any of the partitions are FAT, FAT32 or NTFS, then it's a classic MBR. If it's one of these, then it's GPT: Basic Data (this is the most common one) EFI System LDM Metadata LDM Data MS Recovery MS Reserved Unused Regards, Fiery

I wouldn't worry too much about those idle temperatures. Of course there may be a bit of room for improvement if you could improve the air flow of your system case. E.g. install a rear exhaust fan, and/or have a CPU cooler that blows air straight into the rear exhaust. I personally am not a huge fan of side mounted CPU fans

Please try to replace /SAFE with /SAFEST. Let me know if it helps. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you for the info, we've added those O&O software licenses to AIDA64, and fixed the 64-bit Windows issues. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

We've implemented the changes you requested. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2036mxyv0c7zkwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Cca. 70 Celsius is a bit high for core temperature, but not critical. You can check the maximum working temperature (TJMax) on the Motherboard / CPUID page in AIDA64. Regards, Fiery

Thank you for the feedback

What GTX670 and GTX680 cards can measure is not an absolute Wattage value, but rather a "Percentage of TDP" value that is not really easy to fit into the existing hardware monitoring module of AIDA64. We'll work on it though

First of all, please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2029bcq0xs8flwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Then please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Thanks, Fiery

I'm sorry, but having a very small gauge size plus a different style where red colour would be at the low end of the scale is not something we'd want to do at this time -- unless we get more user requests on the same idea

100 MB/sec is very low difference on modern processors.

I think we've figured out what the reason behind the C-State anomaly. Apparently Intel Turbo Boost only considers a core sleeping (inactive) when it enters either the C3 or C6 state: http://download.inte...nots/320354.pdf (Check 3.3 and 3.4 in the PDF) Hence, if you disable C-States (C3 and C6), Turbo Boost will work less efficiently. And that effectively means that single-threaded performance will suffer when you disable C-States. It is reflected by AIDA64 memory benchmarks which are single-threaded benchmarks. It will not be reflected by multi-threaded benchmarks like AIDA64 CPU and FPU benchmarks -- or Sandra memory benchmarks for that matter. BTW, if you check the measured core clock on the Cache & Memory Benchmark Panel, you may see that with C-States enabled your processor will work at a higher core clock level. On our test system (Core i7-2600 + Gigabyte Z68XP-UD3-iSSD) Turbo Boost could push the CPU up to 3.70 GHz during the memory benchmarks when C-States were enabled, but it managed to push the CPU up to only 3.50 GHz with C-States disabled.

What I meant to say was: the Gadget feature requires the Registry to pass on sensor values between AIDA64 (main application) and the Gadget. Without using the Registry it cannot work at all.

It's a false alarm. But if you're unsure, just let it remove the file, it's mostly not utilized. Regards, Fiery