Trueboss345 Posted November 9, 2017 Share Posted November 9, 2017 I checked the Reliability Monitor for any issues regarding my custom built PC and noticed that there are multiple Critical events regarding Corsair Link service has stopped working. This happens when i try to shut down the PC normally. This has been going on for a while now, but I noticed this happening more often after I updated Windows to Fall Creators Update. It's been spamming my Reliability Monitor. Any ideas why a typically triggered shutdown could cause this error? Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Dustin Posted November 9, 2017 Corsair Employee Share Posted November 9, 2017 My first question would be which Corsair products are you controlling with Corsair Link? Link to comment Share on other sites More sharing options...
Trueboss345 Posted November 10, 2017 Author Share Posted November 10, 2017 My first question would be which Corsair products are you controlling with Corsair Link? I just have a H100iV2 Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Dustin Posted November 10, 2017 Corsair Employee Share Posted November 10, 2017 Do you regularly sleep and wake your system or are these just happening during normal use? Link to comment Share on other sites More sharing options...
Trueboss345 Posted November 10, 2017 Author Share Posted November 10, 2017 I always do the normal shutdown by going to start menu > shut down. The next time I boot, I go into the Reliability Monitor, and I see that event has occurred. So it's during the startup/shutdown phase that it happens. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Dustin Posted November 13, 2017 Corsair Employee Share Posted November 13, 2017 Other than the flags in the reliability monitor, are you having any issues with the Corsair Link software? Link to comment Share on other sites More sharing options...
Trueboss345 Posted November 14, 2017 Author Share Posted November 14, 2017 Besides the one that i mentioned, I am not having any other problems. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Dustin Posted November 14, 2017 Corsair Employee Share Posted November 14, 2017 I'm going to give you possibly the worst advice you've ever received from someone ostensibly supposed to be giving you tech support: Ignore it. As long as the Corsair Link software is otherwise functioning normally, and is only crashing when Windows tries to shut it down, I'd just ignore it. Link to comment Share on other sites More sharing options...
Trueboss345 Posted November 16, 2017 Author Share Posted November 16, 2017 I am ignoring it. But to see that occuring every day , it bothers me and disturbs my OCD. I would prefer if I could have a clean reliability history. It must either be the way how Windows handles its shutdown/startup , or something within the Link program. For now i don't mind , but could you please reference this to the developers so they'll take note of it ? Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Dustin Posted November 17, 2017 Corsair Employee Share Posted November 17, 2017 I can, but honestly it's such a minor issue I don't know when or even if they'll get to it. We have to prioritize bugs that break functionality. Link to comment Share on other sites More sharing options...
DevBiker Posted November 17, 2017 Share Posted November 17, 2017 Maybe enable the debug logging ... that'll write a detailed log file that maybe you can post/send to Corsair Dustin. You never know ... maybe the log will show that it's something easy. If nothing else, the dev team will have the log so that, when they have time, they can investigate. Link to comment Share on other sites More sharing options...
Muddie2202 Posted November 18, 2017 Share Posted November 18, 2017 I am also receiving the same error for my Corsair H80i V2, And I only shutdown my system through the normal methods. Link to comment Share on other sites More sharing options...
Trueboss345 Posted November 19, 2017 Author Share Posted November 19, 2017 I can, but honestly it's such a minor issue I don't know when or even if they'll get to it. We have to prioritize bugs that break functionality. Maybe enable the debug logging ... that'll write a detailed log file that maybe you can post/send to Corsair Dustin. You never know ... maybe the log will show that it's something easy. If nothing else, the dev team will have the log so that, when they have time, they can investigate. Here's that log file. According to the reliability monitor, the most recent one happened at 11/18/2017 4:40 PMlogs.zip Link to comment Share on other sites More sharing options...
DevBiker Posted November 19, 2017 Share Posted November 19, 2017 Hmmm ... no exceptions in the log file. Maybe also check Application Event Log for an error at that same time (around 16:40:18) from the .NET Runtime. The details would look something like the following: Application: IAStorDataMgrSvc.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at IAStorUtil.SystemDataModelListener.ProcessSystemDataModelChanges() at IAStorUtil.SystemDataModelListener.LoadSavedSystemState() at IAStorDataMgr.EventRelay.<Start>b__12_0(System.Object) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Link to comment Share on other sites More sharing options...
Trueboss345 Posted November 19, 2017 Author Share Posted November 19, 2017 I looked for event logs under Applications , i couldn't find one that you mentioned. Maybe i am looking in the wrong place? However i did find other errors but they are from an old version (10/19/2017 7:44:41 PM): Faulting application name: CorsairLink4.exe, version: 4.8.2.1, time stamp: 0x598c467c Faulting module name: PrecisionXServerHooks.dll_unloaded, version: 6.1.8.0, time stamp: 0x594221f8 Exception code: 0xc0000005 Fault offset: 0x00005583 Faulting process id: 0x24f8 Faulting application start time: 0x01d3494aa4ba6f09 Faulting application path: C:\Program Files (x86)\CorsairLink4\CorsairLink4.exe Faulting module path: PrecisionXServerHooks.dll Report Id: c7a1f4ed-5bf2-4eb9-8f07-166065a6bab0 Faulting package full name: Faulting package-relative application ID: And then I found another similar one under Information category: Fault bucket 129599499487, type 5 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: CorsairLink4.Service.exe P2: 4.9.1.23 P3: 59e5f3d1 P4: System.Management P5: 4.7.2556.0 P6: 59b83606 P7: 8a P8: 51 P9: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3894.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_CorsairLink4.Ser_8bc6a3343f2b6c6ec669a2251dd169574a35838_ca2d05a4_19083c0f Analysis symbol: Rechecking for solution: 0 Report Id: a241b484-8d3f-461b-935d-c76020e7fe09 Report Status: 268435456 Hashed bucket: 4a4cf4c8d7586994ae6738f7f6335583 Link to comment Share on other sites More sharing options...
Trueboss345 Posted November 25, 2017 Author Share Posted November 25, 2017 Anyone please? Link to comment Share on other sites More sharing options...
DevBiker Posted November 25, 2017 Share Posted November 25, 2017 Unfortunately, what you posted doesn't really tell us much except that it crashed. A stack trace (which will look like my example) will tell us exactly where it crashed and that's exceedingly useful for root cause analysis. For .NET applications, there usually will be a stack trace in the event viewer as a separate event, with a source as ".NET Runtime", around the same time. So ... I got nothin'. Link to comment Share on other sites More sharing options...
Trueboss345 Posted December 13, 2017 Author Share Posted December 13, 2017 I've been trying to do a little experiment. I went to Windows power options > Choose what the power buttons do > Change settings that are unavailable > Turn off Fast startup. Now aside from that, every time before I shut down the computer, I right click on the Corsair system tray icon and choose Exit. I've been doing this for about 2 weeks now. And there has been a difference! I only see it occuring twice during the past 2 weeks, probably because I forgot to shut it down via context menu. So instead of letting Windows handle quitting the program, I have to do it manually. And maybe also that fast startup was the reason why I've been getting those errors. Now that I've narrowed the problem (or so I think) can the developers do something so that it can shut down properly with Windows? Link to comment Share on other sites More sharing options...
DevBiker Posted December 13, 2017 Share Posted December 13, 2017 That's ... interesting. Question: have you updated to the latest version? Do you see the same behavior? Link to comment Share on other sites More sharing options...
Trueboss345 Posted December 13, 2017 Author Share Posted December 13, 2017 That's ... interesting. Question: have you updated to the latest version? Do you see the same behavior? No, this has been done using the same version (4.9.1.23 ). I might update it later this week. Link to comment Share on other sites More sharing options...
Trueboss345 Posted March 8, 2018 Author Share Posted March 8, 2018 Yeah so I have had fast-startup turned off for a few months now. My reliability monitor has come clean. I'm using the latest version of Link now (4.9.5.25) I have seen no problems occur. So it wasn't until then I recently turned Fast-startup back on, and then later my computer just randomly shut down. Couldn't tell if it was the program causing it or the setting with Fast-startup, but it was really odd. Link to comment Share on other sites More sharing options...
vkone Posted March 13, 2018 Share Posted March 13, 2018 Yeah so I have had fast-startup turned off for a few months now. My reliability monitor has come clean. I'm using the latest version of Link now (4.9.5.25) I have seen no problems occur. So it wasn't until then I recently turned Fast-startup back on, and then later my computer just randomly shut down. Couldn't tell if it was the program causing it or the setting with Fast-startup, but it was really odd. Hi, I created an account just to say thanks! I have been having the same issue (4.9.5.25) and I can confirm the solution that fixed it for me was turning off fast startup under windows / power options. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.