What does BSOD 170 (BOOTING_IN_SAFEMODE_DSREPAIR) mean?

 
Could be also:
ConstantTypeOS
ERROR_BUSYWin32 errorWindows
Previous Next
BOOTING_IN_SAFEMODE_NETWORK SESSION_HAS_VALID_POOL_ON_EXIT

BOOTING_IN_SAFEMODE_DSREPAIR

Directory Services Repair Mode marker for BOOTING_IN_SAFEMODE_DSREPAIR

BOOTING_IN_SAFEMODE_DSREPAIR is bug check code 0x000000AA. This boot-state marker is meaningful on domain controllers or systems entering Directory Services Repair Mode. It changes which services and identity stores are expected to be active during diagnosis.

How to read it in a dump for BOOTING_IN_SAFEMODE_DSREPAIR

  • Interpret the dump with the DSRM boot profile in mind.
  • Directory services, storage, security policy, and boot-critical drivers are more relevant than normal workstation logon behavior.
  • The marker is not itself a failing component.

What to check for BOOTING_IN_SAFEMODE_DSREPAIR

  • Check whether the machine is a domain controller or was intentionally started in DSRM.
  • Review directory-service database, security policy, and storage health.
  • Compare with normal and minimal Safe Mode boot results.

References for BOOTING_IN_SAFEMODE_DSREPAIR

Dump evidence for BOOTING_IN_SAFEMODE_DSREPAIR

For BOOTING_IN_SAFEMODE_DSREPAIR, 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 BOOTING_IN_SAFEMODE_DSREPAIR, allStat summarizes the condition as “The system is booting in safemode - Directory Services Repair”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for BOOTING_IN_SAFEMODE_DSREPAIR

  • Run WinDbg !analyze -v, then inspect the documented meaning of each BOOTING_IN_SAFEMODE_DSREPAIR parameter instead of relying only on the probably-caused-by line.
  • For BOOTING_IN_SAFEMODE_DSREPAIR, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with booting / in / safemode / dsrepair.
  • For BOOTING_IN_SAFEMODE_DSREPAIR, 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 BOOTING_IN_SAFEMODE_DSREPAIR before collecting the dump and event logs. For BOOTING_IN_SAFEMODE_DSREPAIR, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for BOOTING_IN_SAFEMODE_DSREPAIR

For BOOTING_IN_SAFEMODE_DSREPAIR, 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 BOOTING_IN_SAFEMODE_DSREPAIR, allStat summarizes the condition as “The system is booting in safemode - Directory Services Repair”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for BOOTING_IN_SAFEMODE_DSREPAIR

  • Run WinDbg !analyze -v, then inspect the documented meaning of each BOOTING_IN_SAFEMODE_DSREPAIR parameter instead of relying only on the probably-caused-by line.
  • For BOOTING_IN_SAFEMODE_DSREPAIR, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with booting / in / safemode / dsrepair.
  • For BOOTING_IN_SAFEMODE_DSREPAIR, 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 BOOTING_IN_SAFEMODE_DSREPAIR before collecting the dump and event logs. For BOOTING_IN_SAFEMODE_DSREPAIR, 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.