DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)

NTFSD
1

When the bug check DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
(ce) happens, is there any way to determine which pending operation (timers,
DPCs, worker threads, etc. ) was still out

standing?

Thanks,

Ken

2

You can trace IRPs by yourself and check outstanding IRPs before unloading

–

Regards,
ZG [@ Sydney]
Windows Driver Developer
[Remove ‘stopspam’ & ‘nospam’ when you send email to me]

“Ken Galipeau” wrote in message news:xxxxx@ntfsd…
When the bug check DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce) happens, is there any way to determine which pending operation (timers, DPCs, worker threads, etc. ) was still out

standing?

Thanks,

Ken

3

Are you talking about IRPs issued by the driver or IRPs passing through my
driver that are waiting for completion return?

Thanks,

Ken

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of ZG
Sent: Wednesday, February 16, 2005 1:05 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
(ce)

You can trace IRPs by yourself and check outstanding IRPs before unloading

–

Regards,
ZG [@ Sydney]
Windows Driver Developer
[Remove ‘stopspam’ & ‘nospam’ when you send email to me]

“Ken Galipeau” > wrote
in message news:xxxxx@ntfsd news:xxxxx …

When the bug check DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
(ce) happens, is there any way to determine which pending operation (timers,
DPCs, worker threads, etc. ) was still out

standing?

Thanks,

Ken

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com</news:xxxxx>

4

Well, IRPs which are issued by your driver *should* be traced and canceled.

Usually, IRPs which are passed through by your driver are counted by the upper drivers or the originator. These drivers take the responsible for canceling outstanding IRPs when they receive an unloading/stoping/removing. But, I think it’s better choice to count these IRPs in your driver as well and verify this in your unloading/removing routine, since some drivers who issue these IRPs may *forget* to cancel them.

–

Regards,
ZG [@ Sydney]
Windows Driver Developer
[Remove ‘stopspam’ & ‘nospam’ when you send email to me]

“Ken Galipeau” wrote in message news:xxxxx@ntfsd…
Are you talking about IRPs issued by the driver or IRPs passing through my driver that are waiting for completion return?

Thanks,

Ken

------------------------------------------------------------------------------

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of ZG
Sent: Wednesday, February 16, 2005 1:05 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)

You can trace IRPs by yourself and check outstanding IRPs before unloading

–

Regards,
ZG [@ Sydney]
Windows Driver Developer
[Remove ‘stopspam’ & ‘nospam’ when you send email to me]

“Ken Galipeau” wrote in message news:xxxxx@ntfsd…

When the bug check DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce) happens, is there any way to determine which pending operation (timers, DPCs, worker threads, etc. ) was still out

standing?

Thanks,

Ken

—
Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com