Either the function has a serious bug or you are calling it with
invalid parameters or wrongly setup parameters. The problem happening
here is that your DLL passes somehow invlid parameters to a system
device driver and that driver causes a protection fault. For device
driver execeptions which happen in the privileged kernel, Windows does
not try to attempt to message a user in such cases (other than the
threaded blue screen of dead which when you get it really means a full
restart) but unloads the current application as fast as possible.
Check the documentation for this function and try to see where you call
it srong or contact the developer of this DLL for assitence.
Rolf Kalbermatter