Fiery

Koolance provided us the necessary programming documentation, so we could implement shared memory support in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1224q0sln8yrvxzip 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 fixed the sensor readings for Sabertooth X58 motherboard in the following new beta version of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1224q0sln8yrvxzip 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 implemented sensor tweakings for Asus P8P67 boards in the following new beta version of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1224q0sln8yrvxzip 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 implemented sensor tweakings for Asus P8P67 boards in the following new beta version of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1224q0sln8yrvxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. I'm not sure what you mean. Can you please show it to me on a screen shot? Thanks, Fiery

Thank you, we've added those monitoring in the following new beta version of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1224q0sln8yrvxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

I think the differences comes from the fact that the Physical Drives page enumerates drives using Windows driver database calls, while the Hardware Monitoring module (incl. OSD, Sidebar, LCD features) enumerates drives using ATA autodetect calls. I guess Windows driver database truncates the HDD model number, and that's why the last character is missing there.

As far as we know, Crucial C300 SSD drives don't support temperature monitoring. Let's hope in RealSSD C400 drives they will add that feature

We asked Koolance for help about implementing shared memory support in AIDA64 on Dec-27, but got no reply from them yet. We've resent the inquiry email today, and hopefully this time it will go through. (Hungarian is indeed a very tough language, so no need for excuses )

We don't know about Corsair C300 SSD family. Do you mean Crucial RealSSD C300? Or maybe you meant Corsair Performance 3 Series? Either way, if the SSD has a SandForce controller, then the controller itself does support temperature monitoring. But it still requires hardware implementation and firmware support. AIDA64 itself supports temperature readout on any SSDs, but most SSDs simply don't implement temperature monitoring in their hardware or firmware.

We've tested it with ForceWare 266.35 and GTX295, under Win7 64-bit SP1 RC. We've found no issues at all. Please try it with the latest WHQL ForceWare driver as well, or try to re-install ForceWare 266.35. Also, you may try to switch the option "nVIDIA GPU SMBus access through nVIDIA ForceWare" in AIDA64 / main menu / File / Preferences / Stability.

Can you please provide us the full model number of that monitor? Something like 2043BW, 2043N. Thanks

That seems like a ForceWare issue, and not an AIDA64 bug. Have you tried with the latest WHQL ForceWare driver? Have you tried ForceWare 266.44? BTW, what version of Windows do you have installed? 64-bit Windows 7 SP1 RC?

Thank you for the feedback, we're glad it works fine now.

AIDA64 doesn't use the mentioned DLL at all, and it doesn't use SQL Server services. It may use a driver or another DLL that depends on those services though, so we need to investigate this to provide you a proper answer (and hopefully a fix too). Please let us know more about your system: 1) Notebook model? 2) Windows version, kernel type (32-bit or 64-bit), Service Pack applied? 3) Any external disk drives (USB, eSATA, FireWire) connected? Thanks, Fiery

Thanks. Does the exception come up if you simply start AIDA64 with no hardware monitoring features (so Sensor Icons, LCD, OSD, Sidebar, Ext.Apps) enabled?

We have the same development team. You seem to be reporting issues that noone else finds, so I suspect it could be due to either some pecularity with your system configuration, or an extreme overclocking, or due to improper drivers installed, or ... I have no idea

Thank you for the feedback!

For Sandy Bridge processors, yes. For Asus P8P67 motherboard sensors, not yet I'm afraid.

Thank you for your feedback Unfortunately most SSD on the market today are unable to measure disk temperature Even the ones where the controller supports temperature measurement (e.g. SandForce controllers), sometimes the hardware implementation lacks the diode, and/or the firmware doesn't support temperature readout

Yes, feel free to post them all into this topic We'll then add them to the AIDA64 monitor database.

Thank you for the feedback.

AIDA64 follows industry standards by reading SMART attributes (incl. disk temperature attribute) via standard Windows API calls just like any other Windows software. In case WD implemented the power-saving features (the head parking) in a way that the head unnecesserily moves everytime the SMART attributes are read from the drive, then IMHO it is a serious hardware implementation flaw that should be fixed in a form of a firmware upgrade for the affected WD Green drives. However, the LCC can be minimized if you could adjust the polling frequency for the SMART disk temperature readout, hence we've decided to implement a new option in AIDA64 to help you fight the LCC issue easier. The polling rate is default 20 seconds, but you can raise it all the way up to 3600 seconds (1 hour) in 1 second increment. You can adjust the disk temperature polling frequency in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Note: If you raise the polling frequency too much, AIDA64 will be able to detect a potential disk drive overheating situation much later than when it actually happens, so make sure to try to find a balance between 20 seconds and 3600 seconds Thanks, Fiery

I'm sorry for the delays. It took us a while to come up with a -- hopefully -- proper fix for the startup delays, and to thoroughly test it on multiple nForce RAID configurations. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip 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 implemented support for the new JMicron RAID drivers in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

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