Fiery

If the new beta works out, then you won't need to upload the dump file. If it will still produce the same issue, then we'll check what goes wrong about the file upload

We've implemented a fix for the Intel RAID array enumeration the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2208x6wkg7ntyhzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps to get rid of the BSoD issues

I guess the easiest way is to restart AIDA64, go to the Storage / SMART page, and refresh it a couple of times (you can use the F5 key to refresh a page). Then close AIDA64 and restart the whole process again. The most USB-ATA bridge communication is done at AIDA64 startup, and when you refresh the SMART info.

1) You don't need Everest anymore 2) You only need the new AIDA64 beta: http://www.aida64.com/downloads/aida64extremebuild2320tjb6lpwyzxzip 3) Start the new AIDA64 beta, go to Preferences, but only press the OK button there. Then close AIDA64 4) Go to AIDA64 folder, and find the file called AIDA64.INI. You need to edit that file, using e.g. Notepad 5) Inside the AIDA64.INI file you need to change the line: HWMonSharedMemName=AIDA64_SensorValues In that line you need to change AIDA64 to EVEREST to make the new AIDA64 compatible with AlphaCool. So the line should look like this: HWMonSharedMemName=EVEREST_SensorValues I'm afraid I cannot use better or more basic English than this

Please do NOT use the RAID Dump, since it would still scan all devices using all methods, regardless of the disable facility. It's up to you which method do you try. I'd start with all disabled, and try that first. If it's stable, then I'd try to enable them one by one, so in 5 steps I'd get to the "everything enabled" state. If you find a problemous one, please note it down, but continue the testing, since there's a slim chance multiple methods cause the same issues in the USB-ATA bridge chip. Thank you for your time.

I'm sorry, but I cannot phrase that more clearly in English, I really did my best to make it clear. Please use Google Translate to translate it to your native language.

It's absolutely not recommended to have the low-level register access when AI Suite is installed, since it would cause various issues, e.g. fan alerts (when they are spinning fine), system lockup, voltage delivery issues, etc. AIDA64 automatically detects AI Suite, and when it is installed, AIDA64 will use the AI Suite method based on ATKEX calls.

Here's a PDF document that covers various methods to set up AIDA64 Business Edition in enterprise networks to compile software and hardware audits: http://www.aida64.com/files/AIDA64_Business_Edition_Setup_Guide.pdf

Here's a new document that describes various methods to collect network audit using AIDA64 Business Edition: http://www.aida64.com/files/AIDA64_Business_Edition_Setup_Guide.pdf

Good idea, we'll check how can it be done, and will post updates to this topic. Regards, Fiery

Try to compress the files into a ZIP or RAR package, and then attach it to your post.

Please let me know if you experience any issues about AIDA64's SMBus protocol. We are not responsible for any anomalies you have in someone else's software Regards, 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.