While doing tests of removing USB device abruptly (i.e. physically upluggin it) during activity (basically reading on a data enpoint in a loop) I systematically got a BSOD.
My stack is an application using libusb-1.0, libubsK.dll and libuskK.sys (latest signed versions)
Analysis of the minidump using WinDbg gave the following output, in which libusbK.sys is clearly identified as doing something wrong.
It is a bit beyond my knowledge, could someone have a look at it? I guess it's easily reproducible.. Thanks
While doing tests of removing USB device abruptly (i.e. physically upluggin it) during activity (basically reading on a data enpoint in a loop) I systematically got a BSOD.
My stack is an application using libusb-1.0, libubsK.dll and libuskK.sys (latest signed versions)
Analysis of the minidump using WinDbg gave the following output, in which libusbK.sys is clearly identified as doing something wrong.
It is a bit beyond my knowledge, could someone have a look at it? I guess it's easily reproducible.. Thanks
Here is WinDbg output: