Same problem here:
Speccy 1.28.709 (64 bit)
Windows 10 (64 bit, 10.0.10240)
It appears Speccy leverages the CPU-Z driver to gather CPU information (CPUID v1.0.3.8) and it extracts it in %TEMP%\cpuz138 folder and probably calling it through %TEMP%\speccycpuid.dll (CPUDI SDK DLL, v1.1.1.6).
The problem doesn't happen all the time, but it is annoying if you happen to start Speccy when you have things unfinished / unsaved.