If the component exception is propagated up the stack to managed code, .NET framework tries to map it to a managed exception. For example, STATUS_NO_MEMORY maps to OutOfMemoryException and STATUS_ACCESS_VIOLATION maps to NullReferenceException.
For better clarity, you catch the exception details in
try {...}
catch (Exception ex) {...}
Then, share the details of the exception, code and component details. That will help us to provide the solution.