| Previous | Next |
| WORKER_THREAD_RETURNED_AT_BAD_IRQL | RESOURCE_NOT_OWNED |
MANUALLY_INITIATED_CRASH
The MANUALLY_INITIATED_CRASH bug check has a value of 0x000000E2. This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
MANUALLY_INITIATED_CRASH Parameters
None
Remarks for MANUALLY_INITIATED_CRASH
For more information about manually-initiated crash dumps, see Forcing a System Crash..
Dump evidence for MANUALLY_INITIATED_CRASH
For MANUALLY_INITIATED_CRASH, 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 “MANUALLY_INITIATED_CRASH”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for MANUALLY_INITIATED_CRASH
- Run WinDbg
!analyze -v, then inspect the documented meaning of each MANUALLY_INITIATED_CRASH parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with manually / initiated / crash.
- For MANUALLY_INITIATED_CRASH, 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 MANUALLY_INITIATED_CRASH before collecting the dump and event logs. For MANUALLY_INITIATED_CRASH, 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.