Mouse Input filter driver- WdfDriverCreate crash

NTDEV
21

xxxxx@gmail.com wrote:

From the setupapi.dev.log file i have got an error message as,
“Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.”

I have searched regarding this error and i found that this error means one of the driver in device’s driver stack has failed in ‘IRP_MN_START_DEVICE’. (as Maxim said in his comment.).

Actually i am not handling this IRP anywhere in my driver code. So i am not able to understand why its failing. Is there is compulsory need to handle this IRP in my mouse filter driver or is there anything wrong i am doing in my driver because of which other driver in stack is failing

Did you write a KMDF filter? If so, then IRP_MN_START_DEVICE ends up
calling EvtDevicePrepareHardware and EvtDeviceD0Entry.

http://msdn.microsoft.com/en-us/library/windows/hardware/gg583867.aspx

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

22

> Did you write a KMDF filter? If so, then IRP_MN_START_DEVICE ends up calling EvtDevicePrepareHardware and EvtDeviceD0Entry.

Yes i am writing a KMDF filter. Actually it is Mouse Input filter driver sample from WDK 8. In this driver, i am not doing any Power management and there is no any implementation for EvtDevicePrepareHardware and EvtDeviceD0Entry functions. Should i compulsory need to handle above mentioned functions in my kmdf filter driver?
FYI, same filter driver is getting installed properly on Windows 7. Only it fails on Windows 8 and above.

Thanks.