| Previous | Next |
| ERROR_SET_POWER_STATE_VETOED | ERROR_TOO_MANY_LINKS |
ERROR_SET_POWER_STATE_FAILED
The system BIOS failed an attempt to change the system power state.
ERROR_SET_POWER_STATE_FAILED has decimal value 1141 (0x475). It means that the platform firmware or BIOS path did not complete a requested system power-state transition. On current ACPI systems, the visible code can summarize a more detailed firmware, device, or platform transition failure recorded elsewhere.
Affected transitions
- entering or leaving sleep or hibernation
- a restart or shutdown path that depends on firmware power control
- platform-specific low-power states on laptops and Modern Standby systems
- virtual-machine power transitions implemented by emulated firmware
- device and bus state changes that prevent the platform from completing system sleep
The wording points below ordinary application policy. Closing user programs may remove workload, but persistent 1141 results require platform, firmware, chipset, and device-power evidence.
Information to capture
- computer model, firmware version, ACPI mode, operating-system build, and chipset drivers
- requested sleep state and whether hibernation or fast startup is involved
- Kernel-Power, ACPI, device-driver, WHEA, and firmware events around the transition
powercfg /a, system sleep diagnostics, SleepStudy where applicable, and last wake data- external devices, docks, storage adapters, and display hardware connected during failure
Record whether the system fails entering the state, remains powered unexpectedly, or cannot resume. Those are different transition phases and often implicate different firmware or device paths.
Troubleshooting order
- install supported BIOS/UEFI, chipset, storage, graphics, and power-management updates
- reproduce with external devices and optional docks removed
- restore supported firmware power settings rather than experimenting with undocumented toggles
- compare supported sleep states before and after configuration changes
- collect a power trace or vendor diagnostics when event logs do not identify the failing device
Firmware updates and power-state tests can interrupt service, so apply them during a maintenance window with recovery media and configuration backups available.
Application and administrator response
An application should report that the requested transition failed and preserve the platform code; it should not assume the system actually entered sleep. Management software must verify the resulting state and avoid declaring a maintenance reboot successful until a new boot is observed.
Administrators should not repeatedly force sleep on a platform that fails firmware transitions. Until corrected, use a supported alternative such as full shutdown if operational requirements permit and data is safely closed.
Difference from a veto
ERROR_SET_POWER_STATE_VETOED indicates that an application or driver refused the transition. Error 1141 says the BIOS or firmware attempt failed. A driver can still contribute indirectly, but the diagnostic trail should include platform firmware and ACPI behavior.
Example
After a BIOS update, a laptop intermittently powers off its display but never completes hibernation. The transition returns 1141 and ACPI events appear at the same time. Reverting to a supported firmware revision and updating the chipset package resolves the platform failure; changing application sleep timers does not.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: Powercfg command-line options
- Microsoft: Debugging power problems with standby
- Microsoft: System sleep criteria
Looking for a different code? Search another status or error code.