GOverlay Forum

The two zero's above are connected to:
- The chipset fan speed (X570 motherboard) which works semi passive. So at this momemt the fan is not spinning.
- A case fan header which is not connected.

After rebooting my PC I see this, so a lot of elements are suddenly not shown anymore.



When a fan have not spinned yet or a fan header is not connected the sensor is invisible in AIDA64 (or any sensor program for that matter). So when the screen of the LCDSysInfo is now trying to load those elements it propably crashes behind the scenes and all other elements which are not initialised yet will not load anymore.

Is there a handy workaround for this issue?

uhm, if aida64 is not reporting the sensor after a reboot, goverlay will not be able to fetch its information.
GOverlay should be able to get its data once the sensor is back up on aida, unless aida is modifying its reference to the sensor like if it would be a brand new sensor each time.

does this happen with hwinfo too? have you tried?

I actually don't know how to use HWInfo sensors in Goverlay, but those fan speed sensor will also not show up in HWInfo until it has spin once during the runtime of the program. Once a fan has spinned once the sensor will stay even if the fan later stops spinning.

If I start the chipset fan manually the GOverlay will initialise the whole screen again.

My suggestion will be to make GOverlay more robust when the given sensor is not present To me it make no sense that one wrong element will prevent others to be initialised.
This could actually problematic if you configure your case fans such that it will only spin when the CPU temp is at certain value.

The LcdSysInfo will replace my screen of the Logitech G510 keyboard. I use AIDA64 to fill this screen. When AIDA cannot find the chipset fan sensor it will simply show 0 instead.

i think i now understand what you mean.
So other sensors that are present on AIDA arent showing up when the missing sensor is also added on GOverlay?
If thats the case, that shouldnt happen.
I will need the log after this happens on goverlay startup and see if there is any error there thats preventing loading more sensors

This is how it looks when de chipset fan sensor is missing:



This is how it looks when I start de chipset fan manually. It's the zero in bottom right corner (I have stopped the fan when I took the photo).



This is the log:

"de objectverwijzing is niet op een exemplaar van een object ingesteld" is Dutch and means "the object reference is not set to an instance of an object".

I have included my GOverlay profile.

And I am using GOverlay 1.6.9.

okay, i think i found the issue

Try this beta


Download & Install:


let me know how it goes

Nice, with this beta version it is solved!