Fiery

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

The new release comes with support for a wider range of external LCD and VFD displays, including alphanumeric, monochrome and color panels, on which AIDA64 can directly display temperatures, voltages and fan speeds as well as other system information. The July update also introduces support for the latest and upcoming processor and graphics technologies and storage devices. New features & improvements - Support for new LCD and VFD devices: Abacom (ExpertProfi), AlphaCool, Digital Devices, LCD2USB, Mad Catz Venom, Matrix Orbital LK, Matrix Orbital GLK, Matrix Orbital GX, nMedia Pro-LCD, Pertelian X2040, SDC Megtron, SoundGraph iMon VFD, VL System LIS, VL System LIS 2 - Advanced support for monochrome LCDs - SMTP SSL support - Improved handling of XSL files - OpenGL ES 3.1 support - Revamped Direct3D Compute Shader devices enumeration - Plextor M6M, Plextor M6S, Samsung 845DC Evo, Samsung 850 Pro SSD support - GPU details for Mobile AMD Radeon R9 Series, FirePro W8100 - GPU details for nVIDIA GeForce GT 730, Quadro K2200M What's new since AIDA64 v4.00 - Microsoft Windows 8.1 Update 1 and Windows Server 2012 R2 Update 1 support - OpenCL GPGPU Benchmark Suite - AMD Mantle graphics accelerator diagnostics - Multi-threaded memory stress test with SSE, SSE2, AVX, AVX2, FMA, BMI and BMI2 acceleration - Optimized 64-bit benchmarks for AMD “Kaveri”, “Bald Eagle”, “Mullins”, “Beema” APUs - Optimized 64-bit benchmarks for Intel Atom C2000 “Avoton” and “Rangeley” SoC - Optimized 64-bit benchmarks for Intel “Bay Trail” desktop, mobile and tablet SoC - Full support for the Intel “Haswell Refresh” platform with Intel “Wildcat Point” PCH - Razer SwitchBlade LCD support - Improved support for Intel "Broadwell" CPU - Preliminary support for AMD "Carrizo” and "Toronto" APUs - Preliminary support for Intel Quark X1000 “Clanton” SoC - Preliminary support for Intel "Skylake", "Cherry Trail", "Denverton" CPUs - Improved support for Intel “Haswell-E” CPU and DDR4 memory modules - Support for DDR4 XMP 2.0 memory profiles - Intel H97 and Z97 chipset based motherboards support - Socket AM1 motherboards support - CUDA 6.0 support - Improved support for OpenCL 2.0 - Support for VirtualBox v4.3 and VMware Workstation v10 - A-Data SP920, Crucial M550, Intel 730, OCZ Vector 150, OCZ Vertex 460, Samsung XP941 SSD support - GPU details for AMD Radeon R5, R7, R9 Series - GPU details for nVIDIA GeForce 700 and 800 Series [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ Press Release (Русский) ] [ Press Release (český) ] [ Press Release (polski) ] [ What's new in AIDA64 v4.60 ] [ Download ]

We've checked, and unfortunately Microsoft doesn't offer a method to verify whether an instance of the gadget is already running on your desktop. The interface itself claims that only one instance can be run at any given time, but in your case it seems things work a bit different for some odd reason. http://msdn.microsoft.com/en-us/library/windows/desktop/dd378390(v=vs.85).aspx We'll have to do more test runs and come up with a workaround (or a new option in the AIDA64 Preferences) to fix the issue that you're experiencing. I'll let you know in this topic once we've got a resolution. Thank you for your patience. Thanks, Fiery

1) We've implemented a workaround for the CPU multiplier decimal digits issue. It will round the values on Intel Nehalem family (Bloomfield, Nehalem-EP, Clarkdale, Arrandale, Lynnfield, Clarksfield, Gulftown, Westmere, Sandy Bridge, Ivy Bridge, Haswell, Crystal Well, Broadwell, Skylake, etc) and Intel Silvermont family (Bay Trail, Avoton, Rangeley, Cherry Trail, Denverton, etc) processors. The fix will be rolled out with the next AIDA64 update due in 3 days from now. 2) I'm not sure what you mean about that idea. Please explain with more details Thanks, Fiery

It means your system is not stable. You have to return to a more conservative overclocking/tweaking setting, or find out which hardware component causes the issues. Regards, Fiery

Th Please note that what you're experiencing is not what should happen -- it's not by design AIDA64 System Stability Test has got a lot checkpoints in it, and when it finds any unusual or unexpected results, it should report it and stop the test by changing the System Stability Test window to red colour (indicating an error). What you're experiencing however looks more like if the Stability Test background process was crashed, before it could detect the issue. In many cases a BSoD, system lockup or unexpected system restart (reset) comes before the stress testing process could find an error.

Yes, they should work like that.

You can check the order of the CPU utilization readings and their relation to phyisical cores if you go to the Motherboard / CPU page, and scroll down to the bottom of the page. Under modern operating systems (Vista, Win7, Win8, Win8.1, etc) it usually alternates between physical and virtual cores. So first logical processor is first physical core, second logical processor is first virtual core, 3rd logical processor is 2nd physical core, 4th logical processor is 2nd virtual core, etc.

Okay, we'll work on it in August

Is the system in question overclocked or specially tuned? I'm just asking because if it is, then maybe the stress testing process simply dies because the system is unstable.

On the Computer / Sensor page only physical cores are listed. Please note that many processors use half-step multipliers like 20.5x, and some of them use even less round numbers like 1.75x. Regards, Fiery

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

What does the Task Manager (Performance tab) show about memory utilization once the AIDA64 System Stability Test gets into the dormant state? Is your system memory exhausted or there's plenty more left?