Z68A-GD80 B3 CPUz won't start (Resolved)

[owcraftsman]

My question is, is anyone else having the same problem? or not? I need to know either way

When I'm running Aida64 Extreme ver. 1.80.1450 I can not start an instance of CPUz 1.58 or 1.57
I use the OSD and have Aida64 start with windows yet I want to be able to run CPUz at any given time for various reason.
CPUz works fine if Aida is not running which points to a conflict between the apps but there are those running both on different boards which points to This motherboard hence the question.

 

[Jack the Newbie]

Use CPU-Z v1.56, that should work.

This is a case of conflicting applications, that you should notify the AIDA and/or CPU-Z developers about.

 

[owcraftsman]

Interesting TY Jack I have notified both they determined CPUz was to blame and I will email Franck (CPUz developer) today to let them know about this work around since 1.56 does work with aida running. TY again!

 

[Jack the Newbie]

Just in case:  Inform MSI Technical Support about it as well, just in case: http://support.msi.com/  ... However, if both apps [CPU-Z & AIDA] work independently of each other, this rather sounds like a conflict between the applications, rather than with the hardware or BIOS/UEFI implementation. 

 

[owcraftsman]

Yes!

I'm happy to report a work around for this issue provided by the developers. I'd like to thank them for quickly responding and getting on this issue for me and ultimately anyone else whom it has effected. If you edit the CPUz configuration settings changing the default "Sensor=1" to "Sensor=0" without the quotes of course it will fix this issue.

This is the settings .ini found in the "Program Files" Folder on C:\. By saving this change it allows CPUz 1.58 to open and run normally while Aida64 is running. All tabs appear to be reporting correctly and the validation tool is working properly too with this change.

Would a moderator please mark this resolved

 

[Jack the Newbie]

Thanks for sharing the solution here. 

 

[owcraftsman]

Unfortunately I was a bit to quick to say this is resolved. By setting the Sensor=1 to Sensor=0 CPUz is no longer reading Vcore. Instead it is reading VID the capture below illustrates what I mean. See this link for an explanation of how CPUz works. To be clear CPUz works fine when AIDA64 is not running so bare minimum there is a conflict between the two apps, however this does not explain why Aida64 CPUID & MSI own "Control Center" will display Vcore properly at +/-.03v of what is set in bios or why CPUz refuses to work when Aida64 is running.

 

[HU16E]

To be clear CPUz works fine when AIDA64 is not running so bare minimum there is a conflict between the two apps, however this does not explain why Aida64 CPUID & MSI own "Control Center" will display Vcore properly at +/-.03v of what is set in bios or why CPUz refuses to work when Aida64 is running.

Not really sure exactly what MSI has to do with a third party software that doesn't work correctly when used in conjunction with another piece of third party software.

For any possible MSI connection in a third party software conflict, Jack's Reply #3 gives an excellent recommendation on how to proceed.