HTML Sitemap
Complete navigation index of ErrorsFixer. Search for diagnostic guides, troubleshooting manuals, and specific hardware/software error code databases.
Main Pages & Diagnostic Guides
Homepage/index.htmlMain database search engine, filters, categories and statistics.PC Build Guide/guides/pc-build-guide/Detailed step-by-step diagnostic guide for building and checking your custom PC.CPU Overheating Guide/guides/cpu-overheating/Learn how to identify, monitor and resolve processor thermal throttling and high temperatures.DirectX Errors Manual/guides/directx-errors/Fix common gaming issues like DXGI_ERROR_DEVICE_REMOVED or D3D compile errors.BSOD Codes Reference/guides/bsod-codes/Resolving Windows Blue Screen of Death stop codes and driver conflicts.GPU Crash Troubleshooting/guides/gpu-crash-gaming/Resolve graphics card black screens, TDR crashes, and DDU driver reinstalls.BIOS/UEFI Startup Errors/guides/bios-startup-errors/Fix POST failure codes, secure boot violation, and CMOS battery leakage.PC Diagnostics Tools/guides/pc-diagnostics-tools/Our recommended software suite for monitoring and benchmarking computer hardware.Windows Error Codes/guides/windows-error-codes/A deep dive into system processes, Event Viewer logs, and Windows Update failures.RAM Troubleshooting/guides/ram-troubleshooting/Fix memory crashes, test for hardware failure with MemTest86, and configure motherboard XMP/EXPO overclocking profiles.SSD & HDD Diagnostics/guides/ssd-hdd-diagnostics/Check storage drive health using S.M.A.R.T., run filesystem repairs with chkdsk, and resolve boot device errors.Windows Update Fix/guides/windows-update-fix/Troubleshoot Windows Update loops, reset the local update services database, and resolve WinRE partition sizing issues.PSU Troubleshooting/guides/psu-troubleshooting/Diagnose hardware shutdowns under gaming/3D load, run the PSU paperclip test, and check motherboard voltage rails.
Hardware Error Database
BIOS / UEFIAGESA-BOOT-FAILURE/error/AGESA-BOOT-FAILURE/This critical-severity issue affects the hardware BIOS/UEFI. 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 initialization failed before the BIOS environment was fully established. This causes no-POST situations with debug LED codes. It's also often linked to incompatible RAM speed or timing. The steps below are ordered to resolve this efficiently.BIOS_ROM_CORRUPTED/error/BIOS-ROM-CORRUPTED/BIOS_ROM_CORRUPTED is a critical-severity hardware BIOS/UEFI problem. The motherboard BIOS firmware ROM checksum verification failed. The system cannot POST and cycles with fans at maximum speed or reports error beeps. This usually traces back to static discharge and failing flash EEPROM chip. The steps below are ordered to resolve this efficiently.BIOS-ROM-ERR/error/BIOS-ROM-ERR/BIOS ROM checksum error ranks as a critical-severity hardware BIOS/UEFI issue in our database. The BIOS ROM memory is corrupted or unreadable. It sometimes comes down to defective EEPROM chip. Work through the steps below in order.BIOS-UEFI-BOOT-ORDER/error/BIOS-UEFI-BOOT-ORDER/This low-severity issue affects the hardware BIOS/UEFI. 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. Use the steps below to track down and fix the cause.BIOS-UPDATE-FAIL/error/BIOS-UPDATE-FAIL/This critical-severity issue affects the hardware BIOS/UEFI. Firmware update failed. The board does not need to boot. Reports of BIOS update failure usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. Another common trigger is aborting process. See the troubleshooting steps below for the fix.Boot Device Not Found/error/BOOT-DEVICE-NOT-FOUND/Boot Device Not Found shows up as a critical-severity hardware BIOS/UEFI fault. The BIOS/UEFI firmware cannot locate a bootable operating system partition or storage drive. Reports of Boot Device Not Found usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. The steps below are ordered to resolve this efficiently.CMOS-CHECKSUM-ERROR/error/CMOS-CHECKSUM-ERROR/CMOS-CHECKSUM-ERROR is a medium-severity hardware BIOS/UEFI problem. BIOS detected invalid data in CMOS. Settings have been lost. It sometimes comes down to power failure. Work through the steps below in order.CPU Vcore Out of Range/error/CPU-VCORE-OUT-OF-RANGE/CPU Vcore Out of Range is a high-severity hardware BIOS/UEFI issue. 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). Follow the steps below to fix it.DRAM Light (Q-LED)/error/DRAM-LIGHT/DRAM Light (Q-LED) is a critical-severity hardware BIOS/UEFI problem. The motherboard POST diagnostic LED indicates a memory initialization error, preventing the system from booting. See the troubleshooting steps below for the fix.ME-FIRMWARE-CORRUPTION/error/ME-FIRMWARE-CORRUPTION/Intel Management Engine (ME) corruption (ME-FIRMWARE-CORRUPTION) is a high-severity fault affecting the hardware BIOS/UEFI. 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 version and hardware failure of ME chip on board. See the troubleshooting steps below for the fix.Overclocking Failed/error/OVERCLOCKING-FAILED/This medium-severity issue affects the hardware BIOS/UEFI. 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 unresponsiveness, or a stop-code screen appearing out of nowhere. Typical causes include excessive memory or processor frequency and incompatible memory timings. The steps below are ordered to resolve this efficiently.POST-CODE-5D/error/POST-CODE-5D/POST Code 5d - Unsupported Processor is a critical-severity hardware BIOS/UEFI issue. 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 BIOS. It sometimes comes down to faulty CPU memory controller channel. Use the steps below to track down and fix the cause.POST-CODE-15/error/POST-CODE-15/POST-CODE-15 shows up as a high-severity hardware BIOS/UEFI fault. 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. This can also stem from incompatible RAM specifications or speed profiles. The steps below are ordered to resolve this efficiently.POST-FAILURE/error/POST-FAILURE/POST failure ranks as a critical-severity hardware BIOS/UEFI issue in our database. Power-On Self Test failed. The PC will not pass the check and will not boot. This usually traces back to defective RAM, defective CPU, disconnected GPU and faulty PSU. Work through the steps below in order.ROM-SPACE-EXHAUSTED/error/ROM-SPACE-EXHAUSTED/ROM-SPACE-EXHAUSTED shows up as a medium-severity hardware BIOS/UEFI fault. 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. Follow the steps below to fix it.SECURE_BOOT_RED_SCREEN/error/SECURE-BOOT-RED-SCREEN/This high-severity issue affects the hardware BIOS/UEFI. The motherboard BIOS displays a red warning screen stating 'Secure Boot Violation: Invalid signature detected' on boot, blocking startup. It sometimes comes down to unsigned operating system bootloader. See the troubleshooting steps below for the fix.SECURE-BOOT-VIOLATION/error/SECURE-BOOT-VIOLATION/Violation of Secure Boot is a high-severity hardware BIOS/UEFI issue. Secure Boot blocked unsigned boot code from running. This usually traces back to old bootloader and corrupted EFI. Use the steps below to track down and fix the cause.TPM-NOT-FOUND/error/TPM-NOT-FOUND/TPM-NOT-FOUND is a medium-severity hardware BIOS/UEFI problem. 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. See the troubleshooting steps below for the fix.UEFI-SECURE-BOOT-DB-EXPIRED/error/UEFI-SECURE-BOOT-DB-EXPIRED/UEFI-SECURE-BOOT-DB-EXPIRED is a high-severity hardware BIOS/UEFI problem. 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). After a BIOS or Windows update applies the revocation, previously trusted bootloaders or recovery media become untrusted, preventing boot. See the troubleshooting steps below for the fix.
CPU / Processor0x0000009C/error/0x0000009C/0x0000009C shows up as a critical-severity processor (CPU) fault. A Machine Check Exception (MCE) is a hardware error detected by the CPU itself, indicating a fatal hardware failure. Commonly caused by hardware overheating, unstable overclocking multipliers, incorrect CPU core voltages, or failing motherboard power regulators. Follow the steps below to fix it.0x00000124/error/0x00000124/0x00000124 shows up as a critical-severity processor (CPU) fault. The Windows Hardware Error Architecture (WHEA) has detected an uncorrectable hardware exception. Most commonly caused by CPU core voltage instability, overheating cores, unstable memory profiles (XMP/EXPO), or physical damage to the processor socket. See the troubleshooting steps below for the fix.AMD-FCLK-INFINITY-ERR/error/AMD-FCLK-INFINITY-ERR/AMD-FCLK-INFINITY-ERR is a high-severity processor (CPU) problem. 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. Work through the steps below in order.AMD-PSP-ERROR/error/AMD-PSP-ERROR/AMD Platform Security Processor (PSP) error is a high-severity processor (CPU) issue. 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. PSP handles secure boot validation, fTPM operations, and AMD Memory Guard encryption. Errors here block system initialization. This can also stem from incompatible AGESA version. The steps below are ordered to resolve this efficiently.AVX-PANIC/error/AVX-PANIC/Crash when executing AVX instructions is a high-severity processor (CPU) issue. Calculation error when using AVX/AVX2 wide vector instructions. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Use the steps below to track down and fix the cause.BCLK-JITTER/error/BCLK-JITTER/This high-severity issue affects the processor (CPU). 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. The usual suspects are dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Use the steps below to track down and fix the cause.BRANCH-PRED-ER/error/BRANCH-PRED-ER/Branch prediction error ranks as a high-severity processor (CPU) issue in our database. 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. Use the steps below to track down and fix the cause.C-STATE-HUNG/error/C-STATE-HUNG/Stuck on hibernation is a high-severity processor (CPU) issue. The processor failed to properly wake up from sleep. Common triggers are dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Use the steps below to track down and fix the cause.CLOCK_WATCHDOG_TIMEOUT/error/CLOCK-WATCHDOG-TIMEOUT/CLOCK_WATCHDOG_TIMEOUT (0x00000101) is a critical-severity Windows operating system issue. The processor waited too long for a response from another processor or core and caused a BSOD. Common triggers are unstable CPU or RAM overclocking (XMP) and incorrect setting of C-states in BIOS. Use the steps below to track down and fix the cause.CLOCK_WATCHDOG_TIMEOUT/error/CLOCK-WATCHDOG-TIMEOUT-2/CLOCK_WATCHDOG_TIMEOUT is a critical-severity processor (CPU) problem. The CPU core stopped responding to an interrupt request. Caused by overclocking or faulty driver. This can also stem from overheating cores. Use the steps below to track down and fix the cause.CORE_PAGING_MULTIPLE_IRP_COMPLETE_REQUESTS/error/CORE-PAGING-MULTIPLE-IRP-COMPLETE-REQUESTS/Core paging multiple IRP complete requests is a critical-severity processor (CPU) issue. 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 memory controller or a defective driver causing double-free conditions in kernel paging buffers. This can also stem from faulty RAM interacting with CPU. Work through the steps below in order.CPPC-NOT-SUPPORTED/error/CPPC-NOT-SUPPORTED/This low-severity issue affects the processor (CPU). Collaborative Processor Performance Control is not active. Reduces the effectiveness of CPU boost. Typical causes include old BIOS and CPPC disabled in BIOS. See the troubleshooting steps below for the fix.CPU-PACKAGE-TEMP-LIMIT/error/CPU-PACKAGE-TEMP-LIMIT/CPU Package temperature limit reached ranks as a high-severity processor (CPU) issue in our database. 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 permanent silicon degradation. This is different from throttling — the system halts completely. Common triggers are insufficient CPU cooler TDP rating and blocked airflow in case. The steps below are ordered to resolve this efficiently.CPU-PSTATE-ERR/error/CPU-PSTATE-ERR/This medium-severity issue affects the processor (CPU). Processor failed to transition to a requested performance state. This usually traces back to BIOS bug and faulty power management driver. Use the steps below to track down and fix the cause.CPU-THERMAL-THROTTLE/error/CPU-THERMAL-THROTTLE/This high-severity issue affects the processor (CPU). 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 system slowdowns or shutdown warnings. It's most often caused by dusty radiator and poor cooling. Use the steps below to track down and fix the cause.CPU-VCORE-LOW/error/CPU-VCORE-LOW/Low CPU supply voltage is a high-severity processor (CPU) issue. Powering the processor below the minimum causes instability and crashes. Common triggers are weak resource, damaged VRM and bad EPS connector. See the troubleshooting steps below for the fix.FPU-MATH-ERR/error/FPU-MATH-ERR/FPU-MATH-ERR is a high-severity processor (CPU) problem. 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. The usual suspects are dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Use the steps below to track down and fix the cause.IMC-FAULT-00/error/IMC-FAULT-00/This high-severity issue affects the processor (CPU). 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 appearing out of nowhere. It's most often caused by dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Use the steps below to track down and fix the cause.INTEL_13_14_DEGRADATION/error/INTEL-13-14-DEGRADATION/Intel 13th & 14th Gen Raptor Lake Instability ranks as a critical-severity processor (CPU) issue in our database. 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 errors in games, and system crashes. This usually traces back to elevated operating temperatures and aggressive motherboard power limits (PL1/PL2 profile limits). See the troubleshooting steps below for the fix.INTEL_TDP_THROTTLING/error/INTEL-TDP-THROTTLING/This high-severity issue affects the processor (CPU). 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 insufficient CPU cooling or air flow and low motherboard VRM quality or overheating VRMs. Work through the steps below in order.INTEL-MICROCODE-UPDATE-FAIL/error/INTEL-MICROCODE-UPDATE-FAIL/INTEL-MICROCODE-UPDATE-FAIL is a medium-severity processor (CPU) problem. 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, Downfall), and stability bugs. A failed microcode load leaves the processor operating with known silicon bugs active. It sometimes comes down to CPU generation mismatch. The steps below are ordered to resolve this efficiently.L1-CACHE-ERROR/error/L1-CACHE-ERROR/CPU Memory L1 Cache Error (L1-CACHE-ERROR) is a critical-severity fault affecting the processor (CPU). The processor's internal L1 cache reported an unrecoverable data error. Extreme system instability. This usually traces back to too aggressive overclocking and overvoltage and manufacturing defect. See the troubleshooting steps below for the fix.L2-CACHE-EXC/error/L2-CACHE-EXC/Exception while reading from L2/L3 cache ranks as a high-severity processor (CPU) issue in our database. The processor encountered corrupted data in its own cache. Common triggers are dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Follow the steps below to fix it.MACHINE_CHECK_EXCEPTION/error/MACHINE-CHECK-EXCEPTION/MCE - Machine Check Exception (MACHINE_CHECK_EXCEPTION) is a critical-severity fault affecting the processor (CPU). The CPU has detected a fatal hardware error. It could be a faulty processor or motherboard. It's most often caused by defective CPU, unstable power supply and l3 cache failure. See the troubleshooting steps below for the fix.POWER-LIMIT-THROTTLE/error/POWER-LIMIT-THROTTLE/Limiting CPU performance with a performance limit of ranks as a medium-severity processor (CPU) issue in our database. 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, or a stop-code screen appearing out of nowhere. It's also often linked to intel XTU settings. Follow the steps below to fix it.PROCHOT-1/error/PROCHOT-1/Thermal throttling of CPU performance is a high-severity processor (CPU) issue. The processor slows down to avoid overheating and damage. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Follow the steps below to fix it.PROCHOT-SIGNAL/error/PROCHOT-SIGNAL/Activation of PROCHOT signal (PROCHOT-SIGNAL) is a high-severity fault affecting the processor (CPU). 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 / sensor. Use the steps below to track down and fix the cause.RING-BUS-FAIL/error/RING-BUS-FAIL/Loss of internal bus synchronization ranks as a high-severity processor (CPU) issue in our database. 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. Use the steps below to track down and fix the cause.SMT-SYNC-FAIL/error/SMT-SYNC-FAIL/SMT-SYNC-FAIL shows up as a high-severity processor (CPU) fault. The logical cores have lost synchronization with each other. Typical causes include dried thermal paste, overclocking too aggressively, silicon degradation and weak power supply. Use the steps below to track down and fix the cause.SOCKET-PIN-FLT/error/SOCKET-PIN-FLT/Bad contact in processor socket is a high-severity processor (CPU) issue. 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. Use the steps below to track down and fix the cause.TDP-LIMIT-MAX/error/TDP-LIMIT-MAX/TDP-LIMIT-MAX is a high-severity processor (CPU) problem. The processor draws more power than the BIOS allows. The usual suspects are dried thermal paste, overclocking too aggressively and silicon degradation. Follow the steps below to fix it.Thermal Shutdown/error/THERMAL-SHUTDOWN/PC shuts off without warning at load ranks as a critical-severity processor (CPU) issue in our database. 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 damage. The usual suspects are dried-out or incorrectly applied thermal paste, failing or disconnected CPU cooler fan or pump and dust accumulation clogging the heatsink fins. The steps below are ordered to resolve this efficiently.UCODE-0x1A/error/UCODE-0x1A/This high-severity issue affects the processor (CPU). 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. See the troubleshooting steps below for the fix.VCORE-DROP/error/VCORE-DROP/This high-severity issue affects the processor (CPU). 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. The steps below are ordered to resolve this efficiently.VRM-TEMP-CRIT/error/VRM-TEMP-CRIT/Power cascade overheating (VRM) (VRM-TEMP-CRIT) is a high-severity fault affecting the processor (CPU). 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. See the troubleshooting steps below for the fix.WHEA_BOOT_LOOP/error/WHEA-BOOT-LOOP/WHEA_BOOT_LOOP shows up as a critical-severity processor (CPU) fault. A critical CPU power delivery or microcode stability failure that prevents the operating system from completing its boot sequence, triggering a repetitive Blue Screen (BSOD) before reaching the desktop. The usual suspects are faulty CPU core, incompatible BIOS version and unstable CPU core voltage offset. The steps below are ordered to resolve this efficiently.WHEA_UNCORRECTABLE_ERROR/error/WHEA-UNCORRECTABLE-ERROR/WHEA_UNCORRECTABLE_ERROR is a critical-severity processor (CPU) problem. Critical CPU or chipset hardware error (BSOD 0x124). Caused by voltage instability, overheating or overclocking. This can also stem from defective RAM. Follow the steps below to fix it.
Graphics Card / GPU
VIDEO_TDR_FAILURE/error/VIDEO-TDR-FAILURE/VIDEO_TDR_FAILURE shows up as a critical-severity graphics card (GPU) fault. GPU stopped responding, Windows reset it. Crash caused by driver or hardware failure. The screen goes black and the system restarts the driver. It's most often caused by outdated GPU Drivers, overheating, overclocking and defective card. See the troubleshooting steps below for the fix.nvlddmkm.sys/error/nvlddmkm.sys/nvlddmkm.sys shows up as a high-severity graphics card (GPU) fault. NVIDIA kernel driver crash. The screen goes black, the system tries to restart the driver. One of the most common NVIDIA BSOD codes. This usually traces back to memory overclocking, VRAM overheating and insufficient PCIe power. Follow the steps below to fix it.CODE-43-GPU/error/CODE-43-GPU/Code 43 - GPU Stopped Windows ranks as a high-severity graphics card (GPU) issue in our database. Windows stopped the GPU in Device Manager. The driver reported an unrecoverable error to the kernel. The most common GPU error after driver issues. Common triggers are insufficient power supply and overheating. See the troubleshooting steps below for the fix.DXGI_ERROR_DEVICE_HUNG/error/DXGI-ERROR-DEVICE-HUNG/DXGI - GPU stopped responding ranks as a high-severity graphics card (GPU) issue in our database. DirectX has detected that the GPU has stopped processing commands. Game or app crashes. This usually traces back to GPU overclocking, defective driver and GPU overheating. The steps below are ordered to resolve this efficiently.GPU-FAN-FAILURE/error/GPU-FAN-FAILURE/GPU-FAN-FAILURE shows up as a critical-severity graphics card (GPU) fault. The GPU fan stopped spinning. Causes rapid overheating and emergency shutdown. Typical causes include mechanical fault, dust in bearing and damaged connector. Follow the steps below to fix it.atikmpag.sys/error/atikmpag.sys/atikmpag.sys is a critical-severity graphics card (GPU) problem. AMD GPU kernel driver crash. NVIDIA nvlddmkm.sys equivalent for AMD Radeon cards. Typical causes include GPU overclocking and overheating. Use the steps below to track down and fix the cause.GPU-BLACK-SCREEN/error/GPU-BLACK-SCREEN/Black screen with no signal (GPU-BLACK-SCREEN) is a high-severity fault affecting the graphics card (GPU). The monitor shows a black screen with no signal, although the PC appears to be running. Typical causes include defective HDMI/DP cable, GPU overheating, driver failure and insufficient PCIe power. See the troubleshooting steps below for the fix.VRAM-CORRUPTION/error/VRAM-CORRUPTION/VRAM corruption is a critical-severity graphics card (GPU) issue. The GPU video memory contains bad data. It causes artifacts, app crashes or BSODs. Common triggers are VRAM overclocking, faulty GPU and defective driver. See the troubleshooting steps below for the fix.GPU-ARTIFACTING/error/GPU-ARTIFACTING/This high-severity issue affects the graphics card (GPU). Random colored dots, stripes or triangles appear on the screen. Caused by VRAM error or overheating. Typical causes include GPU memory overclocking, faulty GPU and insufficient power supply. See the troubleshooting steps below for the fix.PCI-E-BANDWIDTH-ISSUE/error/PCI-E-BANDWIDTH-ISSUE/This medium-severity issue affects the graphics card (GPU). 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 settings in BIOS. See the troubleshooting steps below for the fix.VRAM-ART-01/error/VRAM-ART-01/Video Memory Artifacts (Checkerboard) ranks as a high-severity graphics card (GPU) issue in our database. 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. See the troubleshooting steps below for the fix.PCIE-TDR-116/error/PCIE-TDR-116/PCIe bus timer timeout ranks as a high-severity graphics card (GPU) issue in our database. The graphics card did not respond to the motherboard within the timeout. Reports of PCIe bus timer timeout usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. Typical causes include high temperatures, wear of memory chips, faulty driver and poor quality video cable. Work through the steps below in order.CORE-CLK-CRASH/error/CORE-CLK-CRASH/CORE-CLK-CRASH shows up as a high-severity graphics card (GPU) fault. 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. Follow the steps below to fix it.PWR-LIM-THROT/error/PWR-LIM-THROT/GPU power limit hit hard (PWR-LIM-THROT) is a high-severity fault affecting the graphics card (GPU). 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. Work through the steps below in order.FAN-CRV-FAIL/error/FAN-CRV-FAIL/This high-severity issue affects the graphics card (GPU). 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. This usually traces back to high temperatures, wear of memory chips, faulty driver and poor quality video cable. Use the steps below to track down and fix the cause.DISP-SYNC-LOSS/error/DISP-SYNC-LOSS/DISP-SYNC-LOSS is a high-severity graphics card (GPU) problem. 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. Work through the steps below in order.DEV-REMOVED/error/DEV-REMOVED/DEV-REMOVED shows up as a high-severity graphics card (GPU) fault. The game will report that the graphics card has been disconnected from the system while running. The usual suspects are high temperatures, wear of memory chips, faulty driver and poor quality video cable. See the troubleshooting steps below for the fix.GSYNC-FLICKER/error/GSYNC-FLICKER/Image flickering (G-Sync/FreeSync) is a high-severity graphics card (GPU) issue. 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. Follow the steps below to fix it.SHD-COMP-ERR/error/SHD-COMP-ERR/SHD-COMP-ERR shows up as a high-severity graphics card (GPU) fault. 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. See the troubleshooting steps below for the fix.SLI-DESYNC/error/SLI-DESYNC/Desynchronization of linking multiple graphics ranks as a high-severity graphics card (GPU) issue in our database. 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. The steps below are ordered to resolve this efficiently.HOTSPOT-110C/error/HOTSPOT-110C/This high-severity issue affects the graphics card (GPU). 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. See the troubleshooting steps below for the fix.NVLDDMKM-TMOUT/error/NVLDDMKM-TMOUT/View controller timeout and refresh ranks as a high-severity graphics card (GPU) issue in our database. 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. Use the steps below to track down and fix the cause.COIL-WHINE-MAX/error/COIL-WHINE-MAX/COIL-WHINE-MAX shows up as a high-severity graphics card (GPU) fault. 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. The steps below are ordered to resolve this efficiently.VBIOS-CORRUPT/error/VBIOS-CORRUPT/Corrupted graphics card firmware (VBIOS) ranks as a high-severity graphics card (GPU) issue in our database. 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. Common triggers are high temperatures, wear of memory chips, faulty driver and poor quality video cable. Work through the steps below in order.ZERO-RPM-FAIL/error/ZERO-RPM-FAIL/ZERO-RPM-FAIL is a high-severity graphics card (GPU) problem. 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. The steps below are ordered to resolve this efficiently.HDMI-NO-SIGNAL/error/HDMI-NO-SIGNAL/Monitor reports No Signal via HDMI is a medium-severity graphics card (GPU) issue. 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. Use the steps below to track down and fix the cause.DISPLAYPORT-NO-SYNC/error/DISPLAYPORT-NO-SYNC/This medium-severity issue affects the graphics card (GPU). 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). The steps below are ordered to resolve this efficiently.RESIZABLE-BAR-ERROR/error/RESIZABLE-BAR-ERROR/This low-severity issue affects the graphics card (GPU). 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 configuration of Above 4G Decoding in BIOS. See the troubleshooting steps below for the fix.GPU-FAN-STOP/error/GPU-FAN-STOP/This critical-severity issue affects the graphics card (GPU). The graphics card fan controller has failed, fans are not spinning. This usually traces back to hardware defect and driver crash. See the troubleshooting steps below for the fix.GPU-PCIE-BANDWIDTH-ERROR/error/GPU-PCIE-BANDWIDTH-ERROR/GPU-PCIE-BANDWIDTH-ERROR is a medium-severity graphics card (GPU) problem. 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. Detected in GPU monitoring tools as 'PCIe x4 @ Gen3' when the card requires x16 @ Gen4 for full performance. The steps below are ordered to resolve this efficiently.NVIDIA-NVLDDMKM-CRITICAL/error/NVIDIA-NVLDDMKM-CRITICAL/NVIDIA-NVLDDMKM-CRITICAL is a critical-severity graphics card (GPU) problem. 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. This commonly occurs with corrupt driver installations, hardware memory errors in VRAM, or PCIe power delivery issues. Follow the steps below to fix it.AMD-DISPLAY-DRIVER-CRASH/error/AMD-DISPLAY-DRIVER-CRASH/AMD display driver crash (amdkmdag.sys) (AMD-DISPLAY-DRIVER-CRASH) is a high-severity fault affecting the graphics card (GPU). The AMD kernel-mode display driver (amdkmdag.sys) has crashed. This driver handles all communication between DirectX, Windows Display Driver Model (WDDM), and AMD Radeon hardware. Crashes manifest as black screen recovery events, blue screens with 'VIDEO_TDR_FAILURE' pointing to amdkmdag.sys, or complete display output loss. This usually traces back to overclocked GPU memory and corrupted shader cache. Use the steps below to track down and fix the cause.TDR Event/error/TDR-EVENT/Display driver stopped responding and recovered is a high-severity graphics card (GPU) issue. Timeout Detection and Recovery (TDR) was triggered because the GPU did not respond within the allocated time, forcing Windows to reset the display driver. Typical causes include unstable GPU core or memory overclock and GPU overheating under load. Work through the steps below in order.VIDEO_DXGKRNL_FATAL_ERROR/error/VIDEO-DXGKRNL-FATAL-ERROR/DirectX kernel fatal error (0x00000113) ranks as a critical-severity graphics card (GPU) issue in our database. 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. Work through the steps below in order.No Display/error/NO-DISPLAY/This high-severity issue affects the graphics card (GPU). Upon pressing the power button, the computer fans spin and LEDs light up, but no video output is sent to the monitor. This can also stem from RAM module not fully seated or dirty contacts. Use the steps below to track down and fix the cause.RAM / Memory0x0000002E/error/0x0000002E/0x0000002E shows up as a critical-severity system memory (RAM) fault. 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 failing processor cache. It's also often linked to oxidized RAM gold finger connector pins. Use the steps below to track down and fix the cause.1T-CMD-FAIL/error/1T-CMD-FAIL/This critical-severity issue affects the system memory (RAM). 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. Use the steps below to track down and fix the cause.BAD_POOL_HEADER/error/BAD-POOL-HEADER/BAD_POOL_HEADER is a critical-severity system memory (RAM) problem. Pool manager detected corrupted data in memory. It could be the RAM or the driver. This usually traces back to defective RAM and malware. Use the steps below to track down and fix the cause.BNK-INT-ERR/error/BNK-INT-ERR/BNK-INT-ERR shows up as a critical-severity system memory (RAM) fault. 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. Follow the steps below to fix it.DCH-ASYNC/error/DCH-ASYNC/Asymmetry of two-channel memory connection ranks as a critical-severity system memory (RAM) issue in our database. 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. The steps below are ordered to resolve this efficiently.DDR5-PMIC-TMP/error/DDR5-PMIC-TMP/This critical-severity issue affects the system memory (RAM). 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. The steps below are ordered to resolve this efficiently.DOUBLE_FAULT/error/DOUBLE-FAULT/DOUBLE_FAULT shows up as a critical-severity system memory (RAM) 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 typically caused by severe memory corruption, a corrupted stack, or a defective memory module that corrupted critical kernel data structures. The steps below are ordered to resolve this efficiently.DRAM_POST_TIMEOUT/error/DRAM-POST-TIMEOUT/DRAM Training Timeout / POST Loop ranks as a high-severity system memory (RAM) issue in our database. 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 troubleshooting steps below for the fix.ECC-LIM-EXC/error/ECC-LIM-EXC/ECC error limit exceeded (ECC-LIM-EXC) is a critical-severity fault affecting the system memory (RAM). 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. Work through the steps below in order.ECC-MEMORY-ERROR/error/ECC-MEMORY-ERROR/ECC-MEMORY-ERROR shows up as a high-severity system memory (RAM) fault. 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. Even correctable errors indicate the RAM module is degrading and should be monitored closely. ECC is common in workstations, servers, and AMD Ryzen Pro/Threadripper systems. It's most often caused by physical RAM degradation (aging), cosmic ray bit flip (transient) and overheating causing bit instability. Use the steps below to track down and fix the cause.GEAR-MD-FAIL/error/GEAR-MD-FAIL/Loss of controller divider sync (GEAR-MD-FAIL) is a critical-severity fault affecting the system memory (RAM). The motherboard cannot run stably in split controller frequency mode. It sometimes comes down to dust in slot. Use the steps below to track down and fix the cause.IMP-CAL-FAIL/error/IMP-CAL-FAIL/Memory calibration failure on PC startup ranks as a critical-severity system memory (RAM) issue in our database. 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. Follow the steps below to fix it.MCE-MEM-READ-ERR/error/MCE-MEM-READ-ERR/This critical-severity issue affects the system memory (RAM). 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. See the troubleshooting steps below for the fix.MEMORY_MANAGEMENT/error/MEMORY-MANAGEMENT/Memory Management - BSOD is a critical-severity system memory (RAM) issue. Windows has detected a critical RAM problem. Most often a faulty memory module. Typical causes include defective RAM, bad DIMM slots and bad XMP profiles. Work through the steps below in order.MemTest Error/error/MEMTEST-ERROR/This critical-severity issue affects the system memory (RAM). A diagnostic scan with MemTest86 or a similar tool has detected defective memory cells that cannot reliably hold data. Reports of RAM cell failure detected – module defective usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. This can also stem from overheating RAM modules or slot connection issues. The steps below are ordered to resolve this efficiently.MEMTEST-ERR-8/error/MEMTEST-ERR-8/MEMTEST-ERR-8 shows up as a critical-severity system memory (RAM) fault. Memory diagnostics detected a hardware defect in the memory cell. Common triggers are different modules in one board, poor quality CPU controller, frequency too high and dust in slot. Use the steps below to track down and fix the cause.PAGE-FAULT-BOOT/error/PAGE-FAULT-BOOT/PAGE-FAULT-BOOT shows up as a critical-severity system memory (RAM) fault. BIOS/UEFI detected a fatal page fault during operating system startup. Windows won't load. The usual suspects are dead or severely damaged RAM module, high interference on the motherboard and unsupported RAM speed or timing. Work through the steps below in order.PIN-OXIDATION/error/PIN-OXIDATION/Oxidation of the gold contacts of the memory module (PIN-OXIDATION) is a critical-severity fault affecting the system memory (RAM). 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. Follow the steps below to fix it.RAM_MEMORY_LEAK_SYSTEM/error/RAM-MEMORY-LEAK-SYSTEM/RAM_MEMORY_LEAK_SYSTEM is a high-severity system memory (RAM) problem. 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 third-party network driver (e.g. Killer Network Control), leak in virtualization helper driver and outdated hardware monitoring software. The steps below are ordered to resolve this efficiently.RAM-DUAL-CHANNEL-FAIL/error/RAM-DUAL-CHANNEL-FAIL/RAM dual channel mode failure (RAM-DUAL-CHANNEL-FAIL) is a medium-severity fault affecting the system memory (RAM). 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. Operating in single-channel can reduce performance by 15-30% in memory-intensive tasks and can cause instability in some configurations. Typical causes include RAM modules inserted in wrong DIMM slots and one RAM module failed. The steps below are ordered to resolve this efficiently.RAM-ECC-ERROR/error/RAM-ECC-ERROR/ECC RAM Error ranks as a high-severity system memory (RAM) issue in our database. 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. See the troubleshooting steps below for the fix.RAM-NOT-DETECTED/error/RAM-NOT-DETECTED/RAM-NOT-DETECTED shows up as a critical-severity system memory (RAM) fault. Motherboard doesn't recognize RAM - reports low memory or won't boot. Typical causes include module incorrectly inserted, oxidized contacts and defective DIMM slot. Follow the steps below to fix it.REF-TIMEOUT/error/REF-TIMEOUT/REF-TIMEOUT shows up as a critical-severity system memory (RAM) fault. 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. Follow the steps below to fix it.ROW-HAM-DET/error/ROW-HAM-DET/Charge Leakage Detection (Row Hammer) is a critical-severity system memory (RAM) issue. 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. Work through the steps below in order.SPD-CHK-ERR/error/SPD-CHK-ERR/Bad memory profile (SPD) checksum ranks as a critical-severity system memory (RAM) issue in our database. 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. The steps below are ordered to resolve this efficiently.SPD-CORRUPTION/error/SPD-CORRUPTION/SPD-CORRUPTION is a medium-severity system memory (RAM) problem. 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. The steps below are ordered to resolve this efficiently.SUBTIM-CORRUPT/error/SUBTIM-CORRUPT/This critical-severity issue affects the system memory (RAM). 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. See the troubleshooting steps below for the fix.VDDQ-U-VOLT/error/VDDQ-U-VOLT/Insufficient RAM supply voltage is a critical-severity system memory (RAM) issue. 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. Follow the steps below to fix it.XMP_PROFILE_BOOT_LOOP/error/XMP-PROFILE-BOOT-LOOP/XMP_PROFILE_BOOT_LOOP is a high-severity system memory (RAM) problem. 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 QVL, weak memory controller (IMC) in the CPU and incorrect DRAM voltage or memory training parameters. The steps below are ordered to resolve this efficiently.XMP-BOOT-FAIL/error/XMP-BOOT-FAIL/XMP-BOOT-FAIL is a critical-severity system memory (RAM) problem. 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. Work through the steps below in order.XMP-INSTABILITY/error/XMP-INSTABILITY/XMP Profile Instability is a medium-severity system memory (RAM) issue. 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. Work through the steps below in order.
Storage / HDD & SSD
SMART-REALLOCATED/error/SMART-REALLOCATED/S.M.A.R.T.: Remapped Sectors is a high-severity storage drive (SSD/HDD) issue. SSD/HDD remaps bad sectors. The disk is nearing the end of its life. This usually traces back to physical wear and tear, power outages and electromagnetic interference. Follow the steps below to fix it.NTFS_FILE_SYSTEM/error/NTFS-FILE-SYSTEM/NTFS_FILE_SYSTEM is a critical-severity storage drive (SSD/HDD) problem. NTFS file system error. The disk or driver has a read/write problem. The usual suspects are damaged FS and defective cable. The steps below are ordered to resolve this efficiently.INACCESSIBLE_BOOT_DEVICE/error/INACCESSIBLE-BOOT-DEVICE/INACCESSIBLE_BOOT_DEVICE is a critical-severity storage drive (SSD/HDD) problem. Windows cannot access the system disk at startup. Common triggers are changing SATA mode in BIOS and corrupt MBR/GPT. Use the steps below to track down and fix the cause.SSD-TRIM-FAIL/error/SSD-TRIM-FAIL/SSD TRIM not working is a medium-severity storage drive (SSD/HDD) issue. 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. Use the steps below to track down and fix the cause.NVME-CONTROLLER-RESET/error/NVME-CONTROLLER-RESET/NVMe controller reset is a high-severity storage drive (SSD/HDD) issue. The NVMe storage controller has been reset by Windows due to a command timeout. The NVMe driver sends a command to the drive and waits a maximum of 8 seconds for a response. If the drive does not respond within this window, the controller is reset. Frequent resets cause system freezes, data corruption, and eventual BSOD crashes. It sometimes comes down to pCIe slot power management issue. Follow the steps below to fix it.NVME-CONTROLLER-RESET/error/NVME-CONTROLLER-RESET-2/NVMe controller reset is a high-severity storage drive (SSD/HDD) issue. The NVMe SSD controller has reset due to a communication error. It causes system crashes or data loss. It sometimes comes down to insufficient power to PCIe slot. Follow the steps below to fix it.SSD-WEAR-CRITICAL/error/SSD-WEAR-CRITICAL/SSD critical wear (SSD-WEAR-CRITICAL) is a critical-severity fault affecting the storage drive (SSD/HDD). The SSD has reached the critical TBW (Total Bytes Written) wear limit. Risk of failure. The usual suspects are TBW capacity exceeded, intensive Enrollment and disk age. Follow the steps below to fix it.DISK-READ-ERROR/error/DISK-READ-ERROR/This critical-severity issue affects the storage drive (SSD/HDD). Windows reports 'A disk read error occurred' when booting. PC won't boot. The usual suspects are corrupted MBR and allowed SATA cable. See the troubleshooting steps below for the fix.CRC-DATA-ERROR/error/CRC-DATA-ERROR/CRC-DATA-ERROR is a high-severity storage drive (SSD/HDD) problem. The operating system encountered a Cyclic Redundancy Check error while reading from the file. The data is corrupted and cannot be read. This usually traces back to bad sectors on disk, defective SATA cable and a surviving hard disk drive (HDD) or SSD. Follow the steps below to fix it.RAW-FILE-SYSTEM/error/RAW-FILE-SYSTEM/This critical-severity issue affects the storage drive (SSD/HDD). The disk's file system (NTFS/FAT32) has been corrupted and the system sees it as unformatted (RAW). Data is unavailable. It's most often caused by sudden power failure during write, unfinished formatting or resizing of partition and virus attack on MBR/MFT table. Follow the steps below to fix it.SMART-PRE-FAIL/error/SMART-PRE-FAIL/S.M.A.R.T. warning - Impending disk failure ranks as a high-severity storage drive (SSD/HDD) issue in our database. 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. Follow the steps below to fix it.NVME-CTL-RST/error/NVME-CTL-RST/M.2 NVMe Controller Unexpected Reset ranks as a high-severity storage drive (SSD/HDD) issue in our database. The controller on the SSD lost communication and restarted itself (OS crashes). Typical causes include end of life (age), defective cable, power outages and high temperatures in the M.2 slot. Follow the steps below to fix it.SATA-CRC-ERR/error/SATA-CRC-ERR/This high-severity issue affects the storage drive (SSD/HDD). 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. Follow the steps below to fix it.BAD-SEC-UNC/error/BAD-SEC-UNC/Physically bad sectors found on disk is a high-severity storage drive (SSD/HDD) issue. 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. Work through the steps below in order.CACHE-FLSH-FAIL/error/CACHE-FLSH-FAIL/Failed to write data from disk cache ranks as a high-severity storage drive (SSD/HDD) issue in our database. 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. Work through the steps below in order.MBR-GPT-CORR/error/MBR-GPT-CORR/MBR-GPT-CORR shows up as a high-severity storage drive (SSD/HDD) fault. 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. Follow the steps below to fix it.VSS-FREEZE/error/VSS-FREEZE/Stuck in the Shadow Copy (Backup) process (VSS-FREEZE) is a high-severity fault affecting the storage drive (SSD/HDD). 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. See the troubleshooting steps below for the fix.TRIM-IGNORE/error/TRIM-IGNORE/TRIM-IGNORE is a high-severity storage drive (SSD/HDD) problem. 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 appearing out of nowhere. Common triggers are end of life (age), defective cable, power outages and high temperatures in the M.2 slot. Work through the steps below in order.SPN-MOT-FAIL/error/SPN-MOT-FAIL/Plate disc spindle motor failure ranks as a high-severity storage drive (SSD/HDD) issue in our database. 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. See the troubleshooting steps below for the fix.TBW-LIM-RCH/error/TBW-LIM-RCH/Critical Cell Wear (SSD End of Life) (TBW-LIM-RCH) is a high-severity fault affecting the storage drive (SSD/HDD). The SSD has reached the end of its write life (TBW) and has entered read-only mode. Common triggers are defective cable, power outages and high temperatures in the M.2 slot. Use the steps below to track down and fix the cause.M2-THROTTLING/error/M2-THROTTLING/M2-THROTTLING shows up as a high-severity storage drive (SSD/HDD) fault. 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. The steps below are ordered to resolve this efficiently.BIT-ROT-DET/error/BIT-ROT-DET/Silent Disk Data Corruption (Bit Rot) is a high-severity storage drive (SSD/HDD) issue. 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. Follow the steps below to fix it.DRAM-CAC-FAIL/error/DRAM-CAC-FAIL/SSD internal DRAM cache failure ranks as a high-severity storage drive (SSD/HDD) issue in our database. A buffer built directly on the disk reports a hardware error. Typical causes include end of life (age), defective cable, power outages and high temperatures in the M.2 slot. Use the steps below to track down and fix the cause.SEC-ERS-LOCK/error/SEC-ERS-LOCK/Blocked attempt to securely delete data (SEC-ERS-LOCK) is a high-severity fault affecting the storage drive (SSD/HDD). 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. See the troubleshooting steps below for the fix.PCIE-LANE-DRP/error/PCIE-LANE-DRP/PCIE-LANE-DRP is a high-severity storage drive (SSD/HDD) problem. 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. Work through the steps below in order.NVME-PCIE-DEMOTION/error/NVME-PCIE-DEMOTION/NVME-PCIE-DEMOTION shows up as a medium-severity storage drive (SSD/HDD) fault. 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.SSD-DRAM-CACHE-FAIL/error/SSD-DRAM-CACHE-FAIL/SSD DRAM cache failure ranks as a high-severity storage drive (SSD/HDD) issue in our database. 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. Work through the steps below in order.CHKDSK-STAGE3-STUCK/error/CHKDSK-STAGE3-STUCK/CHKDSK-STAGE3-STUCK is a high-severity storage drive (SSD/HDD) problem. 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 for hours and the hard drive is physically damaged and takes too long to read. Use the steps below to track down and fix the cause.BITLOCKER-RECOVERY-LOOP/error/BITLOCKER-RECOVERY-LOOP/BitLocker recovery screen loop is a high-severity storage drive (SSD/HDD) issue. 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 Boot toggle), invalidating the stored encryption keys. Entering the recovery key once should resolve it, but the loop indicates the underlying trigger persists. See the troubleshooting steps below for the fix.BITLOCKER-RECOVERY-LOOP/error/BITLOCKER-RECOVERY-LOOP-2/BITLOCKER-RECOVERY-LOOP is a high-severity storage drive (SSD/HDD) problem. The computer asks for the 48-digit BitLocker key every time it is restarted, even if the password is not changed. Work through the steps below in order.SSD-TEMP-WARN/error/SSD-TEMP-WARN/This medium-severity issue affects the storage drive (SSD/HDD). The NVMe or SATA SSD is operating above optimal temperatures. This usually traces back to poor case airflow and missing M.2 heatsink. The steps below are ordered to resolve this efficiently.NVME_READ_ONLY/error/NVME-READ-ONLY/NVME_READ_ONLY shows up as a critical-severity storage drive (SSD/HDD) fault. 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. Another common trigger is excessive bad blocks. Use the steps below to track down and fix the cause.NVME_OVERHEATING_CRASH/error/NVME-OVERHEATING-CRASH/This high-severity issue affects the storage drive (SSD/HDD). 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 heavy continuous read/write load on the SSD and SSD placed directly under a hot graphics card slot. The steps below are ordered to resolve this efficiently.DISK-WRITE-PROTECT-ERROR/error/DISK-WRITE-PROTECT-ERROR/DISK-WRITE-PROTECT-ERROR is a medium-severity storage drive (SSD/HDD) problem. 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 drives with incorrect registry settings. The disk appears operational but all write operations fail silently or with error 0x80070013. The steps below are ordered to resolve this efficiently.HDD-SLOW-READ-SPEED/error/HDD-SLOW-READ-SPEED/HDD-SLOW-READ-SPEED shows up as a medium-severity storage drive (SSD/HDD) fault. 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. Causes include bad sector remapping slowing down reads, head misalignment, or degraded drive spindle motor. The steps below are ordered to resolve this efficiently.Motherboard / PortsARGB-HDR-SHRT/error/ARGB-HDR-SHRT/ARGB-HDR-SHRT is a critical-severity motherboard problem. 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. Use the steps below to track down and fix the cause.AUDIO-CONTROLLER-NO-SOUND/error/AUDIO-CONTROLLER-NO-SOUND/AUDIO-CONTROLLER-NO-SOUND shows up as a low-severity motherboard fault. 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 Realtek HD Audio driver conflicts with Intel's Smart Sound Technology (SST) driver on modern platforms. Work through the steps below in order.AZA-AUD-MISS/error/AZA-AUD-MISS/Integrated sound card not found (AZA-AUD-MISS) is a critical-severity fault affecting the motherboard. 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. The steps below are ordered to resolve this efficiently.BATT-NOT-CHARGING/error/BATT-NOT-CHARGING/Laptop battery is connected but not charging ranks as a high-severity motherboard issue in our database. 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 MyAsus) and ACPI battery controller error. The steps below are ordered to resolve this efficiently.BIFURC-FAIL/error/BIFURC-FAIL/Failure to split PCIe lines (Bifurcation) is a critical-severity motherboard issue. The splitter adapter (eg for multiple M.2 drives) did not get the correct PCIe lines. This usually traces back to dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age of capacitors. Work through the steps below in order.BIOS-FLS-FAIL/error/BIOS-FLS-FAIL/BIOS-FLS-FAIL is a critical-severity motherboard problem. 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. Work through the steps below in order.BT-ERR-43/error/BT-ERR-43/Bluetooth adapter error 43 (BT-ERR-43) is a medium-severity fault affecting the motherboard. Bluetooth has stopped working, the icon has disappeared and the device is reporting Code 43. Common triggers are chip firmware (Intel/Realtek) stuck due to static electricity and outdated Driver. Work through the steps below in order.CMOS-BAT-LEAK/error/CMOS-BAT-LEAK/CMOS-BAT-LEAK is a critical-severity motherboard problem. 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. Follow the steps below to fix it.CMOS-CHK-ERR/error/CMOS-CHK-ERR/Corrupt CMOS checksum (CMOS-CHK-ERR) is a critical-severity fault affecting the motherboard. 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. Common triggers are short circuit on the motherboard and age of capacitors. Use the steps below to track down and fix the cause.DMI-LNK-DOWN/error/DMI-LNK-DOWN/Loss of connection with PCH chipset is a critical-severity motherboard issue. 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. Follow the steps below to fix it.FAN-HDR-BURN/error/FAN-HDR-BURN/Burnt connector for connecting the fan is a critical-severity motherboard issue. 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. The steps below are ordered to resolve this efficiently.LPC-BUS-HANG/error/LPC-BUS-HANG/Sensor bus (LPC) freeze (LPC-BUS-HANG) is a critical-severity fault affecting the motherboard. 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. Follow the steps below to fix it.PCH-OVERHEAT/error/PCH-OVERHEAT/PCH-OVERHEAT shows up as a critical-severity motherboard fault. 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. See the troubleshooting steps below for the fix.PCIE-BIFURCATION-ERROR/error/PCIE-BIFURCATION-ERROR/PCIe bifurcation error is a medium-severity motherboard issue. The motherboard incorrectly distributes the PCIe lines for the adapter (NVME RAID, PLX switch). It's also often linked to bifurcation disabled in BIOS. See the troubleshooting steps below for the fix.PCIE-ERROR/error/PCIE-ERROR/PCIe communication error is a high-severity motherboard issue. Error on the PCIe line between the motherboard and the component. This usually traces back to misplaced card and defective driver. See the troubleshooting steps below for the fix.PCIE-GEN-MISMATCH/error/PCIE-GEN-MISMATCH/PCIE-GEN-MISMATCH shows up as a medium-severity motherboard fault. 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 screen appearing out of nowhere. Work through the steps below in order.POST-CODE-55/error/POST-CODE-55/POST Critical Error (Code 55 - Memory) (POST-CODE-55) is a critical-severity fault affecting the motherboard. The board failed to initialize RAM during boot. The usual suspects are dead battery CR2032, short circuit on the motherboard, aborted BIOS update process and age of capacitors. Follow the steps below to fix it.POST-CODE-99/error/POST-CODE-99/POST Code 99 - Super I/O Initialization ranks as a high-severity motherboard issue in our database. 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, graphics card seating issues, or conflicting USB devices. This can also stem from corrupt BIOS settings or outdated firmware. Use the steps below to track down and fix the cause.POST-CODE-A2/error/POST-CODE-A2/POST Code A2 - IDE Detect ranks as a high-severity motherboard issue in our database. 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 controllers, or loose power connections. This can also stem from corrupted boot partitions or MBR/GPT configurations. Follow the steps below to fix it.SEC-BOT-KEY-MS/error/SEC-BOT-KEY-MS/SEC-BOT-KEY-MS shows up as a critical-severity motherboard fault. 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. Work through the steps below in order.THUNDERBOLT-CONTROLLER-ERROR/error/THUNDERBOLT-CONTROLLER-ERROR/Thunderbolt controller initialization error (THUNDERBOLT-CONTROLLER-ERROR) is a medium-severity fault affecting the motherboard. 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. This affects Thunderbolt 3 and Thunderbolt 4 docking stations, external GPUs (eGPUs), and high-speed storage enclosures connected to the TB port. It sometimes comes down to driver version mismatch. Follow the steps below to fix it.TPM-ATT-FAIL/error/TPM-ATT-FAIL/TPM-ATT-FAIL shows up as a critical-severity motherboard fault. 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. The steps below are ordered to resolve this efficiently.TPM-CLR-PROMPT/error/TPM-CLR-PROMPT/TPM-CLR-PROMPT is a medium-severity motherboard problem. 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 invalidated the and keys BitLocker enabled and TPM has mismatch. Use the steps below to track down and fix the cause.USB-CONTROLLER-ERROR/error/USB-CONTROLLER-ERROR/USB-CONTROLLER-ERROR is a medium-severity motherboard problem. The motherboard's USB controller reports a Code 43 (device stopped) or Code 10 (cannot start) error in Device Manager. This affects all USB ports managed by the failing controller. Symptoms include USB devices suddenly disconnecting, USB ports not powering devices, or the controller disappearing from Device Manager entirely. Follow the steps below to fix it.USB-CTL-DEAD/error/USB-CTL-DEAD/Critical failure of USB controller on board (USB-CTL-DEAD) is a critical-severity fault affecting the motherboard. 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 of capacitors. Use the steps below to track down and fix the cause.USB-DEV-DESC-FAIL/error/USB-DEV-DESC-FAIL/USB device handle request failed is a low-severity motherboard issue. When connecting a USB device, the system failed to read its identifier and reports error code 43. This can also stem from bad USB controller on board. Work through the steps below in order.USB-OVERCURRENT/error/USB-OVERCURRENT/USB-OVERCURRENT shows up as a critical-severity motherboard fault. System shutting down after 15 seconds to protect motherboard from USB short circuit. Another common trigger is damaged USB device. Work through the steps below in order.USB-POWER-SURGE/error/USB-POWER-SURGE/USB-POWER-SURGE is a critical-severity motherboard problem. 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. Follow the steps below to fix it.VRM-OVERHEAT/error/VRM-OVERHEAT/Motherboard VRM overheating (VRM-OVERHEAT) is a critical-severity fault affecting the motherboard. The Voltage Regulator Module is overheating. Limits CPU performance or causes shutdown. Typical causes include no airflow through the VRM, aggressive OC and cheap board with high TDP CPU. Work through the steps below in order.VRM-OVERTEMP-THROT/error/VRM-OVERTEMP-THROT/This high-severity issue affects the motherboard. 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 CPU and bad air flow through VRM cooling. Work through the steps below in order.VRM-PHS-IMB/error/VRM-PHS-IMB/VRM-PHS-IMB is a critical-severity motherboard problem. 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 age of capacitors. The steps below are ordered to resolve this efficiently.
Power Supply (PSU)
PSU-OVERVOLTAGE/error/PSU-OVERVOLTAGE/PSU-OVERVOLTAGE shows up as a critical-severity power supply unit (PSU) fault. The power supply supplies a higher voltage than specified. Risk of component damage. It's most often caused by faulty PSU, failure of OVP protection and poor quality source. Use the steps below to track down and fix the cause.PSU-INSUFFICIENT/error/PSU-INSUFFICIENT/PSU-INSUFFICIENT shows up as a high-severity power supply unit (PSU) fault. The resource does not have time to cover the consumption of all components. Causes resets. This usually traces back to GPU upgrade without PSU replacement and PSU degradation. The steps below are ordered to resolve this efficiently.PSU-RIPPLE-NOISE/error/PSU-RIPPLE-NOISE/Higher power ripple (Ripple) (PSU-RIPPLE-NOISE) is a medium-severity fault affecting the power supply unit (PSU). The source produces higher than permitted supply voltage ripple. It causes instability or damage to the capacitors on the board. It's most often caused by cheap poor quality PSU, congested resource and faulty PFC circuit. Use the steps below to track down and fix the cause.OCP-TRIGGERED/error/OCP-TRIGGERED/OCP-TRIGGERED is a critical-severity power supply unit (PSU) problem. 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.COIL-WHINE-EXTREME/error/COIL-WHINE-EXTREME/COIL-WHINE-EXTREME shows up as a low-severity power supply unit (PSU) fault. 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). Work through the steps below in order.OVP-TRIPPED/error/OVP-TRIPPED/Overvoltage protection (OVP) activated ranks as a critical-severity power supply unit (PSU) issue in our database. 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). Use the steps below to track down and fix the cause.OCP-TRIPPED/error/OCP-TRIPPED/OCP-TRIPPED is a critical-severity power supply unit (PSU) problem. 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. Work through the steps below in order.UVP-TRIPPED/error/UVP-TRIPPED/Undervoltage protection (UVP) activated ranks as a critical-severity power supply unit (PSU) issue in our database. The voltage fell below the critical limit, the system shut down as a precaution. Another common trigger is leaked capacitor. Use the steps below to track down and fix the cause.OPP-TRIPPED/error/OPP-TRIPPED/Overload protection (OPP) activated is a critical-severity power supply unit (PSU) issue. 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. See the troubleshooting steps below for the fix.SCP-TRIPPED/error/SCP-TRIPPED/Short circuit protection (SCP) activated (SCP-TRIPPED) is a critical-severity fault affecting the power supply unit (PSU). 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 and sunken screw under the base plate (cracking about case). Work through the steps below in order.OTP-TRIPPED/error/OTP-TRIPPED/OTP-TRIPPED is a critical-severity power supply unit (PSU) problem. 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 installed 'upside down' on a carpet. See the troubleshooting steps below for the fix.PG-SIGNAL-FAIL/error/PG-SIGNAL-FAIL/PG-SIGNAL-FAIL shows up as a critical-severity power supply unit (PSU) fault. 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. See the troubleshooting steps below for the fix.RIPPLE-NOISE-MAX/error/RIPPLE-NOISE-MAX/RIPPLE-NOISE-MAX shows up as a high-severity power supply unit (PSU) fault. 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 due to age. The steps below are ordered to resolve this efficiently.PWR-CABLE-MELT/error/PWR-CABLE-MELT/PWR-CABLE-MELT shows up as a critical-severity power supply unit (PSU) fault. 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. Work through the steps below in order.COIL-WHINE-PSU/error/COIL-WHINE-PSU/This low-severity issue affects the power supply unit (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 saving features in BIOS. The steps below are ordered to resolve this efficiently.PSU_POWER_SAG_FREEZE/error/PSU-POWER-SAG-FREEZE/Power Sag System Freeze / Lockup ranks as a high-severity power supply unit (PSU) issue in our database. 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 steps below to fix it.PSU-CAPACITOR-BULGE/error/PSU-CAPACITOR-BULGE/PSU capacitor bulging/failure is a critical-severity power supply unit (PSU) issue. Physical inspection reveals bulged or leaking electrolytic capacitors inside the power supply unit. Bulging capacitors are a sign of imminent catastrophic failure. A failing capacitor can cause voltage ripple, power rail instability, and complete PSU failure. In worst cases, capacitor failure can cause fire or damage downstream components. Follow the steps below to fix it.PSU-RAIL-UNDERVOLTAGE/error/PSU-RAIL-UNDERVOLTAGE/PSU-RAIL-UNDERVOLTAGE shows up as a high-severity power supply unit (PSU) fault. 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. Undervoltage causes instability, unexpected shutdowns, and can corrupt data on storage drives due to incomplete write operations. This usually traces back to PSU degradation over time and PSU operating in high ambient temperature. Use the steps below to track down and fix the cause.Software Error Database
Network / Wi-Fi
NETIO-ERROR/error/NETIO-ERROR/Network I/O Error (NETIO-ERROR) is a medium-severity fault affecting the network adapter. A network driver or hardware caused an I/O communication error. It's also often linked to damaged ethernet cable or faulty port. Work through the steps below in order.DNS-RESOLUTION-FAIL/error/DNS-RESOLUTION-FAIL/DNS translation failure is a low-severity network adapter issue. PC cannot translate domain names to IP addresses. This usually traces back to bad DNS servers, problem with ISP and firewall blocking DNS. Work through the steps below in order.WINSOCK-CORRUPT/error/WINSOCK-CORRUPT/WINSOCK-CORRUPT shows up as a medium-severity network adapter fault. Winsock catalog is corrupted, network connections are not working. Website not loading. It's most often caused by malware, bad update and antivirus interference. See the troubleshooting steps below for the fix.WIFI-DRIVER-CRASH/error/WIFI-DRIVER-CRASH/Wi-Fi driver crash is a medium-severity network adapter issue. 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. Use the steps below to track down and fix the cause.SSL-HANDSHAKE-FAIL/error/SSL-HANDSHAKE-FAIL/SSL handshake failure is a low-severity network adapter issue. 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. Work through the steps below in order.GATEWAY-UNAVAILABLE/error/GATEWAY-UNAVAILABLE/Default gateway not available ranks as a medium-severity network adapter issue in our database. 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. Follow the steps below to fix it.IP-ADDRESS-CONFLICT/error/IP-ADDRESS-CONFLICT/This low-severity issue affects the network adapter. 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. This can also stem from DHCP server error on router. Follow the steps below to fix it.DHCP-TIMEOUT/error/DHCP-TIMEOUT/This medium-severity issue affects the network adapter. 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. Follow the steps below to fix it.DNS-RES-FAIL/error/DNS-RES-FAIL/This medium-severity issue affects the network adapter. The browser cannot translate the web address to an IP address (DNS problem). Reports of Domain name resolution (DNS) failure usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. This usually traces back to ISP Provider Error, corrupt network card driver and stuck Router. Work through the steps below in order.IPV6-LOOP/error/IPV6-LOOP/IPV6-LOOP is a medium-severity network adapter problem. 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. Follow the steps below to fix it.WLAN-RST-LOOP/error/WLAN-RST-LOOP/WLAN-RST-LOOP shows up as a medium-severity network adapter fault. The Wi-Fi card keeps disconnecting and restarting due to a driver error. Typical causes include stuck Router and IP address conflict. Use the steps below to track down and fix the cause.CBL-UNPL-FLS/error/CBL-UNPL-FLS/False report of unplugged network cable is a medium-severity network adapter issue. 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. The steps below are ordered to resolve this efficiently.MAC-CONFLICT/error/MAC-CONFLICT/Physical MAC address conflict in network (MAC-CONFLICT) is a medium-severity fault affecting the network adapter. Two devices on the network share the same physical MAC address. It's most often caused by ISP Provider Error and stuck Router. Work through the steps below in order.TCP-IP-CORR/error/TCP-IP-CORR/TCP/IP protocol structure corruption is a medium-severity network adapter issue. Windows internal networking layer is corrupt, no internet working. Common triggers are ISP Provider Error, stuck Router and IP address conflict. The steps below are ordered to resolve this efficiently.WINSOCK-REG-ER/error/WINSOCK-REG-ER/Missing or corrupted Winsock registries is a medium-severity network adapter issue. Application communication via internet sockets has completely crashed. Typical causes include ISP Provider Error, corrupt network card driver, stuck Router and IP address conflict. Work through the steps below in order.VPN-TUN-DROP/error/VPN-TUN-DROP/VPN-TUN-DROP is a medium-severity network adapter problem. 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. Follow the steps below to fix it.QOS-THROTTLE/error/QOS-THROTTLE/Connection speed limiter (QoS) error is a medium-severity network adapter issue. 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. Work through the steps below in order.IGMP-SNP-FAIL/error/IGMP-SNP-FAIL/This medium-severity issue affects the network adapter. 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. Use the steps below to track down and fix the cause.ARP-POISON/error/ARP-POISON/ARP Cache Poisoning Detection (Network Attack) is a medium-severity network adapter issue. 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. See the troubleshooting steps below for the fix.PRX-DET-STLL/error/PRX-DET-STLL/Proxy detection failure ranks as a medium-severity network adapter issue in our database. 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. Work through the steps below in order.MTU-MISMATCH/error/MTU-MISMATCH/MTU-MISMATCH shows up as a medium-severity network adapter fault. Different Maximum Transmission Unit settings cause fragmentation and brutal network slowdown. Typical causes include ISP Provider Error, stuck Router and IP address conflict. The steps below are ordered to resolve this efficiently.WLAN-AUTO-FAIL/error/WLAN-AUTO-FAIL/WLAN-AUTO-FAIL shows up as a medium-severity network adapter fault. The wireless network configuration service has failed, the Wi-Fi icon has completely disappeared. The usual suspects are ISP Provider Error, stuck Router and IP address conflict. Work through the steps below in order.NET-WIFI-NO-INTERNET/error/NET-WIFI-NO-INTERNET/Connected but no internet access ranks as a high-severity network adapter issue in our database. Wi-Fi reports a connection to the router, but Windows says that it cannot access the outside. This usually traces back to incorrectly set DNS on PC and outage by ISP. Follow the steps below to fix it.WLAN-LIMITED/error/WLAN-LIMITED/Limited network connection is a medium-severity network adapter issue. There is a yellow triangle with an exclamation mark on the Wi-Fi icon. The usual suspects are IP address conflict (multiple devices have the same IP) and the DHCP server in the router is stuck. The steps below are ordered to resolve this efficiently.ERR-SSL-PROTOCOL-ERR/error/ERR-SSL-PROTOCOL-ERR/ERR-SSL-PROTOCOL-ERR shows up as a medium-severity network adapter fault. 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. ESET, Avast) scan SSL transmission poorly and outdated operating system without root certificates. See the troubleshooting steps below for the fix.WINSOCK-CORRUPT/error/WINSOCK-CORRUPT-2/WINSOCK-CORRUPT shows up as a high-severity network adapter fault. The Internet connection works on the router, but Windows cannot establish any TCP/IP connections. Common triggers are faulty uninstall of VPN software (Cisco AnyConnect, Avast SecureLine), malware damaging the network stack and aborted network driver update. The steps below are ordered to resolve this efficiently.IPV6-LEAK-TUNNEL/error/IPV6-LEAK-TUNNEL/IPv6 tunnel causes connectivity issues is a medium-severity network adapter issue. 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.DNS-REBINDING-ATTACK/error/DNS-REBINDING-ATTACK/DNS-REBINDING-ATTACK is a high-severity network adapter problem. 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. The steps below are ordered to resolve this efficiently.NET-DHCP-LEASE/error/NET-DHCP-LEASE/DHCP lease renewal failure is a medium-severity network adapter issue. The system failed to renew its IP address from the DHCP server. This can also stem from network switch misconfiguration. See the troubleshooting steps below for the fix.WIFI_AUTOPREP_FAIL/error/WIFI-AUTOPREP-FAIL/WLAN AutoConfig Service Failed to Start (Error 1068) is a high-severity network adapter issue. The WLAN AutoConfig service (Wlansvc) failed to start, causing all wireless network adapters to become unresponsive and preventing the PC from scanning or connecting to Wi-Fi networks. Typical causes include corrupt ndis.sys driver, disabled dependency services (e.g. Native WiFi Filter) and corrupt system registry. See the troubleshooting steps below for the fix.DNS_PROBE_FINISHED_NXDOMAIN/error/DNS-PROBE-FINISHED-NXDOMAIN/This medium-severity issue affects the network adapter. A common browser error code displaying when the web browser cannot resolve a website's domain name because the DNS server reports that the domain name does not exist (Non-Existent Domain). It's most often caused by corrupt local DNS resolver cache, incorrect network DNS servers and VPN/firewall blocking DNS requests. The steps below are ordered to resolve this efficiently.WIFI-DRIVER-BSOD/error/WIFI-DRIVER-BSOD/Wi-Fi adapter driver BSOD is a high-severity network adapter issue. 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 to a Wi-Fi driver file. Often occurs after Windows Update automatically installs an incompatible wireless driver version. Use the steps below to track down and fix the cause.NETWORK-BOOT-FAIL/error/NETWORK-BOOT-FAIL/Network boot (PXE) failure ranks as a medium-severity network adapter issue in our database. 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 device and no PXE server is available, or when the DHCP server fails to provide a boot file path. See the troubleshooting steps below for the fix.IPV6-CONNECTIVITY-FAIL/error/IPV6-CONNECTIVITY-FAIL/IPv6 connectivity failure is a low-severity network adapter issue. The system has no IPv6 connectivity while IPv4 functions normally. Modern applications and services increasingly require IPv6 (Microsoft services, Google, gaming platforms). IPv6 failure causes slow connection initiation as apps fall back to IPv4, and some services may be inaccessible or degraded. Windows shows 'No Internet access' for IPv6 in Network Status. See the troubleshooting steps below for the fix.Windows OS / BSOD0x0000000A/error/0x0000000A/This critical-severity issue affects the Windows operating system. A kernel process attempted to access memory at an unauthorized high interrupt level (IRQL). Typical causes include badly programmed driver and processor overheating. Follow the steps below to fix it.0x000000C1/error/0x000000C1/SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION is a critical-severity Windows operating system issue. A special pool driver check detected that a kernel driver wrote to memory outside its allocated block. This is a critical RAM integrity BSOD. Commonly caused by driver memory leaks, incompatible chipset drivers, or faulty RAM. This can also stem from registry database corruption. Work through the steps below in order.0x000000C2/error/0x000000C2/0x000000C2 is a high-severity Windows operating system problem. The current thread made an invalid request to the memory pool. Work through the steps below in order.0x000000D1/error/0x000000D1/DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) is a critical-severity fault affecting the Windows operating system. A kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. Caused by corrupt drivers, faulty memory, or antivirus software. It sometimes comes down to corrupted system files. See the troubleshooting steps below for the fix.0x000000EA/error/0x000000EA/This high-severity issue affects the Windows operating system. 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. Work through the steps below in order.0x000000EF/error/0x000000EF/CRITICAL_PROCESS_DIED (0x000000EF) is a critical-severity fault affecting the Windows operating system. A critical system process (winlogon, csrss, lsass) has terminated. Typical causes include malware and bad update. See the troubleshooting steps below for the fix.0x000000EF/error/0x000000EF-2/This critical-severity issue affects the Windows operating system. A critical system process (eg svchost, csrss, wininit) terminated unexpectedly. This usually traces back to malware terminating important processes, extensive registry corruption and failed to read from SSD disk. Use the steps below to track down and fix the cause.0x000000F4/error/CRITICAL-OBJECT-TERMINATION/0x000000F4 shows up as a critical-severity Windows operating system fault. A critical system process or thread was terminated unexpectedly, causing the system to halt. This can also stem from SATA/NVMe controller connection issue. Work through the steps below in order.0x000000FC/error/0x000000FC/ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY is a high-severity Windows operating system issue. An attempt was made to execute code in memory that is marked as 'read only'. This usually traces back to outdated and incompatible drivers, buffer Overflow attack and defective RAM. The steps below are ordered to resolve this efficiently.0x000001A/error/0x0000001A/MEMORY_MANAGEMENT BSOD (0x000001A) (0x000001A) is a critical-severity fault affecting the Windows operating system. Stop code 0x0000001A (MEMORY_MANAGEMENT) indicates a severe Windows kernel memory management error. This is one of the most common critical BSODs in Windows 10 and 11. This usually traces back to defective RAM module and failing SSD/HDD causing page file corruption. Follow the steps below to fix it.0x000001D5/error/0x000001D5/DRIVER_PNP_WATCHDOG ranks as a critical-severity Windows operating system issue in our database. 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. It's also often linked to faulty storage controller. Work through the steps below in order.0x0000001E/error/0x0000001E/KMODE_EXCEPTION_NOT_HANDLED (0x0000001E) is a high-severity fault affecting the Windows operating system. A program running in kernel mode generated an exception that was not caught by the routine code. The usual suspects are incompatibility of hardware and new driver, system hit by rootkit and faulty third party service. See the troubleshooting steps below for the fix.0x0000003B/error/0x0000003B/SYSTEM_SERVICE_EXCEPTION (0x0000003B) is a critical-severity fault affecting the Windows operating system. A system service threw an exception. Caused by drivers or system files. It sometimes comes down to antivirus conflict. See the troubleshooting steps below for the fix.0x0000003B/error/0x0000003B-2/SYSTEM_SERVICE_EXCEPTION (0x0000003B) is a high-severity fault affecting the Windows operating system. An exception occurred while transitioning from unprotected user code to a protected kernel. The usual suspects are corrupt system files (ntoskrnl.exe), conflict with antivirus software and faulty Windows Updates. See the troubleshooting steps below for the fix.0x0000003D/error/0x0000003D/0x0000003D is a critical-severity Windows operating system problem. 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. This can also stem from corrupted device drivers (typically network or USB controllers). Use the steps below to track down and fix the cause.0x0000004A/error/0x0000004A/This critical-severity issue affects the Windows operating system. 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. Work through the steps below in order.0x0000004E/error/0x0000004E/PFN_LIST_CORRUPT (0x4E) is a critical-severity Windows operating system issue. The Page Frame Number (PFN) database list was detected as corrupted. This is a critical memory management BSOD. Most commonly caused by driver conflicts writing to page tables incorrectly, physical RAM hardware failure, or corrupted system files. Use the steps below to track down and fix the cause.0x0000007B/error/0x0000007B/INACCESSIBLE_BOOT_DEVICE is a critical-severity Windows operating system issue. Windows lost access to the root system partition during startup. Typical causes include change disk controller mode in BIOS (IDE -> AHCI/RAID) and corrupt storage driver. Work through the steps below in order.0x0000007E/error/0x0000007E/0x0000007E shows up as a critical-severity Windows operating system fault. A system thread threw an unhandled exception. A very common Windows BSOD caused by drivers. It sometimes comes down to RAM errors. The steps below are ordered to resolve this efficiently.0x0000009F/error/0x0000009F/This high-severity issue affects the Windows operating system. The driver put the device into an erroneous power state and the system crashed. This can also stem from sleep/Hibernate Problems. The steps below are ordered to resolve this efficiently.0x00000019/error/0x00000019/BAD_POOL_HEADER (0x19) is a critical-severity Windows operating system issue. The pool header checking routine detected corrupted memory blocks. This is a critical memory corruption BSOD. Most commonly caused by driver conflicts, hardware failure of RAM sticks, or active virus/malware memory injection. It's also often linked to unstable XMP/EXPO voltage offsets. The steps below are ordered to resolve this efficiently.0x00000024/error/0x00000024/NTFS_FILE_SYSTEM is a critical-severity Windows operating system issue. Fatal error inside NTFS driver. The usual suspects are corrupt file system on hard disk, serious problem with SATA cable and HDD physical damage (bad sectors). Use the steps below to track down and fix the cause.0x00000050/error/0x00000050/This critical-severity issue affects the Windows operating system. Windows accessed an invalid memory address. The usual suspects are defective RAM, corrupt driver and overheating. See the troubleshooting steps below for the fix.0x00000050/error/0x00000050-2/PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) is a high-severity fault affecting the Windows operating system. An error occurred when requesting non-paged memory because the data was not found there. Reports of PAGE_FAULT_IN_NONPAGED_AREA usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. It's most often caused by RAM module failure, faulty graphics driver and corrupt paging file (pagefile.sys). Work through the steps below in order.0x00000078/error/0x00000078/0x00000078 shows up as a critical-severity Windows operating system fault. 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. It sometimes comes down to CPU core voltage instability or sag. Work through the steps below in order.0x00000100/error/0x00000100/LOADER_BLOCK_MISMATCH is a critical-severity Windows operating system issue. 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 unstable overclocking. It's also often linked to failed storage driver installation. Follow the steps below to fix it.0x00000109/error/0x00000109/0x00000109 is a critical-severity Windows operating system problem. The kernel has detected corruption of key system data or kernel memory structure. This usually traces back to faulty RAM (bit flipped) and android emulators with a bug (eg old BlueStacks). Work through the steps below in order.0x00000116/error/0x00000116/0x00000116 shows up as a high-severity Windows operating system fault. An attempt to reset the graphics driver and recover after timeout failed. It's most often caused by severely unstable GPU overclocking and card physical malfunction. The steps below are ordered to resolve this efficiently.0x00000119/error/0x00000119/This critical-severity issue affects the Windows operating system. The video scheduler has detected a fatal violation in the display driver. Caused by graphics driver corruption, memory leaks or faulty GPU hardware. Typical causes include unstable GPU overclock and thermal throttling. Use the steps below to track down and fix the cause.0x00000133/error/0x00000133/DPC_WATCHDOG_VIOLATION (0x00000133) is a critical-severity fault affecting the Windows operating system. A deferred procedure call (DPC) routine took too long and crashed the system. Reports of DPC_WATCHDOG_VIOLATION usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. Typical causes include bad SSD/SATA controller driver, incompatible disk firmware and graphics driver error. The steps below are ordered to resolve this efficiently.0x00000139/error/0x00000139/KERNEL_SECURITY_CHECK_FAILURE (0x00000139) is a critical-severity fault affecting the Windows operating system. The kernel detected corruption of security-critical data structures. Another common trigger is driver conflict (typically anticheat or antivirus). Work through the steps below in order.0x00000154/error/0x00000154/UNEXPECTED_STORE_EXCEPTION is a critical-severity Windows operating system issue. The store component has thrown an unexpected exception. Caused by hard drive failure, SSD controller timeout, or corrupted system files. The usual suspects are SSD/HDD sector corruption, outdated SSD firmware and antivirus software conflict. Work through the steps below in order.0x00000709/error/0x00000709/0x00000709 shows up as a low-severity Windows operating system fault. Windows cannot set the default printer or connect to a network printer. The usual suspects are registry key restriction and driver mismatch. Use the steps below to track down and fix the cause.0x800B0109/error/0x800B0109/0x800B0109 - Untrusted Root Certificate Error (0x800B0109) is a medium-severity fault affecting the Windows operating system. 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 certificates are missing. Common triggers are corrupt cryptographic store components and network proxy SSL redirection interferences. See the troubleshooting steps below for the fix.0x800F081F/error/0x800F081F/This high-severity issue affects the Windows operating system. This error is triggered when Windows Update or the DISM tool cannot locate the required source files to complete a system repair or component installation. Work through the steps below in order.0x800F0900/error/0x800F0900/0x800F0900 - DISM CBS Manifest Corruption is a high-severity Windows operating system issue. 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. Follow the steps below to fix it.0x800f0922/error/0x800f0922/Windows Update Error 0x800f0922 (Secure Boot / Space Issue) ranks as a high-severity Windows operating system issue in our database. This error is triggered when Windows Update fails to install due to a secure boot configuration mismatch, insufficient system reserved partition space, or a connection failure to Microsoft servers. See the troubleshooting steps below for the fix.0x800F0984/error/0x800F0984/0x800F0984 is a high-severity Windows operating system problem. The component store matching binary file is missing. This is a severe Windows Update corruption error that blocks cumulative updates from applying. Use the steps below to track down and fix the cause.0x800f0988/error/0x800f0988/0x800f0988 is a high-severity Windows operating system problem. 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.0x803f8001/error/0x803f8001/Windows Store Game License Error 0x803f8001 (0x803f8001) is a high-severity fault affecting the Windows operating system. 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 verify that your account owns the product license. Use the steps below to track down and fix the cause.0x8000FFFF/error/0x8000FFFF/Catastrophic Windows Update Failures is a high-severity Windows operating system issue. 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. The steps below are ordered to resolve this efficiently.0x80072efd/error/0x80072efd/Windows Update Connection Timeout 0x80072efd ranks as a high-severity Windows operating system issue in our database. This error indicates that the Windows Update service encountered a network connection timeout while trying to reach Microsoft's update servers, usually caused by network filters, firewalls, or proxy settings. Follow the steps below to fix it.0x80073CF9/error/0x80073CF9/0x80073CF9 - Store App Installation Failure ranks as a medium-severity Windows operating system issue in our database. 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. It's most often caused by incorrect Windows system time or region settings and background update installer service blockages. The steps below are ordered to resolve this efficiently.0x80073D05/error/0x80073D05/0x80073D05 shows up as a medium-severity Windows operating system fault. 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, Minecraft, or Netflix. It's also often linked to orphaned user registry database keys for the app. Follow the steps below to fix it.0x800704cf/error/0x800704cf/Network location cannot be reached ranks as a medium-severity Windows operating system issue in our database. The network location cannot be reached. Error occurs when trying to sign in to Microsoft services or access network drives. Common triggers are TCP/IP stack corruption and incorrect DNS settings. Use the steps below to track down and fix the cause.0x8007000E/error/0x8007000E/0x8007000E shows up as a medium-severity Windows operating system fault. 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, disabled paging files, or memory leaks in update processes. Work through the steps below in order.0x8007007B/error/0x8007007B/Windows activation error 0x8007007B is a medium-severity Windows operating system issue. 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 appearing out of nowhere. Typical causes include invalid KMS server and DNS resolution for KMS failed. The steps below are ordered to resolve this efficiently.0x8007007e/error/0x8007007e/Windows Module Load Failure 0x8007007e is a high-severity Windows operating system issue. 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. Follow the steps below to fix it.0x8007045D/error/0x8007045D/I/O Device Error - Storage is a high-severity Windows operating system issue. Request could not be performed because of an I/O device error. Often indicates failing sectors. This usually traces back to faulty SATA cable and USB connection drop. See the troubleshooting steps below for the fix.0x8024200B/error/WU-0x8024200B/Windows Update Installation Error 0x8024200B is a medium-severity Windows operating system issue. 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 below to track down and fix the cause.0x8024401F/error/0x8024401F/0x8024401F is a medium-severity Windows operating system problem. 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 corrupt local update caches. See the troubleshooting steps below for the fix.0x80004005/error/0x80004005/This high-severity issue affects the Windows operating system. 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. It sometimes comes down to antivirus software blockages. The steps below are ordered to resolve this efficiently.0x80070002/error/0x80070002/Windows Update File Failure (0x80070002) (0x80070002) is a medium-severity fault affecting the Windows operating system. This error occurs when Windows Update or an installer attempts to access a critical installation file that has been deleted, moved, or corrupted. It's also often linked to damaged registry keys pointing to incorrect driver package paths. See the troubleshooting steps below for the fix.0x80070003/error/0x80070003/0x80070003 - Path Not Found Update Error (0x80070003) is a medium-severity fault affecting the Windows operating system. 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. It sometimes comes down to incomplete background cumulative downloads. Work through the steps below in order.0x80070005/error/0x80070005/0x80070005 is a high-severity Windows operating system problem. Windows Update failed due to permissions or blocking. It's also often linked to corrupted UpdateDB. See the troubleshooting steps below for the fix.0x80070017/error/0x80070017/0x80070017 - CRC Data Read Error is a high-severity Windows operating system issue. 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 copies due to bad sectors or faulty cables. Use the steps below to track down and fix the cause.0x80070057/error/0x80070057/0x80070057 is a high-severity Windows operating system problem. An invalid parameter was passed to a service or method (E_INVALIDARG). Commonly encountered during Windows Update, System Restore, or disk formatting. It sometimes comes down to corrupted registry keys. Follow the steps below to fix it.0x80070070/error/0x80070070/0x80070070 - Disk Full Update Error (0x80070070) is a medium-severity fault affecting the Windows operating system. There is insufficient disk space on the system drive (C:) or update cache partition to complete the installation. Commonly occurs during major Windows feature updates or large store downloads. Use the steps below to track down and fix the cause.0x80070091/error/0x80070091/0x80070091 shows up as a medium-severity Windows operating system fault. The directory is not empty. Commonly occurs during failed System Restore operations or when attempting to delete Windows.old or app folders. It sometimes comes down to bad sectors on the storage partition. See the troubleshooting steps below for the fix.0x80070422/error/0x80070422/This medium-severity issue affects the Windows operating system. Windows Update has been disabled or is not working properly. Unable to download updates. This usually traces back to missing permission and conflict with antivirus. Use the steps below to track down and fix the cause.0x80070422/error/0x80070422-2/0x80070422 shows up as a medium-severity Windows operating system fault. Windows Update reports error 0x80070422 and refuses to download updates. It sometimes comes down to BITS (Background Intelligent Transfer) is turned off. See the troubleshooting steps below for the fix.0x80070422/error/0x80070422-3/Windows Defender service disabled (0x80070422) is a high-severity fault affecting the Windows operating system. The Windows Defender service cannot start, leaving the system vulnerable. It's also often linked to third-party antivirus interference. Work through the steps below in order.0x80070643/error/0x80070643/Windows Update Error 0x80070643 (WinRE size too small) is a critical-severity Windows operating system issue. This error is triggered when Windows Update fails to install the recovery partition update (often KB5034441) due to the Windows Recovery Environment (WinRE) partition size being too small. It's also often linked to system servicing stack corruption. Use the steps below to track down and fix the cause.0x80073712/error/0x80073712/This high-severity issue affects the Windows operating system. Windows updates fail with code 0x80073712 due to corrupt or missing component system files. See the troubleshooting steps below for the fix.0x80080005/error/0x80080005/0x80080005 is a high-severity Windows operating system problem. 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 broken file permissions on the System Volume Information or SoftwareDistribution directories. Follow the steps below to fix it.0x80240034/error/0x80240034/Windows Update Error 0x80240034 (Download Database Fail) (0x80240034) is a medium-severity fault affecting the Windows operating system. 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.0x80242006/error/0x80242006/0x80242006 - Windows Update Handler Error (0x80242006) is a medium-severity fault affecting the Windows operating system. 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. Follow the steps below to fix it.0x80244007/error/0x80244007/Windows Update SOAP Client Error 0x80244007 (0x80244007) is a medium-severity fault affecting the Windows operating system. 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. Work through the steps below in order.0x80244018/error/0x80244018/This high-severity issue affects the Windows operating system. 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. Follow the steps below to fix it.0x80246007/error/0x80246007/Windows Update Error 0x80246007 (Download Interrupted) is a medium-severity Windows operating system issue. This error indicates that the update download was interrupted unexpectedly. This is typically related to background intelligent transfer service (BITS) dropouts or network conflicts. This can also stem from aggressive firewall filters closing persistent connections. Follow the steps below to fix it.0xC004F074/error/0xC004F074/This medium-severity issue affects the Windows operating system. Windows could not contact the activation server or the key is invalid. Typical causes include hardware change and offline PC. The steps below are ordered to resolve this efficiently.0xC0000005/error/0xC0000005/0xC0000005 shows up as a high-severity Windows operating system fault. The application attempted to access memory to which it does not have access rights. Typical application or driver error. The usual suspects are defective RAM, CPU overheating and malware. Use the steps below to track down and fix the cause.0xC0000006/error/0xC0000006/0xC0000006 shows up as a high-severity Windows operating system fault. 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. Follow the steps below to fix it.0xC000021A/error/0xC000021A/STATUS_SYSTEM_PROCESS_TERMINATED (0xC000021A) (0xC000021A) is a critical-severity fault affecting the Windows operating system. Error 0xC000021A occurs when a critical user-mode subsystem process (Winlogon.exe or CSRSS.exe) terminates unexpectedly. Windows immediately issues a BSOD because these processes cannot safely terminate. This is often seen during Windows upgrades, after corrupt Windows updates, or when system files are replaced by malware. Work through the steps below in order.0xC000021A/error/0xC000021A-2/0xC000021A is a critical-severity Windows operating system problem. A critical user subsystem (such as WinLogon or CSRSS) has been critically terminated. The system cannot continue to run. It's most often caused by incomplete or incorrect installation of update and incompatible third-party software. See the troubleshooting steps below for the fix.0xc0000034/error/0xc0000034/0xc0000034 is a critical-severity Windows operating system problem. The Windows boot loader file (winload.efi) is missing, corrupt, or unreadable, preventing the operating system from booting. It's also often linked to failing storage drive sectors. See the troubleshooting steps below for the fix.0xC0000428/error/BOOT-0xC0000428/Digital Signature Verification Failure (0xC0000428) ranks as a critical-severity Windows operating system issue in our database. 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. See the troubleshooting steps below for the fix.802-1X-AUTH-FAIL/error/802-1X-AUTH-FAIL/802.1X authentication failure on enterprise Wi-Fi ranks as a high-severity Windows operating system issue in our database. Cannot connect to corporate or university Wi-Fi that uses 802.1X (RADIUS) authentication. Windows prompts for credentials repeatedly. The usual suspects are expired or untrusted certificate on the client and network Policy Server (NPS) rejecting connection. Follow the steps below to fix it.AUDIO-RENDERER-ERR/error/AUDIO-RENDERER-ERR/AUDIO-RENDERER-ERR is a low-severity Windows operating system problem. Browser (Chrome/Edge) reports 'Audio renderer error' and cannot play media until restarted. Another common trigger is exclusive mode lock by another application. Work through the steps below in order.AUDIO-SERVICE-DEAD/error/AUDIO-SERVICE-DEAD/AUDIO-SERVICE-DEAD shows up as a medium-severity Windows operating system fault. The Windows Audio service (Audiosrv) has crashed or cannot start. No sound output is available system-wide. The steps below are ordered to resolve this efficiently.BLUETOOTH-AUDIO-STUTTER/error/BLUETOOTH-AUDIO-STUTTER/This low-severity issue affects the Windows operating system. Wireless headphones/speakers connected via Bluetooth experience intermittent dropouts, stuttering or low audio quality. It's also often linked to USB 3.0 interference on nearby ports. Follow the steps below to fix it.BLUETOOTH-PAIRING-FAIL/error/BLUETOOTH-PAIRING-FAIL/Bluetooth device fails to pair ranks as a medium-severity Windows operating system issue in our database. Bluetooth device cannot complete the pairing process, shows 'Try connecting your device again' or stays stuck at 'Pairing'. Common triggers are driver mismatch after Windows update and too many paired devices in registry cache. Use the steps below to track down and fix the cause.BOOTMGR-MISSING/error/BOOTMGR-MISSING/BOOTMGR is missing (BOOTMGR-MISSING) is a critical-severity fault affecting the Windows operating system. The 'BOOTMGR is missing' error appears at startup before Windows loads. The Windows Boot Manager (BOOTMGR) is the first program loaded by UEFI/BIOS to find and launch the Windows OS loader. If BOOTMGR is missing, corrupted, or on a partition that is not marked as active/bootable, Windows cannot start at all. The steps below are ordered to resolve this efficiently.BSOD on install/error/BSOD-ON-INSTALL/Windows installer crash (driver/RAM issue) (BSOD on install) is a high-severity fault affecting the Windows operating system. 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 mode in BIOS (IDE vs AHCI/RAID). The steps below are ordered to resolve this efficiently.CPU-FAN-ERROR/error/CPU-FAN-ERROR/CPU-FAN-ERROR shows up as a high-severity Windows operating system fault. The motherboard BIOS cannot detect a CPU fan signal during POST. System may refuse to boot to protect the CPU. The usual suspects are fan not connected to CPU_FAN header and faulty fan motor. Use the steps below to track down and fix the cause.D3D11-CREATE-DEVICE-FAILED/error/D3D11-CREATE-DEVICE-FAILED/D3D11-CREATE-DEVICE-FAILED is a high-severity Windows operating system problem. The application or game could not initialize Direct3D 11. This occurs when the graphics driver is corrupted or the GPU does not support the required DirectX 11 features. Follow the steps below to fix it.DIRECTSTORAGE-NOT-SUPPORTED/error/DIRECTSTORAGE-NOT-SUPPORTED/DirectStorage not available on this system (DIRECTSTORAGE-NOT-SUPPORTED) is a medium-severity fault affecting the Windows operating system. 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. Work through the steps below in order.DISK-USAGE-100/error/DISK-USAGE-100/DISK-USAGE-100 shows up as a medium-severity Windows operating system fault. 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. Use the steps below to track down and fix the cause.DISM-RESTOREHEALTH-FAIL/error/DISM-RESTOREHEALTH-FAIL/DISM-RESTOREHEALTH-FAIL shows up as a high-severity Windows operating system fault. DISM fails to repair Windows Component Store with error 0x800f081f or 0x800f0906 when component source cannot be found. Follow the steps below to fix it.DPC_WATCHDOG_VIOLATION/error/DPC-WATCHDOG-VIOLATION/DPC Watchdog Violation is a critical-severity Windows operating system issue. The Deferred Procedure Call was not handled in time. Caused by driver or SSD firmware issues. The steps below are ordered to resolve this efficiently.DXGI-ERROR-DEVICE-REMOVED-3/error/DXGI-ERROR-DEVICE-REMOVED-3/This high-severity issue affects the Windows operating system. The graphics card has been physically removed or a driver crash has caused the device to reset. This usually traces back to GPU Overclock instability and insufficient power supply voltage. Use the steps below to track down and fix the cause.Event ID 7034/error/EVENT-ID-7034/Event ID 7034 is a medium-severity Windows operating system problem. A registered Windows system service terminated unexpectedly. It's also often linked to software conflicts or crashed processes. Follow the steps below to fix it.EVENT-ID-41-KERNEL-POWER/error/EVENT-ID-41-KERNEL-POWER/Event ID 41 – Kernel-Power unexpected shutdown ranks as a critical-severity Windows operating system issue in our database. Windows logs Event ID 41 (Kernel-Power) after an unexpected power loss or system crash without a proper shutdown. This can also stem from BSOD that did not generate a dump file. See the troubleshooting steps below for the fix.EVENT-ID-6008/error/EVENT-ID-6008/EVENT-ID-6008 shows up as a high-severity Windows operating system fault. Event Log records ID 6008 indicating the previous system shutdown was unexpected (power loss or hard crash). Another common trigger is BSOD without BSOD screen (automatic restart enabled). See the troubleshooting steps below for the fix.FAULTY_HARDWARE_CORRUPTED_PAGE/error/FAULTY-HARDWARE-CORRUPTED-PAGE/Faulty Hardware Corrupted Page BSOD (0x0000012B) is a critical-severity Windows operating system issue. A FAULTY_HARDWARE_CORRUPTED_PAGE blue screen crash occurs when the Windows memory manager detects corruption in single-bit error correction memory pages, indicating failing physical memory or system file corruption. See the troubleshooting steps below for the fix.HYPER-V-MEM-OVERCOMMIT/error/HYPER-V-MEM-OVERCOMMIT/This high-severity issue affects the Windows operating system. 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.KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL/error/KERNEL-AUTO-BOOST-LOCK-ACQUISITION-WITH-RAISED-IRQL/Kernel auto boost lock IRQL error (KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL) is a critical-severity fault affecting the Windows operating system. 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. The error is almost exclusively caused by a buggy third-party driver — particularly security software, antivirus kernel drivers, or gaming anti-cheat systems that hook into kernel lock primitives. The steps below are ordered to resolve this efficiently.KERNEL_DATA_INPAGE_ERROR/error/KERNEL-DATA-INPAGE-ERROR/Error reading kernel data from page (KERNEL_DATA_INPAGE_ERROR) is a critical-severity fault affecting the Windows operating system. Windows could not retrieve the requested data from the paging file or disk. Typically a disk or RAM problem. Typical causes include defective HDD/SSD and defective RAM. See the troubleshooting steps below for the fix.KERNEL_SECURITY_CHECK_FAILURE/error/KERNEL-SECURITY-CHECK-FAILURE/This critical-severity issue affects the Windows operating system. The KERNEL_SECURITY_CHECK_FAILURE bug check has a value of 0x00000139. This BSOD indicates that the kernel has detected corruption of a critical data structure. This is usually caused by memory corruption, driver issues, or hardware failure. Common triggers are corrupted system drivers and corrupted Windows system files. Use the steps below to track down and fix the cause.KERNEL_SECURITY_CHECK_FAILURE/error/KERNEL-SECURITY-CHECK-FAILURE-2/KERNEL_SECURITY_CHECK_FAILURE is a critical-severity Windows operating system problem. Windows has detected corruption of kernel data structures. Most often caused by a faulty driver or memory corruption. It's most often caused by defective RAM, overclocking and malware. The steps below are ordered to resolve this efficiently.KMODE_EXCEPTION_NOT_HANDLED/error/KMODE-EXCEPTION-NOT-HANDLED/0x0000001E BSOD is a critical-severity Windows operating system issue. A kernel process generated an exception that the system could not handle. It usually points to faulty drivers or memory. Follow the steps below to fix it.MEM-LEAK-SYS/error/MEM-LEAK-SYS/This high-severity issue affects the Windows operating system. A critical system process is consuming available memory indefinitely. The usual suspects are faulty driver (Non-paged pool leak) and buggy background service. Work through the steps below in order.MEMORY-INTEGRITY-INCOMP/error/MEMORY-INTEGRITY-INCOMP/Memory Integrity Protection (HVCI) - incompatible driver (MEMORY-INTEGRITY-INCOMP) is a medium-severity fault affecting the Windows operating system. Windows Security reports that Memory Integrity Protection is disabled due to an incompatible driver. Another common trigger is cheating software or old anti-cheat. The steps below are ordered to resolve this efficiently.OPENGL-INVALID-OPERATION/error/OPENGL-INVALID-OPERATION/OpenGL GL_INVALID_OPERATION error (OPENGL-INVALID-OPERATION) is a medium-severity fault affecting the Windows operating system. An OpenGL command was issued that is not valid for the current OpenGL state. Application may crash or render incorrectly. This can also stem from using deprecated functions on core profile context. The steps below are ordered to resolve this efficiently.PFN_LIST_CORRUPT/error/PFN-LIST-CORRUPT/PFN_LIST_CORRUPT shows up as a critical-severity Windows operating system fault. The PFN (Page Frame Number) data structure is corrupted. The system detected an inconsistency in memory. Common triggers are registry corruption, faulty RAM and bad hard disk driver. Follow the steps below to fix it.POWERCFG-HIGH-DRAIN/error/POWERCFG-HIGH-DRAIN/This medium-severity issue affects the Windows operating system. Laptop battery discharges significantly faster than expected, even in sleep/standby mode. Another common trigger is high background CPU usage (Windows Search, Defender). The steps below are ordered to resolve this efficiently.PRN-OFFLINE/error/PRN-OFFLINE/PRN-OFFLINE is a low-severity Windows operating system problem. Although the printer is turned on and connected, Windows says it is in Offline mode. Another common trigger is the WSD port created an incorrect connection. Use the steps below to track down and fix the cause.REGISTRY_ERROR/error/REGISTRY-ERROR/This critical-severity issue affects the Windows operating system. 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 or file system faults. Use the steps below to track down and fix the cause.SLEEP-WAKE-FAIL/error/SLEEP-WAKE-FAIL/PC fails to wake from sleep (S3/Modern Standby) ranks as a high-severity Windows operating system issue in our database. The computer appears to enter sleep/standby but cannot wake up. Requires hard reset. It sometimes comes down to BIOS setting disabling wake-on-USB. See the troubleshooting steps below for the fix.SMB-SIGN-MISMATCH/error/SMB-SIGN-MISMATCH/SMB signing mismatch – network share unavailable (SMB-SIGN-MISMATCH) is a medium-severity fault affecting the Windows operating system. Cannot connect to a Windows file share. Error: 'The network path was not found' or 'Access denied' due to SMB signing policy conflict. Common triggers are outdated NAS firmware with SMB1 only and firewall blocking port 445. Follow the steps below to fix it.SPATIAL-SOUND-FAIL/error/SPATIAL-SOUND-FAIL/This low-severity issue affects the Windows operating system. Spatial sound format (Windows Sonic, Dolby Atmos, DTS) fails to activate or produces distorted output. It's also often linked to exclusive mode conflict. The steps below are ordered to resolve this efficiently.STATUS_ACCESS_VIOLATION/error/STATUS-ACCESS-VIOLATION/STATUS_ACCESS_VIOLATION shows up as a high-severity Windows operating system fault. The application attempted to access a protected area of memory. Most often an application or driver error. Common triggers are incompatible software and malware. Work through the steps below in order.STORAGE-SPACES-DEGRADED/error/STORAGE-SPACES-DEGRADED/Windows Storage Spaces pool degraded (STORAGE-SPACES-DEGRADED) is a critical-severity fault affecting the Windows operating system. 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. Follow the steps below to fix it.SVC-FAIL-Audiosrv/error/SVC-FAIL-Audiosrv/System Service Crash: Windows Sound is a medium-severity Windows operating system issue. The Audiosrv service terminated unexpectedly. Services dependent on this process may not work. The usual suspects are blocked by antivirus and missing permission. Work through the steps below in order.SVC-FAIL-BITS/error/SVC-FAIL-BITS/SVC-FAIL-BITS shows up as a medium-severity Windows operating system fault. The BITS service has terminated unexpectedly. Services dependent on this process may not work. This usually traces back to blocked by antivirus and missing permission. Use the steps below to track down and fix the cause.SVC-FAIL-CryptSvc/error/SVC-FAIL-CryptSvc/This medium-severity issue affects the Windows operating system. The CryptSvc service terminated unexpectedly. Services dependent on this process may not work. The usual suspects are blocked by antivirus and missing permission. Work through the steps below in order.SVC-FAIL-LanmanServer/error/SVC-FAIL-LanmanServer/SVC-FAIL-LanmanServer shows up as a medium-severity Windows operating system fault. The LanmanServer service terminated unexpectedly. Services dependent on this process may not work. This usually traces back to blocked by antivirus and missing permission. Follow the steps below to fix it.SVC-FAIL-LanmanWorkstation/error/SVC-FAIL-LanmanWorkstation/System service crashed: Workstation (SVC-FAIL-LanmanWorkstation) is a medium-severity fault affecting the Windows operating system. The LanmanWorkstation service terminated unexpectedly. Services dependent on this process may not work. Typical causes include blocked by antivirus and missing permission. Use the steps below to track down and fix the cause.SVC-FAIL-Spooler/error/SVC-FAIL-Spooler/System Service Crash: Print Spooler Service is a medium-severity Windows operating system issue. The Spooler service terminated unexpectedly. Services dependent on this process may not work. It's most often caused by blocked by antivirus and missing permission. The steps below are ordered to resolve this efficiently.SVC-FAIL-TermService/error/SVC-FAIL-TermService/SVC-FAIL-TermService shows up as a medium-severity Windows operating system fault. TermService terminated unexpectedly. Services dependent on this process may not work. Common triggers are blocked by antivirus and missing permission. Use the steps below to track down and fix the cause.SVC-FAIL-VSS/error/SVC-FAIL-VSS/SVC-FAIL-VSS is a medium-severity Windows operating system problem. The VSS service terminated unexpectedly. Services dependent on this process may not work. This usually traces back to blocked by antivirus and missing permission. Work through the steps below in order.SVC-FAIL-Winmgmt/error/SVC-FAIL-Winmgmt/System service crash: WMI (Winmgmt) ranks as a medium-severity Windows operating system issue in our database. The Winmgmt service terminated unexpectedly. Services dependent on this process may not work. Common triggers are blocked by antivirus and missing permission. Follow the steps below to fix it.SVC-FAIL-wuauserv/error/SVC-FAIL-wuauserv/System Service Crash: Windows Update ranks as a medium-severity Windows operating system issue in our database. The wuauserv service terminated unexpectedly. Services dependent on this process may not work. It's most often caused by blocked by antivirus and missing permission. Use the steps below to track down and fix the cause.TASK-SCHEDULER-ERR/error/TASK-SCHEDULER-ERR/Scheduled task fails with error 0x1 ranks as a medium-severity Windows operating system issue in our database. 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' mismatch. The steps below are ordered to resolve this efficiently.UNEXPECTED_KERNEL_MODE_TRAP/error/UNEXPECTED-KERNEL-MODE-TRAP/UNEXPECTED_KERNEL_MODE_TRAP shows up as a critical-severity Windows operating system fault. The CPU generated an interrupt that the kernel could not catch. Typically HW error or damaged driver. Common triggers are defective RAM, overclocking and high CPU temperature. Follow the steps below to fix it.USB-DEVICE-NOT-RECOGNIZED/error/USB-DEVICE-NOT-RECOGNIZED/USB Device Not Recognized is a medium-severity Windows operating system issue. Windows shows the 'USB Device Not Recognized' notification and the device is not functional. Typical causes include USB port providing insufficient power and USB root hub driver error. The steps below are ordered to resolve this efficiently.VULKAN-ERROR-OUT-OF-DATE-KHR/error/VULKAN-ERROR-OUT-OF-DATE-KHR/Vulkan: swapchain out of date (VK_ERROR_OUT_OF_DATE_KHR) is a medium-severity Windows operating system issue. The Vulkan surface has changed (window resize, alt-tab) and the swapchain needs to be recreated. Games may crash instead of handling this. See the troubleshooting steps below for the fix.VULKAN-VALIDATION-ERROR/error/VULKAN-VALIDATION-ERROR/Vulkan validation layer error ranks as a low-severity Windows operating system issue in our database. Vulkan validation layers report API usage errors. Usually only visible to developers but can cause crashes in debug builds. It's most often caused by wrong synchronization primitives and unsupported extension called. Follow the steps below to fix it.WIN-APP-CRASH-0xc0000005/error/WIN-APP-CRASH-0xc0000005/Access Violation when reading (Access Violation) ranks as a high-severity Windows operating system issue in our database. The application crashed with exception code 0xc0000005. This is a general memory access error. Common triggers are RAM incompatibility (XMP) and DEP (Data Execution Prevention) is blocking the. The steps below are ordered to resolve this efficiently.WIN-LICENSE-EXPIRE/error/WIN-LICENSE-EXPIRE/WIN-LICENSE-EXPIRE shows up as a low-severity Windows operating system fault. Windows pops up with a message that activation will expire. It also occurs frequently with legal systems of activated organizations (KMS). The usual suspects are error after hardware change and illegal activator lost functionality. The steps below are ordered to resolve this efficiently.WINDOWS-ACTIVATION-ERROR-0x803F7001/error/WINDOWS-ACTIVATION-ERROR-0x803F7001/WINDOWS-ACTIVATION-ERROR-0x803F7001 is a medium-severity Windows operating system problem. 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 linked to a Microsoft account, or after a clean Windows reinstall on a previously OEM-licensed system. The steps below are ordered to resolve this efficiently.WINDOWS-DEFENDER-STUCK/error/WINDOWS-DEFENDER-STUCK/WINDOWS-DEFENDER-STUCK shows up as a low-severity Windows operating system fault. 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. The steps below are ordered to resolve this efficiently.WINDOWS-ROLLBACK-STUCK/error/WINDOWS-ROLLBACK-STUCK/WINDOWS-ROLLBACK-STUCK is a high-severity Windows operating system problem. 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. Follow the steps below to fix it.WSL2-NETWORK-BROKEN/error/WSL2-NETWORK-BROKEN/WSL2 network not working after sleep/wake (WSL2-NETWORK-BROKEN) is a medium-severity fault affecting the Windows operating system. After the PC wakes from sleep, WSL2 has no internet connectivity. DNS fails and ping fails inside the subsystem. See the troubleshooting steps below for the fix.WU-0x800b0100/error/WU-0x800b0100/WU-0x800b0100 shows up as a high-severity Windows operating system fault. 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. See the troubleshooting steps below for the fix.WU-0x800f081f/error/WU-0x800f081f/Windows Update Error 0x800f081f (Source Files Missing) ranks as a high-severity Windows operating system issue in our database. This error code is triggered when the Deployment Image Servicing and Management (DISM) tool or Windows Update fails to install packages because the required source files to repair the local component store (WinSxS) are corrupted or missing. It's also often linked to lack of internet connection. Follow the steps below to fix it.WU-0x800f081f/error/WU-0x800f081f-2/WU-0x800f081f is a high-severity Windows operating system problem. The source files required for the Windows Update package could not be found, causing installation failure (often occurs during DISM deployment tasks or .NET Framework 3.5 updates). Work through the steps below in order.WU-0x800f0922/error/WU-0x800f0922/Windows Update Error 0x800f0922 (WU-0x800f0922) is a high-severity fault affecting the Windows operating system. Windows Update fails to install, typically caused by insufficient space in the System Reserved or EFI System Partition (ESP), Secure Boot configuration conflicts, or active VPN connection blocks. Follow the steps below to fix it.WU-0x800f0988/error/WU-0x800f0988/This high-severity issue affects the Windows operating system. Windows Update fails to install cumulative updates, typically caused by system language pack mismatches, corrupted update package files, or incomplete servicing stack logs. Use the steps below to track down and fix the cause.WU-0x80070bc2/error/WU-0x80070bc2/WU-0x80070bc2 shows up as a medium-severity Windows operating system fault. 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. It sometimes comes down to pending file rename operations in the registry are locked or stuck. The steps below are ordered to resolve this efficiently.WU-0x80072EE7/error/WU-0x80072EE7/Windows Update Failure (0x80072EE7) ranks as a medium-severity Windows operating system issue in our database. Windows cannot check for or install updates. Error code: 0x80072EE7. Typical causes include corrupt SoftwareDistribution folder and stopped BITS service. Use the steps below to track down and fix the cause.WU-0x8007000d/error/WU-0x8007000d/This medium-severity issue affects the Windows operating system. The update data is invalid. This error indicates that the downloaded update files are incomplete, corrupted, or have failed validation checks. Use the steps below to track down and fix the cause.WU-0x8007001F/error/WU-0x8007001F/Windows Update Failure (0x8007001F) is a medium-severity Windows operating system issue. Windows cannot check for or install updates. Error code: 0x8007001F. Reports of Windows Update Failure (0x8007001F) usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. Typical causes include corrupt SoftwareDistribution folder and stopped BITS service. Use the steps below to track down and fix the cause.WU-0x8009000B/error/WU-0x8009000B/WU-0x8009000B shows up as a medium-severity Windows operating system fault. Windows cannot check for or install updates. Error code: 0x8009000B. This usually traces back to corrupt SoftwareDistribution folder and stopped BITS service. Use the steps below to track down and fix the cause.WU-0x8024402c/error/WU-0x8024402c/Windows Update Error 0x8024402c is a high-severity Windows operating system issue. Windows Update connection fails. This error occurs when the update client is unable to connect to the Windows Update servers, usually due to incorrect proxy settings, custom firewall restrictions, or invalid DNS configurations. Use the steps below to track down and fix the cause.WU-0x80004005/error/WU-0x80004005/This medium-severity issue affects the Windows operating system. Windows cannot check for or install updates. Error code: 0x80004005. This usually traces back to corrupt SoftwareDistribution folder and stopped BITS service. See the troubleshooting steps below for the fix.WU-0x80070002/error/WU-0x80070002/WU-0x80070002 shows up as a medium-severity Windows operating system fault. Windows cannot check for or install updates. Error code: 0x80070002. Common triggers are corrupt SoftwareDistribution folder and stopped BITS service. Work through the steps below in order.WU-0x80070003/error/WU-0x80070003/This medium-severity issue affects the Windows operating system. The system cannot find the path specified, preventing Windows Update, Windows Backup, or installer services from accessing the target directories. The steps below are ordered to resolve this efficiently.WU-0x80070005/error/WU-0x80070005/WU-0x80070005 is a medium-severity Windows operating system problem. Windows cannot check for or install updates. Error code: 0x80070005. The usual suspects are corrupt SoftwareDistribution folder and stopped BITS service. See the troubleshooting steps below for the fix.WU-0x80070020/error/WU-0x80070020/Windows Update Error 0x80070020 is a medium-severity Windows operating system issue. The process cannot access the file because it is being used by another process. This occurs when Windows Update attempts to modify or copy critical system files that are locked by a background program or third-party security software. The steps below are ordered to resolve this efficiently.WU-0x80070057/error/WU-0x80070057/WU-0x80070057 is a medium-severity Windows operating system problem. Windows cannot check for or install updates. Error code: 0x80070057. Common triggers are corrupt SoftwareDistribution folder and stopped BITS service. Use the steps below to track down and fix the cause.WU-0x80070422/error/WU-0x80070422/Windows Update Failure (0x80070422) ranks as a medium-severity Windows operating system issue in our database. Windows cannot check for or install updates. Error code: 0x80070422. Common triggers are corrupt SoftwareDistribution folder and stopped BITS service. See the troubleshooting steps below for the fix.WU-0x80070424/error/WU-0x80070424/Windows Update Failure (0x80070424) is a medium-severity Windows operating system issue. Windows cannot check for or install updates. Error code: 0x80070424. Typical causes include corrupt SoftwareDistribution folder and stopped BITS service. The steps below are ordered to resolve this efficiently.WU-0x80070490/error/WU-0x80070490/This high-severity issue affects the Windows operating system. The Component Store or Component-Based Servicing (CBS) manifest file is corrupted, causing Windows Update installation attempts to fail. It's also often linked to registry corruption inside the HKEY_LOCAL_MACHINE\Components registry hive. Use the steps below to track down and fix the cause.WU-0x80070643/error/WU-0x80070643/WU-0x80070643 shows up as a medium-severity Windows operating system fault. Windows cannot check for or install updates. Error code: 0x80070643. The usual suspects are corrupt SoftwareDistribution folder and stopped BITS service. Work through the steps below in order.WU-0x80073701/error/WU-0x80073701/Windows Update Error 0x80073701 ranks as a high-severity Windows operating system issue in our database. The referenced assembly could not be found. This error indicates missing or corrupted assembly manifest files inside the Windows Component Store (WinSxS). Another common trigger is interrupted installation steps from previously attempted updates. Work through the steps below in order.WU-0x80240017/error/WU-0x80240017/Windows Update Error 0x80240017 ranks as a medium-severity Windows operating system issue in our database. 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. The steps below are ordered to resolve this efficiently.WU-0x80240020/error/WU-0x80240020/Windows Update Error 0x80240020 ranks as a medium-severity Windows operating system issue in our database. 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.WU-0x80244018/error/WU-0x80244018/WU-0x80244018 is a medium-severity Windows operating system problem. Connection to the Microsoft update servers is blocked, usually caused by custom proxy servers, custom firewall rules, or stale DNS resolver cache settings. The steps below are ordered to resolve this efficiently.WU-0x80246007/error/WU-0x80246007/Windows Update Error 0x80246007 ranks as a medium-severity Windows operating system issue in our database. The update failed to download. This error indicates that the Background Intelligent Transfer Service (BITS) has stopped or is misconfigured, preventing file retrieval. See the troubleshooting steps below for the fix.
Drivers / Controllers0x000000BE/error/ATTEMPTED-WRITE-TO-READONLY-MEMORY/0x000000BE is a medium-severity system driver problem. A driver attempted to write to a read-only segment of system memory. Work through the steps below in order.0x000000C4/error/DRIVER-VERIFIER-DETECTED-VIOLATION/This medium-severity issue affects the system driver. Driver Verifier detected a violation in a running kernel-mode driver. Use the steps below to track down and fix the cause.0x000000C5/error/DRIVER-CORRUPTED-EXPOOL/This high-severity issue affects the system driver. A driver attempted to access an invalid memory pool at an elevated IRQL. This can also stem from faulty system RAM. The steps below are ordered to resolve this efficiently.0x000000D8/error/0x000000D8/0x000000D8 shows up as a critical-severity system driver fault. 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. The steps below are ordered to resolve this efficiently.0x000001D1/error/0x000001D1/CHIPSET_LIVEDUMP (0x000001D1) is a medium-severity fault affecting the system driver. 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 saving settings, or VRM voltage sags. Follow the steps below to fix it.0x000001D4/error/0x000001D4/This medium-severity issue affects the system driver. 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. It sometimes comes down to conflicting external Thunderbolt/USB-C dock. Work through the steps below in order.0x80070005-AUDIO/error/0x80070005-AUDIO/0x80070005-AUDIO is a medium-severity system driver problem. The audio service cannot start because it doesn't have permissions to access the sound driver. This can also stem from antivirus blocking. See the troubleshooting steps below for the fix.ACPI-BIOS-ERROR/error/ACPI-BIOS-ERROR/ACPI_BIOS_ERROR BSOD ranks as a critical-severity system driver issue in our database. 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.AUDIO-NO-OUTPUT/error/AUDIO-NO-OUTPUT/This medium-severity issue affects the system driver. Windows says it doesn't see speakers or headphones. Another common trigger is disabled chip in BIOS. Work through the steps below in order.BSOD-amdkmdag.sys/error/BSOD-amdkmdag.sys/amdkmdag.sys critical driver error (BSOD) is a critical-severity system driver issue. 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. Use the steps below to track down and fix the cause.BSOD-classpnp.sys/error/BSOD-classpnp.sys/Classpnp.sys Driver Critical Error (BSOD) (BSOD-classpnp.sys) is a critical-severity fault affecting the system driver. 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. Use the steps below to track down and fix the cause.BSOD-dxgkrnl.sys/error/BSOD-dxgkrnl.sys/dxgkrnl.sys critical driver error (BSOD) is a critical-severity system driver issue. 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. Follow the steps below to fix it.BSOD-fltmgr.sys/error/BSOD-fltmgr.sys/BSOD-fltmgr.sys shows up as a critical-severity system driver fault. 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. Work through the steps below in order.BSOD-igdkmd64.sys/error/BSOD-igdkmd64.sys/BSOD-igdkmd64.sys shows up as a critical-severity system driver fault. 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. Use the steps below to track down and fix the cause.BSOD-ndis.sys/error/BSOD-ndis.sys/ndis.sys critical driver error (BSOD) (BSOD-ndis.sys) is a critical-severity fault affecting the system driver. 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. The steps below are ordered to resolve this efficiently.BSOD-ntfs.sys/error/BSOD-ntfs.sys/ntfs.sys critical driver error (BSOD) is a critical-severity system driver issue. Windows has terminated due to a fatal error in the ntfs.sys kernel module. It's most often caused by outdated or faulty driver, hardware incompatibility and conflict with antivirus. Work through the steps below in order.BSOD-nvlddmkm.sys/error/BSOD-nvlddmkm.sys/nvlddmkm.sys critical driver error (BSOD) (BSOD-nvlddmkm.sys) is a critical-severity fault affecting the system driver. Windows has terminated due to a fatal error in the nvlddmkm.sys kernel module. This usually traces back to outdated or faulty driver, hardware incompatibility and conflict with antivirus. Use the steps below to track down and fix the cause.BSOD-tcpip.sys/error/BSOD-tcpip.sys/BSOD-tcpip.sys is a critical-severity system driver problem. 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 out of nowhere. The usual suspects are hardware incompatibility and conflict with antivirus. The steps below are ordered to resolve this efficiently.BSOD-usbport.sys/error/BSOD-usbport.sys/This critical-severity issue affects the system driver. 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. The steps below are ordered to resolve this efficiently.CODE-10-DEVICE-CANNOT-START/error/CODE-10-DEVICE-CANNOT-START/CODE-10-DEVICE-CANNOT-START shows up as a medium-severity system driver fault. 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. See the troubleshooting steps below for the fix.CODE-43-USB/error/CODE-43-USB/USB device - Code 43 ranks as a medium-severity system driver issue in our database. Windows has stopped the USB device due to a reported problem. It sometimes comes down to corrupted USB driver. Follow the steps below to fix it.CODE-43-USB-HUB/error/CODE-43-USB-HUB/CODE-43-USB-HUB shows up as a medium-severity system driver fault. 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. Follow the steps below to fix it.CRITICAL_STRUCTURE_CORRUPTION/error/CRITICAL-STRUCTURE-CORRUPTION/Critical Structure Corruption BSOD (0x109) is a critical-severity system driver issue. A critical system kernel structure corruption occurred. The Windows kernel detected that a third-party driver or hardware modified critical kernel code or data structure. The steps below are ordered to resolve this efficiently.DDU-FAIL/error/DDU-FAIL/DDU clean uninstall failure (DDU-FAIL) is a low-severity fault affecting the system driver. 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 restrictive Antivirus. Follow the steps below to fix it.DRIVER_IRQL_NOT_LESS_OR_EQUAL/error/DRIVER-IRQL-NOT-LESS-OR-EQUAL/This critical-severity issue affects the system driver. The driver accessed memory at the wrong IRQL level. The most common type of BSOD. It sometimes comes down to corrupted INF file. Follow the steps below to fix it.DRIVER_POWER_STATE_FAILURE/error/DRIVER-POWER-STATE-FAILURE/DRIVER-POWER-STATE-FAILURE shows up as a high-severity system driver fault. Stop code 0x0000009F indicates a driver failed to handle a power management state change properly. This BSOD is triggered when Windows transitions power states (sleep, hibernate, resume) and a driver does not respond correctly to the IRP_MN_SET_POWER request. Very common on laptops after Windows updates change USB, network, or GPU driver power management behavior. Follow the steps below to fix it.DRIVER_POWER_STATE_FAILURE/error/DRIVER-POWER-STATE-FAILURE-2/Controller power status error ranks as a critical-severity system driver issue in our database. The driver returned an invalid power state when the system went to sleep or wake up. It's also often linked to hibernation problem. The steps below are ordered to resolve this efficiently.DRIVER-IRQL-MISMATCH/error/DRIVER-IRQL-MISMATCH/Driver IRQL mismatch (IRQL_NOT_LESS_OR_EQUAL variant) ranks as a critical-severity system driver issue in our database. A driver attempted to access memory at an incorrect IRQL level. Unlike standard IRQL_NOT_LESS_OR_EQUAL, this variant specifically indicates the driver is operating at a higher IRQL than allowed for the memory access type. Common in drivers that use spinlocks incorrectly or perform I/O at elevated interrupt levels, bypassing Windows kernel safety checks. The steps below are ordered to resolve this efficiently.DRIVER-VERIFIER-DMA-VIOLATION/error/DRIVER-VERIFIER-DMA-VIOLATION/DRIVER_VERIFIER_DMA_VIOLATION (0x000000E6) is a high-severity system driver issue. 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. When Driver Verifier is enabled and catches a driver performing DMA to unmapped or invalid memory regions, it immediately crashes the system to prevent silent memory corruption. Follow the steps below to fix it.DRIVER-VERIFIER-FAIL/error/DRIVER-VERIFIER-FAIL/DRIVER-VERIFIER-FAIL is a critical-severity system driver problem. Windows Driver Verifier detected illegal driver behavior in memory or IRQL. Use the steps below to track down and fix the cause.KERNEL-MODE-HEAP-CORRUPT/error/KERNEL-MODE-HEAP-CORRUPT/Kernel mode heap corruption is a critical-severity system driver issue. A kernel-mode driver corrupted the kernel heap. Results in unpredictable BSODs with varying stop codes. See the troubleshooting steps below for the fix.NVIDIA_NV_DISP_DLL_CRASH/error/NVIDIA-NV-DISP-DLL-CRASH/NVIDIA_NV_DISP_DLL_CRASH shows up as a critical-severity system driver fault. The NVIDIA display driver DLL (nvlddmkm.sys) crashed, causing the screen to go black, games to crash to desktop, or a blue screen of death (BSOD) with code VIDEO_TDR_FAILURE. The usual suspects are unstable GPU core or memory overclock, insufficient GPU power delivery and overheating graphics card memory or core. The steps below are ordered to resolve this efficiently.NVIDIA-CONTAINER-HIGH-CPU/error/NVIDIA-CONTAINER-HIGH-CPU/This low-severity issue affects the system driver. 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. The steps below are ordered to resolve this efficiently.SYSTEM_SERVICE_EXCEPTION/error/SYSTEM-SERVICE-EXCEPTION/SYSTEM_SERVICE_EXCEPTION (0x0000003B) is a critical-severity system driver issue. The SYSTEM_SERVICE_EXCEPTION bug check indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. Most commonly caused by graphic card drivers or system service conflicts. Work through the steps below in order.SYSTEM-THREAD-EXCEPTION/error/SYSTEM-THREAD-EXCEPTION/SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (SYSTEM-THREAD-EXCEPTION) is a critical-severity fault affecting the system driver. A system thread threw an unhandled exception, most commonly a bad driver (.sys) file. Work through the steps below in order.USB-SELECTIVE-SUSPEND/error/USB-SELECTIVE-SUSPEND/This medium-severity issue affects the system driver. 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. Work through the steps below in order.
DirectX / Graphics API
DXGI_ERROR_DEVICE_REMOVED/error/DXGI-ERROR-DEVICE-REMOVED/DXGI_ERROR_DEVICE_REMOVED shows up as a high-severity graphics API (DirectX) fault. DirectX has lost access to the GPU. The game or application crashes. Typical causes include GPU OC, overheating, defective driver and insufficient power supply. Use the steps below to track down and fix the cause.D3D-INIT-ERROR/error/D3D-INIT-ERROR/This high-severity issue affects the graphics API (DirectX). The application cannot initialize Direct3D. The GPU or driver does not support the required version. The usual suspects are outdated GPU Drivers and corrupt DX installation. See the troubleshooting steps below for the fix.DIRECTX-FEATURE-LEVEL/error/DIRECTX-FEATURE-LEVEL/This medium-severity issue affects the graphics API (DirectX). The application requires DirectX Feature Level 11.0 or higher, which is not supported by the GPU. This can also stem from outdated Driver. Follow the steps below to fix it.OPENCL-INIT-FAIL/error/OPENCL-INIT-FAIL/OpenCL initialization failed (OPENCL-INIT-FAIL) is a medium-severity fault affecting the graphics API (DirectX). An application or software cannot initialize the OpenCL interface for GPU computation. Another common trigger is incompatible GPU. Work through the steps below in order.DXGI_ERROR_DEVICE_REMOVED/error/DXGI-ERROR-DEVICE-REMOVED-2/Graphics adapter has been disconnected (DXGI_ERROR_DEVICE_REMOVED) is a high-severity fault affecting the graphics API (DirectX). The Direct3D device has been removed or the driver has crashed. It's most often caused by unstable GPU overclocking and card overheating. Work through the steps below in order.DXGI_ERROR_DEVICE_HUNG/error/DXGI-ERROR-DEVICE-HUNG-2/Video adapter freezing (DXGI_ERROR_DEVICE_HUNG) is a high-severity fault affecting the graphics API (DirectX). The application sent an invalid command and the GPU became unresponsive. This usually traces back to game error, underclocking/overclocking too aggressively and VRAM memory corruption. Work through the steps below in order.D3D11_ERROR_OUT_OF_MEMORY/error/D3D11-ERROR-OUT-OF-MEMORY/D3D11_ERROR_OUT_OF_MEMORY is a medium-severity graphics API (DirectX) problem. The game or program has exhausted the available VRAM on the graphics card. It's also often linked to texture resolution too high. Work through the steps below in order.DXGI_ERROR_INVALID_CALL/error/DXGI-ERROR-INVALID-CALL/Invalid call to API function is a high-severity graphics API (DirectX) issue. The application provided incorrect parameters to DirectX. The usual suspects are software developer error and corrupted system files. The steps below are ordered to resolve this efficiently.D3D12_ERROR_ADAPTER_NOT_FOUND/error/D3D12-ERROR-ADAPTER-NOT-FOUND/DX12 compatible GPU not found is a critical-severity graphics API (DirectX) issue. The application requires DirectX 12 Feature Level, which the graphics card does not support. Common triggers are old hardware and missing driver. Follow the steps below to fix it.DXGI_ERROR_WAS_STILL_DRAWING/error/DXGI-ERROR-WAS-STILL-DRAWING/Image rendering conflict is a low-severity graphics API (DirectX) issue. 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. Use the steps below to track down and fix the cause.D3D_COMPILER_ERROR/error/D3D-COMPILER-ERROR/Failed to compile HLSL shader is a high-severity graphics API (DirectX) issue. The driver failed to compile the shader program for the graphics card. It sometimes comes down to unreadable game files. The steps below are ordered to resolve this efficiently.DXGI_ERROR_UNSUPPORTED/error/DXGI-ERROR-UNSUPPORTED/This medium-severity issue affects the graphics API (DirectX). 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. Follow the steps below to fix it.DXGI_ERROR_ACCESS_DENIED/error/DXGI-ERROR-ACCESS-DENIED/DXGI_ERROR_ACCESS_DENIED is a medium-severity graphics API (DirectX) problem. 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 for security reasons. Common in gaming environments with overlays, screen capture software, or virtual display drivers active. Use the steps below to track down and fix the cause.DXGI_ERROR_ACCESS_DENIED/error/DXGI-ERROR-ACCESS-DENIED-2/DirectX resource access denied ranks as a medium-severity graphics API (DirectX) issue in our database. The application does not have rights or the resource is exclusively locked by another program. Another common trigger is conflict with recording software (OBS, Shadowplay). Follow the steps below to fix it.DXGI_ERROR_NOT_CURRENT/error/DXGI-ERROR-NOT-CURRENT/DXGI_ERROR_NOT_CURRENT is a low-severity graphics API (DirectX) problem. 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). Work through the steps below in order.D3D11_ERROR_FILE_NOT_FOUND/error/D3D11-ERROR-FILE-NOT-FOUND/Missing DirectX system library is a high-severity graphics API (DirectX) issue. The requested file (eg d3dx11_43.dll) was not found in the system. This can also stem from older game requiring DX9 components. Work through the steps below in order.DXGI_ERROR_MODE_CHANGE_IN_PROGRESS/error/DXGI-ERROR-MODE-CHANGE-IN-PROGRESS/DXGI_ERROR_MODE_CHANGE_IN_PROGRESS shows up as a low-severity graphics API (DirectX) fault. Call failure due to resolution or refresh rate change in progress. This can also stem from quick alt-tab switching. See the troubleshooting steps below for the fix.D3D12_ERROR_NOT_SUPPORTED_OS/error/D3D12-ERROR-NOT-SUPPORTED-OS/The Windows version does not support DX12 is a critical-severity graphics API (DirectX) issue. DirectX 12 requires a newer build of Windows 10/11. The steps below are ordered to resolve this efficiently.DXGI_ERROR_DRIVER_INTERNAL_ERROR/error/DXGI-ERROR-DRIVER-INTERNAL-ERROR/DXGI_ERROR_DRIVER_INTERNAL_ERROR is a high-severity graphics API (DirectX) problem. The video card driver encountered an error and could not complete the operation. It's also often linked to conflict with Windows update. Use the steps below to track down and fix the cause.D3D11_CREATE_DEVICE_FAIL/error/D3D11-CREATE-DEVICE-FAIL/D3D11_CREATE_DEVICE_FAIL is a critical-severity graphics API (DirectX) problem. CreateDevice failed, probably hardware not responding. It sometimes comes down to using the Microsoft Basic Display Driver. Follow the steps below to fix it.DXGI_ERROR_NONEXCLUSIVE/error/DXGI-ERROR-NONEXCLUSIVE/DXGI_ERROR_NONEXCLUSIVE shows up as a medium-severity graphics API (DirectX) fault. 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). Work through the steps below in order.D3D12_RAYTRACING_UNSUPPORTED/error/D3D12-RAYTRACING-UNSUPPORTED/D3D12_RAYTRACING_UNSUPPORTED is a high-severity graphics API (DirectX) problem. 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). See the troubleshooting steps below for the fix.DXGI_ERROR_FRAME_STATISTICS_DISJOINT/error/DXGI-ERROR-FRAME-STATISTICS-DISJOINT/DXGI_ERROR_FRAME_STATISTICS_DISJOINT shows up as a low-severity graphics API (DirectX) fault. 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). Use the steps below to track down and fix the cause.D3D_SHADER_LINK_ERROR/error/D3D-SHADER-LINK-ERROR/D3D_SHADER_LINK_ERROR shows up as a medium-severity graphics API (DirectX) fault. 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). Follow the steps below to fix it.DXGI_ERROR_WAIT_TIMEOUT/error/DXGI-ERROR-WAIT-TIMEOUT/This high-severity issue affects the graphics API (DirectX). 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. Work through the steps below in order.D3D12_ERROR_OUT_OF_MEMORY/error/D3D12-ERROR-OUT-OF-MEMORY/DirectX 12 Out of Memory (D3D12_ERROR_OUT_OF_MEMORY) is a high-severity fault affecting the graphics API (DirectX). 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. It sometimes comes down to high resolution textures. Use the steps below to track down and fix the cause.DXGI_ERROR_DEVICE_RESET/error/DXGI-ERROR-DEVICE-RESET/DXGI_ERROR_DEVICE_RESET shows up as a high-severity graphics card (GPU) fault. DXGI_ERROR_DEVICE_RESET (error code 0x887A0007) indicates the GPU device was reset due to a driver issue or hardware fault. Unlike DEVICE_REMOVED, this error specifically occurs when the GPU has been reset by the OS after a driver hang. It is commonly seen in DirectX 11/12 games and applications that rely on DXGI swap chains. This usually traces back to unstable GPU overclock and overheating VRAM or GPU core. Work through the steps below in order.DXGI_ERROR_DEVICE_RESET/error/DXGI-ERROR-DEVICE-RESET-2/This high-severity issue affects the graphics API (DirectX). The application must be re-initialized. Typical causes include outdated graphics driver, unstable GPU overclock, system power state transition and background Windows Update installing new drivers. See the troubleshooting steps below for the fix.DIRECTX_OUT_OF_VRAM/error/DIRECTX-OUT-OF-VRAM/DirectX Out of Video Memory / Crash is a high-severity graphics API (DirectX) issue. 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, resulting in a crash to desktop. Follow the steps below to fix it.D3D11-FEATURE-LEVEL-NOT-SUPPORTED/error/D3D11-FEATURE-LEVEL-NOT-SUPPORTED/This medium-severity issue affects the graphics API (DirectX). 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 require 11_1 or 12_0. This affects very old GPUs (pre-2008) or virtual machines without proper GPU passthrough. It sometimes comes down to directX installation corrupted. See the troubleshooting steps below for the fix.d3dx9_43.dll missing/error/d3dx9_43.dll-missing/This medium-severity issue affects the graphics API (DirectX). A legacy game or program requires the DirectX 9 runtime library (d3dx9_43.dll) to launch, but the file is missing from your system. Reports of Legacy DirectX 9 component missing usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. It's also often linked to incorrect application folder installation paths. See the troubleshooting steps below for the fix.DirectX Function Error/error/DIRECTX-FUNCTION-ERROR/DirectX Function Error shows up as a high-severity graphics API (DirectX) fault. 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. Use the steps below to track down and fix the cause.Runtimes / Frameworks0xc000007b/error/0xc000007b/0xc000007b shows up as a high-severity software runtime fault. An application built for a 64-bit architecture tries to load a 32-bit library (or vice versa). It's most often caused by confusion in System32 and SysWOW64 folders (mixed DLLs) and corrupt DirectX/VC++ installation. See the troubleshooting steps below for the fix.0xC000012F/error/0xC000012F/0xC000012F is a medium-severity software runtime problem. 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 when launching games or specialized software after partial updates. Another common trigger is damaged application or system DLL files. See the troubleshooting steps below for the fix.0xc0000142/error/0xc0000142/Error initializing application is a medium-severity software runtime issue. 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. Use the steps below to track down and fix the cause.BATTLEYE-KICK/error/BATTLEYE-KICK/BattlEye anti-cheat blocked launch ranks as a high-severity software runtime issue in our database. 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). Follow the steps below to fix it.DLL_MISSING_MSVCP140/error/DLL-MISSING-MSVCP140/MSVCP140.dll / VCRUNTIME140.dll Missing ranks as a medium-severity software runtime issue in our database. An application error dialog stating that the program cannot start because MSVCP140.dll or VCRUNTIME140.dll was not found on your system. This DLL is part of the Microsoft Visual C++ Redistributable framework. Another common trigger is file corrupted or deleted by antivirus. Follow the steps below to fix it.DLL-FAULT-d3d11.dll/error/DLL-FAULT-d3d11.dll/Missing or corrupt library d3d11.dll is a high-severity software runtime issue. 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. Follow the steps below to fix it.DLL-FAULT-dxgi.dll/error/DLL-FAULT-dxgi.dll/Missing or corrupt dxgi.dll library (DLL-FAULT-dxgi.dll) is a high-severity fault affecting the software runtime. 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. The steps below are ordered to resolve this efficiently.DLL-FAULT-hal.dll/error/DLL-FAULT-hal.dll/This high-severity issue affects the software runtime. 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. Work through the steps below in order.DLL-FAULT-kernel32.dll/error/DLL-FAULT-kernel32.dll/DLL-FAULT-kernel32.dll shows up as a high-severity software runtime fault. 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. Follow the steps below to fix it.DLL-FAULT-msvcp140.dll/error/DLL-FAULT-msvcp140.dll/DLL-FAULT-msvcp140.dll shows up as a high-severity software runtime fault. The application could not be started because the msvcp140.dll module threw an exception or was not found. Common triggers are deleted library file, incompatible version of Visual C++ and malware Damage. See the troubleshooting steps below for the fix.DLL-FAULT-ntdll.dll/error/DLL-FAULT-ntdll.dll/Missing or corrupt library ntdll.dll is a high-severity software runtime issue. 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. Work through the steps below in order.DLL-FAULT-ucrtbase.dll/error/DLL-FAULT-ucrtbase.dll/Missing or corrupt library ucrtbase.dll (DLL-FAULT-ucrtbase.dll) is a high-severity fault affecting the software runtime. 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. Work through the steps below in order.DLL-FAULT-user32.dll/error/DLL-FAULT-user32.dll/Missing or corrupt library user32.dll ranks as a high-severity software runtime issue in our database. 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. The steps below are ordered to resolve this efficiently.DLL-FAULT-vcruntime140.dll/error/DLL-FAULT-vcruntime140.dll/Missing or corrupt library vcruntime140.dll ranks as a high-severity software runtime issue in our database. The application could not be started because the vcruntime140.dll module threw an exception or was not found. Reports of Missing or corrupt library vcruntime140.dll usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing out of nowhere. It's most often caused by incompatible version of Visual C++ and malware Damage. Use the steps below to track down and fix the cause.DLL-FAULT-xinput1_3.dll/error/DLL-FAULT-xinput1-3.dll/Missing or corrupt library xinput1_3.dll is a high-severity software runtime issue. The application could not be started because the xinput1_3.dll module threw an exception or was not found. Common triggers are deleted library file, incompatible version of Visual C++ and malware Damage. The steps below are ordered to resolve this efficiently.DLL-NOT-FOUND/error/DLL-NOT-FOUND/DLL file not found is a medium-severity software runtime issue. The application cannot find the required DLL and will not start. It's most often caused by missing redistributable packages, deleted DLL and malware. See the troubleshooting steps below for the fix.DOTNET-FRAMEWORK-INSTALL-FAIL/error/DOTNET-FRAMEWORK-INSTALL-FAIL/.NET Framework installation failure (DOTNET-FRAMEWORK-INSTALL-FAIL) is a medium-severity fault affecting the software runtime. The .NET Framework installation or update fails with errors such as 0x80070002, 0x800F081F, or 'HRESULT 0x800f0906'. Many Windows applications and system tools depend on specific .NET Framework versions (2.0, 3.5, 4.8). The most common failure is .NET 3.5 requiring Windows installation media to install the optional Windows feature. The steps below are ordered to resolve this efficiently.EPIC-GAMES-0004/error/EPIC-GAMES-0004/EPIC-GAMES-0004 is a medium-severity software runtime problem. 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 (VC++, .NET). The steps below are ordered to resolve this efficiently.GAME-EAC-VIOLATION/error/GAME-EAC-VIOLATION/This high-severity issue affects the software runtime. 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. Work through the steps below in order.INSTALLER-ERROR-1603/error/INSTALLER-ERROR-1603/Windows Installer error 1603 ranks as a medium-severity software runtime issue in our database. Fatal error installing MSI package. Installation failed. The usual suspects are insufficient permissions, corrupt installer and full disk. Use the steps below to track down and fix the cause.MSVCP140-DLL-MISSING/error/MSVCP140-DLL-MISSING/MSVCP140-DLL-MISSING shows up as a medium-severity software runtime fault. MSVCP140.dll is the C++ Standard Library implementation distributed as part of the Microsoft Visual C++ 2015-2022 Redistributable. Applications compiled with MSVC need this DLL for STL containers, algorithms, streams, and other C++ standard library features. Its absence blocks application launch entirely. This usually traces back to DLL accidentally deleted and antivirus quarantined the file. Use the steps below to track down and fix the cause.MSVCR140-MISSING/error/MSVCR140-MISSING/MSVCR140-MISSING is a medium-severity software runtime problem. 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. Follow the steps below to fix it.NET-FRAMEWORK-ERROR/error/NET-FRAMEWORK-ERROR/This medium-severity issue affects the software runtime. The application requires the .NET Framework, which is missing or corrupted. This can also stem from version conflict. The steps below are ordered to resolve this efficiently.PYTHON-DLL-LOAD/error/PYTHON-DLL-LOAD/Error loading Python DLL is a low-severity software runtime issue. Python cannot load the required DLL (python3xx.dll). The application or script does not start. This can also stem from missing VC++ redistributable package. Follow the steps below to fix it.STATUS-ACCESS-VIOLATION/error/STATUS-ACCESS-VIOLATION-2/STATUS-ACCESS-VIOLATION is a medium-severity software runtime problem. A process attempted to read or write to a memory address to which it does not have appropriate access permissions. Extremely common in web browsers (Chrome, Edge) and gaming applications. This can also stem from unstable RAM overclocking (XMP/EXPO) causing calculation discrepancies. See the troubleshooting steps below for the fix.STEAM_DISK_WRITE_ERROR/error/STEAM-DISK-WRITE-ERROR/Steam Disk Write Error is a high-severity software runtime issue. Steam download or update is interrupted because Steam cannot write game files to your storage drive. Typically caused by folder permission conflicts, corrupted drive sectors, or active antivirus lockups. The steps below are ordered to resolve this efficiently.STEAM-CONTENT-FILE-LOCKED/error/STEAM-CONTENT-FILE-LOCKED/Steam: content file locked ranks as a medium-severity software runtime issue in our database. Steam cannot update a game and reports 'An error occurred while updating [Game] (content file locked)'. See the troubleshooting steps below for the fix.STEAM-DISK-WRITE-ERR/error/STEAM-DISK-WRITE-ERR/STEAM-DISK-WRITE-ERR shows up as a medium-severity software runtime fault. 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. See the troubleshooting steps below for the fix.VCRUNTIME-MISSING/error/VCRUNTIME-MISSING/Missing Visual C++ Runtime ranks as a medium-severity software runtime issue in our database. The application requires the Visual C++ Redistributable, which is missing. It's also often linked to corrupt runtime files. The steps below are ordered to resolve this efficiently.VCRUNTIME140-DLL-MISSING/error/VCRUNTIME140-DLL-MISSING/VCRUNTIME140-DLL-MISSING is a medium-severity software runtime problem. The error 'VCRUNTIME140.dll was not found' indicates the Visual C++ 2015-2022 Redistributable runtime library is missing or corrupted. VCRUNTIME140.dll is part of the Microsoft Visual C++ Redistributable package and is required by thousands of modern Windows applications, games, and tools compiled with MSVC 2015 or later. The steps below are ordered to resolve this efficiently.VCRUNTIME140-DLL-MISSING/error/VCRUNTIME140-DLL-MISSING-2/VCRUNTIME140.dll is missing (VCRUNTIME140-DLL-MISSING) is a high-severity fault affecting the software runtime. The application cannot start because the file VCRUNTIME140.dll or MSVCP140.dll is missing. Common triggers are uninstalled Microsoft Visual C++ 2015-2022 Redistributable and deleting DLL files by user or antivirus. Follow the steps below to fix it.
Software BIOS / Firmware
BIOS-BOOT-LOOP/error/BIOS-BOOT-LOOP/BIOS-BOOT-LOOP is a critical-severity firmware problem. The PC restarts in an endless loop after POST. Problem with UEFI boot records or corrupted BCD. The usual suspects are damaged BCD and bad EFI entry. The steps below are ordered to resolve this efficiently.UEFI-SHELL-ERROR/error/UEFI-SHELL-ERROR/UEFI-SHELL-ERROR shows up as a high-severity firmware fault. The system booted into the UEFI shell instead of the OS. The boot record is missing or corrupted. Another common trigger is deleted EFI partition. The steps below are ordered to resolve this efficiently.FIRMWARE-ROLLBACK-BLOCKED/error/FIRMWARE-ROLLBACK-BLOCKED/FIRMWARE-ROLLBACK-BLOCKED shows up as a medium-severity firmware fault. An attempt to downgrade the BIOS was blocked by board protection or Intel Boot Guard. The steps below are ordered to resolve this efficiently.NVRAM-FULL/error/NVRAM-FULL/NVRAM-FULL shows up as a medium-severity firmware fault. UEFI NVRAM is full of variables. It causes boot problems and the inability to save settings. Typical causes include many installed OS, old EFI records and bug in firmware. Use the steps below to track down and fix the cause.CSM-CONFLICT/error/CSM-CONFLICT/CSM-CONFLICT shows up as a medium-severity firmware fault. Compatibility Support Module (CSM) conflicts with UEFI OS or Secure Boot. It's also often linked to old OS installed in Legacy mode. See the troubleshooting steps below for the fix.UEFI-BOOT-LOOP/error/UEFI-BOOT-LOOP/System stuck in loop into UEFI/BIOS is a critical-severity firmware issue. 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). See the troubleshooting steps below for the fix.CSM-CONFLICT-VGA/error/CSM-CONFLICT-VGA/Conflict between UEFI and old graphics driver (CSM-CONFLICT-VGA) is a high-severity fault affecting the firmware. 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. Use the steps below to track down and fix the cause.SEC-BOOT-VIOLATION/error/SEC-BOOT-VIOLATION/Violation of Secure Boot rules ranks as a high-severity firmware issue in our database. System boot stopped due to unsigned bootloader or driver. This usually traces back to installing Linux (Grub) or modified Windows and unofficial drivers on. Follow the steps below to fix it.NVRAM-FULL-ERR/error/NVRAM-FULL-ERR/This high-severity issue affects the firmware. The NVRAM memory capacity for storing boot variables is full. It's most often caused by too many OS installed and UEFI error (eg creating duplicate entries). Follow the steps below to fix it.UEFI-SHELL-FALLBACK/error/UEFI-SHELL-FALLBACK/Drop into the built-in EFI Shell is a critical-severity firmware issue. 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. Work through the steps below in order.ME-FW-UPDATE-FAIL/error/ME-FW-UPDATE-FAIL/This critical-severity issue affects the firmware. The Intel Management Engine firmware update failed or was interrupted. This can also stem from power interruption while flashing. Work through the steps below in order.AMD-AGESA-MICROCODE/error/AMD-AGESA-MICROCODE/This high-severity issue affects the firmware. The installed processor is not fully supported by the current version of AGESA libraries in the BIOS. Follow the steps below to fix it.ACPI-TABLE-CORRUPT/error/ACPI-TABLE-CORRUPT/This high-severity issue affects the firmware. Windows BSOD ACPI_BIOS_ERROR due to faulty BIOS power management configuration. Follow the steps below to fix it.FAST-BOOT-HANG/error/FAST-BOOT-HANG/This medium-severity issue affects the firmware. The computer won't start because it's stuck in the fast boot phase. This can also stem from incompatible USB device connected. Follow the steps below to fix it.BIOS-PWD-LOCKOUT/error/BIOS-PWD-LOCKOUT/BIOS-PWD-LOCKOUT is a critical-severity firmware problem. Access to the computer is blocked due to an unknown UEFI administrator password. The steps below are ordered to resolve this efficiently.SSD-FIRMWARE-BRICK/error/SSD-FIRMWARE-BRICK/SSD firmware update bricked drive is a critical-severity firmware issue. 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. Some SSD manufacturers have utilities that can attempt firmware recovery mode via USB, but data recovery is rarely possible without professional services. Use the steps below to track down and fix the cause.INTEL-ME-FIRMWARE-ERROR/error/INTEL-ME-FIRMWARE-ERROR/INTEL-ME-FIRMWARE-ERROR is a high-severity firmware problem. The Intel Management Engine (ME) — a separate microcontroller embedded in Intel chipsets — has reported a firmware error. The ME handles out-of-band management, AMT (Active Management Technology), and hardware security features. ME errors can prevent the system from booting, cause unexpected shutdowns, or display as error codes in the BIOS POST screen. See the troubleshooting steps below for the fix.Malware & Virus Database
Malware / Security
ADWARE_POPUP_LOOP/error/ADWARE-POPUP-LOOP/Background Adware Pop-up Generator ranks as a low-severity malware/security issue in our database. 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 software bundles bundled with Potentially Unwanted Applications (PUA). Follow the steps below to fix it.BROWSER_HIJACKER_REDIRECT/error/BROWSER-HIJACKER-REDIRECT/BROWSER_HIJACKER_REDIRECT shows up as a medium-severity malware/security fault. 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 bundled during free software package installations. Use the steps below to track down and fix the cause.DNS_HOSTS_REDIRECT/error/DNS-HOSTS-REDIRECT/DNS_HOSTS_REDIRECT shows up as a high-severity malware/security fault. 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 in order.HIGH_CPU_CRYPTOMINER/error/HIGH-CPU-CRYPTOMINER/Unauthorized Background Cryptocurrency Miner (High CPU/GPU) is a high-severity malware/security issue. 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 system slowdown. See the troubleshooting steps below for the fix.KEYLOGGER_TROJAN_SPY/error/KEYLOGGER-TROJAN-SPY/Keyboard Logger and Spyware Trojan is a critical-severity malware/security issue. 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 downloading infected software utilities and use of compromised public network access. See the troubleshooting steps below for the fix.RANSOMWARE_ENCRYPTION_ATTACK/error/RANSOMWARE-ENCRYPTION-ATTACK/This critical-severity issue affects the malware/security. 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 executing unverified attachments or cracked software payloads, compromised Server Message Block (SMB) exposures on local networks and outdated security configuration allowing remote code execution. Use the steps below to track down and fix the cause.SECURITY_SERVICE_DISABLED/error/SECURITY-SERVICE-DISABLED/Security Center Service Blockage (Defender Disabler) ranks as a critical-severity malware/security issue in our database. 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 malicious scripts executed with administrative privileges. The steps below are ordered to resolve this efficiently.WANNACRY_RANSOMWARE/error/WANNACRY-RANSOMWARE/WANNACRY_RANSOMWARE shows up as a critical-severity malware/security fault. 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) in the SMBv1 protocol. It's most often caused by exposure of port 445 directly to the internet and lack of endpoint security monitoring. Follow the steps below to fix it.PETYA_NOTPETYA_WIPER/error/PETYA-NOTPETYA-WIPER/Petya / NotPetya Ransomware-Wiper is a critical-severity malware/security issue. 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 the operating system from booting. It's most often caused by SMB vulnerabilities (EternalBlue/EternalRomance) on unpatched machines, compromised administrative credentials harvested via Mimikatz-like methods and malicious updates in accounting software supply chains. The steps below are ordered to resolve this efficiently.EMOTET_BOTNET_LOADER/error/EMOTET-BOTNET-LOADER/This critical-severity issue affects the malware/security. 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 laterally across networks. Work through the steps below in order.RYUK_RANSOMWARE/error/RYUK-RANSOMWARE/Ryuk Enterprise Ransomware is a critical-severity malware/security issue. 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 lateral movement. It sometimes comes down to compromised Remote Desktop Protocol (RDP) entry points. See the troubleshooting steps below for the fix.LOCKBIT_3_RANSOMWARE/error/LOCKBIT-3-RANSOMWARE/LockBit 3.0 (LockBit Black) Ransomware ranks as a critical-severity malware/security issue in our database. 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 multi-threaded engine while stealing sensitive data for extortion. The usual suspects are exploiting vulnerabilities in VPNs and edge firewalls, phishing campaigns containing malicious script attachments and compromised administrative credentials. Use the steps below to track down and fix the cause.QAKBOT_STEALER_BACKDOOR/error/QAKBOT-STEALER-BACKDOOR/Qbot / Qakbot Info-Stealer & Backdoor (QAKBOT_STEALER_BACKDOOR) is a high-severity fault affecting the malware/security. 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 Black Basta. Common triggers are drive-by downloads on compromised web pages and lateral movement via SMB share exploits. Follow the steps below to fix it.REDLINE_INFO_STEALER/error/REDLINE-INFO-STEALER/RedLine Information Stealer is a high-severity malware/security issue. 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 infected hosts. Typical causes include downloading cracked software, game cheats, or keygens from untrusted sites, malicious phishing emails containing obfuscated loaders and social engineering attachments on messaging platforms. Work through the steps below in order.CLOP_RANSOMWARE/error/CLOP-RANSOMWARE/Clop Ransomware (MOVEit Exploit) ranks as a critical-severity malware/security issue in our database. 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), to steal data and demand ransom without initially encrypting systems. It's also often linked to direct exposure of administrative panels to the public internet. The steps below are ordered to resolve this efficiently.LAZARUS_BLUENOROFF_APT/error/LAZARUS-BLUENOROFF-APT/LAZARUS_BLUENOROFF_APT is a critical-severity malware/security problem. 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 sophisticated custom malware, trojanized applications, and spear-phishing. It's also often linked to exploitation of public-facing server vulnerabilities. See the troubleshooting steps below for the fix.VOLT_TYPHOON_APT/error/VOLT-TYPHOON-APT/VOLT_TYPHOON_APT is a critical-severity malware/security problem. 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 blend in with normal system activity and maintain long-term undetected persistence. Common triggers are compromised edge devices (SOHO routers, firewalls, VPN appliances) and lack of command-line logging and network telemetry monitoring. Use the steps below to track down and fix the cause.ROOTKIT-DETECTED/error/ROOTKIT-DETECTED/Kernel rootkit detected (ROOTKIT-DETECTED) is a critical-severity fault affecting the malware/security. 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. They intercept system calls to conceal malicious processes, files, and network connections. Detection is typically only possible with specialized offline scanners or Secure Boot verification checks. Another common trigger is exploitation of signed driver vulnerabilities. See the troubleshooting steps below for the fix.CRYPTOMINER-HIGH-CPU/error/CRYPTOMINER-HIGH-CPU/Cryptominer malware (high CPU/GPU usage) is a high-severity malware/security issue. 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 slowdowns. Miners often disguise themselves as system processes or inject into legitimate processes like svchost.exe or browser extensions. It's also often linked to trojanized software download. Use the steps below to track down and fix the cause.