Tech Reference
Most Common Windows Error Codes & How to Fix Them
Windows errors are cryptic by design. This guide translates the most frequent ones into plain English and gives you the fix, step by step.
Blue Screen of Death (BSOD) Errors
0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
What it means: A system process triggered an error that Windows could not recover from, usually caused by an incompatible or corrupt driver.
Most likely cause: Recently installed driver (graphics, USB, or network), corrupt system file, or failing RAM.
Fix: 1) Boot into Safe Mode (hold Shift while clicking Restart). 2) Open Device Manager and roll back the most recently updated driver. 3) Run sfc /scannow from an elevated Command Prompt. 4) If it persists, test RAM with Windows Memory Diagnostic.
IRQL_NOT_LESS_OR_EQUAL
What it means: A driver or kernel process tried to access a memory address it does not have permission to use.
Most likely cause: Faulty driver, overclocked RAM, or incompatible antivirus software.
Fix: 1) Disable any recent overclock settings in BIOS. 2) Update all drivers via Windows Update or the manufacturer's site. 3) Temporarily uninstall third-party antivirus to test. 4) Run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.
CRITICAL_PROCESS_DIED
What it means: A process essential to Windows operation stopped unexpectedly.
Most likely cause: Corrupt system files, failing hard drive, or a bad Windows update.
Fix: 1) Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. 2) Check your hard drive with chkdsk /f /r. 3) If the error started after an update, use Settings > Recovery > Go Back to roll back the update. 4) As a last resort, run a repair install from a Windows USB.
KERNEL_DATA_INPAGE_ERROR
What it means: Windows tried to read data from the page file (virtual memory on disk) and failed.
Most likely cause: Failing hard drive or SSD, bad sectors, or a loose SATA cable.
Fix: 1) Run chkdsk /f /r on your system drive. 2) Check drive health with CrystalDiskInfo (look for "Caution" or "Bad" status). 3) Reseat SATA and power cables. 4) If the drive is failing, back up immediately and replace it.
DPC_WATCHDOG_VIOLATION
What it means: A Deferred Procedure Call (DPC) took too long, triggering a timeout. Usually a driver hanging the system.
Most likely cause: Outdated SSD firmware, storage controller driver (especially with NVMe drives), or iGPU driver conflict.
Fix: 1) Update your SSD firmware from the manufacturer's site. 2) Update the Intel Rapid Storage Technology (IRST) or AMD StoreMI driver. 3) Update chipset drivers. 4) If on a laptop, update both integrated and discrete GPU drivers.
Windows Update Errors
0x80070002
What it means: Windows Update cannot find a file it expects. The update download is incomplete or corrupt.
Most likely cause: Interrupted download, corrupted update cache, or incorrect system date/time.
Fix: 1) Verify your date and time are correct (Settings > Time & Language). 2) Run the Windows Update Troubleshooter (Settings > Troubleshoot). 3) Clear the update cache: stop the Windows Update service (net stop wuauserv), delete contents of C:\Windows\SoftwareDistribution\Download, then restart the service. 4) Re-run Windows Update.
0x80240034
What it means: The update download itself is corrupt and cannot be installed.
Most likely cause: Network interruption during download, VPN interference, or disk space running low.
Fix: 1) Free up at least 20 GB on your system drive. 2) Disconnect VPN and try again. 3) Download the specific update manually from the Microsoft Update Catalog (catalog.update.microsoft.com) and install it. 4) If it persists, use the Media Creation Tool to perform an in-place upgrade.
0x800f081f
What it means: Windows cannot find the source files needed to install a feature or update component.
Most likely cause: Group Policy or registry settings blocking Windows Update from fetching repair files, or a corrupt component store.
Fix: 1) Run DISM /Online /Cleanup-Image /RestoreHealth. 2) If DISM fails, specify a source: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim (using a mounted Windows ISO). 3) Check Group Policy: Computer Configuration > Administrative Templates > System > ensure "Specify settings for optional component installation" is Not Configured.
Installation & Activation Errors
0x80070570
What it means: A file required for installation is corrupt or unreadable.
Most likely cause: Corrupt installation media (USB or ISO), bad RAM, or failing storage drive.
Fix: 1) Re-download the ISO and re-create the USB using the Media Creation Tool or Rufus. 2) Try a different USB port (preferably USB 2.0 for older systems). 3) Run Windows Memory Diagnostic to check for RAM errors. 4) If installing to an SSD, check the drive health first.
0xC004F074
What it means: Windows could not be activated because it cannot reach the Key Management Service (KMS) or the product key is invalid.
Most likely cause: No internet connection during activation, firewall blocking activation servers, or a mismatched product key.
Fix: 1) Verify internet connectivity. 2) Open an elevated Command Prompt and run slmgr /ato to force activation. 3) If on a corporate network, confirm with IT that the KMS server is reachable. 4) If the key is incorrect, re-enter it via Settings > Activation > Change Product Key.
0x8007025D
What it means: Windows setup failed while copying files to the installation drive.
Most likely cause: Corrupt USB installer, insufficient disk space, or a drive with bad sectors.
Fix: 1) Re-create the installation USB with a fresh ISO download. 2) During setup, delete all partitions on the target drive and let Windows create fresh ones. 3) Disconnect any extra hard drives during installation. 4) If the error repeats, the target drive may be failing -- test with another drive.
0xC1900101 (various sub-codes)
What it means: A driver compatibility issue prevented a Windows feature update from completing. The sub-code (e.g., 0x20017, 0x30018) indicates which phase failed.
Most likely cause: Outdated or incompatible driver (most commonly graphics, audio, or storage controllers).
Fix: 1) Update all drivers before retrying the update. 2) Disconnect non-essential peripherals (printers, external drives, docks). 3) Temporarily disable antivirus. 4) Check C:\$WINDOWS.~BT\Sources\Panther\setuperr.log for the specific driver causing the failure.
When to Call a Professional
Most Windows errors are fixable with the steps above. But there are warning signs that something deeper is wrong: the same BSOD recurring after every fix attempt, multiple unrelated errors appearing in rapid succession, or clicking and grinding noises from a mechanical hard drive. These suggest hardware failure -- bad RAM, a dying drive, or motherboard issues -- that no software fix will resolve.
If you have tried the steps above, run all diagnostics clean, and the error persists, it is time to bring the machine to a qualified repair technician. Back up your data first.
Got a different error code?
Search any Windows, Mac, HTTP, or application error code for a plain-English explanation and fix.
Search any error code →