JohnOh

Virgo I think you could be right, I have just found out that SVChost.exe terminated our application with code 1067 and sure enough the "Stop task if it runs longer than:" was checked. (it is not checked by default - maybe that has changed I didn't personally create the task but its not something we would check). Our task scheduler runs our application on startup - so I can understand why if it was started via the task schedule it would stop after 3 day but I would assume if it was started directly from windows explorer the it would not be stopped but maybe it is. Anyway looks like we have a solution Thanks to you all for posting :) John.

I have a strange problem and I am stuck on how to solve it. My application that has been running fine on windows 7 (embedded) for years is now randomly stopping (being killed) on a windows 10 pc it look likes it is being killed, as if it was closed correctly it would log the events but all I get in my log is a "UDP disconnect message" (I am using UDP ports for the application to communicate with each other and Moxa Nports). There is nothing in the windows events logs It is not crashing as I am using MADexcept and I don't get any error files. It also only stops after 3 days almost to the minute of the start time. I have it running on the several same spec pc's and not all of them fail, the PC's are not connected to the internet but on their own private LAN. I got my customer to installed Gflags on the PC that had the most problem to try and find out what maybe killing my application, but so far that pc has not stopped but another one did. so I need a solution. If anyone has any ideas of what might be causing it or how best to find the problem I would be grateful. Thanks.