Fiery

According ASRock's website, H55M-LE supports 8GB system RAM in 2 DIMM slots, while its big brother (H55M-GE) supports 16GB system RAM in 4 DIMM slots. So your motherboard can hold two pieces of 4GB memory modules. 64-bit software have the potential to perform faster, but most of them perform a bit slower actually, due to 64-bit code is being longer than similar code in 32-bit. With an Atom processor it makes virtually no sense to switch to 64-bit.

Thank you. Under the Hardware Monitoring branch in the Preferences, which features do you have enabled? Alerting is enabled, clearly, but do you have Sensor Icons enabled as well? Maybe others like OSD Panel or Logging?

The most accurate and dependable information is in the motherboard user's manual, because even the BIOS could limit the amount of memory that can be utilized AFAIK Asus Eee PC 1015PE has an Atom N5xx Pineview processor. Such processors can use up to 2GB of system memory, 1GB per DIMM slot, with two DIMM slots supported. If you could tell me the model name of your desktop motherboard, we can check that too. Generally speaking, if a chipset or CPU IMC is capable of supporting e.g. a total of 8GB system RAM in 4 DIMM slots, it means one DIMM can be up to 2GB in size (8GB divided by 4 DIMM slots). There are exceptions from that rule though, so it's best to check both the chipset's datasheet and the motherboard manual.

On the Motherboard / Chipset page AIDA64 reports the capabilities of the chipset (or the IMC of the processor), and not the capabilities of the motherboard design. Because in several cases -- for cost-saving or motherboard dimension constraints -- motherboard manufacturers put less DIMM slots on the motherboard than what the chipset could handle. In such cases the actual max. amount of system memory that you can install could be typically 50% of what AIDA64 reports as the chipset capability. Regards, Fiery

1) What version of AIDA64 are you running? 2) What motherboards do you have in those computers? Are there any common components of them that may be behind this issue? 3) Do you have any other hardware monitoring, tweaking or overclocking software installed? (e.g. Asus AI Suite, Gigabyte EasyTune6, SpeedFan, HWMonitor, etc) Thanks, Fiery

I've sent you a private message about this.

Have you tried to update ForceWare to the latest WHQL version?

Thank you for posting that idea. It looks like it's a very specific usage scenario, so I'm not sure if AIDA64 should provide a ready solution for that. Let's wait and hear if others would like to have it implemented as well. Regards, Fiery

1) Which version of AIDA64 are you using? 2) If it's possible, please export the LCD settings, and attach it to a message in this topic, so we could check it out. Thanks, Fiery

Thank you. Your monitor will be added to the next AIDA64 release due October 29th Regards, Fiery

Close AIDA64, launch Registry Editor (REGEDIT.EXE), navigate to ... HKEY_CURRENT_USER\Software\FinalWire\AIDA64 ... and remove all keys there that starts with OSD. Then start AIDA64 again, and hopefully OSD will revert back to its default position of right edge of the primary monitor. Regards, Fiery

Thank you. Your monitor will be added to the next AIDA64 release due October 29th. Regards, Fiery

I'm sorry, but the whole AIDA64 hardware monitoring module works together, "moves" together, so it's not possible to pick an item and make it update faster than the whole big module

Thank you. We've checked, and unfortunately this is not an easy one Apparently a lot of things have changed internally in AVG 2013. We'll need a bit more time to investigate and try coming up with an anti-virus database detection for the new AVG release. I'll let you know in this topic once we have an update to this matter.

Thank you for the feedback. +3.3V, +5V and +12V are not supported, because of ECS's decision. Any sensor chips could monitor those rails.

I'm glad you managed to work it out

That means AIDA64 may show its main window outside the Windows Desktop for some reason, or on a secondary display that is not connected or somehow misconfigured. Please try to close AIDA64, and remove the following Registry path (and everything inside it) using REGEDIT.EXE: HKEY_CURRENT_USER\Software\FinalWire Also, go to AIDA64 folder, and if there's an AIDA64.INI file, make sure to delete it. That should revert all AIDA64 settings back to default. If it still doesn't work, then please check if there's anything you can configure about multi-display support in Windows to make AIDA64 display its main window properly.

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

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