Fiery

We'll soon completely drop all current memory benchmarks, so that issue will automatically solve itself

Yes, it's normal on Sandy Bridge-E and Sandy Bridge-EN/EP processors. We use a wide scanning range for the memory latency benchmark on those processors to make sure we can "hit" on the best latency score with all possible memory configurations (single-channel, dual-channel, triple-channel, quad-channel).

If you use the Sensor Item item type (and not the Simple Sensor Item), then it's quite easy: you just need to use the same width for the whole item, and also the same width for all units. It will then be perfectly aligned. Please note that unlike the Sensor Icons, OSD Panel and Desktop Gadget features of AIDA64, with the SensorPanel it takes a bit more efforts to achieve the looks you want to see. But it worth the efforts, because with the extremely flexible SensorPanel you can do a lot more than with the mentioned other AIDA64 features.

Please avoid opening multiple topics for the same issue. I've replied in your other forum topic. This topic is closed.

That's how it should look like, to make sure the text fits the icon area. As you can see, on the right-hand side the text doesn't fit in the Everest sensor icon: it's the wrong way to display the text there I suppose the visual distortion is caused by a non-standard DPI setting you applied. Is that the case?

Thank you for the data. I think everything's fine there actually. The Overclock page shows not the Vcore reading, but the CPU VID setting which stays intact even if you raise the Vcore.

In a virtualized environment there's no way to access the underlying host hardware, but only the virtualized hardware. So you need to run AIDA64 natively in order to monitor the thermal status and SMART details of your "real" hardware components. Regards, Fiery

Do you mean a voltage reading called "PCH Core" ? If yes, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full resuls into this topic. Thanks, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Thanks, Fiery

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Also, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. If it's possible, please do those at both default Vcore and at 1.5V (overclock voltage). Make sure to use the latest AIDA64 beta. Thanks, Fiery

In order to avoid log files getting too large, logging is restarted after 24 hours of logging, and so a new log file is opened. If your log file still gets too large in 24 hours, you may want to make update frequency a bit longer. With a 1-second logging rate log files can indeed get a bit huge Alternatively, you can also check if the large log files can be opened better with another browser, e.g. Chrome or Safari. Regards, Fiery

Green line means a process is started, and the red line means a process is finished. If you don't like those lines, you can turn off process logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging / Log started and stopped processes. Regards, Fiery

Windows Gadgets have been removed from Windows 8 by Microsoft, because now they want to push "Metro" (or "Modern") style applications instead. I'm afraid AIDA64 cannot put that feature back into Windows 8 However, you can actually configure the SensorPanel to make it look exactly like a Windows Gadget, so we do not feel the lack of Gadgets a real issue about Windows 8. Regards, Fiery

Usually activating ACC (Advanced Clock Calibration) causes such anomalies. It's unfortunately completely normal, and it's due to a hardware limitation of AMD processors. You could see the same zero temperature readings in other software as well. BTW, ACC is used for e.g. unlocking disabled cores of AMD processors Regards, Fiery

Thank you for the tests. Do you know if there're other USB boxes with the similar VIA VL700 chipset? It would be great if there were alternative device choices, since ordering this particular drive from here seems to be a pain Most retailers refuse to ship items here, and the one that said it would -- well, you know the story already

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