dhague Posted January 25, 2016 Share Posted January 25, 2016 Searched the forum for this particular CLR20r3 problem and did not find any matching. With Corsair Link 3.2.5742 installed, it crashes about 5-10 seconds after startup with a CLR20r3 error (error data and system info below). Corsair Link does detect all Corsair devices before the crash. Multiple removals and clean installs make no difference. The problem is hard repeatable. Web and forum searching has located nothing helpful. I am stumped and any help would be welcome. Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: CorsairLINK.exe Problem Signature 02: 3.2.5742.27109 Problem Signature 03: 56008cca Problem Signature 04: CorsairLink.PlugIns.CpuId Problem Signature 05: 3.2.5742.27108 Problem Signature 06: 56008cc8 Problem Signature 07: 4 Problem Signature 08: 0 Problem Signature 09: System.IndexOutOfRangeException OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 **********Hardware Info********** Supermicro Motherboard: MDB-X10DAL-I-O Dual Processor: 2ea Intel Xeon E5-2650 V2 Corsair AX1500i power supply Corsair H80iGT Cooler, 2ea **********Software Info********** Microsoft Win7x64-Ultimate Microsoft dotNET 4.5.2 Microsoft SQL Server Express 2014 Microsoft Visual C++ 2005, 2008, 2010, 2012, 2013 (lots of other Apps that should not affect Corsair Link) ZoneAlarm Extreme Security V14.1 (all Corsair software set to "Trusted", system & network) Link to comment Share on other sites More sharing options...
red-ray Posted January 25, 2016 Share Posted January 25, 2016 It seems to be crashing out in the CPUID SDK and I wonder if HWM also crashes, have you tried it? Try the 32-bit version. I suspect CL has not seen tested on a SuperMicro X10DAL-i. Do any programs report your CL hardware OK? AIDA64, HWiNFO and my SIV utility should. I guess the system has 40 CPUs, have you tried booting with just 32 as CL is a 32-bit program and more than 32 CPUs may confuse it. Do bcdedit /set {current} numproc 32 and reboot. It might also help to boot the system with two groups of 20 CPUs rather than one group of 40. Do bcbedit /set {current} groupsize 20 and reboot. If you wish to create multiple boot options use similar to bcdedit /copy {current} /d "Windows 7 x64 V6.01 Build 7601 SP1 C:\Windows (2 x 20 CPUs)" I have just noticed you have 2 x H80iGT, have you set IgnoreHWSerNum? If not the I advice you to, see http://forum.corsair.com/forums/showthread.php?p=746122. Link to comment Share on other sites More sharing options...
dhague Posted January 25, 2016 Author Share Posted January 25, 2016 Thank you for responding. HWMonitor does work just fine on my PC (both 32 and 64 bit versions). I also checked my Registry and it does indeed show "40 CPU's". However, BCDedit does not work on my system (error=cannot find file). Probably because I have a dual-boot Ubuntu/Windows setup with GRUB in the boot sector. It appears that I will have to have to blow out Ubuntu and restore the normal Windows boot sector to try your BCDedit suggestions. But I strongly suspect that you are correct about the problem with Corsair Link on my PC. Link to comment Share on other sites More sharing options...
red-ray Posted January 25, 2016 Share Posted January 25, 2016 bcdedit works on my Linux dual boot system. Did you open the command prompt as admin? How many cores did HWM report? I suspect HWM-32 was 16 and HWM-64 was 20. Link to comment Share on other sites More sharing options...
dhague Posted January 25, 2016 Author Share Posted January 25, 2016 Yes, I opened "CMD" as admin. When looking at HWMonitor, I got confused by the slightly weird numbering of Cores and CPU's. I rechecked today with the following results. HWMonitor_32: Xeon #1 shows 10 Cores and 20 CPU's. Xeon #2 shows 6 Cores and 12 CPU's. Total = 16 Cores and 32 CPU's HWMonitor_64: Xeon #1 shows 10 Cores and 20 CPU's. Xeon #2 shows 10 Cores and 20 CPU's. Total = 20 Cores and 40 CPU's. Since Corsair Link is a 32-bit App, could it be "unhappy" because it is seeing an "unbalanced dual-processor". Link to comment Share on other sites More sharing options...
red-ray Posted January 25, 2016 Share Posted January 25, 2016 Since Corsair Link is a 32-bit App, could it be "unhappy" because it is seeing an "unbalanced dual-processor". Thank for the info which is what I expected. From my testing of SIV32 if you boot the system with 2 x 20 CPU groups then HWM-32 should report all 20 cores. In general if a reporting program is CPU Group aware (which HWM and I expect the CPUID SDK are) then if you want the 32-bit version to work you need to limit the number of CPUs in a group to <= 32. The correct solution would be for Corsair to release a 64-bit Corsair Link, but feel this is unlikely. I can't remember if http://forum.corsair.com/forums/showthread.php?p=759572 ever got CL working well on his 72 CPU system with 2 Groups of 36 CPUs. He may just have given up on CL and used SIV. As I recall SIV64 worked with no issues, but I needed to fix one issue in SIV32 as the 64-bit driver reported the information for 36 CPUs and SIV32 was only expecting it for 32 CPUs. Running SIV32 on a 64-bit system is silly, especially so for one with more then 32 CPUs, but I feel it should do the best it can. For information on BCDEDIT options see https://msdn.microsoft.com/en-us/library/windows/hardware/ff542298(v=vs.85).aspx Link to comment Share on other sites More sharing options...
dhague Posted January 26, 2016 Author Share Posted January 26, 2016 At least I now understand what is going on with Corsair Link, which I will give up on until they do a 64 bit version. I will look into SIV. The reason that I was trying to get Corsair Link to work was a bad experience some older Corsair power supplies (the temperature/fan control logic was bad and would go into over-temp shutdown after 15 minutes unless I used Corsair Link to set the fan speed to "manual Fixed" operation). At least I can use HWMonitor to check system temps at intervals. You could say that my current build was over-cooled as even the graphics card only hits a max of 130F, processor max at 96F, and DRAM max at 100F. Thank you again for your assistance. Link to comment Share on other sites More sharing options...
red-ray Posted January 26, 2016 Share Posted January 26, 2016 I was trying to get Corsair Link to work was a bad experience some older Corsair power supplies (the temperature/fan control logic was bad and would go into over-temp shutdown after 15 minutes unless I used Corsair Link to set the fan speed to "manual Fixed" operation). Given you only have a single GPU I doubt if your AX1500i will even need to turn it's fan on. My AX1500i fan only ever starts when I run GPU benchmarks and I have never known it not to start when it should. Most of the time it's running at 36.3°C. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.