Fix It

Windows Error Code Library

Paste the code Windows showed you. Each entry explains what it means, what usually causes it, and the fixes to try in order.

DM TECH never runs commands on your PC. Every command here is reference text you copy and run yourself, in a window you control. Read what a command does before running it, and back up important data first.

14 error codes

0x80070005

Access denied

Windows Update

Windows was refused permission to read or write a file, registry key or service it needed.

Likely causes

  • The action was not run with administrator rights.
  • Security software is blocking access to a system location.
  • File or registry permissions were changed by a cleanup tool.

Try these in order

  1. 1. Retry the action from an elevated Command Prompt or Terminal (Run as administrator).

  2. 2. Temporarily pause third-party security software, retry, then turn it back on.

  3. 3. Run the system file check to repair damaged system components.

    sfc /scannow
0x80070002

The system cannot find the file specified

Windows Update

An expected update or installer file is missing or the download cache is incomplete.

Likely causes

  • Interrupted update download.
  • Corrupted SoftwareDistribution cache.
  • Incorrect system date or time.

Try these in order

  1. 1. Confirm the system date, time and time zone are correct.

  2. 2. Stop the update services before clearing the cache.

    net stop wuauserv && net stop bits
  3. 3. Rename the update cache folder, then start the services again.

    net start wuauserv && net start bits
  4. 4. Retry Windows Update and restart the PC.

0x800f081f

Source files could not be found

Windows Update

DISM or a Windows feature installation could not reach a valid repair source.

Likely causes

  • No internet connection during repair.
  • Damaged component store.
  • Feature-on-demand source blocked by policy.

Try these in order

  1. 1. Connect to the internet and retry the component store repair.

    DISM /Online /Cleanup-Image /RestoreHealth
  2. 2. Run the system file check afterwards.

    sfc /scannow
  3. 3. If it still fails, supply an offline source from matching Windows installation media using the /Source switch.

0xc000000f

Boot configuration data is missing or contains errors

Blue Screen

Windows cannot read the boot configuration store, so startup stops before Windows loads.

Likely causes

  • Damaged BCD store.
  • Failing system drive.
  • Boot order changed or the drive is no longer detected.

Try these in order

  1. 1. Check the BIOS/UEFI boot order and confirm the Windows drive is detected.

  2. 2. Boot from Windows installation media and open Repair your computer > Startup Repair.

  3. 3. From the recovery Command Prompt, rebuild the boot record.

    bootrec /rebuildbcd
  4. 4. If the drive is not detected at all, test the drive before repairing software.

CRITICAL_PROCESS_DIED

Critical process died (0x000000EF)

Blue Screen

A process Windows requires to stay running was terminated, forcing a stop error.

Likely causes

  • Corrupted system files.
  • Faulty or mismatched driver.
  • Failing storage or memory.

Try these in order

  1. 1. Boot into Safe Mode if Windows will not start normally.

  2. 2. Repair system files.

    sfc /scannow
  3. 3. Repair the component store, then repeat the file check.

    DISM /Online /Cleanup-Image /RestoreHealth
  4. 4. Run the Windows Memory Diagnostic and check drive health.

    mdsched
  5. 5. Roll back any driver installed shortly before the crashes started.

MEMORY_MANAGEMENT

Memory management (0x0000001A)

Blue Screen

Windows detected a serious memory-management fault, often but not always caused by faulty RAM.

Likely causes

  • Failing RAM module.
  • Unstable overclock or XMP profile.
  • Bad driver writing to invalid memory.

Try these in order

  1. 1. Run the Windows Memory Diagnostic and let it complete both passes.

    mdsched
  2. 2. Reset any memory overclock or XMP profile to default in BIOS/UEFI.

  3. 3. Update chipset and storage drivers from the PC or motherboard manufacturer.

  4. 4. Test with one memory module at a time to identify a faulty stick.

DPC_WATCHDOG_VIOLATION

DPC watchdog violation (0x00000133)

Drivers

A driver spent too long at high priority without yielding, usually a storage or chipset driver.

Likely causes

  • Outdated SSD firmware.
  • Old SATA/AHCI or chipset driver.
  • Incompatible peripheral driver.

Try these in order

  1. 1. Update storage, chipset and network drivers from the manufacturer's support page.

  2. 2. Check for SSD firmware updates from the drive vendor.

  3. 3. Disconnect recently added USB devices and test.

  4. 4. Review the crash time in Event Viewer to identify the driver named in the event.

0x8007000E

Out of memory

Installation

The operation ran out of available memory, commonly during a large feature update.

Likely causes

  • Too little free disk space for the update staging area.
  • Very low free RAM.
  • Too many background applications.

Try these in order

  1. 1. Free disk space on the system drive.

    cleanmgr
  2. 2. Close background applications and retry.

  3. 3. Restart the PC before starting a feature update so memory is clear.

0xc1900101

Driver rollback during upgrade

Installation

A Windows upgrade failed and rolled back, almost always because of an incompatible driver.

Likely causes

  • Outdated graphics, storage or security drivers.
  • Connected peripherals blocking the upgrade.
  • Insufficient free space.

Try these in order

  1. 1. Update graphics, storage and network drivers before retrying.

  2. 2. Disconnect all non-essential USB devices, docks and external drives.

  3. 3. Ensure at least 20 GB free on the system drive.

  4. 4. Uninstall third-party antivirus for the duration of the upgrade, then reinstall it.

0x80072EE7

Cannot reach the update or Store server

Networking

Windows could not resolve or connect to Microsoft servers.

Likely causes

  • DNS problems.
  • Proxy or VPN interference.
  • Firewall rules blocking the service.

Try these in order

  1. 1. Clear the DNS resolver cache.

    ipconfig /flushdns
  2. 2. Disconnect VPN or proxy and retry.

  3. 3. Test name resolution against a public resolver.

    nslookup microsoft.com 1.1.1.1
  4. 4. Reset the network stack, then restart.

    netsh winsock reset && netsh int ip reset
0x80070570

The file or directory is corrupted and unreadable

Storage

Windows could not read data it expected, usually a file-system or media problem.

Likely causes

  • File-system corruption.
  • Failing drive or bad sectors.
  • Damaged installation media or a bad download.

Try these in order

  1. 1. Check the volume for file-system errors.

    chkdsk C: /f
  2. 2. Re-download the file or recreate the installation media.

  3. 3. Check physical drive health and back up important data if the drive reports problems.

0x803FA067

Windows activation could not be completed

Activation

Windows could not verify the licence with the activation service.

Likely causes

  • Recent hardware change, especially the motherboard.
  • Activation servers temporarily unreachable.
  • Licence not linked to the Microsoft account.

Try these in order

  1. 1. Confirm the PC is online and the date and time are correct.

  2. 2. Open Settings > System > Activation and run the Activation troubleshooter.

  3. 3. Sign in with the Microsoft account the digital licence is linked to.

  4. 4. For a genuine licence that still will not activate, contact Microsoft support — never use activation cracks.

0x80004005

Unspecified error

Windows Update

A generic failure code Windows returns when a component reports no specific reason.

Likely causes

  • Update cache corruption.
  • Permission problems on a target folder.
  • Third-party software interference.

Try these in order

  1. 1. Note exactly what you were doing — the code alone is not diagnostic.

  2. 2. Check Event Viewer at the time of the error for a more specific entry.

  3. 3. Run the built-in troubleshooter for the affected area in Settings > System > Troubleshoot.

  4. 4. Repair system files.

    sfc /scannow
0x80248007

Windows Update licence terms missing

Windows Update

The update service could not find files it needed or could not read the licence terms.

Likely causes

  • Damaged SoftwareDistribution folder.
  • Windows Update service not running.

Try these in order

  1. 1. Confirm the Windows Update service state.

    sc query wuauserv
  2. 2. Restart the update service.

    net stop wuauserv && net start wuauserv
  3. 3. Run the Windows Update troubleshooter from Settings > System > Troubleshoot.