| Previous | Next |
| SESSION4_INITIALIZATION_FAILED | SESSION5_INITIALIZATION_FAILED |
SOFT_RESTART_FATAL_ERROR
Soft restart failure for SOFT_RESTART_FATAL_ERROR
SOFT_RESTART_FATAL_ERROR is bug check code 0x00000070. This code is tied to restart transition state rather than normal runtime execution. It is useful when the system crashes while rebooting, resuming a restart flow, or switching between boot phases without a full power cycle.
How to read it in a dump
- Correlate the dump time with shutdown, restart, firmware handoff, or update installation.
- Power and boot-transition drivers are more relevant than ordinary foreground applications.
- The stack should show whether the failure occurred before or after firmware/boot-loader handoff.
What to check
- Compare cold boot and warm restart behavior.
- Check firmware, chipset, storage, and power-management drivers.
- Look for pending-update and boot-status logs around the failed restart.
References
- Introduction to power management
- Boot-start driver distribution disk
- Microsoft Bug Check Code Reference
- Analyze a kernel-mode dump with WinDbg
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each 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 soft / restart / fatal.
- 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 this result before collecting the dump and event logs. 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.