Surface Pro X (ARM) stuck on SYSTEM_THREAD_EXCEPTION_NOT_HANDLED after BitLocker prompt

Troubleshooting the Surface Pro X: Resolving SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Post-BitLocker Recovery

Introduction

The Microsoft Surface Pro X, powered by ARM architecture and running Windows 11, offers impressive performance and portability. However, like all complex systems, it can encounter issues that challenge even seasoned users. One such problem involves the device becoming unresponsive after a BitLocker recovery process, resulting in a persistent blue screen with the error code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

This article aims to guide users through understanding this error, troubleshooting steps, and potential solutions without resorting to a complete system reset.

Understanding the Issue

In this scenario, upon powering on, the Surface Pro X prompts for the BitLocker recovery key—indicating that Windows detected a possible change in hardware or security breach. After entering the key, instead of booting normally, the device displays a blue error screen with the mentioned code. Attempts to enter Safe Mode by pressing F4 during startup are unsuccessful, and diagnostic tools like WinRE do not produce minidump files or memory dumps, complicating the identification of the root cause.

Common Causes

• Corruption in system files or drivers
• Issues with BitLocker encryption or recovery process
• Hardware changes or failures
• Problems arising after Windows updates or driver installations

Troubleshooting Steps

1. Boot from a Recovery USB

Since the device cannot boot normally, using a Surface recovery drive is a viable first step. This method allows access to repair tools and system recovery options.

1. Attempt Startup Repair

2. Boot from the recovery USB

3. Navigate to the Advanced options menu

4. Select Startup Repair to automatically fix common startup issues

5. Check System Files

While sfc /scannow reports no violations, it’s important to ensure system integrity:

• From the recovery environment, open the Command Prompt
• Run: sfc /scannow (if possible)
• If issues are detected, consider running DISM commands:

bash
DISM /Online /Cleanup-Image /RestoreHealth

However, note that DISM may fail if it cannot access the necessary repair source. In such cases, supply a Windows repair source or use alternative repair methods.

1. Disable BitLocker Temporarily

If BitLocker encryption is suspected to interfere:

• Use the recovery environment to open Command Prompt
• Attempt to suspend BitLocker protection:

“`bash
manage-b