irql not less or equal bsod fix - FIX IRQL Error (irql error windows 10 solution)

You’re in the second boot stage after a Windows Update, and suddenly — BSOD: IRQL NOT LESS OR EQUAL. The system crashes while loading drivers, especially after updating via Windows Update. This usually happens when a driver conflicts with the Windows Update service, causing a kernel memory access violation. In some cases, you'll see the update stall around 87% in DISM.log, and the error points to component mismatch tied to CBS.

Quick steps that actually worked (most of the time)

Instead of chasing every possible fix, here are three actions that break the crash loop. Didn’t fix it at first? Try them in order.

1. Reset CBS components

Open Command Prompt as admin and run:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

This resets the component store. After that, reboot — the IRQL error may disappear. Look for KB5147488 in update history; if it’s partially installed, this step cleans the mismatch.

2. Delete pending.xml (update state reset)

Navigate to C:\Windows\WinSxS and delete pending.xml (make a backup first). This forces Windows Update to rebuild the queue. Branch logic: If pending.xml reset fails → re-register components using regsvr32 on wuapi.dll, wuaueng.dll.

3. Manual update installation (unverified path)

If the above methods didn’t hold, download the standalone update package from Microsoft Update Catalog (matching your Windows version). Install it manually. Note: This approach hasn’t been verified in all environments — it worked on a few systems with the same IRQL crash after KB5147488, but your mileage may vary.

In DISM.log, you’ll often see a state signal stuck at 87% before the crash. That’s the CBS component mismatch. The real solution path is: Pending.xml → CBS Reset → Manual Install + Enable Services. But you don’t always need all steps.

Avoid repeatedly force-restarting — it doesn’t help. Also, don’t skip the CBS reset; otherwise the driver conflict remains. After applying any of these methods, check if the system boots without BSOD and drivers load correctly.

Looking for “how to fix irql not less or equal” or “irql bsod after update fix”? The steps above cover both Windows 10 and 11. A “WORKING BSOD Solution” doesn’t exist for every machine, but resetting CBS + deleting pending.xml resolves the majority of cases.