Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Then right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery

First of all, make sure to have the latest AIDA64 beta release installed, since we're constantly working on keeping AIDA64 up-to-date and issue-free: http://www.aida64.co...66g3h5xslrdtzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. I guess the reason behind the clock differences may be that you have several entries put to the G19 LCD, and while AIDA64 is collecting those data and readings your CPU switches up to a higher clock speed to finish the job quicker. It's considered normal, but if you don't like how AIDA64 works, even with the latest AIDA64 beta, then please note that you have the option to issue a refund and get your money back. We're trying hard to develop a high quality product, but it may not be satisfactory for all PC users and usage scenarios out there Regards, Fiery

I'm not sure if this is what you're looking for, but you can switch page1 and page2 in the AIDA64.INI file (located in AIDA64 installation folder). You can edit that file using Notepad (make sure to close AIDA64 before doing that). Scan the file for the following 2 lines: HWMonLCDItemQ1=... HWMonLCDItemQ2=... And alter them by switching Q1 and Q2. So the beginning of the lines after altering them would look like this: HWMonLCDItemQ2=... HWMonLCDItemQ1=... BTW, "Q" there means QVGA display, so Logitech G19 Regards, Fiery

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2066g3h5xslrdtzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Thank you. We're currently working on fixing a series of bugs related to Windows 8 RTM. I'll soon post a link to a new AIDA64 beta release into this topic Regards, Fiery

You can already do that on the SensorPanel, OSD Panel, Desktop Gadget, Logitech LCD. We currently have no plans to enable such feature for the Sensor page. Regards, Fiery

It's already under development

Maybe, sometimes in the future

Thanks for the feedback. Even if other software reads "a value" as VBAT, it doesn't make it a valid reading if your motherboard doesn't seem to measure that voltage rail.

We've fixed the sensor readings for Gigabyte B75 boards in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2063yt8p6wrjlmzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've fine-tuned the PCH temperature measurement in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2063yt8p6wrjlmzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. As for VBAT voltage, AFAIK your motherboard is not capable of measuring that. You can verify that by checking out the PC Health Status page in the BIOS Setup, or the voltage readings in Gigabyte EasyTune6. Thanks, Fiery

Please copy-paste the full content of the Computer / Sensor page into this topic. Then 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

I'm sorry, but we cannot download from that address. Can you please tell us more about your system? Motherboard model, CPU type? Thanks, Fiery

Generally speaking, those temperatures look a bit high, but most mobile systems tend to run very hot under heavy stress due to their compact chassis. No throttling activity detected, so the CPU could stand the test without overheating. And GPUs can generally work at much higher temperatures than CPUs, so it is fine as well. No worries Regards, Fiery

Thank you for the info. It will help other users encountering similar issues with SanDisk SSDs.

I suppose it's because AIDA64 is unable to read DMI tables from BIOS when EFI boot is used. AIDA64 implements several methods to do that, but maybe on your system in EFI mode all of them fails to provide the right DMI tables. In such case AIDA64 will revert back to reading DMI tables from the classic BIOS range (F000 segment). And even though EFI systems use emulated classic BIOS segments, they sometimes forget to update the BIOS date and BIOS version there. If it's possible, please submit 2 reports from AIDA64 (main menu / Report / Submit Report To FinalWire), one in EFI boot mode, the other in legacy boot mode. At the report submit make sure to put your forum nick name into the Name field, and "code65536 BIOS date issue" in the Comment field. Please also indicate in the Comment field which boot mode was it for. Thanks, Fiery

We've further improved CPU clock measurement and fixed various small issues about Windows 8. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2108tcgh5wb1qjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let us know if you find any issues while using AIDA64 under Windows 8.

Yes, it's still under consideration, but as I've said, putting anything dynamically on the SensorPanel is not easy, especially when it is a hovering bubble. We don't think a static place to display such information is a good idea, but a hovering bubble would be best. Coming up with a proper rendering solution for that is a true challenge, since it would have to be indepent of the regular SensorPanel updates. For example, if you configure a 5 seconds update frequency for the SensorPanel, the hovering bubble has to be updated between 5-second panel updates to make it "smooth". We'll work on it, but right now we're inundated with things to do about the next AIDA64 stable release

It's a tech preview, so it's too early to judge what it would become. Once Microsoft makes that tool a part of Windows (either by default installation or part of a Service Pack or as a hotfix), we'll add it to the Windows Security page. Thanks, Fiery

Thank you

We've implemented support for Asetek liquid cooling based systems in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2056njgtfy1xmrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Please note that our solution requires you to have ChillControl installed, but not running. Unfortunately the USB driver ChillControl installs and uses doesn't allow sharing the cooling device between multiple applications, so AIDA64 can only monitor the device when ChillControl application is not running; and ChillControl can only monitor the device when AIDA64 is not running. We'll try to come up with a better solution, but driver limiations may stop us finding a more useful way

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...56njgtfy1xmrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Please consider Gigabyte's own hardware monitoring application (EasyTune) as the reliable reference. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2056njgtfy1xmrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

GPU temperature is fine, but CPU core temperatures look a bit too high. If it's possible, try to improve the cooling of your CPU, or the exhaust ventilation of your system case. The latter should help to lower both the GPU and CPU temperature.

You may want to try the AIDA64 Logging feature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging) to record your GPU temperatures (so as other temperatures and voltages) into a HTML file while playing games. That may give you an idea on what are the maximum temperatures your video card reaches, and whether it is normal or too high. A slowdown in FPS sounds quite odd, but an overheating video card may explain that...