The error library.
435 errors. Choose the message that matches your computer.
STEAM-DISK-WRITE-ERR
Steam will abort installing or updating a game with a disk write error. Common triggers are insufficient permissions for Steam/steamapps folder and the antivirus program blocks the writing of files.
Apps & runtimeGAME-EAC-VIOLATION
The game will kick you out with an EasyAntiCheat violation even though you're not cheating. Common triggers are overlays (Discord Overlay, MSI Afterburner) conflict with EAC and corrupt EAC installation.
BIOS & startupPOST-FAILURE
Power-On Self Test failed. The PC will not pass the check and will not boot.
BIOS & startupSECURE-BOOT-VIOLATION
Secure Boot blocked unsigned boot code from running. This usually traces back to old bootloader and corrupted EFI.
BIOS & startupBIOS-UPDATE-FAIL
Firmware update failed. The board does not need to boot.
BIOS & startupTPM-NOT-FOUND
Windows 11 or BitLocker does not find the TPM 2.0 module. The usual suspects are TPM disabled in BIOS, missing physical TPM and old firmware.
BIOS & startupBIOS-UEFI-BOOT-ORDER
The computer is booting from the wrong device (USB instead of SSD or vice versa) due to the wrong sequence in the BIOS. It's most often caused by attached USB with bootable media and more OS installations.
BIOS & startupME-FIRMWARE-CORRUPTION
The Intel ME firmware is corrupted, which leads to strange problems (PC won't turn off by itself, fans running at full speed, lack of sensors). Common triggers are aborted BIOS or ME fw update, incompatible BIOS…
BIOS & startupROM-SPACE-EXHAUSTED
The board has too many associated devices with custom ROMs (eg RAID controllers, multiple GPUs) and has run out of space to initialize them (POST). Another common trigger is active Legacy and CSM boot modes.
BIOS & startupBIOS-ROM-ERR
The BIOS ROM memory is corrupted or unreadable. It sometimes comes down to defective EEPROM chip.
BIOS & startupBIOS_ROM_CORRUPTED
The motherboard BIOS firmware ROM checksum verification failed. The system cannot POST and cycles with fans at maximum speed or reports error beeps.
BIOS & startupUEFI-SECURE-BOOT-DB-EXPIRED
A Secure Boot signature in the UEFI signature database (db) has expired. Microsoft has been revoking old Secure Boot certificates as part of CVE mitigations (e.g., Black Lotus bootkit fix).
BIOS & startupAGESA-BOOT-FAILURE
AMD Generic Encapsulated Software Architecture (AGESA) is the foundational firmware layer that initializes AMD processor platforms. An AGESA initialization failure means the CPU, memory controller, or PCIe fabric…
BIOS & startupBoot Device Not Found
Before Windows starts, the PC shows "Boot Device Not Found", "No bootable device" or a similar firmware message. The message comes from the BIOS/UEFI, not from Windows: it did not find a drive it can start from.
BIOS & startupOverclocking Failed
System settings or voltages configured in the BIOS/UEFI for overclocking are unstable, causing a POST failure and automatic reset to baseline. Reports of Overclocking Failed usually describe a sudden crash, brief…
BIOS & startupDRAM Light (Q-LED)
The motherboard POST diagnostic LED indicates a memory initialization error, preventing the system from booting. See the troubleshooting steps below for the fix.
BIOS & startupCPU Vcore Out of Range
The processor voltage is detected by the motherboard sensors as being outside of stable operating bounds. It's also often linked to failing power supply unit (PSU).
BIOS & startupPOST-CODE-15
Motherboard POST code 15 indicates a failure during early North-Bridge memory initialization. Commonly caused by memory compatibility issues, training timeouts on high-frequency DDR4/DDR5 sticks, or bent CPU socket pins.
BIOS & startupPOST-CODE-5D
Motherboard POST code 5d indicates that the installed CPU processor is either unrecognized or unsupported by the current motherboard BIOS firmware version. Commonly occurs after upgrading the CPU without updating the…
ProcessorWHEA_UNCORRECTABLE_ERROR
Windows stopped because a piece of hardware reported an error that could not be corrected. WHEA (Windows Hardware Error Architecture) is the part of Windows that collects these reports, so the stop code says who…
ProcessorCLOCK_WATCHDOG_TIMEOUT
Windows stopped because one of the processor's cores did not respond to a regular clock signal in time. Microsoft explains that the core is usually unresponsive or deadlocked.
ProcessorCPU-THERMAL-THROTTLE
This diagnosis detects processor speed limitation events (Event ID 37 or 196 in the Windows System Event Log). The CPU reached its thermal limit and activated throttling to prevent hardware damage, resulting in…
ProcessorMACHINE_CHECK_EXCEPTION
The processor detected a hardware error it could not correct and stopped Windows to prevent data corruption. On current Windows versions the same event usually appears as WHEA_UNCORRECTABLE_ERROR (0x124); the older…
ProcessorCPU-VCORE-LOW
Powering the processor below the minimum causes instability and crashes. Common triggers are weak resource, damaged VRM and bad EPS connector.
ProcessorCPPC-NOT-SUPPORTED
Collaborative Processor Performance Control is not active. Reduces the effectiveness of CPU boost.
ProcessorPOWER-LIMIT-THROTTLE
The CPU is running below maximum power due to the PL1/PL2 limits of the motherboard or laptop. Reports of Limiting CPU performance with a performance limit of usually describe a sudden crash, brief unresponsiveness,…
ProcessorPROCHOT-SIGNAL
The Processor Hot (PROCHOT) signal has been activated, which causes extreme throttling, sometimes even at low temperatures. Common triggers are defective voltage regulator (VRM) and for laptops – defective battery /…
ProcessorPROCHOT-1
The processor slows down to avoid overheating and damage. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorVCORE-DROP
The power supply cascade does not supply sufficient voltage to the load. This usually traces back to dried thermal paste, overclocking too aggressively and silicon degradation.
ProcessorUCODE-0x1A
The processor's internal instruction set encountered an unknown exception. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorSMT-SYNC-FAIL
The logical cores have lost synchronization with each other. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorIMC-FAULT-00
The controller inside the processor cannot communicate stably with the RAM. Reports of Integrated Memory Controller (IMC) failure usually describe a sudden crash, brief unresponsiveness, or a stop-code screen…
ProcessorAVX-PANIC
Calculation error when using AVX/AVX2 wide vector instructions. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorC-STATE-HUNG
The processor failed to properly wake up from sleep. Common triggers are dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorVRM-TEMP-CRIT
VRM sensors on the motherboard report critical temperatures limiting the CPU. This usually traces back to dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorSOCKET-PIN-FLT
The pins in the processor socket do not touch, which causes accidental disconnection of the lines. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorTDP-LIMIT-MAX
The processor draws more power than the BIOS allows. The usual suspects are dried thermal paste, overclocking too aggressively and silicon degradation.
ProcessorBCLK-JITTER
The basic frequency generator on the board fluctuates. Reports of Base clock instability (BCLK) usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere.
ProcessorBRANCH-PRED-ER
The jump prediction logic inside the CPU failed, typical of aging silicon. The usual suspects are dried thermal paste, overclocking too aggressively and weak power supply.
ProcessorFPU-MATH-ERR
The floating point unit returns imprecise results. Reports of Coprocessor math error (FPU) usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere.
ProcessorRING-BUS-FAIL
The bus connecting the cores inside the processor collapsed. The usual suspects are dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply.
ProcessorCPU-PSTATE-ERR
Processor failed to transition to a requested performance state. This usually traces back to BIOS bug and faulty power management driver.
MotherboardVRM-OVERTEMP-THROT
Processors with a high TDP (i9, Ryzen 9) reduce performance due to overheating of the power supply circuits (VRM) of the board. The usual suspects are an entry-level motherboard with insufficient VRMs for a powerful…
ProcessorAMD-FCLK-INFINITY-ERR
AMD systems crash or become unstable due to out of sync FCLK (Infinity Fabric clock) and MEMCLK. Another common trigger is weak RAM modules with XMP above DDR5-6000.
ProcessorINTEL_13_14_DEGRADATION
A critical microcode and hardware degradation issue affecting Intel Core 13th and 14th Generation desktop processors. The CPU requests excessive voltages, leading to physical degradation of silicon, out-of-memory…
ProcessorINTEL_TDP_THROTTLING
Intel Power Limit Throttling (PL1 or PL2) triggers when the processor exceeds its long-duration or short-duration power limits, reducing core frequencies to keep power draw within design specs. Typical causes include…
ProcessorCORE_PAGING_MULTIPLE_IRP_COMPLETE_REQUESTS
The CORE_PAGING_MULTIPLE_IRP_COMPLETE_REQUESTS error is a critical CPU/memory paging fault occurring when the I/O request packet system detects duplicate completions. This indicates a severe inconsistency in the CPU…
ProcessorCPU-PACKAGE-TEMP-LIMIT
The CPU package temperature has reached or exceeded the manufacturer's maximum junction temperature (Tjmax), typically 100°C for Intel and 95°C for AMD. The processor initiates emergency thermal shutdown to prevent…
ProcessorINTEL-MICROCODE-UPDATE-FAIL
The INTEL-MICROCODE-UPDATE-FAIL error occurs when the system BIOS attempts to load a CPU microcode patch and fails. Intel releases microcode updates to fix CPU errata, security vulnerabilities (Spectre, Meltdown,…
ProcessorAMD-PSP-ERROR
The AMD Platform Security Processor (PSP) is an ARM Cortex-A5 security coprocessor embedded in AMD CPUs and APUs. A PSP error typically manifests as a boot failure with debug LED codes or BIOS error messages.
ProcessorThermal Shutdown
The system firmware or motherboard sensors detected temperatures exceeding critical safe operating limits (usually Tj Max of 95°C to 105°C), triggering an immediate emergency power cut to prevent permanent silicon…
DriversDRIVER_IRQL_NOT_LESS_OR_EQUAL
Windows stopped because a kernel-mode driver tried to access memory at an invalid address while running at a raised priority level. Microsoft says this bug check is usually caused by drivers that used improper memory…
DriversDRIVER-VERIFIER-FAIL
Windows Driver Verifier detected illegal driver behavior in memory or IRQL. Use the steps below to track down and fix the cause.
DriversSYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Windows stopped because a system thread, code that runs inside Windows itself, hit an error that nothing caught, most often an invalid memory access. In almost every case the thread belongs to a driver, and the blue…
DriversCODE-10-DEVICE-CANNOT-START
Windows Device Manager reported that the device could not start due to a failure to load or a faulty driver. Another common trigger is incompatibility with the.
DriversBSOD-ndis.sys
Windows has terminated due to a fatal error in the kernel module ndis.sys. Typical causes include outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-tcpip.sys
Windows has terminated due to a fatal error in the tcpip.sys kernel module. Reports of Critical tcpip.sys driver error (BSOD) usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing…
DriversBSOD-usbport.sys
Windows has terminated due to a fatal error in the usbport.sys kernel module. This usually traces back to outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-fltmgr.sys
Windows has terminated due to a fatal error in the fltmgr.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-classpnp.sys
Windows has terminated due to a fatal error in the classpnp.sys kernel module. It's most often caused by outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-dxgkrnl.sys
Windows has terminated due to a fatal error in the dxgkrnl.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-igdkmd64.sys
Windows has terminated due to a fatal error in the igdkmd64.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-amdkmdag.sys
Windows has terminated due to a fatal error in the kernel module amdkmdag.sys. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversCODE-43-USB-HUB
The entire USB controller reports code 43, which disconnects all USB ports on the given group. Common triggers are corrupt USB xHCI Driver and driver conflict after windows update.
DriversNVIDIA-CONTAINER-HIGH-CPU
The nvcontainer.exe or NvTelemetryContainer.exe processes constantly consume 5-20% CPU even when idle. It's most often caused by corrupt driver installation and conflict with other software.
Drivers0x80070005-AUDIO
The audio service cannot start because it doesn't have permissions to access the sound driver. This can also stem from antivirus blocking.
DriversACPI-BIOS-ERROR
Windows stops with ACPI_BIOS_ERROR (0x000000A5) during boot because the system BIOS is not ACPI compliant or has bugs. Use the steps below to track down and fix the cause.
DriversKERNEL-MODE-HEAP-CORRUPT
A kernel-mode driver corrupted the kernel heap. Results in unpredictable BSODs with varying stop codes.
DriversUSB-SELECTIVE-SUSPEND
USB device (mouse, DAC, webcam) randomly disconnects and reconnects due to Windows USB Selective Suspend feature. This usually traces back to hub turning off port to save power and driver not handling resume correctly.
DriversSYSTEM_SERVICE_EXCEPTION
Windows stopped because code running in the system kernel hit an exception, usually a bad memory address, while handling a request from a normal program. In practice the faulty code almost always belongs to a driver:…
DriversCRITICAL_STRUCTURE_CORRUPTION
Windows stopped because it detected that critical kernel code or data had been changed. 64-bit Windows does not allow its kernel to be modified except by Microsoft's own hot patches, so when something changes it,…
DriversDRIVER-POWER-STATE-FAILURE
Windows stopped because a device driver did not finish a power change, such as sleep, wake-up or shutdown, in time. This also covers devices that Windows turns off to save power.
DriversDRIVER-VERIFIER-DMA-VIOLATION
Stop code 0xE6 indicates a driver performed an illegal DMA (Direct Memory Access) operation. DMA allows hardware to access system memory directly without CPU involvement for performance.
Drivers0x000000C4
Driver Verifier detected a violation in a running kernel-mode driver. Use the steps below to track down and fix the cause.
Drivers0x000000C5
A driver attempted to access an invalid memory pool at an elevated IRQL. This can also stem from faulty system RAM.
Drivers0x000000BE
A driver attempted to write to a read-only segment of system memory. Work through the steps below in order.
Drivers0x000000D8
A kernel-mode driver used too many Page Table Entries (PTEs), depleting the system memory manager's address space. Commonly caused by bad graphics drivers, network drivers, or virtualization drivers with memory leaks.
Drivers0x000001D4
The USB Connector Manager UCSI driver detected a hardware or connection timeout in the USB-C Type-C controller firmware. Commonly caused by faulty USB-C hubs, outdated motherboard BIOS, or degraded USB-C ports.
Drivers0x000001D1
The motherboard chipset controller livedump indicates a communication delay or hardware freeze in the Intel/AMD platform controller hub (PCH) drivers. Commonly caused by outdated chipset firmware, aggressive power…
DirectXDXGI_ERROR_DEVICE_REMOVED
A game or app lost its connection to the graphics card and had to stop. Microsoft lists the situations that cause it: the graphics driver was updated, a laptop switched from its power-saving to its performance GPU,…
DirectXD3D-INIT-ERROR
The application cannot initialize Direct3D. The GPU or driver does not support the required version.
DirectXDIRECTX-FEATURE-LEVEL
The application requires DirectX Feature Level 11.0 or higher, which is not supported by the GPU. This can also stem from outdated Driver.
DirectXOPENCL-INIT-FAIL
An application or software cannot initialize the OpenCL interface for GPU computation. Another common trigger is incompatible GPU.
DirectXD3D11_ERROR_OUT_OF_MEMORY
The game or program has exhausted the available VRAM on the graphics card. It's also often linked to texture resolution too high.
DirectXDXGI_ERROR_INVALID_CALL
The application provided incorrect parameters to DirectX. The usual suspects are software developer error and corrupted system files.
DirectXD3D12_ERROR_ADAPTER_NOT_FOUND
The application requires DirectX 12 Feature Level, which the graphics card does not support. Common triggers are old hardware and missing driver.
DirectXDXGI_ERROR_WAS_STILL_DRAWING
Attempting to access the surface that the GPU is currently drawing on. The usual suspects are bad synchronization of application threads and unstable G-Sync/FreeSync.
DirectXD3D_COMPILER_ERROR
The driver failed to compile the shader program for the graphics card. It sometimes comes down to unreadable game files.
DirectXDXGI_ERROR_UNSUPPORTED
A request has been made for a format or function that the hardware does not support. Common triggers are outdated graphics card and attempting HDR on an unsupported monitor.
DirectXDXGI_ERROR_NOT_CURRENT
The game lost focus or was minimized by a system notification. It's most often caused by windows Notifications and applications running in the background (eg updates).
DirectXD3D11_ERROR_FILE_NOT_FOUND
The requested file (eg d3dx11_43.dll) was not found in the system. This can also stem from older game requiring DX9 components.
DirectXDXGI_ERROR_MODE_CHANGE_IN_PROGRESS
Call failure due to resolution or refresh rate change in progress. This can also stem from quick alt-tab switching.
DirectXD3D12_ERROR_NOT_SUPPORTED_OS
DirectX 12 requires a newer build of Windows 10/11. The steps below are ordered to resolve this efficiently.
DirectXD3D11_CREATE_DEVICE_FAIL
CreateDevice failed, probably hardware not responding. It sometimes comes down to using the Microsoft Basic Display Driver.
DirectXDXGI_ERROR_NONEXCLUSIVE
An application is trying to gain exclusive access to the screen, but another program already has it. It's most often caused by background applications (recording, overlay) and error in window manager (DWM).
DirectXD3D12_RAYTRACING_UNSUPPORTED
The game tries to enable DXR (DirectX Raytracing) on a card without RT cores. The usual suspects are enforcing DXR via config and old Architecture (Pascal, Polaris).
DirectXDXGI_ERROR_FRAME_STATISTICS_DISJOINT
The frame rate counter has lost sync. The usual suspects are sudden drop in performance (Stuttering) and changing the power supply (connecting the laptop to the network).
DirectXD3D_SHADER_LINK_ERROR
Failed to link shaders due to different registers or HLSL version. Typical causes include an outdated game running on a modern system and game mods (eg ReShade).
DirectXDXGI_ERROR_WAIT_TIMEOUT
The application waited too long for a synchronization event from the GPU. Typical causes include the card cannot render the image and processor thread stuck.
DirectXD3D12_ERROR_OUT_OF_MEMORY
DirectX 12 application failed to allocate sufficient video or system memory. Reports of DirectX 12 Out of Memory usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere.
DirectXDXGI_ERROR_ACCESS_DENIED
DXGI_ERROR_ACCESS_DENIED (0x887A002B) occurs when an application attempts to acquire exclusive fullscreen mode on a monitor that another application is already controlling, or when the OS denies GPU resource access…
DirectXD3D11-FEATURE-LEVEL-NOT-SUPPORTED
The application requires a Direct3D 11 feature level (e.g., D3D_FEATURE_LEVEL_11_0) that the installed GPU does not support. Modern games often require at minimum D3D Feature Level 11_0, while some newer titles…
DirectXd3dx9_43.dll missing
An older game fails to start because d3dx9_43.dll, xinput1_3.dll or a similar DirectX file is missing. The same applies to xaudio2_7.dll and other d3dx9_*, d3dx10_* or d3dx11_* files.
DirectXDirectX Function Error
A generic crash occurred inside the graphics engine API loop, reporting a failure from a DirectX function call. This usually traces back to unstable GPU overclocking or power draw and corrupt game files or shader cache.
FirmwareSSD-FIRMWARE-BRICK
An SSD firmware update failed or was interrupted, leaving the drive in an unbootable 'bricked' state. The drive may no longer be recognized by the system, appear as 0 bytes, or fail to initialize.
DriversAUDIO-NO-OUTPUT
Windows plays no sound, the speaker icon shows a red X, or hovering over it says "No audio output device is installed". Either Windows does not see the sound device at all, usually because of a driver problem or a…
Apps & runtime0xc0000142
The application failed to start properly (0xc0000142) and will be terminated. Typical causes include missing old .NET Frameworks, the antivirus blocked the loading of some DLLs and error in program registers.
Apps & runtime0xc000007b
A program or game fails to open with "The application was unable to start correctly (0xc000007b)". Microsoft's name for this code is STATUS_INVALID_IMAGE_FORMAT: a file the program loads is either not designed to run…
NetworkNET-WIFI-NO-INTERNET
Windows shows that it is connected to the Wi-Fi network, often as "No internet, secured" or with a globe or warning icon, but websites do not load. The PC reaches the router, but traffic does not get through to the…
MotherboardBT-ERR-43
The Bluetooth toggle is missing or greyed out in Settings and Quick settings. In Device Manager the adapter may show a yellow warning, often with Code 43 (Windows stopped the device because it reported problems).
Windows & BSODPRN-OFFLINE
Windows shows the printer as Offline, and print jobs stay in the queue instead of printing. The printer is usually fine; Windows simply cannot reach it.
NetworkERR-SSL-PROTOCOL-ERR
The browser refuses to load the web page due to an HTTPS/SSL error. Typical causes include the date and time are incorrectly set on the computer, anti-virus programs (e.g.
Windows & BSODDISK-USAGE-100
The system gets extremely stuck, the response takes seconds, the disk is lit at 100% in the task manager. It's most often caused by sysMain (SuperFetch) or Windows Search aggressively index and corrupt paging file.
Windows & BSODWIN-LICENSE-EXPIRE
Windows pops up with a message that activation will expire. It also occurs frequently with legal systems of activated organizations (KMS).
MotherboardBATT-NOT-CHARGING
The adapter is on the network, the icon shows power, but the percentages do not increase. Common triggers are damaged battery (wear), manufacturer's battery software block (life extension - Lenovo Vantage, Asus…
MotherboardUSB-POWER-SURGE
The USB device has exceeded the power limits of its hub port. The usual suspects are short circuit on the USB front panel on the computer case and damaged controller on board.
MotherboardTPM-CLR-PROMPT
After turning on the PC (often when changing the CPU), a message will appear asking you to press Y or N regarding fTPM NV recovery. Common triggers are replacing the processor with a new model, the BIOS update…
GraphicsVIDEO_TDR_FAILURE
Windows tried to recover an unresponsive graphics driver, but the recovery failed.
GraphicsCODE-43-GPU
Device Manager shows "Windows has stopped this device because it has reported problems. (Code 43)" for the graphics card. Microsoft explains that one of the device's drivers told Windows that the device failed, and…
GraphicsGPU-FAN-FAILURE
The GPU fan stopped spinning. Causes rapid overheating and emergency shutdown.
GraphicsGPU-BLACK-SCREEN
The PC turns on, fans spin and lights come on, but the monitor stays black or says "No signal". The monitor is not receiving a picture, either because the cable or input is wrong, or because the PC never finishes its…
GraphicsVRAM-CORRUPTION
The GPU video memory contains bad data. It causes artifacts, app crashes or BSODs.
GraphicsGPU-ARTIFACTING
Artifacts are image errors drawn by the graphics card: colored dots or snow, stripes, checkerboard patterns, stretched triangles or flickering textures. When they appear only in games or 3D apps, the cause is often…
DriversDDU-FAIL
The Display Driver Uninstaller (DDU) failed to completely remove the old GPU drivers, preventing a new installation. Common triggers are DDU was not started in safe mode, active Windows Update in the background and…
GraphicsPCI-E-BANDWIDTH-ISSUE
The graphics card runs on a lower generation or PCIe bus width (eg Gen3 x4 instead of Gen4 x16), which reduces performance. This usually traces back to misplaced GPU in slot, m.2 NVMe drives sharing lines and bad…
GraphicsVRAM-ART-01
Colored squares or bars appear on the screen caused by a VRAM error. The usual suspects are high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsCORE-CLK-CRASH
The core of the graphics card crashes when switching to 3D load. Typical causes include high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsPWR-LIM-THROT
The card suddenly underclocks because it has hit the maximum consumption. It's most often caused by high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsFAN-CRV-FAIL
Graphics card fans do not spin or run at 100% regardless of temperature. Reports of Graphics fan controller failure usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere.
GraphicsDISP-SYNC-LOSS
The image goes black for a second and pops up again, the connection with the monitor is lost. This usually traces back to high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsGSYNC-FLICKER
The adaptive sync module causes the brightness to flicker violently. Typical causes include high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsSHD-COMP-ERR
The graphics card was unable to process the game's shader code. It's most often caused by high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsSLI-DESYNC
Two graphics cards render images out of order (Micro-stuttering). This usually traces back to high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsHOTSPOT-110C
The hottest sensor inside the core exceeded 110°C. It's most often caused by high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsNVLDDMKM-TMOUT
The graphics driver stopped responding for a second and Windows restarted. Common triggers are high temperatures, wear of memory chips and poor quality video cable.
GraphicsCOIL-WHINE-MAX
Coils make a deafening squeal due to high FPS or load. The usual suspects are wear of memory chips, faulty driver and poor quality video cable.
GraphicsVBIOS-CORRUPT
Graphics card won't boot due to damaged chip BIOS. Reports of Corrupted graphics card firmware (VBIOS) usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere.
GraphicsZERO-RPM-FAIL
The card does not turn off the fans even at zero load and low temperature. Typical causes include high temperatures, wear of memory chips, faulty driver and poor quality video cable.
GraphicsHDMI-NO-SIGNAL
The screen is black and shows 'No Signal' even though the PC is on and the cable is connected. This can also stem from the GPU is not fully seated in the PCIe slot.
GraphicsDISPLAYPORT-NO-SYNC
Monitor connected via DisplayPort randomly flickers, dims, or loses sync. It's also often linked to poor quality or too long DP cable (>1.8m without active converter).
GraphicsRESIZABLE-BAR-ERROR
FPS drops in some games after enabling Resizable BAR (AMD Smart Access Memory) or nVidia NVLink. This usually traces back to an outdated VBIOS of the video card does not fully support ReBAR and incorrect…
DirectXDIRECTX_OUT_OF_VRAM
An out of memory error occurring when a graphics-intensive application (usually a modern game) requests more Video RAM (VRAM) than the graphics card physical hardware or virtual pagefile allocator can provide,…
GraphicsGPU-PCIE-BANDWIDTH-ERROR
The GPU is operating in a degraded PCIe bandwidth state (e.g., PCIe x4 instead of x16, or Gen 3 instead of Gen 4). This can reduce GPU performance by 10-30% in bandwidth-limited scenarios.
GraphicsNVIDIA-NVLDDMKM-CRITICAL
A critical failure in the NVIDIA kernel-mode display driver (nvlddmkm.sys). This is more severe than a standard TDR event — the driver cannot recover and triggers a system BSOD.
GraphicsVIDEO_DXGKRNL_FATAL_ERROR
A fatal error occurred in the Microsoft DirectX graphics kernel subsystem (dxgkrnl.sys), forcing a system crash (BSOD 0x113). It sometimes comes down to hardware-level GPU or VRAM instability.
MalwareROOTKIT-DETECTED
A kernel-level rootkit has been detected on the system. Rootkits modify the Windows kernel, bootloader, or firmware to hide their presence from standard antivirus tools.
MalwareCRYPTOMINER-HIGH-CPU
A cryptocurrency mining malware is silently consuming CPU and GPU resources. Symptoms include unexplained 100% CPU or GPU utilization, elevated electricity consumption, fan noise during idle periods, and system…
MotherboardPCIE-ERROR
Error on the PCIe line between the motherboard and the component. This usually traces back to misplaced card and defective driver.
MotherboardVRM-OVERHEAT
The Voltage Regulator Module is overheating. Limits CPU performance or causes shutdown.
MotherboardPCIE-BIFURCATION-ERROR
The motherboard incorrectly distributes the PCIe lines for the adapter (NVME RAID, PLX switch). It's also often linked to bifurcation disabled in BIOS.
MotherboardCMOS-CHK-ERR
The BIOS has lost its settings due to a dead coin-cell battery on the board. Reports of Corrupt CMOS checksum usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere.
MotherboardPOST-CODE-55
On motherboards whose manual defines POST code 55 as memory not installed or not detected, startup has stopped during memory initialization. The number is a firmware diagnostic code, not a Windows error.
MotherboardSEC-BOT-KEY-MS
Safe boot platform keys deleted, can't boot into Windows 11. The usual suspects are dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age of capacitors.
MotherboardTPM-ATT-FAIL
The Trusted Platform Module failed to verify the identity of the hardware. It's most often caused by dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age of capacitors.
MotherboardVRM-PHS-IMB
One of the power supply phases on the board does not supply current, the others are critically overloaded. The usual suspects are dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and…
MotherboardUSB-CTL-DEAD
Some or all of the USB ports have completely stopped responding, the mouse and keyboard are not working. Common triggers are dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age…
MotherboardPCH-OVERHEAT
The chipset on the board is overheating because the passive cooling has lost contact. Common triggers are dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age of capacitors.
MotherboardAZA-AUD-MISS
The integrated sound card (eg Realtek) completely disappeared from the device manager. Typical causes include dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age of capacitors.
MotherboardBIOS-FLS-FAIL
A corrupt installation file was detected while attempting to update the BIOS. The usual suspects are dead battery CR2032, short circuit on the motherboard and age of capacitors.
MotherboardDMI-LNK-DOWN
Communication between the processor and the rest of the board collapses. Common triggers are dead battery CR2032, short circuit on the motherboard and age of capacitors.
MotherboardCMOS-BAT-LEAK
Physical damage to the board caused by button cell battery acid. Typical causes include short circuit on the motherboard, aborted BIOS update process and age of capacitors.
MotherboardARGB-HDR-SHRT
The motherboard has shorted on the 5V ARGB connector, the lighting is flashing or off. It's most often caused by dead battery CR2032, aborted BIOS update process and age of capacitors.
MotherboardLPC-BUS-HANG
The sensor bus for temperature monitoring and fan control stopped responding. The usual suspects are dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age of capacitors.
MotherboardFAN-HDR-BURN
Connecting a too powerful fan fried the PWM control circuit on the motherboard. Common triggers are dead battery CR2032, aborted BIOS update process and age of capacitors.
MotherboardUSB-OVERCURRENT
System shutting down after 15 seconds to protect motherboard from USB short circuit. Another common trigger is damaged USB device.
MotherboardPCIE-GEN-MISMATCH
GPU or NVMe SSD running on PCIe 3.0 instead of PCIe 4.0/5.0, performance is significantly reduced. Reports of PCIe generation - speed mismatch usually describe a sudden crash, brief unresponsiveness, or a stop-code…
MotherboardAUDIO-CONTROLLER-NO-SOUND
The onboard audio controller reports Code 10 (This device cannot start) in Device Manager, resulting in complete loss of audio. This is extremely common after Windows updates that replace audio drivers, or when the…
MotherboardTHUNDERBOLT-CONTROLLER-ERROR
The Thunderbolt controller (Intel JHL series or AMD equivalent) fails to initialize properly. Thunderbolt ports show up as non-functional in Device Manager or are completely absent.
MotherboardPOST-CODE-99
Motherboard debug code 99 indicates a failure during Super I/O chip initialization, which handles legacy hardware connections, front panel ports, and display outputs. Most commonly caused by loose display cables,…
MotherboardPOST-CODE-A2
Motherboard debug code A2 indicates that the BIOS is attempting to detect and initialize SATA/IDE storage drives but has failed or encountered a timeout. Most commonly caused by bad SSD/HDD data cables, dead drive…
NetworkNETIO-ERROR
A network driver or hardware caused an I/O communication error. It's also often linked to damaged ethernet cable or faulty port.
NetworkWINSOCK-CORRUPT
Windows Sockets (Winsock) is the part of Windows that programs use to make network connections, and TCP/IP is the protocol underneath it. When their settings are damaged, typically after removing a VPN, proxy tool or…
NetworkWIFI-DRIVER-CRASH
The wireless network adapter has stopped responding or is disconnecting. The usual suspects are outdated Wi-Fi driver, 2.4GHz channel interference, problem with Power Management and overheated Wi-Fi module.
NetworkSSL-HANDSHAKE-FAIL
The browser or application cannot establish an encrypted HTTPS connection. The usual suspects are bad system time, obsolete root certificates, firewall blocking TLS and antivirus SSL scan.
NetworkGATEWAY-UNAVAILABLE
The computer is connected to the network (LAN/Wi-Fi) but cannot access the Internet due to loss of connection with the default gateway (router). It's also often linked to incorrectly set static IP address in PC.
NetworkIP-ADDRESS-CONFLICT
Your device has been assigned the same IP address that is already being used by another device in the local network. The connection is not working.
NetworkDHCP-TIMEOUT
The computer connected to the network, but the router did not assign an IP address to it. It's also often linked to ISP Provider Error.
NetworkIPV6-LOOP
Packets in an IPv6 network go around in a loop and never reach their destination. Common triggers are ISP Provider Error, stuck Router and IP address conflict.
NetworkWLAN-RST-LOOP
The Wi-Fi card keeps disconnecting and restarting due to a driver error. Typical causes include stuck Router and IP address conflict.
NetworkCBL-UNPL-FLS
The NIC reports 'Cable disconnected' even though the cable is physically plugged in. Common triggers are ISP Provider Error, corrupt network card driver, stuck Router and IP address conflict.
NetworkMAC-CONFLICT
Two devices on the network share the same physical MAC address. It's most often caused by ISP Provider Error and stuck Router.
NetworkVPN-TUN-DROP
The encrypted VPN connection was unexpectedly terminated by the firewall. Common triggers are ISP Provider Error, corrupt network card driver, stuck Router and IP address conflict.
NetworkQOS-THROTTLE
Quality of Service on the router or in Windows inadvertently limits the speed to a fraction of the maximum. Common triggers are ISP Provider Error, corrupt network card driver and IP address conflict.
NetworkIGMP-SNP-FAIL
A local switch or router does not properly filter multicast traffic, IPTV is interrupted. Typical causes include ISP Provider Error, corrupt network card driver and IP address conflict.
NetworkARP-POISON
An attempted Man-In-The-Middle attack has been detected on your network. Common triggers are ISP Provider Error, stuck Router and IP address conflict.
NetworkPRX-DET-STLL
The computer is stuck detecting proxy settings and is blocking web traffic. This usually traces back to ISP Provider Error, corrupt network card driver and IP address conflict.
NetworkMTU-MISMATCH
Different Maximum Transmission Unit settings cause fragmentation and brutal network slowdown. Typical causes include ISP Provider Error, stuck Router and IP address conflict.
NetworkNET-DHCP-LEASE
The system failed to renew its IP address from the DHCP server. This can also stem from network switch misconfiguration.
NetworkIPV6-LEAK-TUNNEL
Windows automatically creates a 6to4 or Teredo tunnel for IPv6, which causes the connection to slow down or fail. Work through the steps below in order.
NetworkDNS-REBINDING-ATTACK
The web browser or DNS cache has been poisoned, causing redirects to bad websites. The usual suspects are infected router with fake DNS records, malware modifying hosts file and public WiFi hotspot with manipulated DNS.
NetworkWIFI_AUTOPREP_FAIL
Wi-Fi disappears from Windows, and trying to start the WLAN AutoConfig service shows "Error 1068: The dependency service or group failed to start". WLAN AutoConfig (WlanSvc) is the service that finds and connects to…
NetworkDNS_PROBE_FINISHED_NXDOMAIN
Chrome or Edge shows "This site can't be reached" with DNS_PROBE_FINISHED_NXDOMAIN. The browser asked a DNS server for the website's address, and the answer was NXDOMAIN, which means the name does not exist.
NetworkWIFI-DRIVER-BSOD
The wireless network adapter driver (commonly Intel AX series or Realtek RTL) causes a Blue Screen of Death. This typically manifests as SYSTEM_THREAD_EXCEPTION_NOT_HANDLED or DRIVER_IRQL_NOT_LESS_OR_EQUAL pointing…
NetworkNETWORK-BOOT-FAIL
The system is attempting to boot from the network via PXE (Preboot Execution Environment) and failing, resulting in delays or 'BOOTMGR is missing' errors. This occurs when the network adapter is set as the first boot…
NetworkIPV6-CONNECTIVITY-FAIL
The system has no IPv6 connectivity while IPv4 functions normally. Modern applications and services increasingly require IPv6 (Microsoft services, Google, gaming platforms).
Power supplyPSU-OVERVOLTAGE
The power supply supplies a higher voltage than specified. Risk of component damage.
Power supplyPSU-INSUFFICIENT
The resource does not have time to cover the consumption of all components. Causes resets.
Power supplyPSU-RIPPLE-NOISE
The source produces higher than permitted supply voltage ripple. It causes instability or damage to the capacitors on the board.
Power supplyOCP-TRIGGERED
The source detected a dangerously high current draw on some of the lines (typically 12V) and immediately shut down the computer just to be safe. Use the steps below to track down and fix the cause.
Power supplyCOIL-WHINE-EXTREME
The source or graphics card emits a high-pitched, annoying buzzing sound, especially under load or at high FPS. It sometimes comes down to resonance of coils in power cascades (a common physical phenomenon).
Power supplyOVP-TRIPPED
The source immediately shut down because the voltage on some of the branches (12V, 5V, 3.3V) increased dangerously. It's most often caused by fluctuations in the distribution network and poor Quality Resource (Tier F).
Power supplyOCP-TRIPPED
The resource has shut down because one of the components (often the GPU) is drawing more current than the cable/branch can handle. It's also often linked to short circuit in wiring.
Power supplyUVP-TRIPPED
The voltage fell below the critical limit, the system shut down as a precaution. Another common trigger is leaked capacitor.
Power supplyOPP-TRIPPED
The total required system power exceeds the maximum power supply limit. It sometimes comes down to upgrade to a much more greedy CPU/GPU without changing the source.
Power supplySCP-TRIPPED
The source has detected a physical short circuit, immediately disconnects the power supply, the PC does not respond to the button at all. The usual suspects are poorly connected connector, melted EPS/PCIe connector…
Power supplyOTP-TRIPPED
The source's internal temperature sensors exceeded the safe limit and the source shut down. The usual suspects are power supply fan stuck, clogged dust filter on the bottom of the cabinet and the power supply is…
Power supplyPG-SIGNAL-FAIL
The power supply failed to confirm to the motherboard in time that the voltage is stable, therefore the board will not start (POST). Another common trigger is aging capacitors.
Power supplyRIPPLE-NOISE-MAX
The DC power from the power supply contains too much AC interference (noise), causing instability and freezing of the PC. The usual suspects are extremely cheap resource and loss of functionality of filter capacitors…
Power supplyPWR-CABLE-MELT
The plastic connector (typically 12VHPWR or older PCIe) has melted due to contact resistance. This usually traces back to too much bent cable (in a small space) and low quality pins.
Power supplyCOIL-WHINE-PSU
The power supply emits a very unpleasant high-frequency sound, especially when switched off or under load. The usual suspects are resonance of embedded chokes (coils) at certain PWM frequencies and enabled C-States…
Power supplyPSU_POWER_SAG_FREEZE
The power supply unit voltage rails drop below the minimum safety threshold under sudden current transitions (transient power spikes), causing the CPU or GPU to freeze instantly without a Blue Screen. Follow the…
Power supplyPSU-CAPACITOR-BULGE
Physical inspection reveals bulged or leaking electrolytic capacitors inside the power supply unit. Bulging capacitors are a sign of imminent catastrophic failure.
Power supplyPSU-RAIL-UNDERVOLTAGE
The PSU's 12V rail is delivering voltage significantly below the ATX standard of 12V ±5% (11.4V minimum). The 12V rail powers the CPU via EPS connectors and the GPU via PCIe connectors.
MemoryMEMORY_MANAGEMENT
Windows stopped because it found a severe error in how memory is managed, such as damaged page tables or memory records that no longer match. Microsoft describes several of its specific error types as probably…
MemoryBAD_POOL_HEADER
Windows stopped because it found damaged bookkeeping data (a pool header) in the kernel's memory pool, the shared memory drivers use. Microsoft notes that the pool was already corrupted when the crash happened, so…
MemoryXMP-INSTABILITY
Activated XMP/EXPO profile causes instability or non-booting. This usually traces back to RAM incompatible with board, need for higher voltage and BIOS bug.
MemoryRAM-NOT-DETECTED
Motherboard doesn't recognize RAM - reports low memory or won't boot. Typical causes include module incorrectly inserted, oxidized contacts and defective DIMM slot.
MemoryRAM-ECC-ERROR
The ECC memory detected and corrected the error, but there is a risk of an uncorrectable error when retrying. Common triggers are aging of RAM modules, cosmic Rays, electrostatic discharges and unstable power supply.
MemoryPAGE-FAULT-BOOT
BIOS/UEFI detected a fatal page fault during operating system startup. Windows won't load.
MemorySPD-CORRUPTION
The Serial Presence Detect (SPD) chip on the RAM module has corrupted data, the system does not know what timing and frequency to set. It sometimes comes down to SPD read/write voltage failure.
MemorySPD-CHK-ERR
The motherboard cannot read the timing from the memory module. It's most often caused by poor quality CPU controller, frequency too high and dust in slot.
MemoryBNK-INT-ERR
Communication problem between the front and back of the memory module. The usual suspects are different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryXMP-BOOT-FAIL
Memory cannot run at factory overclocked values. Typical causes include different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryMEMTEST-ERR-8
A memory test such as MemTest86 or Windows Memory Diagnostic reported errors: data written to RAM did not read back correctly. Errors like this can cause crashes, blue screens and corrupted files.
MemoryVDDQ-U-VOLT
The modules lack the voltage to maintain the set frequencies. It's most often caused by poor quality CPU controller, frequency too high and dust in slot.
Memory1T-CMD-FAIL
The memory controller does not have time to process commands with a delay of only 1 clock. Common triggers are different modules in one board, frequency too high and dust in slot.
MemoryECC-LIM-EXC
Server memory is fixing so many bugs that it can't keep up. It's most often caused by different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryROW-HAM-DET
Dangerous charge spillage between memory cells noted. It's most often caused by different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryDCH-ASYNC
Although the memories run in Dual-Channel, they are poorly matched, which limits throughput. Typical causes include different modules in one board, frequency too high and dust in slot.
MemoryPIN-OXIDATION
Contact with the socket is broken due to dirt or oxidation on the pin. The usual suspects are different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryREF-TIMEOUT
Memory cells have lost their charge before the next refresh cycle. The usual suspects are different modules in one board, poor quality CPU controller, frequency too high and dust in slot.
MemoryGEAR-MD-FAIL
The motherboard cannot run stably in split controller frequency mode. It sometimes comes down to dust in slot.
MemorySUBTIM-CORRUPT
The board set too aggressive sub-timings (eg tFAW, tRRD). The usual suspects are poor quality CPU controller, frequency too high and dust in slot.
MemoryDDR5-PMIC-TMP
The Power Integrated Controller (PMIC) on the DDR5 memory has overheated. This usually traces back to different modules in one board, frequency too high and dust in slot.
MemoryIMP-CAL-FAIL
The motherboard is stuck in a loop while calibrating the memory signal impedance. The usual suspects are poor quality CPU controller, frequency too high and dust in slot.
Windows & BSODMEM-LEAK-SYS
A critical system process is consuming available memory indefinitely. The usual suspects are faulty driver (Non-paged pool leak) and buggy background service.
MemoryMCE-MEM-READ-ERR
The processor detected an unrecoverable error while reading data from memory and wrote it to the MCE log. Common triggers are physically damaged RAM module and unstable XMP/EXPO profile.
MemoryRAM_MEMORY_LEAK_SYSTEM
The system kernel's non-paged memory pool expands continuously without releasing memory, consuming all physical RAM and causing severe freezes, micro-stutters, and eventual crash/BSOD. The usual suspects are faulty…
MemoryDRAM_POST_TIMEOUT
The motherboard BIOS takes an excessive amount of time training the DDR5 memory channels on boot, eventually timing out and reporting a POST failure or resetting the memory frequency back to 4800MHz. See the…
MemoryXMP_PROFILE_BOOT_LOOP
Enabling Intel XMP or AMD EXPO profiles causes the PC to fail POST, resulting in a series of boot loops before resetting settings to BIOS defaults. The usual suspects are incompatible RAM modules with motherboard…
MemoryDOUBLE_FAULT
DOUBLE_FAULT (Stop Code 0x00000008) occurs when the processor generates an exception while already handling an exception, or when the exception handler itself raises an exception. This is a catastrophic kernel state…
MemoryRAM-DUAL-CHANNEL-FAIL
The system is operating in single-channel memory mode instead of the expected dual-channel configuration. Dual-channel mode doubles the effective memory bandwidth by using two RAM channels simultaneously.
MemoryECC-MEMORY-ERROR
Error-Correcting Code (ECC) memory has detected a bit error in RAM. Correctable single-bit errors (SECE) are automatically fixed by ECC logic, but uncorrectable multi-bit errors (MECE) cause system crashes.
Memory0x0000002E
A DATA_BUS_ERROR occurs when a parity error in system memory is detected, indicating memory bus communication failure. Most commonly caused by defective RAM modules, dusty DIMM slots, motherboard trace damage, or…
Apps & runtimeDLL-NOT-FOUND
The application cannot find the required DLL and will not start. It's most often caused by missing redistributable packages, deleted DLL and malware.
Apps & runtimeINSTALLER-ERROR-1603
A Windows Installer (.msi) setup stops with "Error 1603: A fatal error occurred during installation" and rolls back. Microsoft lists four causes: the app is already installed, the target folder is encrypted, the…
Apps & runtimePYTHON-DLL-LOAD
Python cannot load the required DLL (python3xx.dll). The application or script does not start.
Apps & runtimeMSVCR140-MISSING
The application requires MSVCR140.dll from the Visual C++ 2015-2022 Runtime, which is not installed. It's most often caused by corrupt VC++ installation and deleted DLL.
Apps & runtimeDLL-FAULT-ntdll.dll
The application could not be started because the ntdll.dll module threw an exception or was not found. It's most often caused by deleted library file, incompatible version of Visual C++ and malware Damage.
Apps & runtimeDLL-FAULT-kernel32.dll
The application could not be started because the kernel32.dll module threw an exception or was not found. Common triggers are deleted library file, incompatible version of Visual C++ and malware Damage.
Apps & runtimeDLL-FAULT-user32.dll
The application could not be started because the user32.dll module threw an exception or was not found. It's most often caused by deleted library file, incompatible version of Visual C++ and malware Damage.
Apps & runtimeDLL-FAULT-hal.dll
The application could not be started because the hal.dll module threw an exception or was not found. It's most often caused by deleted library file, incompatible version of Visual C++ and malware Damage.
Apps & runtimeDLL-FAULT-dxgi.dll
The application could not be started because the dxgi.dll module threw an exception or was not found. Typical causes include deleted library file, incompatible version of Visual C++ and malware Damage.
Apps & runtimeDLL-FAULT-d3d11.dll
The application could not be started because the d3d11.dll module threw an exception or was not found. It's most often caused by deleted library file, incompatible version of Visual C++ and malware Damage.
Apps & runtimeDLL-FAULT-ucrtbase.dll
The application could not be started because the ucrtbase.dll module threw an exception or was not found. Common triggers are deleted library file, incompatible version of Visual C++ and malware Damage.
Apps & runtimeBATTLEYE-KICK
BattlEye anti-cheat blocks game launch or kicks from server with 'Blocked loading of file' or 'Corrupted data'. This can also stem from conflicting kernel-level software (VPN drivers, RGB software).
Apps & runtimeEPIC-GAMES-0004
Epic Games Launcher fails to install or update with error code 0004 or IS-DS01. It's most often caused by insufficient disk space on system drive, windows Installer service malfunction and corrupted EGL prerequisites…
Apps & runtimeSTEAM-CONTENT-FILE-LOCKED
Steam cannot update a game and reports 'An error occurred while updating [Game] (content file locked)'. See the troubleshooting steps below for the fix.
Apps & runtimeVCRUNTIME140-DLL-MISSING
A program or game will not start and Windows says that VCRUNTIME140.dll, VCRUNTIME140_1.dll or MSVCP140.dll was not found or is missing. These files belong to the Microsoft Visual C++ Redistributable, a free package…
Apps & runtimeDOTNET-FRAMEWORK-INSTALL-FAIL
An older program asks for .NET Framework 3.5, but installing it fails, often with 0x800F0906, 0x800F081F or 0x800F0907. Version 3.5 is an optional Windows feature whose files are downloaded from Windows Update when…
Apps & runtime0xC000012F
A Bad Image error indicates that a dynamic-link library (DLL) file required by a program is either corrupted, unreadable, or compiled for a different processor architecture (e.g., 32-bit vs 64-bit). Commonly occurs…
StorageSMART-REALLOCATED
SSD/HDD remaps bad sectors. The disk is nearing the end of its life.
StorageNTFS_FILE_SYSTEM
Windows stopped because of a problem in ntfs.sys, the driver that reads and writes NTFS drives. The blue screen often names ntfs.sys after "What failed".
StorageINACCESSIBLE_BOOT_DEVICE
Windows lost access to the drive it starts from while it was booting, so it cannot continue. Microsoft lists the typical triggers: a changed storage controller mode in the BIOS (for example AHCI or RAID), a new disk…
StorageSSD-TRIM-FAIL
TRIM for SSD does not work, it reduces the performance and life of the drive. Common triggers are SSD in RAID array and old firmware.
StorageSSD-WEAR-CRITICAL
The SSD has reached the critical TBW (Total Bytes Written) wear limit. Risk of failure.
StorageDISK-READ-ERROR
Windows reports 'A disk read error occurred' when booting. PC won't boot.
StorageCRC-DATA-ERROR
The operating system encountered a Cyclic Redundancy Check error while reading from the file. The data is corrupted and cannot be read.
StorageRAW-FILE-SYSTEM
The disk's file system (NTFS/FAT32) has been corrupted and the system sees it as unformatted (RAW). Data is unavailable.
StorageSMART-PRE-FAIL
Self-diagnosis of the disk predicts its early physical end. Common triggers are end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StorageSATA-CRC-ERR
Data is lost during cable transmission, indicating a damaged connector. This usually traces back to power outages and high temperatures in the M.2 slot.
StorageBAD-SEC-UNC
The HDD surface or SSD memory cell has been permanently damaged. Common triggers are defective cable, power outages and high temperatures in the M.2 slot.
StorageCACHE-FLSH-FAIL
The data in the disk cache was not saved before the power failure. It's most often caused by end of life (age), defective cable and high temperatures in the M.2 slot.
StorageMBR-GPT-CORR
The system sees the disk as unallocated space with no data. Typical causes include end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StorageVSS-FREEZE
Creating a restore point or backup caused the disk to freeze. Common triggers are end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StorageTRIM-IGNORE
The SSD does not clean up the deleted blocks, which reduces the speed extremely. Reports of TRIM command to clean SSD was ignored usually describe a sudden crash, brief unresponsiveness, or a stop-code screen…
StorageSPN-MOT-FAIL
The platters of a classic hard disk cannot spin (click). This usually traces back to end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StorageM2-THROTTLING
The M.2 disk controller is baked under the graphics card, and the speed has dropped to a minimum. The usual suspects are end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StorageBIT-ROT-DET
The data on the disk has naturally degraded, leading to archive file corruption. The usual suspects are end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StorageSEC-ERS-LOCK
ATA Secure Erase command was rejected by frozen disk security. The usual suspects are end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StoragePCIE-LANE-DRP
M.2 drive running on PCIe x4 suddenly fell into PCIe x1 mode, reading speed dropped drastically. It's most often caused by end of life (age), defective cable, power outages and high temperatures in the M.2 slot.
StorageSSD-TEMP-WARN
The NVMe or SATA SSD is operating above optimal temperatures. This usually traces back to poor case airflow and missing M.2 heatsink.
StorageNVME_READ_ONLY
The solid state drive controller detects media wear or flash array errors and locks itself in read-only write-protection to prevent further data loss. The user can read files but cannot save, modify, or format the drive.
StorageNVME_OVERHEATING_CRASH
High-speed NVMe PCIe SSD temperature exceeds safety thresholds, triggering critical thermal throttling, performance drops, or sudden controller disconnects resulting in BSOD or system freeze. Common triggers are…
StorageNVME-CONTROLLER-RESET
Windows sent a command to the NVMe SSD, got no answer in time and reset the drive's controller. Event Viewer records this as Event ID 129 from stornvme with the message "Reset to device, \Device\RaidPort0, was issued".
StorageDISK-WRITE-PROTECT-ERROR
Windows cannot write to the disk due to write protection. This can occur on USB drives with physical write-protect switches, SSDs with failed controllers entering read-only mode as a self-protection mechanism, or…
StorageBITLOCKER-RECOVERY-LOOP
The system is stuck in a BitLocker recovery screen loop, repeatedly asking for a 48-digit recovery key. This occurs when the TPM chip detects that the boot configuration has changed (BIOS update, new hardware, Secure…
StorageHDD-SLOW-READ-SPEED
A mechanical hard disk drive (HDD) exhibiting extremely slow read/write speeds, typically below 30 MB/s when sequential reads should be 100-200 MB/s. This is an early warning sign of imminent drive failure.
StorageNVME-PCIE-DEMOTION
The M.2 SSD runs at half speed due to shared PCIe lanes with the GPU or chipset. Work through the steps below in order.
StorageSSD-DRAM-CACHE-FAIL
An SSD without a DRAM cache (DRAM-less) is extremely slow when writing large files or reading small files. It's also often linked to defragmenter running on SSD instead of TRIM.
StorageCHKDSK-STAGE3-STUCK
The chkdsk disk checker is stuck at stage 3 (Security Descriptors) or 4 and is not progressing. It's most often caused by extremely large number of file system errors, bad sectors on the HDD slow down the operation…
FirmwareBIOS-BOOT-LOOP
The PC restarts in an endless loop after POST. Problem with UEFI boot records or corrupted BCD.
FirmwareUEFI-SHELL-ERROR
The system booted into the UEFI shell instead of the OS. The boot record is missing or corrupted.
FirmwareFIRMWARE-ROLLBACK-BLOCKED
An attempt to downgrade the BIOS was blocked by board protection or Intel Boot Guard. The steps below are ordered to resolve this efficiently.
FirmwareNVRAM-FULL
UEFI NVRAM is full of variables. It causes boot problems and the inability to save settings.
FirmwareCSM-CONFLICT
Compatibility Support Module (CSM) conflicts with UEFI OS or Secure Boot. It's also often linked to old OS installed in Legacy mode.
FirmwareUEFI-BOOT-LOOP
Every time the PC is started, the system automatically redirects to the BIOS instead of Windows. It's also often linked to change SATA mode (AHCI/RAID).
FirmwareCSM-CONFLICT-VGA
The CSM module has been disabled, but the older graphics card does not have UEFI GOP (Graphics Output Protocol). It sometimes comes down to outdated firmware on GPU.
FirmwareUEFI-SHELL-FALLBACK
It started the EFI command interface instead of the operating system. It's most often caused by deleted EFI partition and disk not found by BIOS.
FirmwareME-FW-UPDATE-FAIL
The Intel Management Engine firmware update failed or was interrupted. This can also stem from power interruption while flashing.
FirmwareAMD-AGESA-MICROCODE
The installed processor is not fully supported by the current version of AGESA libraries in the BIOS. Follow the steps below to fix it.
FirmwareACPI-TABLE-CORRUPT
Windows BSOD ACPI_BIOS_ERROR due to faulty BIOS power management configuration. Follow the steps below to fix it.
FirmwareFAST-BOOT-HANG
The computer won't start because it's stuck in the fast boot phase. This can also stem from incompatible USB device connected.
FirmwareBIOS-PWD-LOCKOUT
Access to the computer is blocked due to an unknown UEFI administrator password. The steps below are ordered to resolve this efficiently.
MalwareADWARE_POPUP_LOOP
This diagnosis detects persistence registry keys, browser push notifications, or scheduled tasks displaying random popup ads, redirection screens, or background browser processes. This can also stem from installing…
MalwareBROWSER_HIJACKER_REDIRECT
This diagnosis detects unauthorized modification of default web browser homepages, search engines, and shortcuts, redirecting users to malicious advertising search portals. It sometimes comes down to adware wrappers…
MalwareDNS_HOSTS_REDIRECT
This diagnosis detects unauthorized local DNS redirect entries added to the Windows Hosts file, preventing access to security updates and redirecting legitimate sites to phishing portals. Work through the steps below…
MalwareHIGH_CPU_CRYPTOMINER
This diagnosis identifies background mining scripts or binaries running under spoofed system process names (e.g. lsass.exe, svchost.exe), causing high CPU/GPU resource utilization, thermal throttling, and severe…
MalwareKEYLOGGER_TROJAN_SPY
This diagnosis detects spyware hooks capturing keyboard inputs, screenshots, or clipboard data, transmitting the records to remote command-and-control servers. The usual suspects are phishing link execution or…
MalwareRANSOMWARE_ENCRYPTION_ATTACK
This diagnosis detects ransomware-like active encryption behavior on system folders, resulting in encrypted document extensions, ransom notes (.txt/.html), and locked administrative panels. Typical causes include…
MalwareSECURITY_SERVICE_DISABLED
This diagnosis identifies active registry or group policy modifications that disable Windows Defender, Security Center services, and Windows Update, leaving the operating system vulnerable. This can also stem from…
MalwareWANNACRY_RANSOMWARE
WannaCry is a notorious ransomware cryptoworm that targeted computers running Microsoft Windows by encrypting data and demanding ransom payments in Bitcoin. It propagates using the EternalBlue exploit (CVE-2017-0144)…
MalwarePETYA_NOTPETYA_WIPER
Petya/NotPetya is a highly destructive wiper malware masquerading as ransomware. It targets Windows computers, encrypting the Master File Table (MFT) and overwriting the Master Boot Record (MBR) to completely prevent…
MalwareEMOTET_BOTNET_LOADER
Emotet is an advanced, modular banking trojan that operates primarily as a downloader or loader for other malware (such as TrickBot or Ryuk). It spreads through malicious email attachments (macros) and propagates…
MalwareRYUK_RANSOMWARE
Ryuk is a sophisticated ransomware variant targeting large enterprises and critical infrastructure. It is typically deployed manually by attackers after gaining access via phishing (often via Emotet or TrickBot) and…
MalwareLOCKBIT_3_RANSOMWARE
LockBit 3.0 (also known as LockBit Black) is a highly aggressive ransomware-as-a-service (RaaS) variant. It employs advanced anti-analysis techniques, disables security tools, and encrypts files using a…
MalwareQAKBOT_STEALER_BACKDOOR
Qakbot (or Qbot) is a long-standing information-stealing Trojan and backdoor. It captures banking credentials, keystrokes, and emails, and acts as an entry point for ransomware gangs to deploy larger payloads like…
MalwareREDLINE_INFO_STEALER
RedLine Stealer is a widely distributed malware-as-a-service info-stealer. It harvests cached browser passwords, credit card details, cookies, autocomplete data, FTP credentials, and cryptocurrency wallet keys from…
MalwareCLOP_RANSOMWARE
Clop is a ransomware family known for pioneering large-scale data extortion campaigns. It famously exploited zero-day vulnerabilities in managed file transfer (MFT) software, such as MOVEit Transfer (CVE-2023-34362),…
MalwareLAZARUS_BLUENOROFF_APT
Lazarus and its sub-group Bluenoroff are state-sponsored advanced persistent threat (APT) actors. They target global financial institutions, SWIFT networks, cryptocurrency exchanges, and blockchain platforms using…
MalwareVOLT_TYPHOON_APT
Volt Typhoon is a state-sponsored cyber actor that targets critical infrastructure. They use 'Living-off-the-Land' (LotL) techniques—using legitimate built-in administrative tools like PowerShell, wmic, and netsh—to…
Windows & BSOD0x000000EF
Windows stopped because a system process it cannot run without ended unexpectedly. These processes manage things like sign-in, sessions and system services, so Windows treats their loss as fatal and restarts.
Windows & BSOD0x00000050
Windows stopped because it tried to use system memory at an address that is not valid, usually a wrong address or memory that was already freed. Microsoft lists three main sources: a faulty driver or system service,…
Windows & BSOD0xC004F074
Windows could not contact the activation server or the key is invalid. Typical causes include hardware change and offline PC.
Windows & BSODKERNEL_DATA_INPAGE_ERROR
Windows stopped because it could not read a page of its own kernel data back from the paging file on the drive into memory. Microsoft's list of causes points mostly at storage: bad sectors on the drive, a loose or…
Windows & BSODDPC_WATCHDOG_VIOLATION
Windows stopped because a driver held the processor for too long. Drivers handle hardware events in short, high-priority routines (deferred procedure calls, DPCs), and a watchdog in Windows triggers this stop code…
Windows & BSODUNEXPECTED_KERNEL_MODE_TRAP
Windows stopped because the processor raised an error (a trap) inside the Windows kernel that the kernel could not handle. A common example is a double fault: an error that happens while the processor is already…
Windows & BSODSTATUS_ACCESS_VIOLATION
The application attempted to access a protected area of memory. Most often an application or driver error.
Windows & BSOD0x8000FFFF
Windows Update encountered an unexpected error and cannot download or install updates. This usually traces back to stopped BITS service and not enough disk space.
Windows & BSOD0xC0000005
The application attempted to access memory to which it does not have access rights. Typical application or driver error.
Windows & BSOD0x0000004A
A critical Windows error indicating that a system service was accessed with an IRQL that was too high. This usually traces back to incompatible software (antivirus, firewall) and bad device driver.
Windows & BSODKMODE_EXCEPTION_NOT_HANDLED
Windows stopped because a program running in kernel mode, almost always a driver or system service, caused an error that nothing caught. Microsoft lists three main sources: a faulty device driver or system service,…
Windows & BSODPFN_LIST_CORRUPT
The PFN (Page Frame Number) data structure is corrupted. The system detected an inconsistency in memory.
Windows & BSOD0x80070422
Windows Update cannot start because a service it needs is disabled. Microsoft's name for the code is ERROR_SERVICE_DISABLED, and for Windows Update it means the Windows Update service stopped working or isn't running.
Windows & BSODWU-0x80070002
A Windows update fails with 0x80070002. Microsoft's name for the code is ERROR_FILE_NOT_FOUND, "The system cannot find the file specified", and lists it among Windows Update corruption errors.
Windows & BSODWU-0x80004005
Windows cannot check for or install updates. Error code: 0x80004005.
Windows & BSODWU-0x80070005
A Windows update fails with 0x80070005, E_ACCESSDENIED. Microsoft explains that the update process could not access required files, folders or registry entries.
Windows & BSODWU-0x8009000B
Windows cannot check for or install updates. Error code: 0x8009000B.
Windows & BSODWU-0x8007001F
Windows cannot check for or install updates. Error code: 0x8007001F.
Windows & BSODWU-0x80070424
Windows cannot check for or install updates. Error code: 0x80070424.
Windows & BSODWU-0x80070643
An update fails with 0x80070643, which is the Windows Update form of installer error 1603, ERROR_INSTALL_FAILURE: an installation failed. The code is generic, so the update's name matters.
Windows & BSODSVC-FAIL-wuauserv
The wuauserv service terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-BITS
The BITS service has terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-Winmgmt
The Winmgmt service terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-Spooler
The Spooler service terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-LanmanWorkstation
The LanmanWorkstation service terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-LanmanServer
The LanmanServer service terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-CryptSvc
The CryptSvc service terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-TermService
TermService terminated unexpectedly. Services dependent on this process may not work.
Windows & BSODSVC-FAIL-VSS
The VSS service terminated unexpectedly. Services dependent on this process may not work.
Windows & BSOD0x0000000A
Windows stopped because a driver or Windows itself accessed memory at an invalid address while running at a raised priority level (IRQL). The cause is typically a bad memory pointer in a driver.
Windows & BSOD0x000000FC
Windows stopped because a driver tried to run code from memory that is marked as data only (non-executable). The processor's No-Execute protection blocks this, because running code from data memory is how both buggy…
Windows & BSOD0x000000C2
Windows stopped because a driver made an invalid request for kernel memory, such as freeing the same memory twice. Requesting memory at a priority level where that is not allowed causes it too.
Windows & BSOD0x000000EA
A thread has been waiting for a device in hardware state for an infinite amount of time. Common triggers are typically the graphics or sound card driver has looped and bad power profile activated.
Windows & BSOD0x80073712
Windows Update cannot install an update because the component store is damaged. The component store (the WinSxS folder) holds the files Windows uses to install updates and features, and Microsoft names this code…
Windows & BSODMEMORY-INTEGRITY-INCOMP
Windows Security reports that Memory Integrity Protection is disabled due to an incompatible driver. Another common trigger is cheating software or old anti-cheat.
Windows & BSODWINDOWS-DEFENDER-STUCK
Windows Defender Antivirus is causing 100% CPU or disk usage and is not responding. Typical causes include security definitions not updated and exception for system folders is not set.
Windows & BSOD0x00000709
Windows cannot set the default printer or connect to a network printer. The usual suspects are registry key restriction and driver mismatch.
Windows & BSOD0x8007007e
The specified module could not be found. This error commonly occurs during Windows Updates, system service operations, or application launches when a critical DLL dynamic link library or driver component is missing.
Windows & BSOD0x8007045D
Request could not be performed because of an I/O device error. Often indicates failing sectors.
Windows & BSOD0x800704cf
The network location cannot be reached. Error occurs when trying to sign in to Microsoft services or access network drives.
Windows & BSOD0x80072efd
Windows Update could not reach Microsoft's servers because the connection timed out. Microsoft groups 0x80072EFD with other time-out errors and says the fix is to make sure no firewall rules or proxies block…
Windows & BSOD0x80080005
This error occurs when the Windows Update client fails to execute because the background service or security catalog database is corrupted, preventing Windows from downloading updates. Another common trigger is…
Windows & BSOD0x800F081F
Windows shows 0x800F081F when it needs repair or feature files and cannot find usable ones. Microsoft names it CBS_E_SOURCE_MISSING: the source path does not contain the files, you lack read access to it, or the…
Windows & BSOD0x800f0922
An update or Windows feature fails to install with 0x800F0922. Microsoft's name for the code is CBS_E_INSTALLERS_FAILED: one of the installers in the servicing process failed, and the update rolls back.
Windows & BSOD0x800f0988
Windows cumulative updates fail to install with error code 0x800f0988, which points to corrupted component files in the Windows Side-by-Side (WinSxS) repository. The steps below are ordered to resolve this efficiently.
Windows & BSOD0x80240034
This error occurs when the Windows Update client fails to download the update package because the download transaction metadata or database state is corrupted. Work through the steps below in order.
Windows & BSOD0x80244007
SOAP client failed. This error is triggered during Windows Update scans when SOAP (Simple Object Access Protocol) XML messages are blocked or misformatted, often due to server-side session timeouts or proxy interference.
Windows & BSOD0x80244018
Windows Update connection was blocked by a proxy, firewall, or gateway, returning an HTTP 403 Forbidden status code. It sometimes comes down to corrupted software distribution directory files.
Windows & BSOD0x80246007
This error indicates that the update download was interrupted unexpectedly. This is typically related to background intelligent transfer service (BITS) dropouts or network conflicts.
Windows & BSOD0x803f8001
This error indicates a licensing or digital rights validation issue when launching or downloading games and apps from the Microsoft Store or Xbox App (such as Minecraft or Xbox Game Pass titles). The system cannot…
Windows & BSOD802-1X-AUTH-FAIL
Cannot connect to corporate or university Wi-Fi that uses 802.1X (RADIUS) authentication. Windows prompts for credentials repeatedly.
Windows & BSODAUDIO-RENDERER-ERR
Browser (Chrome/Edge) reports 'Audio renderer error' and cannot play media until restarted. Another common trigger is exclusive mode lock by another application.
Windows & BSODBLUETOOTH-AUDIO-STUTTER
Bluetooth headphones, speakers or other devices keep disconnecting, or the sound stutters and cuts out. Microsoft says disconnections are often caused by power-saving settings, outdated drivers or temporary glitches.
Windows & BSODBLUETOOTH-PAIRING-FAIL
Windows does not find a Bluetooth device, pairing fails, or a paired device shows as paired but will not connect. Bluetooth itself is working on the PC, but the connection with this device does not succeed.
Windows & BSODCPU-FAN-ERROR
The motherboard BIOS cannot detect a CPU fan signal during POST. System may refuse to boot to protect the CPU.
Windows & BSODDIRECTSTORAGE-NOT-SUPPORTED
A game requires DirectStorage (GPU decompression) but it is not available, causing long load times or a launch failure. It's also often linked to windows 10 version below 1903 or Windows 11 required for full GPU path.
Windows & BSODEVENT-ID-41-KERNEL-POWER
Event Viewer shows a critical Kernel-Power event 41 after the PC restarted or shut off on its own. Its text is "The system has rebooted without cleanly shutting down first", and Event ID 6008 (an unexpected previous…
Windows & BSODHYPER-V-MEM-OVERCOMMIT
A Hyper-V VM crashes or Windows host becomes unresponsive due to memory overcommitment. Use the steps below to track down and fix the cause.
Windows & BSODOPENGL-INVALID-OPERATION
An OpenGL command was issued that is not valid for the current OpenGL state. Application may crash or render incorrectly.
Windows & BSODPOWERCFG-HIGH-DRAIN
Laptop battery discharges significantly faster than expected, even in sleep/standby mode. Another common trigger is high background CPU usage (Windows Search, Defender).
Windows & BSODSLEEP-WAKE-FAIL
The computer appears to enter sleep/standby but cannot wake up. Requires hard reset.
Windows & BSODSMB-SIGN-MISMATCH
Cannot connect to a Windows file share. Error: 'The network path was not found' or 'Access denied' due to SMB signing policy conflict.
Windows & BSODSPATIAL-SOUND-FAIL
Spatial sound format (Windows Sonic, Dolby Atmos, DTS) fails to activate or produces distorted output. It's also often linked to exclusive mode conflict.
Windows & BSODSTORAGE-SPACES-DEGRADED
A Storage Spaces pool is in a degraded state because one or more member drives failed or disconnected. The usual suspects are SATA/USB connection lost and disk firmware bug causing disconnection.
Windows & BSODTASK-SCHEDULER-ERR
A Windows Task Scheduler task runs but exits with return code 0x1 (general error) or 0x41301 (task is running). Another common trigger is 'Run only when user is logged on' vs 'Run whether user is logged on or not'…
Windows & BSODUSB-DEVICE-NOT-RECOGNIZED
Windows shows "USB device not recognized" when you plug in a device, and the device does not work. In Device Manager it may appear as Unknown USB Device with a yellow warning sign.
Windows & BSODVULKAN-ERROR-OUT-OF-DATE-KHR
The Vulkan surface has changed (window resize, alt-tab) and the swapchain needs to be recreated. Games may crash instead of handling this.
Windows & BSODVULKAN-VALIDATION-ERROR
Vulkan validation layers report API usage errors. Usually only visible to developers but can cause crashes in debug builds.
Windows & BSODWINDOWS-ROLLBACK-STUCK
After a failed Windows update, the system is stuck at 'Reverting changes – Do not turn off your computer' for over an hour. It's also often linked to slow or failing storage drive.
Windows & BSODWSL2-NETWORK-BROKEN
After the PC wakes from sleep, WSL2 has no internet connectivity. DNS fails and ping fails inside the subsystem.
Windows & BSODWU-0x8007000d
The update data is invalid. This error indicates that the downloaded update files are incomplete, corrupted, or have failed validation checks.
Windows & BSODWU-0x80070020
A Windows update fails with 0x80070020. Microsoft's name for the code is ERROR_SHARING_VIOLATION: the process cannot access a file because another process is using it.
Windows & BSODWU-0x80070490
Windows Update fails with 0x80070490. Microsoft's name for the code is ERROR_NOT_FOUND: something Windows needed for the update was not found.
Windows & BSODWU-0x80070bc2
A system restart is required to complete the installation of the update. The update installation enters a loop where it continually requests a reboot without completing.
Windows & BSODWU-0x800b0100
No signature was present in the subject. This error indicates that the downloaded update files are missing digital signatures or have been corrupted, causing trust verification to fail.
Windows & BSODWU-0x80240017
The update is not applicable to the operating system. This usually happens when the update package architecture does not match your system (e.g. 64-bit update on 32-bit OS) or prerequisite updates are missing.
Windows & BSODWU-0x80240020
The update installation was blocked or failed to trigger, typically due to upgrade registry locks or incomplete session parameters in the update database. Work through the steps below in order.
Windows & BSODWU-0x8024402c
Windows Update could not look up the address of Microsoft's update servers or of the proxy server it is set to use. Microsoft names 0x8024402C WU_E_PT_WINHTTP_NAME_NOT_RESOLVED: the proxy server or target server name…
Windows & BSOD0x8007007B
The filename, directory name, or volume label syntax is incorrect during activation. Reports of Windows activation error 0x8007007B usually describe a sudden crash, brief unresponsiveness, or a stop-code screen…
Windows & BSOD0x80070422
The Windows Defender service cannot start, leaving the system vulnerable. It's also often linked to third-party antivirus interference.
Windows & BSODKERNEL_SECURITY_CHECK_FAILURE
Windows stopped because the kernel found that one of its critical internal data structures had been corrupted. Windows checks these structures on purpose and stops rather than continue with damaged data.
Windows & BSOD0xC0000428
Error code 0xC0000428 indicates that Windows Boot Manager could not verify the digital signature of a recently installed driver or system file. This prevents Windows from starting up properly.
Windows & BSODREGISTRY_ERROR
The REGISTRY_ERROR bug check has a value of 0x00000051. This BSOD indicates that an I/O error occurred while the registry was trying to read one of its files, or that the registry has become corrupted due to hardware…
Windows & BSOD0x8024200B
A common Windows Update error code indicating that a driver or system file update could not be applied because the active device driver in the system is locked, corrupted, or has a signature mismatch. Use the steps…
Windows & BSODFAULTY_HARDWARE_CORRUPTED_PAGE
Windows stopped because its memory manager found memory corruption caused by hardware or a driver writing to memory directly. Microsoft says such corruption can only come from access by physical address, not through…
Windows & BSODKERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
This BSOD occurs when a driver attempts to acquire a kernel auto-boost lock while operating at an elevated IRQL (Interrupt Request Level). This violates Windows kernel locking rules.
Windows & BSOD0xC000021A
Windows stops with code 0xC000021A, often during startup or right after an update. Microsoft names this bug check WINLOGON_FATAL_ERROR: a user-mode subsystem that Windows cannot run without, such as Winlogon or the…
Windows & BSODBOOTMGR-MISSING
Instead of starting Windows, the PC shows a black screen saying that BOOTMGR is missing and asking you to press Ctrl+Alt+Del to restart. BOOTMGR is the Windows Boot Manager on PCs that start in legacy BIOS mode.
Windows & BSODWINDOWS-ACTIVATION-ERROR-0x803F7001
Windows cannot activate online and displays error 0x803F7001 (HRESULT: No valid Windows license found). This commonly occurs after significant hardware changes (motherboard replacement), when a digital license is not…
Windows & BSOD0x000000F4
A critical system process or thread was terminated unexpectedly, causing the system to halt. This can also stem from SATA/NVMe controller connection issue.
Windows & BSOD0xc0000034
Windows does not start and shows a blue Recovery screen with error code 0xc0000034. Microsoft's name for this code is STATUS_OBJECT_NAME_NOT_FOUND: the Windows Boot Manager looked for something it needs and could not…
Windows & BSODEvent ID 7034
A registered Windows system service terminated unexpectedly. It's also often linked to software conflicts or crashed processes.
Windows & BSODBSOD on install
A blue screen of death (BSOD) crash occurs during the Windows installation process, preventing the setup from completing. It's most often caused by defective or unstable RAM modules and incorrect storage controller…
Windows & BSOD0x00000119
The video scheduler has detected a fatal violation in the display driver. Caused by graphics driver corruption, memory leaks or faulty GPU hardware.
Windows & BSOD0x00000154
The store component has thrown an unexpected exception. Caused by hard drive failure, SSD controller timeout, or corrupted system files.
Windows & BSOD0x000001D5
The Plug and Play (PnP) manager failed to initialize a driver within the timeout limit. Caused by incompatible hardware drivers, corrupt system files, or BIOS settings.
Windows & BSOD0x80070057
0x80070057 means that a Windows component received a value it could not use. Microsoft's name for it is ERROR_INVALID_PARAMETER, "The parameter is incorrect" (programs also call it E_INVALIDARG).
Windows & BSOD0x80070003
The system cannot find the path specified. This error is most commonly encountered during failed Windows Update updates, store app installations, or profile migrations due to missing directory links.
Windows & BSOD0x80070017
A Cyclic Redundancy Check (CRC) error indicates that the operating system was unable to read data from a storage sector or installation media. Most commonly encountered during Windows installation, updates, or file…
Windows & BSOD0x000000C1
A special pool driver check detected that a kernel driver wrote to memory outside its allocated block. This is a critical RAM integrity BSOD.
Windows & BSOD0x80242006
The update handler failed to complete the installation process due to database corruption or service blocks. Commonly encountered during cumulative updates or security definition updates.
Windows & BSOD0x00000100
A Loader Block Mismatch occurs when the boot loader (Winload.efi) passes a system parameters block to the Windows kernel that is incompatible or corrupted. Commonly caused by corrupted boot records, memory faults, or…
Windows & BSOD0x80070091
The directory is not empty. Commonly occurs during failed System Restore operations or when attempting to delete Windows.old or app folders.
Windows & BSOD0x80004005
This is a generic Windows error code representing access denied, missing permissions, or registry blocks. Most commonly occurs during Windows update, networking/sharing folder setup, or virtual machine launching.
Windows & BSOD0x00000078
An unhandled exception occurred during the early boot phase (Phase 0 initialization). Commonly caused by unstable hardware overclocking, outdated CPU microcode, or incompatible RAM memory blocks.
Windows & BSOD0x80073CF9
The app package installation failed due to missing package directories or corrupted store database records. Commonly occurs when updating or installing games/applications from the Microsoft Store.
Windows & BSOD0x0000003D
A hardware interrupt was generated, but the kernel interrupt handler threw an unhandled exception. Commonly caused by driver memory violations, faulty motherboard chipset wiring, or BIOS settings.
Windows & BSOD0x800F0900
The CBS manifest file parsing failed due to corruption in the servicing stack directory. Commonly encountered during cumulative updates, Windows features activation, or DISM restore health execution.
Windows & BSOD0x8007000E
The system has run out of memory (RAM/virtual memory) required to process update downloads, allocate handles, or parse packages. Most commonly occurs during cumulative updates on systems with low physical RAM,…
Windows & BSOD0x800B0109
A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. Commonly occurs during Windows Update downloads, driver installation, or app installation when registry…
Windows & BSOD0x80073D05
The application installation failed because the previously deleted application's data directory was not fully cleared or is locked. Commonly encountered when trying to reinstall Microsoft Store apps like Xbox,…
Windows & BSOD0x8024401F
The Windows Update client received an HTTP status 500 (Internal Server Error) response from the update server or local WSUS gateway. Commonly occurs due to server-side congestion, proxy server misconfigurations, or…
Windows & BSOD0x80070070
A Windows update fails with 0x80070070, ERROR_DISK_FULL: there is not enough space on the disk. Microsoft says quality updates typically need 2–3 GB or more of free space and feature updates 6–11 GB or more, and a…
Windows & BSOD0xC0000006
An in-page read error occurred, meaning the system tried to load a file from memory but failed due to read/write hardware timeouts. Commonly occurs when launching games/apps from external drives or network shares.