Drivers errors
36 errors. Choose the message that matches your computer.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
The driver accessed memory at the wrong IRQL level. The most common type of BSOD.
DriversCODE-43-USB
Windows has stopped the USB device due to a reported problem. It sometimes comes down to corrupted USB driver.
DriversDRIVER_POWER_STATE_FAILURE
The driver returned an invalid power state when the system went to sleep or wake up. It's also often linked to hibernation problem.
DriversDRIVER-VERIFIER-FAIL
Windows Driver Verifier detected illegal driver behavior in memory or IRQL. Use the steps below to track down and fix the cause.
DriversSYSTEM-THREAD-EXCEPTION
A system thread threw an unhandled exception, most commonly a bad driver (.sys) file. Work through the steps below in order.
DriversDDU-FAIL
The Display Driver Uninstaller (DDU) failed to completely remove the old GPU drivers, preventing a new installation. Common triggers are DDU was not started in safe mode, active Windows Update in the background and…
DriversCODE-10-DEVICE-CANNOT-START
Windows Device Manager reported that the device could not start due to a failure to load or a faulty driver. Another common trigger is incompatibility with the.
DriversBSOD-ndis.sys
Windows has terminated due to a fatal error in the kernel module ndis.sys. Typical causes include outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-tcpip.sys
Windows has terminated due to a fatal error in the tcpip.sys kernel module. Reports of Critical tcpip.sys driver error (BSOD) usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing…
DriversBSOD-usbport.sys
Windows has terminated due to a fatal error in the usbport.sys kernel module. This usually traces back to outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-fltmgr.sys
Windows has terminated due to a fatal error in the fltmgr.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-ntfs.sys
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.
DriversBSOD-classpnp.sys
Windows has terminated due to a fatal error in the classpnp.sys kernel module. It's most often caused by outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-dxgkrnl.sys
Windows has terminated due to a fatal error in the dxgkrnl.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-igdkmd64.sys
Windows has terminated due to a fatal error in the igdkmd64.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-amdkmdag.sys
Windows has terminated due to a fatal error in the kernel module amdkmdag.sys. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-nvlddmkm.sys
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.
DriversAUDIO-NO-OUTPUT
Windows says it doesn't see speakers or headphones. Another common trigger is disabled chip in BIOS.
DriversCODE-43-USB-HUB
The entire USB controller reports code 43, which disconnects all USB ports on the given group. Common triggers are corrupt USB xHCI Driver and driver conflict after windows update.
DriversNVIDIA-CONTAINER-HIGH-CPU
The nvcontainer.exe or NvTelemetryContainer.exe processes constantly consume 5-20% CPU even when idle. It's most often caused by corrupt driver installation and conflict with other software.
Drivers0x80070005-AUDIO
The audio service cannot start because it doesn't have permissions to access the sound driver. This can also stem from antivirus blocking.
DriversACPI-BIOS-ERROR
Windows stops with ACPI_BIOS_ERROR (0x000000A5) during boot because the system BIOS is not ACPI compliant or has bugs. Use the steps below to track down and fix the cause.
DriversKERNEL-MODE-HEAP-CORRUPT
A kernel-mode driver corrupted the kernel heap. Results in unpredictable BSODs with varying stop codes.
DriversUSB-SELECTIVE-SUSPEND
USB device (mouse, DAC, webcam) randomly disconnects and reconnects due to Windows USB Selective Suspend feature. This usually traces back to hub turning off port to save power and driver not handling resume correctly.
DriversSYSTEM_SERVICE_EXCEPTION
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…
DriversCRITICAL_STRUCTURE_CORRUPTION
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.
DriversNVIDIA_NV_DISP_DLL_CRASH
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…
DriversDRIVER-IRQL-MISMATCH
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…
DriversDRIVER-POWER-STATE-FAILURE
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…
DriversDRIVER-VERIFIER-DMA-VIOLATION
Stop code 0xE6 indicates a driver performed an illegal DMA (Direct Memory Access) operation. DMA allows hardware to access system memory directly without CPU involvement for performance.
Drivers0x000000C4
Driver Verifier detected a violation in a running kernel-mode driver. Use the steps below to track down and fix the cause.
Drivers0x000000C5
A driver attempted to access an invalid memory pool at an elevated IRQL. This can also stem from faulty system RAM.
Drivers0x000000BE
A driver attempted to write to a read-only segment of system memory. Work through the steps below in order.
Drivers0x000000D8
A kernel-mode driver used too many Page Table Entries (PTEs), depleting the system memory manager's address space. Commonly caused by bad graphics drivers, network drivers, or virtualization drivers with memory leaks.
Drivers0x000001D4
The USB Connector Manager UCSI driver detected a hardware or connection timeout in the USB-C Type-C controller firmware. Commonly caused by faulty USB-C hubs, outdated motherboard BIOS, or degraded USB-C ports.
Drivers0x000001D1
The motherboard chipset controller livedump indicates a communication delay or hardware freeze in the Intel/AMD platform controller hub (PCH) drivers. Commonly caused by outdated chipset firmware, aggressive power…