at .OnCollectionChanged(Object sender, Notif圜ollectionChangedEventArgs args) at 1.OnCollectionChanged(Notif圜ollectionChangedEventArgs e)Īt 1.ClearItems() at () at () at _119_10>d.MoveNext() - End of inner exception stack trace -> (Inner Exception #0) System.NotSupportedException: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread. > System.NotSupportedException: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread. As a result, the unobserved exception was rethrown by the finalizer thread. 11:49:37: Unhandled exception in FanControl v1.0.0.0 11:49:37: System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. This is on an Asus B450M-A Prime, running Windows 10. After that I can refresh sensors correctly. The only way to fix it that I've found is to run HWMonitor.
Log File: 01f6b5ac-ce25-11e7-b8b7-0a002700000d.jsonĪdware.DownLoadAdmin, C:\PROGRAM FILES (X86)\EVGA\PRECISIONX 16\PRECISIONXSERVER.EXE, Quarantined,, ,Īdware.DownLoadAdmin, C:\PROGRAM FILES (X86)\EVGA\PRECISIONX 16\PRECISIONXSERVER.I have a similar issue where when waking up from sleep, FanControl will report incorrect speeds (thousands of RPMs higher) for Chassis Fans, and won't be able to control their speeds. Is this a false positive, or is there really a threat? I have had the same version of EVGA Precision X installed for almost a year now with no detected threats before, but when a scan ran at 2AM this morning, a file, process and module were quarantined from the Precision X folder.
0 kommentar(er)
