don't assume that just because the crash is not happening within libnodave.dll it isn't that library's fault. that library's code may be bringing about an inconsistency either within the jvm or the underlying os services, which is later causing another system call to fail. this is especially indicated by the fact that the errors happen at different place each time.

try to replace calls to libnodave.dll with mocked java code and see if you receive the error again.

Related Query

More Query from same tag