| Previous | Next |
| WORKER_INVALID | DRIVER_VERIFIER_DMA_VIOLATION |
POWER_FAILURE_SIMULATE
Simulated power failure for POWER_FAILURE_SIMULATE
POWER_FAILURE_SIMULATE is bug check code 0x000000E5. This code is not normally interpreted as spontaneous hardware failure. It is useful when testing dump capture, power-failure recovery, crash handling, or validation paths that intentionally force a stop.
How to read it in a dump for POWER_FAILURE_SIMULATE
- Confirm whether a test tool, verifier setting, lab script, or internal trigger requested the simulated failure.
- If it appears unexpectedly, look for power-test infrastructure or debug configuration.
- The reason is usually outside ordinary application behavior.
What to check for POWER_FAILURE_SIMULATE
- Check lab automation, verifier settings, crash-test scripts, and power-management test tools.
- Do not replace hardware solely because this code appears.
- Preserve dump configuration evidence because the crash may have been intentional.
References for POWER_FAILURE_SIMULATE
- Introduction to power management
- Analyze a kernel-mode dump with WinDbg
- Microsoft Bug Check Code Reference
Dump evidence for POWER_FAILURE_SIMULATE
For POWER_FAILURE_SIMULATE, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “POWER_FAILURE_SIMULATE”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for POWER_FAILURE_SIMULATE
- Run WinDbg
!analyze -v, then inspect the documented meaning of each POWER_FAILURE_SIMULATE parameter instead of relying only on the probably-caused-by line. - For POWER_FAILURE_SIMULATE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with power / simulate.
- For POWER_FAILURE_SIMULATE, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by POWER_FAILURE_SIMULATE before collecting the dump and event logs. For POWER_FAILURE_SIMULATE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for POWER_FAILURE_SIMULATE
For POWER_FAILURE_SIMULATE, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “POWER_FAILURE_SIMULATE”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for POWER_FAILURE_SIMULATE
- Run WinDbg
!analyze -v, then inspect the documented meaning of each POWER_FAILURE_SIMULATE parameter instead of relying only on the probably-caused-by line. - For POWER_FAILURE_SIMULATE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with power / simulate.
- For POWER_FAILURE_SIMULATE, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by POWER_FAILURE_SIMULATE before collecting the dump and event logs. For POWER_FAILURE_SIMULATE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.