Scanner device object stuck in REMOVE_PENDING because of reference to FDO. RRS feed

  • Question

  • When a customer (effectively) disconnects their HP USB scanner its PDO gets stuck in REMOVE_PENDING state.  They generated a forced crashdump and I see the scanner PDO when I run "!devnode 1".  I also see a reference count of 1 for the FDO, the device object created by usbscan.sys.  I checked to see if there is an unclosed user mode handle using "!devhandles" on the PDO but nothing showed up.    Also, !irpfind did not show any pending IRPs against the PDO .

    Is there any way to pinpoint the culprit?  It is not possible to trace object references in this customer's environment.  I have run out of ideas.


    Tuesday, November 24, 2015 4:39 PM

All replies

  • is the fdo still attached? if so, the remove irp wasn't processed. a ref on the fdo after detach won't hold up the pdo

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

    Wednesday, November 25, 2015 12:52 AM
  • The FDO is still attached.


    Wednesday, November 25, 2015 1:30 AM