Fiery

On modern computers it's not at all dangerous. Modern CPUs and GPUs both feature thermal protection circuitry, so once they start to overheat, they either throttle themselves down or turn off. We generally recommend running the AIDA64 Stability Test for at least a few hours. You should watch the temperatures and the throttling graph (on Intel processors) as well. AIDA64 Stability Test works on notebooks and servers as well.

AIDA64 Business implements a Logging facility that can be used for such purposes. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging to enable and configure that feature. Regards, Fiery

The link between Fraps and AIDA64 shouldn't cause an issue, so in case there's a serious issue while using them together, I think it must be a bug in either one of those software. If you never experience such issues when you only use one of them, then it's a tough one Then the only thing I can think of is some sort of Direct3D hooking vs. AIDA64 mixup, which may be caused by the underlying video driver. Quite hard to diagnose such issues though, since all those ideas I came up with in this paragraph are just hunches, not based on any evidence or actual experience on our test systems.

Yes, I've read those datasheets. Quite frankly, we could add almost any sensors to AIDA64 as long as you figure out how to connect them to your PC. We haven't implemented support for IOWarrior56 or Phidgets sensors simply because so far no AIDA64 user has shown any interest in them. We however have already added IOWarrior24-based ct-Mausekino LCD and Phidget LCD support in AIDA64, so we know how to handle those devices. It's just not for measuring anything, but for displaying the measured values. If you come to a decision on what stuff and how you would build it, let me know. The only thing required for us to start working on the implementation in AIDA64 is the device to be connected to PC via a standard interface (USB preferred), and the possibility for us to buy the same components from an online store. BTW, when it comes to the Phidget sensor device you've linked above, have you checked what device would you connect that thing into? I suppose either one of the following devices would work: http://www.phidgets.com/products.php?product_id=1018 http://www.phidgets.com/products.php?product_id=1011 We've already got the 8-8-8 device with the integrated LCD ( http://www.phidgets.com/products.php?category=15&product_id=1203_2 ), and it's an impressive piece of kit. Although, we haven't yet connected any sensors to it

You can already do that using Fraps When you install and enable Fraps, a new item will appear among other LCD items, called Fraps (in the System group).

Yes, that's correct. But I'm afraid this part of the year is very busy, with all the new hardware launches, so we need a bit more time to understand and process the layout of the Aquaero readings. Both the old Aquaero 4 and the newer models are very "German", in a good way It's very technical, very well structured, very complex, and capable of doing a lot of things. It's not easy to find a common ground with that and the existing sensor module of AIDA64. It's also time consuming to see what we can do with a standalone Aquaero module, and find out what readings may come from external modules and additional (optional) modules. AIDA64 already supports a few fan controller and temperature measurement devices, but none of them is even half as complicated as the Aquaero devices.

You only have to have the FPU subtest enable for that. In case you've got a discrete video adapter (video card) in your system, then enable the GPU subtest as well. If you've got an integrated video adapter, then do not enable the GPU subtest.

Thank you for the feedback

Idle temperature isn't that important. The only thing really matters is temperatures under heavy load.

Those temperatures look absolutely fine to me.

We've implemented support for parallel port connected Samsung KS0108 controller based LCDs in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta

We've fixed the Haswell-E DRAM:BCLK ratio detection and all other DDR4 related issues in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3143zrvflpc9mdzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We've fixed the Haswell-E DRAM:BCLK ratio detection and all other DDR4 related issues in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3143zrvflpc9mdzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We've implemented CPU core clock measurement in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3143zrvflpc9mdzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We've implemented the copy-paste feature for LCD items in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3143zrvflpc9mdzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

It should be there, that's the right path. What software/tool do you try to use the read the values from WMI?

CPU throttling is not a good thing, although on many Haswell-based systems it could be considered normal under heavy system load. Please don't confuse the throttling graph and the CPU utilization graph. They're included in the same area. The yellow graph is for the CPU utilization measurement, and the other graph -- green or red, depending on the throttling activity -- is for throttling.

USB devices have a lot of information encoded in their firmware, including vendor ID, product ID, manufacturer string, product string, serial number, etc. Since they're all stored in the firmware, they can all be set to any value by a simple firmware reprogramming. Making a USB-connected chip look like another chip (in the USB device information block) is quite easy unfortunately. Regards, Fiery

Have you read the customer review on that page? Also, it would be very important to check how many I2C devices can that dongle handle, and what electrical connections do you have to apply to connect those devices. Also, it would be important to check where the proposed sensor devices would get their power from. Because, unlike with USB, the I2C bus doesn't provide any power to connected devices. So the whole thing, including the hardware and software design could quickly become quite complicated. IMHO you may be better off with a ready-made solution, such a device complex that has everything already developed, and you just have to plug the pieces together. AFAIK Yoctopuce provides such solutions, but I'm not sure whether they provide all kinds of sensors that you would need for your project, like humidity and such.

Such devices typically use I2C connection. With most PCs it's not possible to connect your own I2C devices. That's because most PCs do not feature an I2C bus that would be available for the user to connect his own I2C devices. But, in case you find a solution to connect your I2C devices to your PC in any ways, please let us know the exact solution and provide us with an API or other documentation on how to talk to your I2C devices. We can implement virtually any kind of sensor devices in AIDA64, as long as the communication protocol is well documented, and reading out sensor information doesn't take ages. A couple of potential candidates on connecting I2C devices to your PC via USB port: http://www.harbaum.org/till/i2c_tiny_usb/index.shtml http://www.robot-electronics.co.uk/htm/usb_i2c_tech.htm http://mmdolze.users.sourceforge.net/use-a-lcd-with-twi.html http://www.sprut.de/electronic/pic/projekte/usb4all/usb4all_en.html But, you have to be careful with those: you have to verify how many devices you want to connect to the I2C bus, and whether a specific I2C --> USB converter could support that many devices. Or, you can see whether there're any ready-made solutions offered by the following companies: http://yoctopuce.com http://phidgets.com Yoctopuce has very interesting devices that could measure all sorts of things. AIDA64 already supports their OLED displays, as well as Phidgets LCDs -- but not those companies' sensor devices at this time. Another solution might be building your own USB-connected interface board, based on a Microchip or Atmel microcontroller, and hook up your I2C devices to that board. That solution would provide the most flexibility, but may also be the most expensive solution as well. And then there's using a Raspberry Pi as a slave device connected to your PC via USB port, etc. etc. It all depends on how serious are you about this project, and what exactly would you like to achieve.

The requested feature will be implemented in the next AIDA64 beta update It will be rolled out later this week. Regards, Fiery

I meant the 2 scenarios listed as "1)" and "2)" above. It's unlikely, but it could happen. You can try downloading some big files while running the AIDA64 stress test, maybe it will cause an issue...

I think the confusion about thermal testing is that AIDA64 offers more flexibility for stress testing, and sometimes users cannot find the optimal combination. Usually the FPU subtest alone could put the most thermal stress on modern processors. And if you enable more subtests (like CPU, Cache, etc), the thermal stress will not be that great. So it's best if you decide what do you want to use the AIDA64 System Stability Test for: 1) You want to find potential computing errors or other stability issues. In which case you should have a combination of subtests enabled, e.g. you can enable them all. 2) You want to see how well your cooling solution works by putting the most thermal load on your system. In which case you should have only the FPU subtest enabled. Additionally, if you have a discrete video adapter (one or more video cards), you can enable the GPU test as well. If your system can stand 8 hours with both test #1 and test #2, then I'd consider it quite stable

It doesn't do any harm if you run the disk test while using your computer. The disk stress test simply performs file reading operations, so nothing low-level and nothing critical is being performed.

The disk test uses separate processing threads, so you can use it along with the other subtests if you want. You can also issue that test after the other ones. Based on your description of the issue, I too don't think it's disk related. It sounds more like a PSU, motherboard or memory related problem. Regards, Fiery