Fiery

Alerting is a part of AIDA64 that definitely needs improvement. It should be way more flexible than it is now. We'll work on it later this year, and hopefully we can introduce a revamped Alerting module soon. We're watching this topic, and also the other topics about Alerting-related matters, so make sure to post your experiences, ideas and requests here, and discuss how would you imagine a new Alerting facility in AIDA64. Thanks, Fiery

I understand your frustration about the issues about your computer. It looks like a classic case of PSU (Power Supply Unit) failure. With the new graphics card I guess it worked better because GT610 draws a lot less power than GTS450, especially when the GPU is under heavy load (e.g. GPU stress test in AIDA64 SST - System Stability Test). When you run AIDA64 SST, the most demanding task for most computers is the FPU subtest. It makes the processor to work at full clocks, utilizing Turbo Boost (if supported), and every floating-point processing units are driven to excessive load. It effectively means while running the FPU test your processor will draw the most power through the PSU it is possible. When you enable the GPU subtest on top of the FPU subtest, your GPU is also driven to full load, and so the power draw increases even more. A weak PSU may fail at either the FPU or the GPU subtest, but most definitely cannot stand FPU+GPU subtests combined. Of course, I may be wrong about the PSU issue, so if you have a chance to borrow a reliable PSU from a friend, it may be the best way to further diagnose this issue. There's a slim chance the memory modules are failing, or the motherboard has some weak capacitors, or some other hardware or software flaws occur. But if I had to bet some cash on which component is it, I'd put my money on your PSU I hope this helps. Please let us know about your progress on resolving this issue. Regards, Fiery PS: Don't worry about the fan RPMs. As long as the bottom Throtting graph in AIDA64 SST stays at 0% while running the FPU subtest, your processor is not overheating. While 80 Celsius is quite high, it's not the first thing you need to take care of. First make sure to resolve the restarts and lockups, then you can step on to putting the heat down a bit

Thank you We've fixed the temperature labels, and also implemented support for the CHL8318 chip of your video card. A new special AIDA64 beta is available at: http://users.aida64.com/aida64extreme_build_2073_lightning.zip Please verify all GPU-related readings on the Sensor page. If everything looks fine, then we'll of course roll out these improvements in the next regular AIDA64 beta update, and in the upcoming AIDA64 stable release as well.

Thank you. We've done quite a few test runs using various settings on our LGA2011 systems, but couldn't reproduce the issue. Even when all OSD items, Desktop Gadget items and Logging items were enabled, the clock was still properly measured as 1200 MHz when the system was idle. Maybe on your system there's another monitoring software running which is interfering with AIDA64 hardware monitoring module?

Thank you. We've renamed the 2 new temperatures to match Afterburner readings in the following new special AIDA64 beta release: http://users.aida64....2_lightning.zip If it's possible, please submit a new nVIDIA SMBus Dump, since there was a small glitch in the previous AIDA64 beta about that. We may be able to add more readings for the onboard CHL8318 chip using the dump Thanks, Fiery

Thank you Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...71ky1xzfcthvzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Then please create and send us an updated nVIDIA GPU Registers dump and a nVIDIA SMBus Dump. Please also check if any new readings appear on the Computer / Sensor page.

Thanks for the info. It seems to be the well-known event of low-level hardware calls of AI Suite colliding with similar calls of AIDA64 If you leave AI Suite off your system, it should be fine.

Thanks for Thanks for the info

Thank you. We've checked the dumps, and all 5 fan speeds seem to be properly measured by AIDA64. Are you sure they're not on the Computer / Sensor page? Please note that Opt1 fan speed will be shown as Fan #1 and Opt2 will be shown as Fan #2.

Thank you. If it's possible, please create an I2C Dump using MSI Afterburner too. Steps to do that: 1) Open a Command Prompt 2) Navigate to Afterburner's installation folder, by typing in: cd "%programfiles(x86)%\MSI Afterburner" 3) Create an Afterburner I2C Dump by typing in: MSIAfterburner.exe -i2cdump 4) If you did it properly, then a message box should appear stating "I2C dump has been saved to the application folder". If that's the case, then please send us the I2CDUMP.TXT file you can find in Afterburner's installation folder. 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. Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Thanks, Fiery

It looks like a weird anomaly, so if you could provide more info about your configuration, then we'll try to reproduce the issue on one of our LGA2011 test systems in a hope that we can fix it. Please let us know what Windows version do you have running and what motherboard do you have.

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