Fiery

It seems Win8 Release Preview Build 8400 has fixed this issue.

I'm afraid I cannot provide you with a full source code for the ACPI query module of AIDA64, but I can give you a few key words for API calls and other portions, so you can use Google and MSDN to try and build it up. IoGetDeviceObjectPointer IoBuildDeviceIoControlRequest IOCTL_ACPI_EVAL_METHOD KeInitializeEvent KeWaitForSingleObject Regards, Fiery

Then to you too: please let me know what settings do you alter in the Preferences so frequently that you need such menu item for convenience Because if you need to use the Preferences several times a day, then maybe moving some option(s) from the Preferences to a place that is easier to access may be a good idea for an improvement.

Can you please check how many subpages of the Windows Network page do the "Bytes empfangen" and "Bytes gesendet" lines appear properly? Does it match the 4 NIC items on the OSD items page?

We try to not add many more items to the AIDA64 System Tray context menu to make sure it is kept simple and easy-to-use. Please let me know what settings do you alter in the Preferences so frequently that you need such menu item for convenience. Thanks, Fiery

1) We'll fix that in the next AIDA64 beta update due later this week. I'll drop a message into this topic once the new beta is available. 2) We've changed the rounding logic for fan duty cycle values in AIDA64 v2.50. Before that, duty cycle was rounded down by simply omitting the fractional part of the value. So in AIDA64 v2.30 both 30.2% and 30.9% were rounded down to 30%. In AIDA64 v2.50 we use math rounding, so 30.2% now becomes 30%, but 30.9% now rounded to 31%. I'm afraid ForceWare drivers use the wrong logic for rounding, so now AIDA64 v2.50 shows the correct values, but they sadly don't match ForceWare values IMHO it's actually nVIDIA who has to fix the rounding logic in ForceWare, but in order to avoid confusion we'll adjust AIDA64 (in the next beta update) to match ForceWare values.

Thank you for reporting about that issue. It will be fixed in the next AIDA64 beta release. I'll drop a message into this topic once the new beta is available. Regards, Fiery

How many network adapters do you have? You can check them on the Network / Windows Network page. Is the WLAN adapter among those network adapters? How many network adapters are listed among the hardware monitor items? For example: NIC1 Download Rate, NIC2 Download Rate -- means 2 adapters detected by the hardware monitor module. Thanks, Fiery

No, it's not possible. And we'd prefer to stay away from trying to fix the limitations of HDD firmwares. We've already implemented the disk drive polling option.

Transparency key color is a very basic (and old-fashioned) way of transparency that doesn't look great. What you need is an alpha-channel based transparency. Our forum works well right now. Maybe it was a temporary issue. Regards, Fiery

Corsair let us know that once a SSD is turned into a cache drive, it can no longer be detected or diagnosed by a Windows software or Windows itself. There doesn't seem to be a way to get around that limitation I'm afraid

The latest AIDA64 update extends the SensorPanel module with graphs and gauges, adds a new Speech API information page, and implements full support for the complete nVIDIA GeForce 600 GPU family and the latest generation Intel and OCZ SSD drives. New features & improvements - Speech API information - SensorPanel graphs and gauges - Intel 330 and OCZ Vertex 4 SSD support - GPU details for nVIDIA GeForce 600 Series What's new since AIDA64 v2.00 - OpenCL GPGPU Stress Test - Enhanced UPS support - Revamped Desktop Gadget - 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 - ACPI 5.0 and OpenCL 1.2 support - Intel 520, Intel 710, Samsung 830 SSD support - GPU details for AMD Radeon HD 7000 Series [ Press Release ] [ What's new in AIDA64 v2.50 ] [ Download ]

Everything looks normal for a mobile computer. I'm not sure what could cause the shutdowns while gaming. It may be a hardware issue, or a power supply logic failure. Or, it may as well be a software error or Windows configuration problem. You may want to try updating your drivers and the game itself too.

Thank you for the feedback

Domain is identified on the Operating System / Operating System page in AIDA64. You can see the network structure and identify the workgroups on the Network / Net Resources page. Regards, Fiery

Thank you for the info. AIDA64 GPU stress test module is based on OpenCL, and it doesn't use any low-level code or special tricks. Hence, if it has a conflict with another software or module, any other applications utilizing OpenCL GPGPU capabilities may have the same conflict.

That looks okay to me. Please note that playing a game may put a different sort of stress on the system that it may not stand. You should simply enable logging in AIDA64, play some games, and once your computer powers off, check the log file for maximum temperatures or other anomalies. If you log voltages as well, you could watch for unusual drops or spikes on voltage rails.

The graph that jumped up to 100% is the CPU Usage graph. You need to watch the other, green graph.

Correct, on both. Yes, they look good. If that happens again, just let me know in this topic the highest temperature values you got for CPU, motherboard, GPU and HDD. Alternatively, you can try running the AIDA64 System Stability Test (AIDA64 / main menu / Tools / System Stability Test). If you want to stress your system for overheating, then only have the "FPU" subtest enabled, and disable the rest of the tests. Then push the Start button, and watch the temperatures climb. If the Throttling graph (in the bottom graph) shows anything other than 0% value, then your CPU is overheating. Let the stress test run for at least 15 minutes.

You have to enter a filename in the first edit field Example: C:\MYLOG.HTM

Thank you, but it looks like you've submitted the ISA Sensor Dump twice, and so no SMBus dump was submitted

In that scenario the best would be to enable the Logging function in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. It will create 2 log files, one for all readings, and another one for statistics (minimum / maximum / average values). Regards, Fiery

Thank you for the feedback

Thanks for the feedback

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