0x00000120 BITLOCKER_FATAL_ERROR – Causes and Troubleshooting Guide

Quick Answer

0x00000120 BITLOCKER_FATAL_ERROR is a Windows Blue Screen of Death (BSOD) stop code indicating that BitLocker drive encryption encountered a problem from which it could not recover. When this condition occurs, Windows stops operating to prevent further system-level problems.

BitLocker is Microsoft's built-in drive encryption technology that protects data stored on Windows computers. This error is associated with a fatal condition in the BitLocker encryption subsystem. However, the stop code alone does not identify the exact underlying cause.

To investigate this error, users should check BitLocker protection status, review recent firmware and system changes, verify available recovery keys, examine Windows crash information and update relevant drivers or firmware where appropriate.

What Is BITLOCKER_FATAL_ERROR (0x00000120)?

BITLOCKER_FATAL_ERROR is a Windows bug check that occurs when the BitLocker drive encryption subsystem encounters an unrecoverable problem.

A bug check, commonly known as a Blue Screen of Death (BSOD), is a protective mechanism that Windows uses when it encounters a critical system condition that prevents safe operation.

Microsoft identifies this error using the following information:

Parameter	Description
Stop Code	0x00000120
Bug Check Name	BITLOCKER_FATAL_ERROR
Decimal Value	288
Category	Windows Kernel Bug Check
Associated Technology	BitLocker Drive Encryption
Typical Result	Windows stops and displays a blue screen or stop error screen.

According to Microsoft's official documentation, the first bug check parameter identifies the type of problem. The remaining three parameters are reserved.

Microsoft does not provide a general user-level mapping of the first parameter to specific hardware failures, configuration problems or repair procedures. Therefore, additional diagnostic information is required to determine the actual cause.

What Is BitLocker Drive Encryption?

BitLocker is a Windows security feature that encrypts entire volumes to protect stored information against unauthorized access.

For example, if a laptop is lost or its storage drive is removed and connected to another computer, BitLocker encryption helps prevent unauthorized users from accessing the protected data without the required authentication or recovery credentials.

BitLocker can use several security mechanisms, including:

• Trusted Platform Module (TPM): A hardware security component that can securely store cryptographic information and help validate the computer's startup environment.
• Recovery Password: A 48-digit numerical password used to regain access to a BitLocker-protected drive when normal unlocking methods are unavailable.
• Startup PIN: An additional authentication mechanism that can be required before Windows starts.
• Startup Key: A key stored on removable media that can be used to unlock a protected operating system drive.
• Platform Configuration Registers (PCRs): TPM registers that record measurements of system startup components and help BitLocker determine whether the startup environment has changed.

BitLocker works with Windows startup and security components to ensure that encrypted data remains protected. A serious failure in this subsystem can result in the BITLOCKER_FATAL_ERROR bug check.

For more information, refer to Microsoft's BitLocker Overview.

Symptoms of 0x00000120 BITLOCKER_FATAL_ERROR

A computer experiencing this stop code may exhibit one or more of the following symptoms:

• Windows displays a blue screen with the stop code BITLOCKER_FATAL_ERROR.
• The computer unexpectedly restarts during normal operation.
• The system crashes during startup or while accessing protected storage.
• The computer experiences repeated crashes with the same stop code.
• Windows becomes inaccessible until the system is restarted or recovered.
• A BitLocker recovery screen may appear during startup if a separate recovery condition is also present.

Not every system will exhibit all these symptoms. The actual behavior depends on when and how the underlying failure occurs.

Possible Causes of BITLOCKER_FATAL_ERROR

Microsoft identifies this bug check as an unrecoverable BitLocker encryption problem but does not publish a definitive list of causes for every occurrence. The following situations are relevant areas to investigate, not confirmed causes of this specific stop code.

1. BitLocker or Encryption Subsystem Failure

A failure involving BitLocker-related system components may result in an unrecoverable encryption-related condition.

Investigating crash dump information and Windows system events can help determine whether the failure originated in a BitLocker-related component or another part of the operating system.

2. Firmware or BIOS Changes

Changes to BIOS or UEFI firmware can affect the system startup measurements used by TPM-based BitLocker protection.

Examples include:

• BIOS or UEFI firmware updates.
• Changes to Secure Boot configuration.
• Changes to TPM settings.
• Changes to boot configuration.
• Hardware configuration changes that affect platform measurements.

Such changes are particularly relevant when investigating BitLocker recovery events. However, a firmware change alone does not establish the cause of bug check 0x120.

3. TPM-Related Problems

BitLocker can use the Trusted Platform Module to protect encryption keys and validate the system startup environment.

TPM-related problems, firmware inconsistencies or changes in platform security configuration may affect BitLocker operations.

Check the TPM status and system security configuration before considering any changes to TPM settings.

4. Windows Updates or System Component Changes

Windows updates modify operating system components, drivers and sometimes startup-related files.

Although updates are not established as a direct universal cause of this stop code, recent system changes should be reviewed when a crash begins immediately after an update or upgrade.

5. Device Driver or Storage-Related Problems

Storage controller drivers, firmware and other system-level components can influence how Windows communicates with storage devices.

A faulty or incompatible driver may contribute to system instability. Diagnostic information is required to establish whether a driver was involved in a particular BITLOCKER_FATAL_ERROR crash.

6. System File or Operating System Corruption

Damaged Windows system components can interfere with normal operating system functionality.

If the crash began after an interrupted update, unexpected shutdown or other system failure, checking Windows component integrity may be useful.

How to Troubleshoot 0x00000120 BITLOCKER_FATAL_ERROR

Follow the troubleshooting procedures below in order. Start with data protection and basic diagnostics before attempting advanced recovery operations.

Step 1: Restart the Computer

If the error occurred only once, restart the computer and check whether Windows starts normally.

1. Allow the computer to complete its restart.
2. Check whether Windows loads successfully.
3. Observe whether the same stop code appears again.
4. Note any recent changes that occurred before the crash.

A single occurrence does not necessarily indicate permanent damage. However, repeated crashes require further investigation.

Step 2: Locate and Secure the BitLocker Recovery Key

This is an important precaution before performing recovery or system repair operations.

If the operating system drive is encrypted, make sure that the correct BitLocker recovery key is available before making significant changes to the system.

The 48-digit recovery password may be stored in one of the following locations:

• Microsoft Account: Visit Microsoft BitLocker Recovery Keys and sign in with the account associated with the device.
• Microsoft Entra ID: Business users may have recovery keys stored in their organization's Microsoft Entra environment.
• Active Directory: Domain administrators may be able to retrieve recovery information from Active Directory Domain Services.
• USB Drive: The recovery password may have been saved to a removable storage device.
• Printed or Saved Copy: The recovery information may have been printed or saved in a secure location.

For organizational computers, contact the IT administrator if the recovery key is managed centrally.

Important: Never share the BitLocker recovery key publicly or store it on an unprotected device. Anyone with the required recovery credentials may be able to unlock the encrypted drive.

Step 3: Check BitLocker Protection Status

If Windows starts successfully, check the current BitLocker configuration.

1. Right-click the Start button.
2. Select Terminal (Admin) or Command Prompt (Admin).
3. Approve the User Account Control prompt if displayed.
4. Run the following command:

manage-bde -status

This command displays BitLocker information for available volumes.

Important information includes:

• Conversion Status.
• Percentage Encrypted.
• Encryption Method.
• Protection Status.
• Lock Status.
• Key Protectors.

For example, a volume may show that protection is on, off or suspended. These values help establish the current encryption state.

The command is diagnostic and does not modify BitLocker configuration.

Step 4: Check Recent BIOS and Firmware Changes

If the problem started after a BIOS update or firmware modification, investigate the changes made to the system.

1. Identify the computer manufacturer and exact model.
2. Check the BIOS or UEFI version currently installed.
3. Review recent firmware updates or configuration changes.
4. Check whether TPM and Secure Boot are enabled according to the manufacturer's supported configuration.
5. Review the manufacturer's documentation for known firmware issues.

Do not randomly clear the TPM, change Secure Boot settings or reset BIOS security configuration. Such actions may trigger BitLocker recovery or create additional access problems.

If a firmware update is required, ensure that the BitLocker recovery key is available and follow the manufacturer's instructions. Microsoft recommends suspending BitLocker protection before certain firmware updates that modify startup components and resuming protection after the update is complete.

Refer to Microsoft's BitLocker Recovery Process for additional guidance.

Step 5: Check Windows Event Logs

Windows Event Viewer can provide information about system failures, BitLocker activity and errors that occurred before the crash.

1. Press Windows + R.
2. Type eventvwr.msc and press Enter.
3. Expand Windows Logs.
4. Select System.
5. Review critical errors and warnings around the time of the crash.
6. Check relevant BitLocker-related events where available.

Look for information about:

• Unexpected system shutdowns.
• Storage or disk-related errors.
• TPM or firmware-related events.
• Driver failures.
• BitLocker protection or recovery events.

Record the event source, Event ID, timestamp and complete message. These details can help establish whether another system component failed before the BitLocker-related bug check.

Step 6: Update Windows and Device Drivers

If Windows is operating normally but the error occurred recently, check for available operating system and driver updates.

1. Open Windows Settings.
2. Select Windows Update.
3. Check for available updates.
4. Install applicable updates.
5. Open Device Manager.
6. Check storage controllers, chipset devices and other relevant hardware for warning indicators.
7. Install compatible drivers from the computer or hardware manufacturer's official website.
8. Restart the computer and monitor its stability.

Avoid installing unofficial driver packages or firmware from unverified websites.

If the error began immediately after installing a particular driver or update, investigate that specific change before applying additional updates.

Step 7: Check Windows System File Integrity

If there is evidence of Windows component corruption, use Microsoft's built-in Deployment Image Servicing and Management (DISM) and System File Checker (SFC) utilities.

Open Windows Terminal or Command Prompt as an administrator.

First, run:

DISM /Online /Cleanup-Image /RestoreHealth

This command checks and repairs the Windows component store using available repair sources.

After DISM completes, run:

sfc /scannow

System File Checker scans protected Windows system files and attempts to repair corrupted or missing files.

Restart the computer after both operations have completed.

Note: These utilities are general Windows integrity checks. They are not a guaranteed repair for BITLOCKER_FATAL_ERROR and should not be considered proof that the BitLocker subsystem was the original source of the crash.

Step 8: Start Windows in Safe Mode

If Windows repeatedly crashes during normal startup, Safe Mode can help investigate whether a recently installed driver, service or application is contributing to the instability.

To access Safe Mode when Windows cannot start normally:

1. Enter the Windows Recovery Environment (Windows RE).
2. Select Troubleshoot.
3. Select Advanced options.
4. Choose Startup Settings.
5. Select Restart.
6. After restarting, select the Safe Mode option.

Depending on the computer's security configuration, BitLocker recovery authentication may be required before accessing recovery tools or protected Windows files.

Once Safe Mode loads, investigate recently installed drivers, applications and system changes.

Step 9: Analyze the Crash Dump

If the computer repeatedly produces the same stop code, analyzing its crash dump can provide more detailed information about the failure.

Windows may store crash dump files in the following locations:

• C:\Windows\Minidump - Small memory dump files.
• C:\Windows\MEMORY.DMP - Kernel or complete memory dump, depending on system configuration.

Use WinDbg (Windows Debugger) to analyze the available dump file.

After opening the dump in WinDbg, execute:

!analyze -v

This command displays detailed bug check information, including the stop code, parameters, stack information and other available diagnostic details.

For this error, review:

• The bug check parameters.
• The call stack.
• Any identified faulting module.
• Relevant driver or system component information.
• Additional diagnostic information associated with the crash.

The first parameter of BITLOCKER_FATAL_ERROR is documented as the type of problem, but its exact meaning must be interpreted using appropriate debugging information. Do not assume that a particular module name in the dump automatically identifies the root cause.

Microsoft provides additional information in its Windows Debugging documentation.

What to Do If Windows Cannot Start?

If the computer repeatedly crashes and cannot reach the Windows desktop, use Windows Recovery Environment to investigate the problem.

1. Enter Windows Recovery Environment

Windows RE provides recovery and troubleshooting tools that can be used when the operating system cannot start normally.

Depending on the system, Windows RE may open automatically after repeated unsuccessful startup attempts. It can also be accessed using Windows installation or recovery media.

2. Check BitLocker Recovery Requirements

If the Windows recovery environment requests a BitLocker recovery password, enter the correct 48-digit recovery password for the affected drive.

Make sure that the recovery key corresponds to the correct device and recovery key identifier.

3. Try Startup Repair

From Windows RE, navigate to:

Troubleshoot
> Advanced options
> Startup Repair

Startup Repair checks certain startup-related problems and attempts to repair issues preventing Windows from starting.

It is a general Windows startup repair tool and is not specifically designed to repair every BitLocker fatal error.

4. Consider System Restore

If a suitable restore point exists, System Restore may help reverse certain recent system changes.

Before using this option:

• Confirm that the required BitLocker recovery information is available.
• Understand that recently installed applications, drivers and system changes may be reversed.
• Ensure that important data is backed up wherever possible.

System Restore does not guarantee recovery from an encryption subsystem failure.

5. Seek Professional Recovery Assistance

If the drive remains inaccessible, Windows repeatedly crashes or the available recovery options fail, contact Microsoft support or the computer manufacturer's technical support team.

For business systems, involve the organization's IT administrator before attempting additional recovery operations.

Important Precautions When Troubleshooting BitLocker Errors

BitLocker protects data through encryption. Incorrect recovery operations can make access to important information difficult or impossible.

Keep the following precautions in mind:

• Keep the recovery key safe: Verify that the recovery password is available before making significant system changes.
• Do not clear the TPM unnecessarily: Clearing the TPM can affect access to TPM-protected keys and credentials.
• Avoid formatting encrypted drives: Formatting can destroy access to existing data.
• Do not disable encryption blindly: Decrypting a drive is not a universal solution to this bug check.
• Do not repeatedly change BIOS settings: Unnecessary firmware changes can trigger additional BitLocker recovery events.
• Use official firmware and drivers: Obtain updates from the system or component manufacturer.
• Protect crash dumps: Memory dump files may contain sensitive system information. Do not upload them to public websites without reviewing their contents and security implications.

How to Prevent BitLocker-Related System Problems

Although every BitLocker-related failure cannot be prevented, appropriate system maintenance and recovery planning can reduce operational risks.

• Keep Windows and supported hardware drivers updated.
• Install BIOS and firmware updates from official manufacturer sources.
• Follow BitLocker suspension and resumption guidance when performing supported firmware or boot-related maintenance.
• Maintain secure backups of important data.
• Store BitLocker recovery keys in an approved, secure location.
• Ensure that IT administrators can retrieve recovery keys for managed computers.
• Avoid unnecessary changes to TPM and Secure Boot configuration.
• Monitor Windows system logs for recurring encryption and startup-related errors.
• Document significant hardware, firmware and operating system changes.

Frequently Asked Questions (FAQs)

1. What does stop code 0x00000120 BITLOCKER_FATAL_ERROR mean?

It means that BitLocker drive encryption encountered an unrecoverable problem. Windows generates this bug check when the encryption subsystem reaches a fatal condition that it cannot recover from.

2. Is BITLOCKER_FATAL_ERROR related to a hard disk failure?

Not necessarily. The stop code identifies a fatal BitLocker-related condition, not a confirmed physical disk failure. Storage-related errors may be worth investigating, but additional diagnostic evidence is required to determine whether the drive is involved.

3. Can I fix 0x00000120 without reinstalling Windows?

Possibly. The appropriate solution depends on the underlying cause. Checking BitLocker status, reviewing system changes, updating compatible drivers and analyzing crash dumps may help identify and resolve the problem without reinstalling Windows.

4. Will disabling BitLocker fix this error?

There is no universal guarantee that disabling BitLocker will resolve this bug check. Decrypting a drive is a significant operation and should not be attempted as an initial troubleshooting measure. First identify the cause and secure the recovery key.

5. Can a BIOS update trigger BitLocker problems?

Firmware updates can change startup measurements used by TPM-based BitLocker protection. This can trigger BitLocker recovery under certain circumstances. Microsoft recommends following the appropriate BitLocker suspension and recovery procedures when performing firmware updates.

6. What is the purpose of the BitLocker recovery key?

The BitLocker recovery key is an alternative authentication method used to unlock an encrypted drive when normal unlocking methods are unavailable. The standard numerical recovery password contains 48 digits.

7. Does this error mean that my encrypted data is lost?

No. The stop code itself does not establish that encrypted data has been lost or corrupted. Data accessibility depends on the condition of the storage device, encryption metadata and availability of valid unlocking credentials.

8. Can I use Safe Mode to fix BITLOCKER_FATAL_ERROR?

Safe Mode can help investigate certain driver, service and software-related problems. However, it is not a dedicated BitLocker repair utility and may not resolve an underlying encryption subsystem failure.

9. Which tool can analyze the 0x00000120 crash?

WinDbg (Windows Debugger) can analyze Windows crash dump files. The !analyze -v command provides detailed bug check information that can assist with identifying the failure.

10. When should I contact technical support?

Contact Microsoft or the computer manufacturer's support team if the error occurs repeatedly, Windows cannot start, the encrypted drive remains inaccessible or crash dump analysis does not identify a reliable repair procedure. Business users should involve their IT administrator before attempting advanced recovery operations.

Conclusion

The 0x00000120 BITLOCKER_FATAL_ERROR stop code indicates that Windows encountered an unrecoverable problem involving BitLocker drive encryption. It should be treated as a serious system error, particularly when it occurs repeatedly or prevents access to an encrypted operating system drive.

The safest troubleshooting approach is to secure the BitLocker recovery key, inspect the current encryption status, review recent firmware and system changes, examine Windows event logs and analyze crash dump information where available.

Avoid unnecessary TPM resets, drive formatting or encryption changes. Identifying the actual cause before attempting advanced recovery operations helps protect encrypted data and reduces the risk of creating additional system problems.

Official References

• Microsoft Learn – Bug Check 0x120: BITLOCKER_FATAL_ERROR
• Microsoft Learn – BitLocker Overview
• Microsoft Learn – BitLocker Recovery Process
• Microsoft Learn – BitLocker Operations Guide
• Microsoft Support – Troubleshooting Windows Unexpected Restarts and Stop Code Errors
• Microsoft Learn – Windows Debugging Documentation