I am developing an usb smartcard reader using the usbccid driver from
Microsoft.
The reader works fine except in "hard" condition tests (detailed below) that
have 2 critical consequences: (1) Reboot of the PC or (2) Impossibility to
detect an usb product anymore (as if the usb plug-and-play service was
crashed). For the second consequence, a reboot of the PC is also necessary to
find again a normal behaviour of the PC.
My smartcard reader is not powered by USB, but has an external power supply.
Unfortunately I am unable to find a repeatedly test sequence that make my
reader crash the PC but here is what I have noticed:
(1) Reboot of the PC appears after a lot of quick insertion/removal of both
USB and power supply. I have a blue screen with information: BAD_POOL_CALLER
(i.e. free buffer failed)
(2) The impossibility the find any usb product anymore appears when one or
more CCID messages was/were sent from the PC and the reader did not answered
it/them because the power supply was voluntary removed.
So I want to know if somebody has got similar problems with the usbccid
driver or an idea of what I am doing wrong in my code to produce those
behaviours.
Best regards,
Olivier