| TABLE 2: Device Driver Registry Parameter Definitions That Affect Initialization Order |
| Value Name | Value Setting | Value Setting Description |
|
| Start | SERVICE_BOOT_START (0) | NTLDR or OSLOADER preloads driver so that it is in memory during the boot. Driver |
| | initializes just before SERVICE_SYSTEM_START drivers. |
| SERVICE_SYSTEM_START(1) | Driver loads and initializes after SERVICE_BOOT_START drivers have initialized. |
| SERVICE_AUTO_START (2) | Services subsystem loads and initializes the driver or service. |
| SERVICE_DEMAND_START (3) | Services subsystem starts the driver on demand. |
| SERVICE_DISABLED (4) | Driver or service does not load or initialize. |
| ErrorControl | IGNORE (0) | I/O Manager ignores errors the driver returns. No warning logs or displays. |
| NORMAL (1) | If the driver reports an error, a warning displays. |
| SEVERE (2) | If the driver returns an error and user didn't choose LastKnownGood, reboot into |
| | LastKnownGood. Otherwise, continue the boot. |
| CRITICAL (3) | If the driver returns an error and user didn't choose LastKnownGood, reboot into |
| | LastKnownGood. Otherwise, stop the boot with a blue screen crash. |
| Group | Group Name | Driver initializes when its group initializes. |
| Tag | Tag Number | Specifies location in group initialization order. |
| DependOnGroup | Group Name | Driver won't load unless a driver from the group specified loads. |
| DependOnService | Service Name | Driver or service won't load unless the specified driver or service loads. |