Prev: USB Device does not respond
Next: set_wdf_env.cmd - where is it?
From: Michael on 21 Apr 2008 12:21
When I call NdisMRemoveMiniport(), the return value is successful, but none
of the shutdown handlers get called and the driver stays loaded. What would
cause this behavior?

Thanks!
From: Alireza Dabagh [MS] on 22 Apr 2008 06:14
Chances are miniport adapter is holding on to an OID request or transmit
requests (not completing them) and as a result NDIS can not unbind the
protocols from the miniport adapter.

attach a kernel debugger and do a:
!stacks 2 ndis!

to see blocked NDIS threads.

-ali

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Michael" <Michael(a)discussions.microsoft.com> wrote in message
news:D224C9E6-C08A-41E8-9CC3-214B5F62626C(a)microsoft.com...
> When I call NdisMRemoveMiniport(), the return value is successful, but
> none
> of the shutdown handlers get called and the driver stays loaded. What
> would
> cause this behavior?
>
> Thanks!

 | 
Pages: 1
Prev: USB Device does not respond
Next: set_wdf_env.cmd - where is it?