Fiery

We've added a new option (Wake GPUs up at AIDA64 startup) to the AIDA64 Preferences / Stability page, in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2746bhv2s4qfjlzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Try to enable that option to make AIDA64 pick up the sleeping HD8750M dGPU. Let me know how it works.

We've improved the SMBus communication module of AIDA64 in order to avoid collisions with Synaptics SMBus touchpads. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2746bhv2s4qfjlzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

We've added a new option (Enable disk temperature measurement) to the AIDA64 Preferences / Hardware Monitoring page. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2746bhv2s4qfjlzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it suits your needs

We've just fixed a few more issues that may explain the crashes on your system, so please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2746bhv2s4qfjlzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you for letting us know about the resolution. Regards, Fiery

I'm afraid Office 2013 Home & Business does not seem to store the product key on the local machine, so AIDA64 cannot extract it and show it to you Regards, Fiery

I'm afraid Office 2013 Home & Business does not seem to store the product key on the local machine, so AIDA64 cannot extract it and show it to you Regards, Fiery

Synaptics SMBus touchpads seem to use the SMBus protocol of Intel chipsets in a way that it collides with 3rd party monitoring applications like AIDA64. Synaptics promised to implement a workaround for that in their latest drivers. We'll check the latest drivers, whether it is already implemented, and get back to you with guidelines on what to do to fix this up. Please provide us a few days

I think only the fan needs to be changed. Prices can heavily depend on the availability of replacement parts, I cannot quote you that I'm afraid

The isse will be fixed in the next AIDA64 beta release We also made some improvements in Beta 2742, but the (hopefully) final fix will only come in the next beta after that.

Thank you. Does the HD8750M show up on the following pages in AIDA64? - Display / PCI/AGP Video - Display / Windows Video - Devices / Windows Devices

Are you sure your CPU is not throttling due to overheating? What FPU Julia score do you get at stock settings? (without applying any overclock)

1) What's the model of your notebook? 2) Please try the following, and see if it helps: - close AIDA64 - start AIDA64 - go to the Display / GPGPU page, click on every OpenCL devices in the list, one after the other - go to the Display / GPU page Let me know if it makes the HD8750M GPU appear on the Display / GPU page. Thanks, Fiery

1) If you push the arrow pointing up there, will the icon appear? 2) Are you using AIDA64 v4.00?

Thank you for the feedback

The ATA spec treats the ECC bytes field obsolete for over 15 years now, so it's not since the previous spec release

Thank you for the feedback

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2736cp8ntw1rdszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps Thanks, Fiery

We've done a few test runs with various GeForce cards, and it seems GPU clock gets stuck at 3D rates only when you keep the AIDA64 System Stability Test running and just untick the GPU subtest. That keeps the OpenCL context still open, although not executing any OpenCL kernels (computing tasks). In such case ForceWare keeps the GPU running at high clock speeds for whatever reason, and only lets the clocks drop down to power saving (low) rates when you press the Stop button on the System Stability Test window. That's because when you push the Stop button, AIDA64 closes and invalidates the OpenCL context. While AMD Catalyst drivers vary GPU clocks based on actual GPU load (utilization), ForceWare drivers seem to work based on OpenCL/Direct3D/OpenGL contexts. That's just a different approach, although quite frankly we would prefer to have drivers all work by GPU utilization

AIDA64 isn't really geared towards making an inventory of special networked devices like TVs, amplifiers or DVD/Blu-ray players. We may work on that later on, but it's not on our short-term roadmap right now. Regards, Fiery

Thank you for your kind words. We keep optimizing and improving the G19 support, so make sure to use AIDA64 v4.00 (latest release), where it consumes less CPU cycles to refresh/update the G19 screen. Regards, Fiery

I suppose you mean the Used Video Memory and Free Video Memory hardware monitoring items. Yes, they're available on e.g. the OSD Panel, but those items aren't available on a per-GPU basis, and they're only available on nVIDIA GPUs. Those items should be there on your 750M as well, as long as ForceWare is properly installed.

It seems the latest ATA specification (and a few preceding revisions as well) treats the ECC bytes register field as obsolete. We'll remove that information from AIDA64 to avoid confusion. Thanks, Fiery

Since Vista Windows virtualizes video memory spaces, so it's not possible to detect or measure free video memory size. It is still available under old Windows releases (Windows XP, Windows Server 2003 and Windows 2000). Regards, Fiery

You can use ALT+T to stop the test Regards, Fiery