Fiery

Then please email it to me at: finalwire AT gmail.com (replace AT with @)

Please rename the file to AAA.TXT, and try uploading it again. Thanks, Fiery

Our order from Am***n hasn't arrived, so we've filed a complaint, and without any word from the seller company, we got a refund. But that still left us without a device So what we came up with is a special test build of AIDA64, that unfortunately leaves the testing on you -- I hope you don't mind Please upgrade to the following AIDA64 Extreme Edition beta: http://users.aida64....asonic_test.zip With this you can disable any of the five USB passthru modules of AIDA64. We suspect that either one of them would be behind the dismount issue. What you need to do is create one or more of the following 5 text files in the AIDA64 installation folder: disable_atapt.txt disable_cypress.txt disable_jmicron.txt disable_oxford.txt disable_sunplus.txt Content of the files is irrelevant, they can be empty files. Whenever AIDA64 detects the existence of any of those files (when it starts up with the splash screen), it will disable the relevant USB passthru module. It will notify you about the disabling by creating a text file in the C:\ folder. Please try to disable the modules one by one, and let us know which one is the culprit But first make sure to enable SMART detection in Preferences / Stability. Thanks, Fiery

We've implemented support for Kaspersky 2013 products and Kaspersky Endpoint Security v8 in the latest beta version of AIDA64 Business Edition and AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64businessbuild2203sqb2lvr9zfzip http://www.aida64.co...03vxqt5pcb3gzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

I'm sorry for the delays, but this improvement didn't quite fit into our development schedule of AIDA64 v2.70. But now we got back to it, and implemented it as a non-GUI option. What you need to do is upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...03vxqt5pcb3gzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Then start AIDA64, go to Preferences, and simply press the OK button, and close AIDA64. Then go to AIDA64 folder, open AIDA64.INI, and scan the file for the following line: HWMonSharedMemName=AIDA64_SensorValues You can edit that line to make the shared memory facility of AIDA64 compatible with plugins made for Everest

Thanks for the feedback

We've tested it with a Logitech G19 keyboard, Windows 8 RTM 64-bit, ForceWare 306.97 WHQL and Logitech Gaming Software 8.35.18, and found no errors at all. Everything works just as well as under Windows 7. When exactly do you get the memory allocation error message?

On your motherboard it may be best to leave that option disabled (not checked).

Then you may want to try adjusting the Intel Burn Test process priority to a lower priority, or raising the priority level of AIDA64 process, to make sure they can work together better.

Support for AVG 2013 has been implemented in AIDA64 v2.70 stable releases. Let me know how it works

What would you make you think you have a voltage issue? I don't see any voltage discrepancies there...

NIC1 and NIC2 may not be the adapters that are connected and driving a network traffic. Try to add NIC3, NIC4 and NIC5 as well to your OSD, to see which one belongs to which adapter exactly.

Please note that AIDA64 itself includes a stress test that can put a very heavy load on the system, including OpenCL-capable video cards. You can check it out if you go to AIDA64 / main menu / Tools / System Stability Test. For maximum processor load, just have the "FPU" subtest enabled. For maximum thermal and power load, only have "FPU" and "GPU" enabled.

Since v2.60 we've fixed a major issue about RSTe support, which was again a driver bug that we had to get around with a workaround. Please make sure to use AIDA64 v2.70.

Are you sure you have only 2 network interfaces? In several systems, even with just one physical NIC in use, there are multiple network interfaces due to e.g. not utilized network ports, not utilized Bluetooth LAN interface, unconnected WLAN controller, etc. If it's possible, please create a TXT report of the Network / Windows Network page of AIDA64, and copy-paste it into this topic, so we can check how many network controllers does your computer have. Thanks, Fiery

The issue may be that latest Intel RSTe drivers tend to go crazy after a while if a software polls SMART information (that includes HDD/SSD temperature readings) via driver calls. AIDA64 uses such RSTe driver calls to gain access to individual member drives of RAID arrays. First of all, make sure upgrade to AIDA64 v2.70 (latest release), then disable both RAID options in AIDA64 / main menu / File / Preferences / Stability, restart AIDA64, and try to run it for several hours. Let us know if it helps. Thanks, Fiery

Are you sure it's a crash? Or maybe it's just that AIDA64 fails to get enough processor time cycles because Intel Burn Test stresses the system too much? Please note that when you're running a stress test, especially if the stress test is running at high priority, there may be issues running other software at the same time.

Have you tried to wait? On Core i7-3900 Series "Sandy Bridge-E" processors it may take over 90 seconds to measure memory latency. Regards, Fiery

There are several tools that motherboard manufacturers and system assembly companies use to fill in DMI tables, but they're not for the general public. You basically need a tool that is suitable for your motherboard, since there're one for old Award BIOS, one for newer Award BIOSes, one for AMI BIOS, one for Intel motherboards, etc. etc. But in most cases DMI information doesn't affect any software or driver, so having it improperly filled makes no difference at all.

For custom gauge state PNG images, there are no restrictions on PNG image size. As for depth ordering, it is decided by the items ordering. You can change the items order using the SensorPanel Manager.

Turbo Boost would help to make scores higher, but even without it, i5-2450M should perform at least equal to a i5-460M. Please verify that all cores are enabled on the i5-2450M system, and HyperThreading is also enabled. Please also right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic.

Such warnings are meant to be short and easy to understand The problem with this particular issue is that it takes several sentences to properly explain what's going on, and what factors may determine the actual amount of system memory the motherboard supports.

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?