CPUz 157 & 158 fails to start freezes at initialization screen see capture below
http://img827.imageshack.us/i/cpuznorun.jpg/
Things I have tried to correct the problem:
Uninstalled deleted directories and reinstalled
tried 157 & 158 32 & 64
Uninstalled/Reinstalled Chipset drivers
Uninstalled Intel TPM
Uninstalled Intel IME
Uninstalled MSI Control Center
Uninstalled Aida64
Uninstalled MSI Turbo Boost and all other MSI software
Installed running as admin
Manually added to AV allowed programs
Set Full control to current user
Ran as Admin and set to run as admin in properties
Ran sfc /scannow
tried running at default setting and OCed
All with same result.
I have one thing left to try which is a Diagnostic startup whic I will try on restart and get back to you.
I have seen screen shots of other Z68A-GD80 using CPUz 157 & 158
edit: add system specs
System Specification
Processor: i7 2600k batch L050A853
Motherboard: MSI Z68A-GD80 B3
Bios: V17
Memory: Corsair Vengeance 1866 C9 1.5v
HDD: Raptor WD1500ADFD 2x Intel RAID-0
SSD: none (to be added later with IRST SSD Caching)
GPU: Onboard (at the moment)(GTX 570 SSC HD to be added soon)
LucidLogix: (not installed yet)
PSU: Corsair TX-850-W
Cooling: H70 & Air
Case: CM HAF 932 A 3.0v
OS: W7-U-x64 SP1
IMED: 7.0.10.1203 (Intel Management Engine Driver)
ISBCD: 9.2.0.1030 (Intel SandyBridge Chipset Driver)
CPUz 1.8 does start and run after a diagnostic startup which lead me to the time consuming task od finding which service and or program was the cluprit. I got a bit lucky in that I was half way in to the project when I figured it out.
http://valid.canardpc.com/show_oc.php?id=1891465
#1 CPUz, Everest and Aida64 are all tied to the same windows service "Windows Event Log"
#2 It is not enough to stop Adia64 ver 1.8 it must be uninstalled and restarted for CPUz 1.8 to run
I tried installing Everest Ultimate with and old key but the z68 is not supported so no further testing [uninstalled]
I then tried the previous Aida64 ver 1.7 and again with it installed running or not CPUz will not start.
I do hope there is a resolve for this. I will help in anyway I can, just ask, but for now I will take this issue to Cannard PC and MSI as well.