Fiery

It's not easy to post judgements on that anomaly without knowing a bit more details of the i5-2450M system. Our best guess would be that either a core, or HyperThreading is disabled on that system, or maybe power management settings block your processor to work at full performance.

The latest AIDA64 update introduces completely rewritten PhotoWorxx and AES benchmarks, optimized for AESNI, AVX, SSE4.1, VIA PadLock, and XOP capable AMD, Intel and VIA processors. The new AIDA64 release also implements full support for Socket FM2 motherboards, adds optimized 64-bit benchmarks for AMD FX-Series "Vishera" processors, and supports the latest GeForce and Quadro graphics accelerators by nVIDIA. New features & improvements - Revamped PhotoWorxx digital photo processing benchmark with AVX, SSE4.1 and XOP optimizations - Rewritten AES data encryption benchmark with AESNI, SSE4.1 and VIA PadLock optimizations - Optimized 64-bit benchmarks for AMD FX-Series "Vishera" CPU - Preliminary support for AMD "Kabini" APU - Socket FM2 motherboards support - Support for VirtualBox v4.2 and VMware Workstation v9 - Samsung 840 and 840 Pro SSD support - GPU details for nVIDIA GeForce GTX 650 Ti, Quadro K-Series, VGX K-Series What's new since AIDA64 v2.00 - Microsoft Windows 8 RTM and Windows Server 2012 RTM support - OpenCL GPGPU Stress Test - Enhanced UPS support - SensorPanel graphs and gauges - Revamped Desktop Gadget - Optimized 64-bit benchmarks for AMD A-Series "Trinity" APU - Support for Intel Atom "Cedarview" processors - Support for Intel Core "Ivy Bridge" APUs and Intel 7-Series chipsets - Preliminary support for Intel "Haswell" APU and Intel "Lynx Point" PCH - Preliminary support for Intel "Penwell" SoC - VIA VX11 platform, Nano X2 and QuadCore CPU support - Speech API information - ACPI 5.0, APP SDK 2.7, CUDA 5.0, OpenCL 1.2, OpenGL 4.3 support - Intel 330, Intel, 520, Intel 710, OCZ Vertex 4, Samsung 830 SSD support - GPU details for AMD Radeon HD 7000, nVIDIA GeForce 600 Series [ Press Release ] [ What's new in AIDA64 v2.70 ] [ Download ]

Thank you. If it's possible, please turn off Logitech LCD support in AIDA64, and let us know if it makes a difference. Also, if you have any ASRock software installed (e.g. ASRock Extreme Tuner or F-Stream), then please try to uninstall them, to verify if they cause the issues or not. BTW, what version of Logitech LCD drivers and nVIDIA ForceWare drivers do you have installed?

This is not a Windows 8 related issue, but sounds more of an isolated configuration or driver issue. Can you please tell us more about your hardware configuration? Also, are you running Windows 8 RTM Build 9200 64-bit?

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.