bobg2222

After installing the latest version, 7.60.7300, replacing the beta, I was still having the same problem (i.e., the image would quit updating after something less than a day). That image was actually being updated on a different machine so this machine was getting the image from a network share. As an experiment, I added that image to the machine where the updating code was actually running. On THAT machine, there was never any problem: it updated fine for 2 or 3 days. So, I moved the code which does the image update to the problem machine and now have it running there, with the AIDA64 LCD display updating from a local file. This has now been updating without any problems for over 9 days! I have no idea (do you?) why using a local file instead of a network share would make a difference--but it apparently does. I don't know how to close this out, but the problem is now solved so far as I'm concerned.

I spoke too soon! Although there are no instabilities, the image on the LCD stops updating after about 19 hours--more or less. I haven't been able to track it exactly. It worked for 19.5 hours in one test--but I don't know how much longer than that (and it's entirely possible that I got confused!). In another test it definitely stopped updating by 19.5 hours from a restart. Stopping then restarting AIDA64 resumes updating the image.

I installed the beta. I did NOT do Step 3 above (enter the image size in the Resize Image boxes). This seems to have completely fixed it! The image updates regularly and there are no AIDA64 instability problems. Thanks!

Is there any news on this problem? I haven't heard anything for over a month! The update at the end of my previous post has the exact steps to reproduce the problem; I don't think it even matters what kind of machine AIDA64 is running on.

With all the hustle and bustle of the holidays, I'm afraid there's something crucial I left out in all the description above! When I first upgraded to version 7.50.7200 on that machine, I eventually noticed that my PNG image on the LCD on that machine was not updating; it was just staying the same all the time--even though the program producing the image updates every 5 minutes. There were no error messages or other problems with AIDA64 at that time. When I had time, I double clicked on the image on the LCD Items screen and noticed the dialog looked different than the previous version of AIDA64. Besides the coordinates and the control to specify the image file name, there was also a "Background image" checkbox and a "Resize" control with boxes to specify width and height. I could NOT find anything in Help about the new controls. But, as an experiment, I filled in the Resize boxes with the size of my image (210x50). I did NOT check the Background image box. THIS is the part I left out above! Then i restarted AIDA64. At that point, the image started updating like it always had in the past. But a few hours later it quit updating and this is when I first saw the "Thread creation..." error, etc. I basically went through that same process today as a double check. I deleted the image from the LCD Items. Added it back in with the Resize boxes filled in and waited. It's definitely repeatable: it worked fine for a few hours (6-8 hours I think) then I checked the LCD display and this time it was really screwed up: the PNG image was missing--but so were the custom gauges! I haven't seen that happen before. On the computer, I could not start up Preferences from the AIDA64 System Tray icon. I was able to start AIDA64 from the System Tray by double clicking--but it was unresponsive. When I clicked on something on the Help menu, I got a message that it was "out of system resources" (or something very similar). I could only exit AIDA64 by killing it with the Task Manager. However, once I restarted AIDA64, everything seemed normal and the Image on the LCD was updating. When I get done writing this, I'll try setting everything up the same, but without running the program which changes the Image every 5 seconds. I'll let you know what happens--but I don't think that will make a difference. I have LCD displays on my other two computers, but only the one has an Image item on the LCD. That's probably the difference and not the kind of machine it is, I'd guess. UPDATE: The test with a static, unchanging image ended about the same: the LCD display was updating--but the image was gone (the gauge images were still there this time). AIDA64 was out of resources (and using over 113MB of memory while other machines where I have it running are using around 80MB). I had to stop it with Task Manager. To reproduce the problem: AX-206 Display, updating every 5 seconds Add an image to the display In the image dialog include the image size in the Resize image boxes (do NOT check the Background image box) Wait about 6-8 hours and the image disappears and AIDA64 is in bad shape and unresponsive (Step 3 seems to be the problem, but without it, a dynamically changing image does NOT update on the LCD display.)

All (Gauges and the troublesome image) are 32-bit PNGs. The gauges were created with Inkscape and exported as PNGs. The image is created dynamically by a small C# program (but is also 32-bit PNG). Given the errors I've documented here--and the fact that it takes a few hours after starting AIDA64 for problems to show up--I'm wondering if for Image type files, you're not freeing Windows handles? Mine is updating every 5 seconds, so that would be a LOT of unfreed handles after a few hours!

While still running the older version of AIDA64, I deleted the PNG file at Preferences/LCD Items, so it no longer knows about the file at all. Then I upgraded to version 7.50.7200. It's been about 12 hours now, and there have been no problems. I checked a few times and there have been no "Thread creation..." popups or any other errors. Also, I can start up Preferences or check for updates, etc. with no problems. So, I guess the problem must have something to do with loading that PNG file. Note: I also have other PNG files which are still being loaded. They are images for custom gauges I use for fans and a CPU temp heatmap. The difference, of course, is that the troublesome image is type Image, but the gauges are type Custom Gauge. I also haven't mentioned that all my machines are running Windows 10 with all the latest updates.

I checked that machine after running 7.50.7200 about 6 hours and had the "Thread creation..." error sitting on the screen. Also, all the same symptoms I described above. In addition to that, I was going to just remove the PNG file (on the Preferences/LCD/LCD Items) so I double clicked on that item in the list and got a popup with the title "AIDA64 Extreme" and the message: System Error. Code: 1158 The current process has used all of its system allowance of handles for Window Manager objects. I could get that every time I double clicked the PNG item or clicked the modify button. I finally clicked the delete button and the PNG item went away. Then I exited from AIDA64, restarted it...and lost all my settings! Now there's no LCD items, it didn't start in the system tray, etc. Everything is gone! Got any suggestions about how to recover from that? UPDATE: I backed off on the version again, but still didn't have my settings. Fortunately, i back up that machine regularly, so I got a copy of AIDA64.ini from before the loss of settings and copied it into the AIDA64 install directory. I STILL did not have my settings. Eventually, I found that there was an AIDA64.ini in ...\AppData\Local\Finalwire (with a date/time corresponding to when I had restarted it and lost the settings)--but not on any of the other machines where I run AIDA64. So, I deleted that FinalWire directory and all my settings came back. Whew! I would be very reluctant at this point to go back to the latest version again. It's VERY unstable on that machine for some reason.

I just let it upgrade back to 7.50.7200--and even rebooted. I didn't make any other changes and so far I can bring up Preferences or check for updates without the "Thread creation..." error. I've also forced changes to the PNG and that's also working fine. So, I'm scratching my head right now! Maybe AIDA64 has to run for a while before problems start popping up? I will keep you posted whatever happens. If the error does reappear, what do you mean by hiding the PNG file?

I have a mini PC with a Core i5-12450H CPU and 16gB of memory. When I got the notification that AIDA64 7.50.7200 was available, I let it install (I did this also on two other computers I have and there have been no problems with them). On the mini PC, I have an AX206 LCD display used by AIDA64. I have one PNG file with extra info which is added to the display and updates now and then. I soon noticed I was getting "Thread creation error. Not enough storage is available to process this command" popups, possibly corresponding to when that PNG updates. But it was actually much worse! I can barely do anything with AIDA without getting that "Thread creation..." popup. If I right click on the icon in the system tray and choose Preferences, I get the popup. If I double click on the icon (so the full AIDA64 interface comes up), then choose Help/Check for updates, I get the "Thread creation..." popup--and the update check dialog doesn't do anything; it doesn't check for updates. I finally backed off to the previous version 7.40.7100 and everything is back to normal and works fine. I'm attaching the sensor dump. isasensordump.txt

This gives me a CPU Package temp which matches hwinfo64! I think you got it!

But, as I mentioned above, hwinfo64 gets a CPU Package temp which is perfectly reasonable. How is it getting that? Can't AIDA64 do the same thing?

Any progress on this? Today's update (version 7.30.6900) didn't change anything.

Here's the sensor dump: ------[ Versions ]------ Program Version : AIDA64 Extreme v7.20.6802 LLKD Version : 2 BenchDLL Version: 4.6.889.8-x64 Windows Version : Microsoft Windows 10 Pro 10.0.19045.4170 (64-bit) GetProductInfo : 0x00000030 ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : GMKtec GMKtec Motherboard Chipset : Intel Jasper Point, Intel Jasper Lake DMI MB Manufacturer : GMKtec DMI MB Product : GMKtec DMI MB Version : Default string DMI MB Serial : Default string DMI SYS Manufacturer: GMKtec DMI SYS Product : NucBox5 DMI SYS Version : Default string DMI SYS Serial : Default string DMI BIOS Version : KB05_GMKTEC_1_02_AUTO001 ITE SuperIO Port = 00h ITE SuperIO HWMonitor Port = 0000h ( 0000h / 0000h) ITE SuperIO HWMonitor MMIO = 00000000h (00000000h / 00000000h) ITE SuperIO Device ID = 0000h ( 0000h / 0000h) ITE SuperIO Version = 00h ( 00h / 00h) Winbond SuperIO Port = 00h Winbond SuperIO HWMonitor Port/60 = 0000h (0000h / 0000h) Winbond SuperIO HWMonitor Port/64 = 0000h (0000h / 0000h) Winbond SuperIO Device ID = 0000h (0000h / 0000h) Fintek SuperIO Port = 00h Fintek SuperIO HWMonitor Port = 0000h (0000h / 0000h) Fintek SuperIO Device ID = 0000h (0000h / 0000h) SMSC SuperIO Port = 00h SMSC SuperIO HWMonitor Port = 0000h (0000h / 0000h) SMSC SuperIO Device ID = 0000h (0000h / 0000h) ASpeed SuperIO Port = 00h ------[ ACPI Temperatures & Fans ]------ _TZ_.THM0._TMP : _TZ_.THM1._TMP : _TZ_.THR0._TMP : _TZ_.THR1._TMP : _TZ_.TZ00._TMP : <TYPE>0</TYPE><LEN>4</LEN><DATA>3010</DATA> _TZ_.TZ01._TMP : _TZ_.RTMP : _TZ_.RFAN : _TZ_.RFAN(0) : _TZ_.RFAN(1) : _SB_.ATKD._HID : _SB_.ATKD.TMPR : _SB_.PCI0.LPC0.EC0_.CCTV : _SB_.PCI0.LPC0.EC0_.LRPM : _SB_.PCI0.LPC0.EC0_.HRPM : _SB_.PCI0.SBRG.EC0_.ECPU : _SB_.PCI0.SBRG.EC0_.TACH(0): _SB_.PCI0.SBRG.EC0_.TACH(1): _SB_.PCI0.SBRG.EC0_.TAH0 : _SB_.PCI0.SBRG.EC0_.TAH1 : _SB_.PCI0.SBRG.EC0_.ST00 : _SB_.PCI0.SBRG.EC0_.SC01 : _SB_.PCI0.SBRG.EC0_.SC02 : _SB_.PCI0.SBRG.EC0_.SC03 : _SB_.PCI0.SBRG.EC0_.SC04 : _SB_.PCI0.SBRG.EC0_.SC05 : _SB_.PCI0.SBRG.EC0_.SC06 : _SB_.PCI0.SBRG.EC0_.TH0R : _SB_.PCI0.SBRG.EC0_.TH1R : _SB_.PCI0.SBRG.EC0_.F0TS : _SB_.PCI0.SBRG.EC0_.F1TS : _SB_.PCI0.PIB_.EC0_.TCRT : _SB_.PCI0.SBRG.EC0_.CTPM : _SB_.PCI0.SBRG.EC__.CPUT : _SB_.PCI0.SBRG.EC__.SYST : _SB_.PCI0.LPC_.EC0_.CTMP : _SB_.PCI0.LPCB.EC0_.CTMP : _SB_.PCI0.LPC_.EC0_.TMP1 : _SB_.PCI0.LPC_.EC0_.TMP2 : _SB_.PCI0.LPC_.EC0_.TMPI : _SB_.PCI0.LPC_.EC0_.TMPV : _SB_.PCI0.LPCB.EC0_.A1TP : _SB_.PCI0.LPCB.EC0_.A2TP : _SB_.PCI0.LPCB.EC0_.FAN0 : _SB_.PCI0.LPCB.EC__.TS1R : _SB_.PCI0.LPCB.EC__.TS2R : _SB_.PCI0.LPCB.EC__.TS3R : _SB_.PCI0.LPCB.EC__.F1FL : _SB_.PCI0.LPCB.EC__.F1FH : _SB_.PCI0.LPCB.EC__.F2FL : _SB_.PCI0.LPCB.EC__.F2FH : _SB_.PCI0.LPC_.H8EC.RTMP : _SB_.PCI0.LPC_.H8EC.LTMP : _SB_.PCI0.LPC_.H8EC.MTMP : _SB_.PCI0.LPC_.H8EC.GTMP : _SB_.PCI0.LPCB.H8EC.CTMP : _SB_.PCI0.LPCB.H8EC.DTMP : _SB_.PCI0.LPCB.H8EC.GTMP : _SB_.PCI0.LPCB.H8EC.ITMP : _SB_.PCI0.LPCB.H8EC.MTMP : _SB_.PCI0.LPCB.H8EC.STMP : _SB_.PCI0.LPCB.H8EC.PFAN : _SB_.PCI0.LPCB.EC0_.OTPC : _SB_.PCI0.LPCB.EC0_.VGAT : _SB_.PCI0.LPCB.EC0_.CHPT : _SB_.PCI0.LPCB.EC0_.CPUT : _SB_.PCI0.LPCB.EC0_.SYST : _SB_.PCI0.LPCB.EC0_.DTS1 : _SB_.PCI0.LPCB.EC0_.DTS2 : _SB_.PCI0.LPCB.EC0_.DIMM : _SB_.PCI0.LPCB.EC0_.FANH : _SB_.PCI0.LPCB.EC0_.FANL : _SB_.PCI0.LPCB.EC0_.CUTP : _SB_.PCI0.LPCB.EC0_.PHTP : _SB_.PCI0.LPCB.EC0_.DIMT : _SB_.PCI0.LPCB.EC0_.INLE : _SB_.PCI0.LPCB.EC0_.PANT : _SB_.PCI0.LPCB.EC0_.F0RM : _SB_.PCI0.LPCB.EC0_.F0DT : _SB_.PCI0.LPCB.EC0_.F1RM : _SB_.PCI0.LPCB.EC0_.F1DT : _SB_.PCI0.SBRG.EC0_.CUTP : _SB_.PCI0.SBRG.EC0_.PHTP : _SB_.PCI0.SBRG.EC0_.DIMT : _SB_.PCI0.SBRG.EC0_.INLE : _SB_.PCI0.SBRG.EC0_.PANT : _SB_.PCI0.SBRG.EC0_.F0RM : _SB_.PCI0.SBRG.EC0_.F0DT : _SB_.PCI0.SBRG.EC0_.F1RM : _SB_.PCI0.SBRG.EC0_.F1DT : _SB_.SAMB.TMPC : _SB_.SAMB.TMPH : _SB_.STR0._TMP : _SB_.STR1._TMP : _SB_.STR2._TMP : _SB_.STR3._TMP : _SB_.STR4._TMP : _SB_.STR5._TMP : _SB_.STR6._TMP : _SB_.STR7._TMP : CPUT : GPUT : SYST : FANT : BATT :

I recently cloned one of my PCs to a mini PC with an Intel Celeron N5105 processor (GMKTec Nucbox 5 with all the hardware recognized by AIDA64). This worked perfectly so the mini PC starts up with Windows 10 and all my stuff installed, including AIDA64. But CPU temp is just not right. It's always stuck on 28C when the individual cores are (at idle) in the mid-30s. It NEVER changes. I've tried uninstalling and reinstalling AIDA64 but nothing helps. hwinfo64 shows a "CPU Package" temp which DOES vary and seems reasonable (higher than the individual core temps but similar)--but the only CPU Package in AIDA64 is a power in watts. How do I get a useful CPU temp?