Abb 800xa5.1 version operator workplace crashes.
How to find the reason for Crashing OPerator Workplace?
I disconneted the Client From Aspect Server And Connected Again. this was occuring in connectivity Servers too.
Does it crash spontaneously, or when navigating to certain graphic, etc? If a certain graphic is causing the crash, use "Divide and Conquer" technique to isolate the element, design, etc that is responsible for the crash.
Does your graphic use Visual Basic? If so, it is very very recommended to migrate to PG2 since Microsoft stopped supporting Visual Basic many years ago and several fatal bugs remain that ABB can not do so much about alone. Modern computers with multiple CPU cores makes VB less stable. Regional ABB support can assist you with locking down the workplace process onto a singular processor core. This fixes some, but not all problems from VB6's End-Of-Life.
The workplace uses a lot of virtual memory. On 32-bit operating systems, the practical limit is 1500 MB. Measure Virtual Bytes for AfwWorkplaceApplication.exe using Windows Performance Monitor (not Task Manager). With complex design and many monitors you can easily put yourself on the limit of 1500 MB by just starting a workplace. If your configuration quickly enters 1500MB+ you must make it less compless, prevent too many overlapping windows by using View Class settings, reduce the number of monitors or even upgrade to 64-bit operating system (supported from 5.1RevB and onwards). Several memory leakages have been corrected since 5.1 up to the present 5.1 RevE/FP4RevE - an upgrade may solve your memory problem.
After ruling out the above it might be time to enable "Dump on Exception" in the Configuration Wizard, provoke a crash, collect, compress and make the crash dump available to regional ABB support for analysis.