CRITICAL_SERVICE_FAILED (0x5A) BSOD after enabling UEFI Secure Boot on Windows 10

Troubleshooting Critical Service Failed (0x5A) BSOD After Enabling UEFI Secure Boot on Windows 10

Enabling UEFI Secure Boot on your Windows 10 system can enhance security by preventing unauthorized software from executing during startup. However, users sometimes encounter critical system errors, such as the Blue Screen of Death (BSOD) with the bug check code CRITICAL_SERVICE_FAILED (0x5A), following this change. Below is an overview of this issue, its potential causes, and recommended troubleshooting steps to resolve it without resorting to a full reinstall.

Understanding the Issue

The BSOD occurs during driver loading, as evidenced by analysis tools like WinDbg pointing to nt!IopLoadDriver. This suggests an incompatibility or conflict with a driver that is either unsigned or not properly configured for UEFI Secure Boot.

Condition Trigger:
The crash specifically manifests after switching the BIOS mode to UEFI from “Other OS” on an ASUS motherboard, with subsequent attempts to boot into Windows 10 failing repeatedly, including Safe Mode.

User Goals:
– Enable Secure Boot for Windows 11 compatibility
– Maintain system stability during and after Secure Boot activation

Common Troubleshooting Measures Already Attempted

Converting all disks to GPT partitioning style
Ensuring the BIOS is set to UEFI rather than Legacy/CSM mode
Clearing and resetting the TPM (Trusted Platform Module)
Reconfiguring security keys associated with Secure Boot
Restoring BIOS to default settings and updating firmware
Using Autoruns to identify unsigned or conflicting drivers
Removing potentially conflicting software or drivers

Despite these efforts, the BSOD persists, signalling that underlying driver or configuration issues require further investigation.

Recommended Diagnostic and Resolution Steps

1. Verify Driver Signatures and Compatibility
Secure Boot enforces driver integrity; unsigned drivers can cause boot failures. Review system drivers for signatures:

Use sigcheck (Sysinternals) or DriverView to examine driver signatures.
Disable non-essential third-party drivers temporarily to identify incompatibilities.

2. Enable Boot Logging for Detailed Error Analysis
Capture detailed boot logs for pinpointing problematic drivers: