Error AtlasError Documentation and ResolutionWindows documented errors
Browse documented Windows errors with exact messages, troubleshooting context, and practical remediation steps.
Tool
Windows / .NET
StackOverflowException.NET process terminated with StackOverflowExceptionruntime: The .NET runtime terminated the process with a StackOverflowException because the call stack exceeded its maximum size. Unlike most .NET exceptions this cannot be caught in a try/catch block (since .NET 2.0) — the CLR terminates the process immediately to prevent heap corruption. The cause is almost always infinite or excessively deep recursion.
BadImageFormatException.NET runtime threw BadImageFormatException when loading an assemblyruntime: The .NET runtime threw a BadImageFormatException because it tried to load an assembly or DLL that was compiled for a different CPU architecture than the current process, or because the file is not a valid .NET assembly at all. The most common cause is a mismatch between a 32-bit (x86) DLL and a 64-bit process (or vice versa).
DllNotFoundException.NET runtime threw DllNotFoundException when loading a native libraryruntime: The .NET runtime threw a DllNotFoundException because a P/Invoke call (or a library using one) attempted to load a native DLL that could not be found in any of the expected search paths. The DLL may be missing from the deployment, in the wrong location, targeting the wrong architecture, or missing its own dependencies.
OutOfMemoryException.NET runtime threw OutOfMemoryExceptionruntime: The .NET runtime threw an OutOfMemoryException because it could not allocate the requested memory from the managed heap or the process address space. On 32-bit processes this can occur well before physical RAM is exhausted due to the 2–4 GB virtual address space limit. On 64-bit processes it usually indicates a genuine memory exhaustion problem — a memory leak, unexpectedly large allocations, or fragmentation of the Large Object Heap (LOH).
TypeInitializationException.NET runtime threw TypeInitializationException when initialising a typeruntime: The .NET runtime threw a TypeInitializationException because an exception was thrown inside a type's static constructor (the type initializer). Once a type initializer fails, the type is permanently marked as failed for the lifetime of the application domain — subsequent attempts to use the type will throw the same exception, even if the underlying problem was transient. The inner exception contains the actual error.
0x80240034Windows Update download failed with error 0x80240034installation: Windows Update could not complete the download of one or more update packages with error 0x80240034 (WU_E_DOWNLOAD_FAILED). This error means the download was initiated but could not be completed — usually due to a network interruption, corrupted temporary download files, or problems with the BITS (Background Intelligent Transfer Service) that Windows Update uses to download files.
0x80073712Windows Update failed with error 0x80073712 — component store corruptedinstallation: Windows Update failed because a required component or package in the Windows component store (WinSxS) is missing or corrupted. Error 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT) means the servicing stack cannot find or use a package it needs to apply the update.
0x8024402CWindows Update failed with error 0x8024402C — cannot connect to update serverinstallation: Windows Update failed to connect to its update server — either Windows Update on the internet or a corporate WSUS server — with error 0x8024402C (WU_E_PT_WINHTTP_NAME_NOT_RESOLVED). This is a network connectivity error meaning the Windows Update client could not resolve or reach the update endpoint.
0x80070005Windows Update or activation failed with error 0x80070005 Access Deniedinstallation: A Windows operation — most commonly Windows Update, application activation, or a component installation — was blocked with error 0x80070005 (ERROR_ACCESS_DENIED) because the process attempting the operation did not have sufficient permissions to access a required file, registry key, or system resource.
Tool
Windows BSOD
BAD_POOL_HEADERWindows blue screen BAD_POOL_HEADERruntime: Windows stopped with a BAD_POOL_HEADER (bug check 0x00000019) because corruption was detected in the kernel pool memory header. The pool allocator found that a block's header had been overwritten or was in an inconsistent state, which indicates that some code (usually a driver) has written beyond the end of a pool allocation or otherwise corrupted pool metadata.
CLOCK_WATCHDOG_TIMEOUTWindows blue screen CLOCK_WATCHDOG_TIMEOUTruntime: Windows stopped with a CLOCK_WATCHDOG_TIMEOUT (bug check 0x00000101) because an expected clock interrupt was not received by a secondary processor within the allocated interval. This indicates that a processor in the system has stopped or is stuck, and the primary processor's watchdog has detected the hang. It is predominantly a hardware issue — most commonly caused by CPU overclocking, faulty RAM, or a failing CPU.
DPC_WATCHDOG_VIOLATIONWindows blue screen DPC_WATCHDOG_VIOLATIONruntime: Windows stopped with a DPC_WATCHDOG_VIOLATION (bug check 0x00000133) because the DPC watchdog timer detected that either a single Deferred Procedure Call (DPC) or Interrupt Service Routine (ISR) ran for longer than its allotted time, or that the system spent a prolonged period at IRQL DISPATCH_LEVEL or above. DPCs should complete within 100 microseconds; when a driver violates this, Windows forcibly stops to prevent a system hang.
DRIVER_IRQL_NOT_LESS_OR_EQUALWindows blue screen DRIVER_IRQL_NOT_LESS_OR_EQUALruntime: Windows stopped with a DRIVER_IRQL_NOT_LESS_OR_EQUAL (bug check 0x000000D1) because a kernel-mode driver attempted to access pageable memory at an interrupt request level (IRQL) that was too high. This is similar to IRQL_NOT_LESS_OR_EQUAL (0x0A) but specifically implicates a driver rather than the kernel itself. The offending driver is usually named on the blue screen or in the crash dump.
DRIVER_POWER_STATE_FAILUREWindows blue screen DRIVER_POWER_STATE_FAILUREruntime: Windows stopped with a DRIVER_POWER_STATE_FAILURE (bug check 0x0000009F) because a driver is in an inconsistent or invalid power state. This almost always occurs during or immediately after a power state transition — such as waking from sleep or hibernate, or shutting down — because a driver failed to correctly handle the transition.
KERNEL_SECURITY_CHECK_FAILUREWindows blue screen KERNEL_SECURITY_CHECK_FAILUREruntime: Windows stopped with a KERNEL_SECURITY_CHECK_FAILURE (bug check 0x00000139) because a kernel-level security check detected that data structures have been corrupted. This is a protective stop — Windows intentionally halts execution when it detects kernel memory corruption that could allow a security bypass or system compromise.
NTFS_FILE_SYSTEMWindows blue screen NTFS_FILE_SYSTEMruntime: Windows stopped with an NTFS_FILE_SYSTEM (bug check 0x00000024) because the NTFS file system driver encountered an unexpected condition it could not handle. This most commonly indicates corruption on the disk, bad sectors, a failing storage device, or a problem with the NTFS driver itself.
UNEXPECTED_KERNEL_MODE_TRAPWindows blue screen UNEXPECTED_KERNEL_MODE_TRAPruntime: Windows stopped with an UNEXPECTED_KERNEL_MODE_TRAP (bug check 0x0000007F) because the Intel or AMD CPU generated a trap (an internal processor exception) that the Windows kernel was unable to catch. The first parameter in the crash dump identifies the specific CPU trap type. The most common causes are hardware faults — defective memory, CPU issues, or incompatible hardware — though driver bugs can also trigger this stop code.
VIDEO_TDR_FAILUREWindows blue screen VIDEO_TDR_FAILUREruntime: Windows stopped with a VIDEO_TDR_FAILURE (bug check 0x00000116) because the GPU stopped responding and the Timeout Detection and Recovery (TDR) mechanism failed to reset it within the allowed window. Windows tried to recover the display driver but the GPU did not recover in time, forcing a system crash. The offending file is usually atikmpag.sys (AMD) or nvlddmkm.sys (NVIDIA).
WHEA_UNCORRECTABLE_ERRORWindows blue screen WHEA_UNCORRECTABLE_ERRORruntime: Windows stopped with a WHEA_UNCORRECTABLE_ERROR (bug check 0x00000124) because a fatal hardware error was reported to the Windows Hardware Error Architecture (WHEA) that the operating system could not recover from. This is one of the most hardware-definitive BSODs — it almost always indicates a physical problem with the CPU, memory, motherboard, or power delivery rather than a software or driver fault.