Device Manager Error Code 43? Check Power Management First

Open the USB Root Hub properties in Device Manager, go to the Power Management tab, and uncheck Allow the computer to turn off this device to save power – this single setting resolves a large percentage of USB Code 43 errors on laptops and is almost always checked last in guides, even though it should be checked first. Error Code 43 means the device driver reported an unspecified failure to Windows – the hardware signalled a problem that the driver marked as fatal, causing Windows to stop the device. The error is hardware-reported, which is why it appears across very different device types (USB peripherals, GPUs, webcams, game controllers) and why the correct fix depends entirely on what type of device is showing the error.

What Code 43 Actually Means

The full Device Manager message for Code 43 is: Windows has stopped this device because it has reported problems. (Code 43). The key phrase is the device has reported problems – unlike Code 10 where the driver fails to initialize the hardware, Code 43 means the hardware responded to the driver with an error. This can happen because the hardware is failing, because the power supply to the device is unstable, because the driver sent an invalid command the device rejected, or because the device woke from a suspended state incorrectly. All of these surface as the same Code 43, which is why the fix list is longer than for other Device Manager errors.

USB Code 43 – Work Through This Order

Step 1 – Change Port and Cable First

Before touching any software setting, try a different USB port and a different cable. A large proportion of USB Code 43 errors are caused by port-level power instability or cable signal integrity issues, not by the driver. USB 3.0 ports are more sensitive to cable quality than USB 2.0 – a cable that works fine for data transfer at USB 2.0 speeds may cause Code 43 when the same device tries to negotiate USB 3.0 speeds. Move the device to a port on the opposite side of the case (desktop) or a different physical port (laptop). Try a certified USB cable rated for the speed the device requires. If the device works after the port or cable change, the original port or cable was the problem – no driver action needed.

Step 2 – Disable USB Power Management (Fix This First on Laptops)

On laptops, Windows uses USB Selective Suspend to save battery life – it powers down USB devices when it decides they are idle, then wakes them when needed. Some devices do not wake correctly from the suspended state, which causes Code 43. Open Device Manager, expand Universal Serial Bus controllers, and right-click the first USB Root Hub entry. Select Properties, go to the Power Management tab, and uncheck Allow the computer to turn off this device to save power. Repeat this for every USB Root Hub listed – there will typically be two to six entries on a laptop. Restart and test. This step should be done before any driver reinstall because it resolves the root cause without touching driver files. I saw this on a Lenovo ThinkPad where a Logitech webcam returned Code 43 every time the machine came back from sleep. Disabling USB power management on all root hubs completely stopped the Code 43 from returning – the webcam has worked without a single error since.

Per Sophia L., who is an IT Support Engineer at PwC, “Power management is the first thing I check for USB Code 43 on laptops. Windows aggressively suspends USB devices on battery, and disabling selective suspend in Device Manager fixes it more often than driver reinstalls do – but most guides put it last instead of first.”

Step 3 – Disable USB Selective Suspend in Power Options

For a system-wide fix that affects all USB devices, disable USB Selective Suspend in Windows Power Plan settings. Open Control Panel > Power Options. Click Change plan settings next to your current plan, then Change advanced power settings. Expand USB settings > USB selective suspend setting and set it to Disabled. Apply. This disables power-based USB suspension globally, which is more aggressive than the per-hub Device Manager setting. This approach trades battery life for USB stability – acceptable on a desktop PC or a plugged-in laptop but less ideal when running on battery frequently.

Step 4 – Uninstall the Device and Reinstall the Driver

If power management is not the cause, try a clean driver reinstall. In Device Manager, right-click the USB device showing Code 43 and select Uninstall device. If the option to delete the driver software appears, check it. Unplug the device from the USB port. Wait 30 seconds. Plug it back in. Windows will re-detect the hardware and reinstall the driver from its driver store. If Code 43 returns after this, go to the device manufacturer’s support site and download the latest driver manually. Do not rely on Windows automatic detection for the reinstall – download the manufacturer’s driver package and run the installer. Some USB devices (audio interfaces, game controllers, drawing tablets) require proprietary drivers that Windows Update does not distribute, and the generic class driver that Windows installs automatically is what causes Code 43 in the first place.

Step 5 – Check for Driver Updates and BIOS Updates

Check the USB device manufacturer’s support page for updated driver versions. Also check your motherboard or laptop manufacturer’s site for BIOS firmware updates – some Code 43 errors on USB devices are caused by USB host controller firmware bugs at the motherboard level. Release notes for BIOS updates sometimes specifically mention USB compatibility improvements or Code 43 fixes for specific device types. Applying the firmware update can resolve Code 43 permanently when no driver change makes a difference. According to Microsoft’s USB connection troubleshooting documentation, checking for system firmware updates is a recommended step for persistent USB errors that driver reinstalls do not resolve.

GPU Code 43 – A Different Problem With Different Fixes

Code 43 on a GPU is completely different from USB Code 43. A GPU reporting Code 43 usually means the driver has crashed and been stopped, the driver was corrupted, or the GPU hardware itself is failing. The symptoms are typically a black screen, the display switching to a lower resolution, or the GPU disappearing from Device Manager entirely before returning with Code 43. The port change and power management checks that resolve USB Code 43 are irrelevant for GPUs.

Fix – DDU Clean Uninstall in Safe Mode

The most effective fix for GPU Code 43 is a clean uninstall using Display Driver Uninstaller (DDU). Standard GPU driver uninstalls via Device Manager or the Windows uninstaller leave behind registry entries and service records that cause Code 43 to return even after a fresh driver install. DDU removes everything – driver files, registry keys, and service entries – leaving the system in a state equivalent to a fresh install with no GPU driver. Download DDU from TechPowerUp (search DDU TechPowerUp download – the official page is at techpowerup.com). Boot into Safe Mode before running DDU. Hold Shift, click Restart, go to Troubleshoot > Advanced Options > Startup Settings, press 4 for Safe Mode. In Safe Mode, run DDU, select your GPU brand (NVIDIA, AMD, or Intel), and choose Clean and restart. After the DDU reboot, boot normally, download the latest driver from the GPU manufacturer, and install fresh. Do not install from Windows Update for this step – go directly to nvidia.com, amd.com, or intel.com for the driver package.

Failed Overclocking Causing GPU Code 43

If GPU Code 43 appeared after using an overclocking tool (MSI Afterburner, EVGA Precision X1, GPU Tweak), the instability from the overclock may have corrupted the driver state. Reset GPU clocks to default in your overclocking tool before running DDU. If the tool itself crashes during reset because the GPU is already in an error state, boot into Safe Mode (where the GPU runs without the overclocking service active) and use the DDU clean to start fresh at stock clocks. After the DDU reinstall, test at stock clocks first before applying any overclocking.

GPU Code 43 After Windows Update

Windows Update sometimes replaces a working GPU driver with a Microsoft-generic WDDM driver that does not fully support the GPU. This causes Code 43 because the generic driver sends commands the GPU does not understand. The fix is to roll back the driver (Device Properties > Driver tab > Roll Back Driver) or use DDU and reinstall from the GPU manufacturer’s site. To prevent Windows Update from replacing your GPU driver again, use the wushowhide tool to hide the Windows Update GPU driver entry after your working manufacturer driver is installed.

GPU Hardware Failure

If Code 43 on a GPU persists after a DDU clean reinstall on both normal and Safe Mode boots, and the same behaviour appears when the GPU is tested in a different system, the GPU hardware itself may be failing. A GPU reporting Code 43 consistently across drivers and systems typically indicates VRAM failure, a damaged power connector, or core hardware degradation. Check the GPU in a second known-good system with a fresh DDU reinstall to confirm hardware failure before replacing the card. Also check that the PCIe power connectors are fully seated – a loose 6-pin or 8-pin connector can cause intermittent power delivery failures that surface as Code 43.

Code 43 on Other Device Types

Code 43 appears on non-USB, non-GPU devices too – most commonly on Bluetooth adapters, webcams integrated into laptop lids, SD card readers, and Thunderbolt controllers. For these devices, the fix order is: driver rollback or reinstall first, then check for BIOS/firmware updates. Thunderbolt Code 43 in particular is frequently caused by a BIOS or Thunderbolt firmware version mismatch rather than a driver issue – check the laptop manufacturer’s site for both a BIOS update and a separate Thunderbolt firmware update, as these are often packaged separately. Intel provides a Thunderbolt driver and firmware package for Intel-based controllers that resolves most Thunderbolt Code 43 cases not fixed by the laptop OEM driver alone.

Frequently Asked Questions

Why does Code 43 keep coming back after reinstalling the driver?

Persistent Code 43 after driver reinstall usually means one of three things: the root cause is hardware-level (power instability, failing hardware), a residual driver registry entry is causing conflict (fix: DDU clean reinstall for GPUs, or delete store entry for USB devices), or the USB power management setting is re-enabling itself after each reinstall. For USB, check the Power Management tab after every reinstall and confirm it is still unchecked – some driver packages reset this setting on install.

Does Code 43 mean my hardware is dying?

Not necessarily. Code 43 frequently has software causes – driver corruption, power management suspension, Windows Update replacing a working driver with an incompatible one. Hardware failure is one possible cause among many. Test by working through the software fixes first. If Code 43 persists after DDU (for GPU) or clean driver reinstall (for USB) and the device shows Code 43 on a second PC as well, then hardware failure is the likely cause.

Can Code 43 cause data loss on a storage device?

If Code 43 appears on an external USB storage device (external SSD, USB flash drive, HDD enclosure), stop using it for new writes until the cause is identified. A storage device reporting Code 43 could indicate power instability, a faulty USB bridge controller, or early hardware failure – all of which could affect data integrity. Back up the data immediately by trying the device on a different port or PC. If the device shows Code 43 everywhere, access it with a data recovery tool rather than trying to fix the driver.

Will disabling USB power management affect battery life significantly?

Disabling USB Selective Suspend has a small but real effect on battery life. USB devices in selective suspend use significantly less power than when fully active. On a laptop with many USB peripherals connected, disabling it can reduce battery life by 20 to 45 minutes under typical use. For a desktop or a plugged-in laptop, this does not matter. For battery-powered use, consider only disabling power management for the specific USB Root Hub port that the problem device uses, rather than all root hubs, to minimise the battery impact.

Conclusion

For USB Code 43 on laptops, the first thing to check is the USB Root Hub Power Management setting in Device Manager – disabling Allow the computer to turn off this device to save power resolves the majority of persistent USB Code 43 cases before any driver work is needed. For USB devices where power management is not the cause, try a different port and cable, then a clean driver uninstall and reinstall from the manufacturer’s site. For GPU Code 43, DDU in Safe Mode followed by a fresh driver install from the GPU manufacturer is the standard fix. If Code 43 persists after all driver-level fixes on both USB and GPU, check for BIOS or firmware updates – firmware bugs are a real but underreported cause of Code 43 that no driver reinstall can fix.