System Thread Exception Not Handled Fix – Working BSOD Solution

After a Windows Update finishes and the system restarts, you might hit a BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. On my test machine (Windows 11, KB5147497), the crash happened right at the login screen. Checking SetupDiag.log showed nothing obvious — but digging into WinSxS and service states revealed the real mess.

This usually happens when thread execution gets blocked by mismatched component store files and the Windows Update Service being half‑enabled. I tried the standard DISM + SFC first, but that didn’t fix it at first. What finally worked was a different order: enable the update‑related services before running DISM, then force a repair install as the last resort.

Step that stopped the BSOD loop (unverified path, but worked twice)

Instead of following the usual “DISM → SFC” chain, I reversed it:

• Open Command Prompt as administrator.
• Enable all update services manually:
  sc config wuauserv start= auto & net start wuauserv
sc config bits start= auto & net start bits
sc config cryptsvc start= auto & net start cryptsvc
• Then run DISM repair: DISM /Online /Cleanup-Image /RestoreHealth
• After DISM completes, execute SFC scan: sfc /scannow

In some cases the SFC scan reported corrupted files but couldn’t fix them — that’s when you move to a repair install (keep apps and data). I’ve seen this stop the system thread exception immediately on two Windows 10 machines. However, this path hasn’t been verified on all hardware, so your mileage may vary.

Why does this happen? The update completion stage loads thread‑related drivers. If the component store (WinSxS) is inconsistent and the Windows Update Service is misconfigured, the kernel throws SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. The reverse order (services first, then DISM) ensures the servicing stack is healthy before touching the image. If the BSOD reappears after a reboot, try the branch: when SFC fails, go directly to Repair Install via the Windows ISO (setup /auto upgrade). That finally resolved the crash for me after two failed attempts.

Looking for a working system thread exception not handled fix? The combination of service enablement + DISM + SFC is what finally broke the loop. And if you’re troubleshooting system thread exception windows 10 solution or how to repair system thread exception, don’t waste time on generic driver updates — focus on the servicing stack and service states.