What is the order drivers are shutdown (at least the critical ones like
those of disk, file system and also tcp stack) . Is it the reverse order
they come
up at boot according to the Registry (start=0,1,2… and also and also
location at ServiceGroupOrder and GroupOrderList.) or there is some
location at the registry where this is defined explicitly ?
I don’t think that IP stack itself is ever shut down, but the underlying miniports are surely yes, and sometimes this can cause problems in TDI client code - for instance, being unable to send a FIN on shutdown due to NIC adapter already down. TDI PnP callbacks can be helpful to solve this.
The order of shutdown is:
- MJ_SHUTDOWN for the drivers which registered for it
- MJ_SHUTDOWN for FSD volumes
- MJ_SHUTDOWN for disk stacks (in fact propagated by the FSD down the disk stack)
- MJ_POWER IRPs.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: Zvi Dubitzky
To: Windows System Software Devs Interest List
Sent: Thursday, October 14, 2004 10:45 PM
Subject: [ntdev] drivers shutdown order
What is the order drivers are shutdown (at least the critical ones like those of disk, file system and also tcp stack) . Is it the reverse order they come
up at boot according to the Registry (start=0,1,2… and also and also location at ServiceGroupOrder and GroupOrderList.) or there is some location at the registry where this is defined explicitly ?
— Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 You are currently subscribed to ntdev as: xxxxx@storagecraft.com To unsubscribe send a blank email to xxxxx@lists.osr.com