How to fix Error 159 on Windows 11

by

Troubleshooting Guide: Error 159 – “The Address for the Thread ID Is Not Correct” (Windows 11)

Why This Error Happens

Error 159 typically occurs when a thread’s memory address reference becomes invalid due to corrupted system files, a mismatched or outdated device driver, or improper thread synchronization caused by a failing application module. This is often triggered after an incomplete Windows update, driver installation, or memory corruption in the process handling the thread. In some cases, it can also stem from third-party software conflicting with core Windows threading APIs (such as CreateThread or GetThreadContext).

Step-by-Step Resolution Guide

  1. Run System File Checker (SFC) and DISM
    Open Command Prompt as Administrator and run:
   sfc /scannow

Once complete, run:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be causing invalid thread address references.

  1. Update or Roll Back Device Drivers
    Go to Settings > Windows Update > Advanced Options > Optional Updates > Driver Updates, and install any pending driver updates. If the error started after a recent driver update, open Device Manager, right-click the affected device, select Properties > Driver tab > Roll Back Driver.

  2. Check Event Viewer for the Faulting Module
    Open Event Viewer (eventvwr.msc), navigate to Windows Logs > Application or System, and locate the Error 159 entry. Note the faulting module name (e.g., a .dll or .sys file) — this identifies which application or driver is triggering the thread error.

  3. Update or Reinstall the Affected Application
    If the error points to a specific application (not a core OS process), uninstall it via Settings > Apps > Installed Apps, download the latest version from the vendor, and reinstall it.

  4. Check for Memory Issues
    Run Windows Memory Diagnostic by typing mdsched.exe in the Start menu search, then select Restart now and check for problems. Faulty RAM can cause invalid thread addresses at the hardware level.

Alternative or Verification Steps

  • After completing the steps above, reopen the application that triggered Error 159 and monitor Event Viewer for 24–48 hours to confirm the event no longer appears.
  • If the error persists, boot into Safe Mode and attempt to reproduce the issue — if it does not occur in Safe Mode, a third-party service or startup program is likely the root cause, and a clean boot troubleshooting process should be performed.