Runnning CL V3.1, CAM and other monitoring software at the same time

red-ray · May 17, 2015

I have just checked and CAM seems to use the CPUID SDK and unlike CL 3.1 (seems to be fixed in CL 3.2) uses a version that seems to interlock correctly. I can tell this as PE shows all of Access_SMBUS.HTP.Method, Access_ISABUS.HTP.Method, ... Mutants/Mutexes have been opened. There is no way anyone can tell if they are being used correctly though, but given they are open hopefully they are :[pouts:.

Looking at http://forum.corsair.com/forums/showthread.php?p=784450 the official Corsair position seems to be that CAM and CL should not be used at the same time as they will conflict.

As both CL 3.1 releases have the issue I stated in http://forum.corsair.com/forums/showthread.php?t=138035 it is not safe to run CAM and CL 3.1 at the same time, is not safe to run CL 3.1 and ANY other monitoring program at the same time :eek:. I expect it should be OK to have CAM and CL 2.7 active at the same time, but use PE to check the versions you are using have the Mutants/Mutexes open first.

As far as I can tell it is safe to have all of CAM, AIDA64, HWiNFO, OHM, SpeedFan and SIV active at the same time. If you wish to also run other programs use PE to check if they have the locks I mentioned above open before doing this.

The general rule is if a monitoring program does not have the Mutants/Mutexes open you should not run ANY other monitoring software at the same time as it :!:. ASUS AI Suite does not so if you run any other monitoring program at the same time you are effectively playing Russian Roulette :uzi:.

While the mutants being open is a good indicator that a program will interlock correctly it is not a certainty. I can recall at least one case of Access_SMBUS.HTP.Method being open and not being used correctly by a released program and have tested many development versions that had issues that needed to be resolved. Eventually I got the offending released program corrected, but convincing the author there was an issue with his code was tricky and time consuming. In the end I added code to the SIV SMBus driver to detect the report the conflicting information in the SMBus controller hardware registers and sent him the SIV SMBus driver trace. The code is still in there, but it's been a few years since I needed it :biggrin:

PE can be downloaded from https://technet.microsoft.com/en-gb/sysinternals/bb896653.aspx?f=255&MSPPError=-2147217396