The reason is always the same: a processor command references memory outside the space allocated to that process by the Operating System. Unfortunately there's no way to know the cause of that specific error. See http://fox.wikis.com/wc.dll?Wiki~C0000005ExError for more info.

>Do we have an error-catch handler available also able to trap the error reason on a C00005 error? With the usual error handler is 'killed' so the it is little bit difficult to find the cause.
>
>