Common Windows Error Messages (and What They Actually Mean)
A curated starting point if you don't have an exact code yet
If you're seeing an error but aren't sure which one, or want to understand what a message actually means before diving into fix steps, start here. Every entry below links to the full breakdown — meaning, causes, and step-by-step fix — in our complete error database, which currently covers 109 specific errors, not just a handful.
Blue Screen (BSOD) Errors
IRQL_NOT_LESS_OR_EQUAL
Almost always a driver — usually one installed or updated recently — trying to access memory it isn't allowed to.
INACCESSIBLE_BOOT_DEVICE
Windows can't find the drive it's supposed to boot from, often after a hardware or storage-controller change.
CRITICAL_PROCESS_DIED
A core Windows process was forced to close unexpectedly — frequently tied to corrupted system files or a failing drive.
General System Errors
Access Denied
Windows or an app doesn't have the permission it needs to complete an action — one of the single most common Windows errors overall.
Access Violation (STATUS_ACCESS_VIOLATION)
A program tried to access a part of memory it shouldn't have — can point to a buggy app, a driver conflict, or failing RAM.
Not Enough Storage / Out of Memory
Windows or an app ran out of available memory to complete what it was doing, whether that's truly low RAM or a resource leak.
Windows Update Errors
File Not Found
A file Windows Update expected to find is missing — often fixed by clearing the update cache.
Component Store Corruption
A core system file Windows Update relies on has become corrupted — this is exactly what sfc and DISM are built to repair.
Feature Update Installation Failure
A driver or app is blocking a larger feature update from installing — usually resolved by uninstalling the specific conflicting software.
Network & Browser Errors
DNS_PROBE_FINISHED_NXDOMAIN
Your browser couldn't translate a web address into the server it needs to reach — often a DNS or connectivity issue rather than the site itself being down.
ERR_CONNECTION_TIMED_OUT
The connection was attempted but never got a response in time — can be your network, the site's server, or something in between.
Installer (MSI) Errors
Fatal Error During Installation
A catch-all "something went wrong" from the Windows Installer — usually needs the installer's own log file to pin down the real cause.
Another Installation Is Already in Progress
Another installation is already running (even invisibly) and needs to finish or be closed before this one can proceed.
Excel & Word Errors
Excel Has Stopped Working / Not Responding
Excel has frozen or crashed outright — often tied to a misbehaving add-in or a file that's grown too large or complex.
Microsoft Word Has Stopped Working / Not Responding
The same pattern as Excel, usually traced to add-ins, a corrupted template, or a specific problem file rather than Word itself.
This page covers the ones people hit most often — the full database has many more, including specific stop codes, activation errors, and Command Prompt errors.
Search the full error database