STOP 0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS ?
I have a Windows vista based computer and using it last few months. One day I disable the USB device and at that time it was in an idle state and then I get this “STOP 0x00000044(parameter1, parameter2, parameter3, parameter4) MULTIPLE_IRP_COMPLETE_REQUESTS” message on my computer screen. My friend had told me that it is an error message. Then please tell me how can I solve my problem? Can anyone help me?
Answer 1
Hi! The message “STOP 0x00000044(parameter1, parameter2, parameter3, parameter4) MULTIPLE_IRP_COMPLETE_REQUESTS” you are getting on your computer screen is really an error message. This problem occurs if the USB device uses a driver which is written with the help of the Kernel Mode Driver Framework version 1.7 or the earlier version. You can solve this problem by using the Kernel Mode Driver Framework version 1.9 and the later version. A KMDF-based USB device driver developer may work for this problem by doing the following actions: 1. It registers an EvtDeviceReleaseHardware callback routine in a driver\'s EvtDriverDeviceAdd callback routine. 2. It allocates a WDFWORKITEM object in a driver\'s EvtDriverDeviceAdd callback routine. 3. It allocates and then initializes a KEVENT object, queue the work item in the driver\'s EvtDeviceReleaseHardware callback routine, passing this event as the Context parameter, and wait for the event to be signaled. 4. In the work item callback routine, it delays a thread by approximately two seconds and then set an event. The exact delay value which is required may differ across the systems and should be tested earlier to the final implementation.
Hi! The message “STOP 0x00000044(parameter1, parameter2, parameter3, parameter4) MULTIPLE_IRP_COMPLETE_REQUESTS” you are getting on your computer screen is really an error message. This problem occurs if the USB device uses a driver which is written with the help of the Kernel Mode Driver Framework version 1.7 or the earlier version. You can solve this problem by using the Kernel Mode Driver Framework version 1.9 and the later version. A KMDF-based USB device driver developer may work for this problem by doing the following actions: 1. It registers an EvtDeviceReleaseHardware callback routine in a driver\'s EvtDriverDeviceAdd callback routine. 2. It allocates a WDFWORKITEM object in a driver\'s EvtDriverDeviceAdd callback routine. 3. It allocates and then initializes a KEVENT object, queue the work item in the driver\'s EvtDeviceReleaseHardware callback routine, passing this event as the Context parameter, and wait for the event to be signaled. 4. In the work item callback routine, it delays a thread by approximately two seconds and then set an event. The exact delay value which is required may differ across the systems and should be tested earlier to the final implementation.
Know the Answer? Share it...
STOP 0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS ?
