“Windows has stopped this device because it has reported problems” (Code 43)
Updated Sep 17, 2026
Code 43 is the status Device Manager shows when a driver told Windows that its device failed: “Windows has stopped this device because it has reported problems. (Code 43)”. It appears most often on graphics cards, USB devices and Bluetooth adapters.
The code itself is generic — it says the driver detected a failure, not why. The cause can be a temporary glitch, a broken or mismatched driver, a power problem or a real hardware fault. Work through the steps below in order; the first three solve most cases.
1. Check which device has Code 43
Open Device Manager (Win + X → Device Manager), find the device with the yellow sign, open Properties and check the Device status box. Then look at Details → Hardware Ids:
USB\VID_0000&PID_0002— the USB device could not even identify itself. Follow the Device Descriptor Request Failed guide instead.PCI\VEN_10DE…(NVIDIA),PCI\VEN_1002…(AMD) orPCI\VEN_8086…(Intel) under Display adapters — see the graphics section.- Any other ID — note it down, you will need it to get the correct driver (how to read hardware IDs).
2. Power-cycle the computer and the device
- Disconnect external devices that show Code 43.
- Hold Shift and click Start → Power → Shut down for a full shutdown (a normal restart may keep the device in its failed state when Fast Startup is on).
- Unplug the power cable (and the charger on a laptop), wait 30 seconds, then start the PC and reconnect the device.
3. Reinstall the driver
- In Device Manager right-click the device → Uninstall device.
- Tick Attempt to remove the driver for this device (on Windows 10: Delete the driver software for this device) and confirm.
- Restart the computer. Windows installs a basic driver automatically.
- If the error returns, install the manufacturer’s driver for your exact hardware ID: search it on this site or on the support page of your laptop or motherboard.
4. Roll back a recent driver update
If Code 43 appeared right after a driver or Windows update: Properties → Driver → Roll Back Driver. If the button is greyed out, no previous driver is stored — download the previous version manually and install it over the current one.
5. Install chipset drivers and update BIOS
Graphics cards, USB controllers and Bluetooth modules all sit on buses managed by the chipset. After a clean Windows install, install the chipset driver first:
Intel:
- Intel Chipset Device Software Driver 10.1.20003.8622 (Nov 5, 2024, Windows 10, 11)
- Intel Chipset Device Software Driver 10.1.19900.8599 (Jul 20, 2024, Windows 10, 11)
AMD Ryzen:
- AMD Ryzen™ Chipset Driver 7.02.13.148 (Feb 26, 2025, Windows 10, 11)
- AMD Ryzen™ Chipset Driver 7.01.08.129 (Jan 14, 2025, Windows 10, 11)
A BIOS/UEFI update from the motherboard or laptop maker is also worth checking — many Code 43 fixes for new graphics cards and USB controllers were shipped as firmware updates.
6. Graphics cards (NVIDIA, AMD, Intel)
- Clean driver install. Remove the current driver completely (the free tool Display Driver Uninstaller in Safe Mode is the usual choice), then install the latest driver from NVIDIA, AMD or Intel for your card and Windows version.
- Laptops with two GPUs. Install the Intel or AMD integrated graphics driver first, then the NVIDIA/AMD discrete driver. Laptop makers’ own driver packages are often more reliable than generic ones.
- Desktops. Re-seat the card, make sure all PCIe power connectors are plugged in, and try another PCIe slot. A power supply that is too weak can cause Code 43 under load.
- Overheating or artefacts (stripes, colored dots) together with Code 43 usually mean a hardware fault of the card.
Browse video card drivers.
7. USB and Bluetooth devices
- Connect the device directly to the computer (no hub), preferably to a rear port on a desktop, and try another cable.
- Disable USB selective suspend and hub power saving — see steps 5–6 in the USB guide.
- For built-in Bluetooth, turn off airplane mode, do a full power-off as in step 2, and install the Bluetooth driver that matches the hardware ID (often Intel
USB\VID_8087or RealtekUSB\VID_0BDA). See Bluetooth drivers.
8. When it is a hardware fault
Suspect the hardware when the error persists after a clean driver install, appears in another computer too, or when the device also fails outside Windows (for example a graphics card that shows no image in BIOS). In that case contact the manufacturer or the shop — especially while the device is under warranty.