24x7 engine error monitoring

We've had a couple of fairly embarrassing crashes in 24x7 in the last month or so, leading to application error this program will be closed sort of messages.

What would be the best way to monitor 24x7 for this?
The 24x7 service remains 'up' until the popup is Ok'd so monitoring that service won't work. Would the scheduler be listening on port 1096 still in this state?

Monitoring port 1096 is one way.

Another method is making Windows send you an email whenever a message is recorded to the Windows event log with the text like "application error" and "24x7.exe" In most cases the error is either reported as occurring in 24x7.exe or in pbvm080.dll files, which are top-level processes from which the rest of code is called. Anyway, if you are running Windows 2003 or Vista or 2008, you can set Windows to auto-email you in such errors or run some custom batch file. The batch can be used to restart 24x7 automatically.