Hello,
thanks for response, I understand. Some additional questions:

1. When the problem happens, and the notifications stop coming, is the user interface of the program still responsive in basic sense? That is, if you form has any controls such as edit boxes, list boxes etc., when you try to use e.g. mouse to click and select, do they react by changing the focus or selection, OR is the user interface completely dead, which is usually then indicated by extra sound and/or Windows detecting that the program is "irresponsive" and showing a message box about it.

2. In this "problem" state, can the program be closed using the "X" on the window caption or its other usual means? Or, does it have to be "terminated" from the Task Manager?

3. Please start Windows Event Viewer, and navigate to Windows Logs -> Application. Are there any events coming from the application during its run, and specifically close to the when it stops responding? (or, if it is close to the time the problem happened, ANY events, even from other sources, would be of interest).

Thank you

Actually , given that you already provided the code of a Form-derived class , I think the answer to the first question is "It is a Windows Forms application". So I just need the answer to the second question please.

Regards

Thank you.
I have some additional questions:

1. What kind of project is your application? E.g. Console app, Windows desktop app (Windows Forms or WPF), Windows Service, Web app, Web service, etc.

2. Would you be able to attach a Visual Studio debugger to the application in the state when it has stopped receiving updates (in order to extract some thread information that I would describe to you)? Or, is the application in the production setup where this is not possible?

Regards

Of course it does not work. It was valid for 30 days, as written below when I sent it.
Will send you a new one by email. And yes, test your issue with QuickOPC 2022.2.

Regards