Fiery

We've fixed the LCD blanking issues at Windows shutdown, system restart, sleep and standby. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3110hdscrnq9zvzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

We've performed many test runs, and were able to reproduce the issue on our own test systems. As it seems, the stress testing module doesn't always report about a revealed hardware flaw to the main AIDA64 application before stopping the stress test. In such case the System Stability Test session keeps going, but the CPU utilization graph drops to 0%. We're already working on the fix, but it will take a week to properly implement and evaluate the fix before we can roll it out in a new AIDA64 beta update. I'll post a message into this topic once the fixed AIDA64 update is available for download.

We've performed many test runs, and were able to reproduce the issue on our own test systems. As it seems, the stress testing module doesn't always report about a revealed hardware flaw to the main AIDA64 application before stopping the stress test. In such case the System Stability Test session keeps going, but the CPU utilization graph drops to 0%. We're already working on the fix, but it will take a week to properly implement and evaluate the fix before we can roll it out in a new AIDA64 beta update. I'll post a message into this topic once the fixed AIDA64 update is available for download.

Razer doesn't have to develop anything, since AIDA64 v4.60 (latest version) already implements full native support for Razer (and many other) LCDs

AIDA64 supports such controllers like Koolance TMS and T-Balancer, but it doesn't support any PCI cards using such facilities. Are you sure the Bitfenix Recon is a PCI card? If yes, then does it offer any SDK or software API that AIDA64 could connect to?

That is unfortunately a known issue of Asus AI Suite software components. We've asked Asus a number of times to do something about it, since it's their software's fault that it fails to implement the industry standard synchronization techniques that would assure their software could side-exist with other monitoring and tweaking software like AfterBurner, AIDA64, CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, Rivatuner, SIV, SpeedFan, etc. All those listed software are in sync with each other, but Asus wouldn't wanna "join the show", no matter how many of those software authors would ask them...

1) What does AIDA64 display on the main menu / File / Preferences / Hardware Monitoring / LCD page, with either green or red colour? 2) What version of AIDA64 are you using? Thanks, Fiery

Yes, you can do that.

You can use the AIDA64 ACPI Browser to extract various ACPI tables and save them to file. However, the ACPI Tool is only available in AIDA64 Engineer and AIDA64 Business, in main menu / Tools / ACPI Browser. Regards, Fiery

AIDA64 follows Intel's DTS specification on TJMax auto-detection. If you believe the automatic value is wrong, you can adjust TJMax in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Regards, Fiery

Maybe those listings do not appear for you because the seller limited the geological availability of the items? I never sold stuff on eBay, so I'm not sure if it's possible to do that. Anyway, if you want to buy one, I can try reaching out to the seller to ask what's the procedure of selling it to you. As for Crystalfontz, your displays will soon be fully supported. CFA533, CFA631, CFA632, CFA633, CFA634 and CFA635 displays with a USB connector (or FTDI RS232 --> USB converter) will be supported first by AIDA64, and then CFA735 and CFA835 will come in the next round. Later on we may add support for RS232 (serial) Crystalfontz and Matrix Orbital devices as well.

Here's the eBay item for a Pearl AX206 already firmware-hacked LCD: http://www.ebay.com/itm/lcd4linux-6-1-cm-2-4-Display-DPF-Coolstream-Dreambox-Enigma-Pearl-Linux-HD-/251599797594?pt=DE_Foto_Camcorder_Digitale_Bilderrahmen&hash=item3a94843d5a We've ordered one from him a few weeks ago. BTW, what kind of Crystalfontz displays do you use, and with which software? Do you have multiple displays connected to a single computer? I'm just asking, because we'll soon implement support for Crystalfontz LCDs as well

It sounds a bit odd. Are you shutting down Windows, or putting the computer to sleep or standby or hibernation? And what motherboard and Windows do you use? We'll try to reproduce the issue on a similar test system if possible.

AIDA64 is supposed to turn all LCDs off when it exits. Not all LCDs support that feature, but AlphaCool does. What happens on your computer when you close AIDA64?

I'm not sure why the AX206 display would have to sold locally in the States for you to purchase it. You can order one from overseas, and pay a little customs tax, and use it happily with AIDA64 GOverlay may cost little money, but its capabilities are also heavily limited. You can get one, but when it comes to what you can achieve with the AIDA64 LCD module, an AX206 display would simply blow it away. The GOverlay display should really have a much more advanced firmware, at least as sophisticated as the one for the Matrix Orbital GTT. You can't even use a background image on the GOverlay, not to mention many other important visual elements. As with the GTT, AIDA64 will support all display sizes, as long as they are in the GTT Rev2 family. So GTT35A, GTT43A, GTT50A and GTT70A will all be fully supported. The old GTT480272A and the discontinued GTT57M are not validated by us, but they may still work properly. However, please note that the GTT protocol doesn't support a few features that AIDA64 would want to use for rendering, e.g. it doesn't support bold or italic font styles at all. Also, when you use a lot of dynamically changing elements, especially graphs and gauges, rendering may take several seconds on those non-directly addressable devices (GTT, 4D Systems, LCDsysinfo). So while those displays look great and feel like a proper external display, their use is not so convenient and could be very limited. It's always best to use a directly addressable display, for them the only issue could be the slow update rate -- but usually it's in the acceptable range of between 100 and 500 milliseconds. BTW, in the not so far future we'll also implement support for Samsung SPF digital photo frames as well. Maybe those things will be easier for you to find locally.

For a Core i7-740QM notebook those temperatures at idle are a bit high, but having C3/C6 disabled may cause such difference. For mobile computers it's mostly not the thermal paste that should be reapplied, but the exhaust ports of the notebooks chassis that should be cleaned. After 2 or 3 years of abuse, such exhaust ports could be filled with dust from the inside. And in many cases it's hard to decide from an outside visual inspection how much dust is collected on the inside of the exhaust port.

Here's the new AIDA64beta that I've mentioned in my previous post: http://www.aida64.com/downloads/aida64extremebuild3104t4gjsw2khpzip

We've already got both the original LCDsysinfo and the newer LCDsysinfo for GOverlay. Problem with those devices is that they're one of the few rare LCD/VFD displays that do not support direct addressing. When I use the term "direct addressing", I mean that you cannot draw individual pixels on the 320x240 display, and you also cannot put a simple full-screen bitmap (or a smaller bitmap) on the display. So with those displays you cannot use the regular LCD module of AIDA64, since that is designed to work in a way that: 1) AIDA64 first collects the items you've defined using the LCD preview (AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items) 2) It then renders all items individually in the memory, in a bitmap back-buffer, in an order that you've defined in #1 3) And finally, it sends the bitmap from the memory buffer straight to the LCD device, using the LCD's own API, which is usually a pre-defined set of USB or HID commands. And when a display doesn't support displaying a bitmap, that whole thing simply cannot work. Now, there are a number of displays that use either a cost-effective hardware solution (like LCDsysinfo displays), or designed in a way that it must support low-speed connections like RS232, Parallel or I2C (like Matrix Orbital and 4D Systems displays). With such displays you cannot display a bitmap, but you can use various commands to draw things on the LCD, like line, rectangle, filled rectangle, circle, ellipse, and write text. While it may sound quite convenient to use such commands to achieve the same layout that you can design with AIDA64 LCD preview, due to the fundamental differences between those protocols (LCDsysinfo, Matrix Orbital GTT, 4D Systems), it takes a lot of time to develop an alternative rendering technique, specific to a particular display model. We're planning to work on LCDsysinfo for GOverlay and 4D Systems, but first we want to finish up the already half-done Matrix Orbital GTT rendering path. We may not get to fully supporting the original LCDsysinfo though, since it is quite a basic protocol, with certain capabilities that are closer to the alphanumeric displays than to the graphical displays. If you're looking for a 320x240 small colour LCD with USB connection, that also supports direct addressing (and so is directly and fully supported by AIDA64 LCD module), I suggest you to check out the AX206-based firmware-hacked DPF (Digital Picture Frame) LCDs, like the one made by Pearl. You can purchase them, with their firmware already hacked on eBay, just search for: lcd4linux Pearl or lcd4linux LCD More information on AX206 DPF hacking: http://picframe.spritesserver.nl/wiki/index.php/DPF_with_AppoTech_AX206 http://bastel.dyndns.info/~dockstar/lcd/ http://sourceforge.net/projects/dpf-ax/ http://www.zebradem.com/wiki/index.php?title=Lcd4linux http://www.oli82.de/blog/?p=600 http://openschemes.com/2011/08/23/our-turn-with-the-ax206-digital-photo-frames/ The next AIDA64 beta (due in 1 or 2 days from now) will implement full support for such AX206-based hacked DPF LCDs. The only trick is that they do not come with a Windows driver, so you either have to patch an existing LibUsb0-based Windows driver, or ping me in private message and I'll send you the driver that we've made for our Pearl AX206 DPF. The driver will work with any other AX206-based firmware-hacked DPF device. The mentioned very next AIDA64 beta will also support the following new LCD and VFD devices BTW: - Acer Idea 500 VFD - ct-Mausekino LCD - Cwlinux LCD - picoLCD - SoundGraph iMon LCD (iMon UltraBay) - Sure Electronics LCDs - Trefon LCDs

I'm glad you managed to fix it. Thank you for letting us know about the resolution.

If it's possible, please try to make a photo of how the LCD screen looks like when AIDA64 tries to initialize it. Attach the photo to a post here, or you can send it to me in email as well. If you prefer the email, please drop me a private message.

Are you sure you've got all cores of your CPU enabled, and accessible by Windows and AIDA64? We can verify that if you could post a CPUID & MSR Dump. Right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic. Thanks, Fiery

We've already got a correction feature in AIDA64 (main menu / File / Preferences / Hardware Monitoring / Correction) to let you correct/adjust the sensor readings by using a ratio and/or an offset.

Please try to do the following: 1) Close AIDA64 2) Disable the AIDA64 kernel driver by renaming the file KERNELD.X64 in AIDA64 installation folder to KERNELD.X64_ 3) Restart Windows 4) Start AIDA64 5) Verify if the kernel driver is really disabled by checking the CPU multiplier and FSB on the Motherboard / CPU page. If the information is not shown there, then the kernel driver is disabled 6) Start the benchmarks, and check if there's a BSoD now. Let me know how it goes 7) Don't forget to rename the file back once the test is done Thanks, Fiery

What we've just rolled out with AIDA64 v4.60 is only the first wave of new LCD and VFD devices. If you consider interface, protocol, controller and all other variables, there are literally hundreds of different LCD/VFD devices out there. We're already working on a number of new devices (Acer Idea 500, AX206-based firmware-hacked DPF, ct-Mausekino, Cwlinux, Futaba MDM166A, picoLCD, SoundGraph iMon UltraBay LCD, Sure Electronics, Trefon, Yoctopuce, etc) that will be added during the next few weeks, and then a lot more is coming. We're collecting ideas on which displays to support next, so feel free to let us know what display you've got, or what display you want to see being supported by AIDA64. Make sure to state display manufacturer, display model, interface (USB, serial, parallel, I2C, etc), and if possible, show us the device you've got by posting a link to the product page or a hardware review. If your unsupported LCD/VFD uses USB connection, please post a USB dump of it: right-click on the bottom status bar of AIDA64 v4.60 --> System Debug --> USB Dump. Copy-paste the full results into this topic. Regards, Fiery

What we've just rolled out with AIDA64 v4.60 is only the first wave of new LCD and VFD devices. If you consider interface, protocol, controller and all other variables, there are literally hundreds of different LCD/VFD devices out there. We're already working on a number of new devices (Acer Idea 500, AX206-based firmware-hacked DPF, ct-Mausekino, Cwlinux, Futaba MDM166A, picoLCD, SoundGraph iMon UltraBay LCD, Sure Electronics, Trefon, Yoctopuce, etc) that will be added during the next few weeks, and then a lot more is coming. We're collecting ideas on which displays to support next, so feel free to let us know what display you've got, or what display you want to see being supported by AIDA64. As for Crystalfontz, they've got a number of different protocols, and we'll support all their USB products soon. I've taken notes on which model you've got, and once it's implemented in AIDA64, I'll post a message into this topic so you can try it out and report back whether it works on your LCD. BTW, the current AIDA64 LCD/VFD module supports brightness and contrast adjustment on such displays that are capable of those adjusments. It also supports polling keypads attached to a display, so you can rotate between the four LCD pages using the keys. Handling the knob of SoundGraph iMon displays is not supported yet though. LED signalling is not supported on any displays at this time. Please let me know what would you like to signal via the LEDs. Also, if possible, please post a USB dump of your CrystalFontz display: right-click on the bottom status bar of AIDA64 v4.60 --> System Debug --> USB Dump. Copy-paste the full results into this topic. Regards, Fiery