| Previous | Next |
| BOOTLOG_NOT_LOADED | ATTEMPTED_SWITCH_FROM_DPC |
BOOTLOG_ENABLED
Boot logging enabled marker for BOOTLOG_ENABLED
BOOTLOG_ENABLED is bug check code 0x000000B7. This value is diagnostic context. It means the boot path is recording driver-load progress, which can be used to correlate a later crash or hang with driver-load ordering.
How to read it in a dump for BOOTLOG_ENABLED
- Do not treat the marker as a failing driver.
- It is useful for reconstructing boot order and comparing multiple boot modes.
- Combine it with loaded and not-loaded entries.
What to check for BOOTLOG_ENABLED
- Preserve the boot log before retrying many times.
- Compare the last successful and failed boot logs.
- Use it together with dump analysis rather than as a replacement for a crash dump.
References for BOOTLOG_ENABLED
- Installing a boot-start driver
- Analyze a kernel-mode dump with WinDbg
- Microsoft Bug Check Code Reference
Dump evidence for BOOTLOG_ENABLED
For BOOTLOG_ENABLED, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. For BOOTLOG_ENABLED, allStat summarizes the condition as “Boot Logging Enabled”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for BOOTLOG_ENABLED
- Run WinDbg
!analyze -v, then inspect the documented meaning of each BOOTLOG_ENABLED parameter instead of relying only on the probably-caused-by line. - For BOOTLOG_ENABLED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with bootlog / enabled.
- For BOOTLOG_ENABLED, 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 BOOTLOG_ENABLED before collecting the dump and event logs. For BOOTLOG_ENABLED, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for BOOTLOG_ENABLED
For BOOTLOG_ENABLED, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. For BOOTLOG_ENABLED, allStat summarizes the condition as “Boot Logging Enabled”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for BOOTLOG_ENABLED
- Run WinDbg
!analyze -v, then inspect the documented meaning of each BOOTLOG_ENABLED parameter instead of relying only on the probably-caused-by line. - For BOOTLOG_ENABLED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with bootlog / enabled.
- For BOOTLOG_ENABLED, 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 BOOTLOG_ENABLED before collecting the dump and event logs. For BOOTLOG_ENABLED, 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.