Error codes with scope, not guesswork.
A code is only useful when you keep the subsystem and failure context attached to it.
Windows Update error 0x80070002: what it means and what to try first
Microsoft groups 0x80070002 among update install failures; preserve the context before using broader repair steps.
Open error record →Windows 11 Windows Update/servicing context · Windows Update0x800F081FWindows Update error 0x800F081F: repair source missing
In Microsoft’s servicing guidance, 0x800F081F maps to CBS_E_SOURCE_MISSING and calls for component-store repair or a valid matching source.
Open error record →Windows 11 Windows Update/servicing context · Windows Update0x80073712Windows Update error 0x80073712: component store inconsistent
Microsoft maps 0x80073712 to ERROR_SXS_COMPONENT_STORE_CORRUPT in the Windows servicing context.
Open error record →Windows 11 Windows Update/servicing context · Windows Update0x800F0831Windows Update error 0x800F0831: CBS store corruption
Microsoft classifies 0x800F0831 as CBS_E_STORE_CORRUPTION and directs troubleshooting toward component-store repair.
Open error record →Windows 11 Device Manager · Devices & driversCode 10Device Manager Code 10: “This device cannot start”
Code 10 means the device could not start; Microsoft’s primary resolution begins with the device driver.
Open error record →Windows 11 Device Manager · Devices & driversCode 28Device Manager Code 28: drivers are not installed
Code 28 means Windows does not have the driver installed for the device; reinstall the device driver rather than applying unrelated fixes.
Open error record →Windows 11 Device Manager · Devices & driversCode 31Device Manager Code 31: Windows cannot load the required drivers
Code 31 is a device-driver loading failure; keep the troubleshooting scoped to the affected hardware.
Open error record →Windows 11 Device Manager · Devices & driversCode 43Device Manager Code 43: Windows stopped a device after it reported a problem
Code 43 means a driver controlling the device told Windows that the device failed in some way; driver and hardware context both matter.
Open error record →Windows 11 stop-code context · Blue screens & stop codesWHEA_UNCORRECTABLE_ERRORWHEA_UNCORRECTABLE_ERROR: treat it as a hardware-oriented stop code
Microsoft identifies WHEA_UNCORRECTABLE_ERROR as a hardware error path; start with updates/drivers and recovery around recent changes.
Open error record →Windows 11 stop-code context · Blue screens & stop codesIRQL_NOT_LESS_OR_EQUALIRQL_NOT_LESS_OR_EQUAL: driver and memory-oriented stop-code diagnosis
Use the stop-code context to check recent drivers and memory rather than treating the crash as a generic Windows error.
Open error record →Windows stop-code / bug-check context · Blue screens & stop codes0x0000009FDRIVER_POWER_STATE_FAILURE: driver stuck in a power transition
Microsoft defines bug check 0x9F as a driver in an inconsistent or invalid power state.
Open error record →Windows stop-code / bug-check context · Blue screens & stop codes0x0000007ESYSTEM_THREAD_EXCEPTION_NOT_HANDLED: an unhandled kernel thread exception
Bug check 0x7E means a system thread generated an exception that the error handler did not catch.
Open error record →Windows stop-code / bug-check context · Blue screens & stop codes0x00000050PAGE_FAULT_IN_NONPAGED_AREA: invalid system memory was referenced
Microsoft defines bug check 0x50 as an invalid system-memory reference; driver and memory evidence matter.
Open error record →Windows graphics stop-code / bug-check context · Blue screens & stop codes0x00000116VIDEO_TDR_FAILURE: Windows could not recover the display driver after a GPU timeout
Bug check 0x116 occurs when Windows attempts to reset the display driver after a timeout and recovery fails.
Open error record →Windows stop-code / bug-check context · Blue screens & stop codes0x000000D1DRIVER_IRQL_NOT_LESS_OR_EQUAL: a kernel driver made an invalid high-IRQL memory access
Microsoft describes bug check 0xD1 as a kernel-mode driver accessing pageable or invalid memory at an IRQL that was too high.
Open error record →Windows startup stop-code / bug-check context · Startup & recovery0x0000007BINACCESSIBLE_BOOT_DEVICE: Windows lost access to the system partition during startup
Stop 0x7B is a startup/storage path failure; preserve recent storage, controller, firmware and driver changes.
Open error record →Windows 11 Device Manager · Devices & driversCode 12Device Manager Code 12: Windows cannot find enough free resources for the device
Code 12 is a resource-allocation problem; confirm the exact device before changing other hardware or firmware settings.
Open error record →Windows 11 Device Manager · Devices & driversCode 22Device Manager Code 22: the device is disabled
Code 22 means Windows sees the device but it has been disabled; enable the device before reinstalling drivers.
Open error record →Windows 11 Device Manager · Devices & driversCode 45Device Manager Code 45: hardware is not connected
Code 45 is a connection/presence state; reconnect or power the hardware before changing drivers.
Open error record →Google Chrome page-loading context on Windows · BrowsersERR_NAME_NOT_RESOLVEDChrome ERR_NAME_NOT_RESOLVED: hostname resolution failed
Google defines this Chrome page-loading code as a hostname that does not exist or now resolves differently; verify the name and DNS path before browser reset.
Open error record →Google Chrome page-loading context on Windows · BrowsersERR_CONNECTION_RESETChrome ERR_CONNECTION_RESET: the connection was interrupted
Google says this error means something interrupted the connection; unstable networking, VPN, outdated browser or security software can be involved.
Open error record →Google Chrome page-loading context on Windows · BrowsersERR_NETWORK_CHANGEDChrome ERR_NETWORK_CHANGED: the active network changed during loading
Google defines this as the device disconnecting from a network or connecting to a new one while the page is loading.
Open error record →Google Chrome page-loading context on Windows · BrowsersERR_CONNECTION_TIMED_OUTChrome ERR_CONNECTION_TIMED_OUT: the destination took too long to connect
Google says the page took too long to connect; the local connection may be slow or the destination may be busy/unreachable.
Open error record →Google Chrome page-loading context on Windows · BrowsersERR_CONNECTION_REFUSEDChrome ERR_CONNECTION_REFUSED: the destination did not accept the connection
Google describes this as the page not allowing Chrome to connect or the page being blocked; prove whether the failure is destination-specific before local resets.
Open error record →Supported Windows client versions · Diagnostics & reliabilityEvent ID 41Kernel-Power: Windows restarted without a clean shutdown
Event ID 41 confirms an unexpected shutdown/restart occurred; it does not by itself name the failed component.
Open error record →Windows 11 / Windows client · Blue screens & stop codesEvent ID 1001WER-SystemErrorReporting bugcheck: preserve the stop code and dump path
When Event ID 1001 says the computer rebooted from a bugcheck, the useful evidence is the exact bugcheck code, parameters and saved dump.
Open error record →Windows client · Diagnostics & reliabilityEvent ID 6008EventLog unexpected shutdown: a timestamp clue, not a root cause
Event ID 6008 records that the previous shutdown was unexpected; correlate it with Event ID 41, bugcheck records and the failure timeline.
Open error record →Windows client · Services & startupEvent ID 7000Service Control Manager: a service failed to start
Use the named service and complete error text to determine whether the failure is timeout, configuration, binary, permission or another service-specific cause.
Open error record →Windows client · Services & startupEvent ID 7001Service Control Manager: dependency service failed to start
A higher-level service can fail because one of its required services failed first; trace the dependency chain instead of repairing only the visible service.
Open error record →Windows client · Diagnostics & reliabilityEvent ID 1000Application Error: application or service crash record
Preserve the faulting application, module and exception code and correlate repeated Event 1000 entries with Windows Error Reporting Event 1001.
Open error record →Windows storage stack · Storage & file systemEvent ID 129Storport reset to device was issued
A storage request timed out at Storport and Windows reset the device path; correlate repeated resets with the affected disk/controller path and hardware/driver state.
Open error record →Windows storage stack · Storage & file systemEvent ID 153Storage I/O operation was retried
The storage miniport request timed out and Windows retried the I/O; repeated occurrences need path/load/driver/hardware correlation.
Open error record →Windows storage stack · Storage & file systemEvent ID 157Disk was surprise removed
Windows recorded that a disk disappeared unexpectedly; prioritize connection/power/controller/device stability and data protection before file-system repairs.
Open error record →Windows application hang context · Diagnostics & reliabilityEvent ID 1002Application Hang: the app stopped interacting with Windows
Treat Application Hang evidence as proof of a non-responsive process state, then correlate the process, report ID, wait chain and WER record before assigning cause.
Open error record →Windows Installer (MSI) · Apps, installers & Microsoft StoreError 1603Windows Installer fatal installation error
1603 is a fatal MSI installation failure, but Microsoft documents multiple possible conditions; preserve package/context before applying a fix.
Open error record →Windows Installer (MSI) · Apps, installers & Microsoft StoreError 1618Another Windows Installer installation is already in progress
1618 means Windows Installer reports another installation already running; finish or clear the legitimate pending operation before retrying.
Open error record →Windows Installer (MSI) · Apps, installers & Microsoft StoreError 1619Windows Installer package could not be opened
1619 means the MSI package could not be opened; verify the file exists, is accessible and is a valid publisher-supplied Windows Installer package.
Open error record →Windows Installer (MSI) · Apps, installers & Microsoft StoreError 1620Windows Installer package is invalid or cannot be opened as a valid package
1620 is a package-validity/opening error; verify the installer with the publisher instead of applying generic Windows repairs.
Open error record →MSIX/AppX deployment · Apps, installers & Microsoft Store0x80073D02MSIX/AppX package resources are currently in use
0x80073D02 means package deployment cannot proceed because a running process is using resources that must be changed.
Open error record →MSIX/AppX deployment · Apps, installers & Microsoft Store0x80073CFBMSIX/AppX package already exists for this user
0x80073CFB indicates an identical package is already registered; verify the installed package/version before attempting another deployment.
Open error record →