Drivers errors
30 errors. Choose the message that matches your computer.
Driver errors usually appear as blue screens that name a .sys file, or as devices with a warning sign in Device Manager. Updating, rolling back or reinstalling the named driver fixes most of them.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Windows stopped because a kernel-mode driver tried to access memory at an invalid address while running at a raised priority level. Microsoft says this bug check is usually caused by drivers that used improper memory…
DriversSYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Windows stopped because a system thread, code that runs inside Windows itself, hit an error that nothing caught, most often an invalid memory access. In almost every case the thread belongs to a driver, and the blue…
DriversSYSTEM_SERVICE_EXCEPTION
Windows stopped because code running in the system kernel hit an exception, usually a bad memory address, while handling a request from a normal program. In practice the faulty code almost always belongs to a driver:…
DriversCRITICAL_STRUCTURE_CORRUPTION
Windows stopped because it detected that critical kernel code or data had been changed. 64-bit Windows does not allow its kernel to be modified except by Microsoft's own hot patches, so when something changes it,…
DriversDRIVER-POWER-STATE-FAILURE
Windows stopped because a device driver did not finish a power change, such as sleep, wake-up or shutdown, in time. This also covers devices that Windows turns off to save power.
DriversAUDIO-NO-OUTPUT
Windows plays no sound, the speaker icon shows a red X, or hovering over it says "No audio output device is installed". Either Windows does not see the sound device at all, usually because of a driver problem or a…
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.
DriversCODE-10-DEVICE-CANNOT-START
Windows Device Manager reported that the device could not start due to a failure to load or a faulty driver. Another common trigger is incompatibility with the.
DriversBSOD-ndis.sys
Windows has terminated due to a fatal error in the kernel module ndis.sys. Typical causes include outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-tcpip.sys
Windows has terminated due to a fatal error in the tcpip.sys kernel module. Reports of Critical tcpip.sys driver error (BSOD) usually describe a sudden crash, brief unresponsiveness, or a stop-code screen appearing…
DriversBSOD-usbport.sys
Windows has terminated due to a fatal error in the usbport.sys kernel module. This usually traces back to outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-fltmgr.sys
Windows has terminated due to a fatal error in the fltmgr.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-classpnp.sys
Windows has terminated due to a fatal error in the classpnp.sys kernel module. It's most often caused by outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-dxgkrnl.sys
Windows has terminated due to a fatal error in the dxgkrnl.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-igdkmd64.sys
Windows has terminated due to a fatal error in the igdkmd64.sys kernel module. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversBSOD-amdkmdag.sys
Windows has terminated due to a fatal error in the kernel module amdkmdag.sys. Common triggers are outdated or faulty driver, hardware incompatibility and conflict with antivirus.
DriversCODE-43-USB-HUB
The entire USB controller reports code 43, which disconnects all USB ports on the given group. Common triggers are corrupt USB xHCI Driver and driver conflict after windows update.
DriversNVIDIA-CONTAINER-HIGH-CPU
The nvcontainer.exe or NvTelemetryContainer.exe processes constantly consume 5-20% CPU even when idle. It's most often caused by corrupt driver installation and conflict with other software.
Drivers0x80070005-AUDIO
The audio service cannot start because it doesn't have permissions to access the sound driver. This can also stem from antivirus blocking.
DriversACPI-BIOS-ERROR
Windows stops with ACPI_BIOS_ERROR (0x000000A5) during boot because the system BIOS is not ACPI compliant or has bugs. Use the steps below to track down and fix the cause.
DriversKERNEL-MODE-HEAP-CORRUPT
A kernel-mode driver corrupted the kernel heap. Results in unpredictable BSODs with varying stop codes.
DriversUSB-SELECTIVE-SUSPEND
USB device (mouse, DAC, webcam) randomly disconnects and reconnects due to Windows USB Selective Suspend feature. This usually traces back to hub turning off port to save power and driver not handling resume correctly.
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…
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…