We have seen similar before with Win 11 and cpu###_64.sys, but I think that yours is the first report with Win 7.
One suggestion was that if the memory integrity feature of Windows 11 Pro is turned on then it can prevent the unsigned cpu###_64.sys from being loaded.
I suspect that something similar may be happening with Win7, always remembering that Win7 is no longer supported so odd things may start to happen with it now.
Previously when that loading error occured it would crash Speccy altogether, so it looks like that may have been worked around now.
As for if it will affect the functioning of Speccy I’m not sure.
Speccy is obviously trying to load it for a reason, so if it can’t then some of the information it would normally display for your system may not be shown.
Have you noticed anything missing that you would expect to be shown?