Windows 11 24H2 Update Triggers SECURE_KERNEL_ERROR BSOD: What You Need to Know

Windows 11 24H2 Update Causes SECURE_KERNEL_ERROR BSOD

Learn how the Windows 11 24H2 update triggers SECURE_KERNEL_ERROR BSOD and find solutions to resolve this critical issue.

Microsoft’s recent Windows 11 24H2 updates have introduced a critical issue causing the dreaded Blue Screen of Death (BSOD) with the error code SECURE_KERNEL_ERROR (0x18B). This problem has affected users across various devices, leading to system instability and frustration. In response, Microsoft has initiated a Known Issue Rollback (KIR) to mitigate the impact.

Understanding the SECURE_KERNEL_ERROR (0x18B)

The SECURE_KERNEL_ERROR (0x18B) indicates a fatal error within the secure kernel of Windows 11. This error typically arises from compatibility issues introduced by recent updates, particularly affecting certain hardware configurations. Affected users may experience frequent system crashes, rendering their devices unusable.

Affected Updates and Devices

The issue has been linked to the following Windows 11 24H2 updates:

  • KB5053598 (March 11, Patch Tuesday)

  • KB5053656 (March 27, optional update)

  • KB5055523 (April 8, Patch Tuesday)

These updates have caused compatibility problems with specific hardware, leading to the SECURE_KERNEL_ERROR BSOD.

Microsoft’s Response: Known Issue Rollback (KIR)

To address this issue, Microsoft has deployed a Known Issue Rollback (KIR). This server-side mechanism remotely disables the problematic code introduced by the updates, effectively rolling back the changes causing the BSOD. The fix is being automatically pushed to all affected consumer and unmanaged business devices via Windows Update. However, the KIR propagation may take up to 24 hours to reach all systems.

Temporary Workarounds

While waiting for the KIR to take effect, users can try the following temporary solutions:

1. Update Intel Smart Sound Technology (SST) Drivers

Devices with Intel 11th Gen Core processors and Intel SST drivers (versions 10.29.0.5152 or 10.30.0.5152) are particularly affected. Updating these drivers to newer versions can resolve the issue. Users can check for driver updates through Windows Update or visit the device manufacturer’s website for the latest drivers.

2. Adjust Host Memory Buffer (HMB) Settings

Users with Western Digital NVMe SSDs, such as the WD Black SN770 and WD Blue SN580, have reported BSODs due to increased HMB allocation in Windows 11 24H2. Manually adjusting the HMB settings in the system’s registry can mitigate this problem. However, this may impact SSD performance and should be done cautiously.

3. Rollback to Previous Windows Version

If the above steps do not resolve the issue, users can consider rolling back to a previous version of Windows 11 (such as 23H2) until a permanent fix is available. This can be done through the “Recovery” options in Windows Settings.

Preventive Measures

To avoid encountering the SECURE_KERNEL_ERROR BSOD in the future:

  • Regularly check for and install Windows updates to ensure your system remains secure and stable.

  • Keep hardware drivers, especially for critical components like audio and storage devices, up to date.

  • Monitor official Microsoft channels for announcements regarding known issues and fixes.

Conclusion

The SECURE_KERNEL_ERROR BSOD caused by Windows 11 24H2 updates has disrupted many users’ computing experiences. Microsoft’s deployment of a Known Issue Rollback (KIR) is a step toward resolving the issue, but affected users may need to wait up to 24 hours for the fix to take effect. In the meantime, updating drivers, adjusting HMB settings, or rolling back to a previous Windows version can serve as temporary solutions. Staying informed and proactive can help mitigate the impact of such issues in the future.

Leave a Comment