Windows Driver Kit: Driver Development Tools
Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE
The DRIVER_POWER_STATE_FAILURE bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.
Parameters
The following parameters appear on the blue screen. Parameter 1 indicates the type of violation.
| Parameter 1 | Parameter 2 | Parameter 3 | Parameter 4 | Cause |
|---|
| 0x1 | The device object | Reserved | Reserved | The device object that is being freed still has an outstanding power request that it has not completed. |
| 0x2 | The target device's device object, if it is available | The device object | The driver object, if it is available | The device object completed the I/O request packet (IRP) for the system power state request, but it failed to call PoStartNextPowerIrp. |
| 0x3 (Windows 2000 only) | A pointer to the target device object | A pointer to the device object | The IRP | The device driver did not properly set the IRP as "pending" or complete the IRP. |
| 0x3 (Windows XP and later) | The physical device object (PDO) of the stack | The functional device object (FDO) of the stack | The blocked IRP | A device object has been blocking an IRP for too long a time. |
| 0x100 (Windows 2000 only) | A pointer to the nonpaged device object | A pointer to the target device object | A pointer to the device object to notify | The device objects in the devnode inconsistently used DO_POWER_PAGABLE. |
| 0x101 (Windows 2000 only) | The child device object (FDO) | The child device object (PDO) | The parent device object | A parent device object has detected that a child device has not set the DO_POWER_PAGABLE bit. |
| 0x500 (Windows XP and Windows Server 2003 only) | Reserved | The target device's device object, if available | Device object | The device object completed the IRP for the system power state request, but it failed to call PoStartNextPowerIrp. |
Cause
For a description of the possible causes, see the description of each code in the Parameters section.
The errors that cause Parameter 1 to be 0x3, 0x100, or 0x101 only exist in Microsoft Windows 2000. In Windows XP and later versions of Windows, these errors are superseded by Driver Verifier tests. For more information about Driver Verifier, see Driver Verifier.