Fiery

To me it sounds like an overheating issue, due to dirty/blocked exhaust vent ports or some other reason. Try to run AIDA64, go to main menu / Tools / System Stability Test. Enable every subtests (like CPU, FPU, etc), press the Start button. Wait for at least 30 minutes before stopping the test. Check if it causes the same freezes, and track the measured temperatures, as well as the bottom graph. On the bottom graph the throttling line should stay at 0% all the time. If it shows a non-zero value and turns to red, it means your computer is overheating. If temperatures climb up to high values (80+ Celsius) and your computer turns off or starts beeping, it is a serious overheating situation. Regards, Fiery

What kind of image did you add? JPEG, PNG, BMP? Thanks, Fiery

What kind of calculation would lead to 260W in such circumstances? Certainly Intel never published any formula to do that. And if you're not going by Intel's own formula, then the result will not be comparable to the Intel CPU power measurement wattage. AIDA64 System Stability Test (SST) -- when you use only the FPU subtest -- puts an enermous stress on the CPU, and makes it draw very high power. I wouldn't state that no other software or trick could make your CPU draw even more power, but our solution (the AVX2 and FMA accelerated FPU subtest of the SST) is considered a "power virus" by Intel, so it's definitely good at driving your CPU to its limits

AFAIK that value is not exported, hence it's not usable by other software. Regards, Fiery

It will be one of the 6 case fan headers that you can find on your motherboard.

The issue will be fixed in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new update is available for download.

Thank you for the feedback. I'm afraid we have no information on how those values are measured or calculated. Our best guess is that the DPS software somehow calculates those, not measure them. DIMM power is measured by the CPU. Only Intel knows what it means exactly and how it is measured.

Yes, the trick about the DPS app was that I simply had to use Windows 8.1 It doesn't start under WinXP at all, and it works very erratic under Win7.

We've added Thermaltake DPS-G sensor support in the following new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta Please note that Thermaltake's own DPS-G monitoring software is not synchronized with other monitoring applications like AIDA64. We've implemented a workaround in AIDA64 to avoid collision issues. But if you don't need the DPS-G software features anyway, then it's best to uninstall it from your system, since it keeps running in the background even after you close the main window and exit from the System Tray icon. Let me know how it works on your system

1) In your case VRM is the motherboard VRM, not the video card VRM It would be called "GPU VRM" if it was for the video card(s). 2) PSU temperature and fan speed can only be measured for such devices that support those measurements. Most PSUs will not support it, or they are simply hooked up on a motherboard fan header, so the motherboard will measure the PSU fan speed. 3) RAM temperature measurement is disabled by default, because in rare case it could cause instability. You can try activating it in AIDA64 / main menu / File / Preferences / Stability / DIMM thermal sensor support. Restart AIDA64 after altering that option. Please note that it will only work in case your memory modules feature a DIMM TS compliant temperature sensing logic. Regards, Fiery

IMHO it is most likely due to a faulty iGPU temperature diode, or due to a temporary malfunction. Try to completely power off your system. Shutdown Windows, and disconnect your computer from the wall plug (A/C power). Leave it disconnected from the power for at least 2 minutes, then connect it again, start your PC, and see if it makes any difference. If not, then probably your only chance to get things back to normal is by replacing your CPU (which should still be under warranty I guess). Regards, Fiery

Thank you for the feedback. When it gets glitchy, is it for a period of just one frame update? Or the graphical artifacts get stuck and you have to restart AIDA64 to make it work again? Can you please post a photo of how it looks like when it goes south? Thanks, Fiery

It is possible to display the time without seconds by using the latest AIDA64 Extreme beta available at: http://www.aida64.com/downloads/latesta64xebeta But I'm afraid displaying multiple time zones is not possible though. Regards, Fiery

You can open the AIDA64 configuration file called AIDA64.INI (that you can find in your AIDA64 installation folder) in e.g. Notepad, and remove the alerting lines easily. Just scan the file for: HWMonAlertItem Regards, Fiery

It is good news, as long as the new Corsair Link gets ready sometime soon.

Yes, we've already got a DPS-G PSU, but it doesn't work properly for some reason. Even its own application cannot find the PSU in most cases. However, since this issue was reported by multiple users on various forums, I suppose it may not be due to a hardware failure, but some other issue, probably in the USB HID interface or the DPS software. We've sent an inquiry to Thermaltake to ask their assistance on this issue, but got no response yet And as long as the PSU fails to work properly (even when we try to use its own software), it's not easy to figure out what needs to be done to read the sensor values from it

Please check the following forum topic about such static labels: http://forums.aida64.com/topic/2610-logitech-arx-control-lcd-for-smartphones-and-tablets/ Regards, Fiery

No, I don't think you understood what I meant What I meant to say is that Uncore is not Package minus DRAM. Your CPU package includes the following components: - Uncore - CPU cores (6 cores) DRAM power is supposed to be the total power draw of the DRAM modules, but the DRAM modules are not part of the CPU package at all. But the six CPU cores are part of the CPU package, but those are not accounted there at all. So the formula used by HWMonitor is completely wrong and pointless.

Since your inquiry is about the business line, probably it would be best to contact our distributor ABSEIRA at: info AT abseira.com Regards, Fiery

I'm pretty sure that value is just calculated as: Uncore = Package - DIMM To me that doesn't sound like a proper formula for your CPU...

I've sent you the requested screen shot in email

v1.4 works on iPhone 5 + iOS 6.1.4 for me. The only problem is: it somehow doesn't work well when one interrupts monitoring by e.g. performing in-app purchase. I don't know why, but it simply fails to connect again after then. It says Server Offline, but the server works fine. If I kill the app and start it again, it works. If I go to Settings, press Done button (without altering any settings), I get a blank white screen and it cannot connect back to the server again. Pushing the Home button and then opening the app again doesn't help either. A cosmetic issue: in the Settings the two pair of buttons are not aligned horizontally.

Since your BCLK is 100 MHz, and your DRAM frequency is 1333 MHz, 40:3 is the right ratio, so AIDA64 is correct there. CPU-Z is not our software, so I cannot tell why and how it could misinterpret or misdetect the DRAM:BCLK ratio. But I'm sure Franck (the author of CPU-Z) could clarify that, and if necessary, fix CPU-Z. Regards, Fiery

HWiNFO and SIV directly control the Corsair Link hardware using the Global\Access_CorsairLink named mutex to synchronise access, however the Corsair Link application does not use this mutex so there are issues when the software collides. We've asked Corsair to provide us with a SDK to let us implement proper support in AIDA64, but they said the current Corsair Link framework is already deprecated, and that a new one with major changes is about to come out. We're still waiting for the new generation of Corsair Link to be released though... Corsair said the new framework will include a SDK that AIDA64 could use to talk to Corsair Link devices, without collision issues. Regards, Fiery

Replied in the WebDash topic