How to do a post-mortem on a Win2K task that died?

[Guest Pat Coghlan]

My 3rd-party app runs a task on a Win2K server. Sometimes, this task -

which is created by its parent service - suddenly dies, requiring the

service to be restarted, or sometimes the server to be rebooted.

 

How can I get information on why this task died so that I can do some

kind of post mortem etc? There is nothing in the event log, so I

presume the task encountered some kind of exception and died.