Re: WdfUsbTargetDeviceCreate() failes in child device after static child device enumeration

Tech-Archive recommends: Speed Up your PC by fixing your registry

On Apr 13, 6:03 am, "Johan Paul" <johan.p...@xxxxxxxxx> wrote:

I realized what I should do and now I try to forward the IRPs from
child PDO to bus FDO. I do this with
WdfRequestForwardToIoQueue(Request, FdoDeviceData->FdoInQueue) in
PDO's EvtIoDefault.

My problem this time is that i get a BSOD from calling the funtion.
Invalid argument it says. I can't understand why because I check the
status of the queue before the call and is says that queue is
accepting IO and that is is ready. Also on the FDO side the queue is
configured and a dispatch handler is registered but the driver never
gets that far. The Request handle is given as parameter and it sounds
wierd to me that it would cause the BSOD.

What are usbccgp_obex and dynambus in this crash dump? Where are the
symbols for usbccgp_obex?

Overall I don't understand the backtrace at all. My best guess is
that dynambus is some sort of lower filter to usbccgp_obex and that
it's handling the the URBs sent by KMDF in your bus driver FDO to
initially configure the device. This is, of course, totally incorrect.

.