From a look at the log file bloat doesn’t seem an unreasonable description.
Something has gone wrong, SGP logs the error and retries in a tight loop, the error keeps reoccurring and no more information seems to be generated after that, just bloat. A better option for handling errors that you can’t recover from is to log it and break out of the loop.
From a look at the log that was posted there’s a problem reported by the Atik Camera driver in the GetSetCCDTemperature call:
[21/07/2014 9:16:50 PM] [DEBUG] [CP Update Thread] ASCOM Camera: Error in GetCoolerTemp. : CLR has been disabled due to unrecoverable error. (Exception from HRESULT: 0x80131023)
at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object args, Boolean byrefModifiers, Int32 culture, String namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object providedArgs, ParameterModifier modifiers, CultureInfo culture, String namedParams)
at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object args, CultureInfo culture)
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type parameterTypes, Object parms) in c:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 266
at ASCOM.DriverAccess.Camera.get_CanSetCCDTemperature() in c:\ASCOM Build\Export\ASCOM.DriverAccess\Camera.cs:line 240
That seems to be repeated interminably. It looks pretty low level, there’s no reason why the CLR should be disabled by an error in the ASCOM driver and pretty unlikely that this error would be generated by a driver that’s successfully connected to a camera.
If it’s reproducible try turning error logging on in the ASCOM ATIK driver and reproduce the error. Post the ASCOM log as well as the SGP error. The ATIK log is more likely to give detail of what’s happening.
The first thing with fixing errors is to find out what is happening.