Major locking issue with CL 3.1 and other monitoring programs

[red-ray]

Looking with process explorer CL does not have the Access_ISABUS.HTP.Method mutex open (mutant is the kernel name for a user mode mutex). So much for the better testing! Do not run CL 3.1 and any other program that reports the motherboard sensors such as AIDA64, HWiNFO, SpeedFan, OWM, SIV, etc. as the access is not interlocked and you may get strange lockups and crashes just like with AI Suite.

If you check CL 2.7 you will find the lock is open.

[red-ray]

When I checked CorsairLink_Installer_RC_v3.1.5570_signed it's still not using the Access_ISABUS.HTP.Method mutex. Corsair should get in contact with the CPUID SDK guys and resolve this issue before you release it!



I also checked and it's still only reporting one of my three CL Minis and the GPU reporting is still far from ideal. When I first ran it then all 4 were reported and after saving the profile, closing down CL and running it again I got another 4! Why does the RM PSU fan flash red?



You need to up the size limit! One of Three.png:
Your file of 2.54 MB bytes exceeds the forum's limit of 1.00 MB for this filetype.

[StealthGaming]

Take a look at the below post, you said " SIV works with multiple monitoring system software without a conflict "?

[StealthGaming]

Originally Posted by red-ray

There was no post below 'till I added this one I would never say that, please quote the URL. What I will say is:

SIV works well with other monitoring programs that correctly interlock access using mutexes. To check the names used look to Menu->Help->SMBus Locks. All of AIDA64, HWiNFO, OHM, SpeedFan and SIV correctly interlock access and work well together.

Heres the posted in which 3 posted were deleted by yourself on 06 May 2015. POST ID # = 776835, Question Corsair Link & Asus AI Suite 3 - issues?

You had also said in this post " I assumed English is your mother tongue or do i have to allow for this ". It's probably a good thing you have deleted that post since some Non-English speaking people may have taken offence to this statement.

[red-ray]

Be warned that the newly released CL V3.1.5570 does not interlock correctly. I have just posted http://forum.corsair.com/forums/show...407#post779407.

[ApexAU]

This is really disappointing. I hadn't checked the forums for a while and was excited to see the new CL release but sounds like it isn't worth installing. Just to be clear: red-ray, will I definitely have problems if I run the latest version of Link alongside AIDA64? I'm keen to try the new Link release but I rely on AIDA64 so if it's one or the other, I'll pick AIDA every time.

[red-ray]

Originally Posted by ApexAU

Just to be clear: red-ray, will I definitely have problems if I run the latest version of Link alongside AIDA64?

As I did not develop either of AIDA64 or CL you need to ask FinalWire or Corsair rather than me. If I was told it was safe to run CL 3.1 and AIDA64 at the same time I could not believe this.

I said in http://forum.corsair.com/forums/showthread.php?t=141037 that I expect AIDA64 and SIV can safely be used together.

[red-ray]

Below you can see that CL v3.1.5667 has the locks open, though I expect them being open multiple is not ideal and gives me cause for concern.

I am keeping my fingers crossed that the locking is correctly implemented and recommend only using CL v3.1.5667 rather than the earlier CL 3.1 releases.