43Code 43 means Windows stopped a device after its driver reported a problem. It does not itself identify a damaged GPU, faulty cable or power supply. The useful test depends on which device is stopped and what changed before the code appeared.
Windows Code 43 error
Windows stopped a device after a driver reported a problem. Code 43 describes that state, not a specific failed part, and can affect different device classes.
Try this first
1 quick checks · ~3 min
Find your situation
See all the clues. Choose the one that matches what you observe.
Diagnostic signals
- ObservationGPU is listed with the code
- Windows can identify it even though it is not working properly. An absent GPU or a PC with no display cannot be diagnosed from 43 alone.
- ObservationCode or failure location changes
- Recording the difference lets you stop repeating a repair that no longer fits.
Step-by-step solutions
Confirm the stopped device
Identify the exact entry before changing it.
Open Device Manager > device with warning > Properties > General. Confirm 43 and record model, complete message and provider/version under Driver.
If the code is not present, use the corresponding USB-not-recognized or display guide. If it is present, choose USB, display or another class below. Do not buy a part based on this number.
Compare device, port and cable
For an external peripheral not required for boot, close its activity and eject drives before disconnecting. Test the same device directly on another compatible port. If it has a detachable cable, compare with a compatible data cable; USB-C charging does not confirm every function.
If 43 disappears without a hub or with another cable, focus on that path. If it persists, test on another compatible, authorized PC. Working there points toward the first PC; failing there too points toward the device or compatibility without proving a specific failed part. In the latter case, stop and consult the manufacturer.
Separate the GPU from the display path
If Windows is usable, confirm which GPU shows 43. An already working secondary output preserves access but does not prove the stopped GPU is healthy. Do not assume a motherboard display connector always has integrated graphics available.
If it began immediately after a new driver, with alternate display access and authorization consider Properties > Driver > Roll Back Driver. Save work and restart if prompted. Recovery supports reporting that regression; otherwise consult the model’s package and manufacturer diagnostics before reinstalling.
If artifacts occur before Windows or you cannot maintain a display, keep that observation and seek hardware assistance; blind reinstalls do not assess that state. Do not flash GPU firmware or use scripts that hide the code.
Consult the exact class and model
For networking, Bluetooth, audio or another device, use the full text and model to consult the OEM. Do not apply a GPU or USB procedure to a different internal controller.
If the manufacturer identifies a compatible package or its own diagnostic, follow that path. If the status changes to Code 10 or 31, use the corresponding related guide; without a specific explanation, gather versions and changes for support.
Advanced checks
Continue if the earlier steps did not help. Read each procedure’s precautions first.
Reinstall only after isolating the device
Only if comparison points toward the original PC or the manufacturer recommends repairing that driver: download the official package for the correct model and Windows first. Save work and prepare alternate display, input and network access.
In Device Manager uninstall only the identified entry without removing additional packages. Use Action > Scan for hardware changes and the official installer if Windows does not restore it. Check status and function; if 43 returns, give the result to the manufacturer instead of repeating.
Still not working?
Persistent 43 needs model-specific diagnosis, not registry modifications, disabled protections or forced packages. Provide comparisons, versions and any code change; do not buy hardware without a test identifying it.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
- Microsoft SupportOfficialError codes in Device Manager in Windows
- Microsoft SupportOfficialUpdate drivers through Device Manager in Windows
- Microsoft SupportOfficialFix USB-C problems in Windows
Source review: . A documentation review, not a physical hardware test.
Related problems
USB device not recognized in Windows
Windows displays a USB device recognition warning. Start with the connection and read device status: the warning does not automatically mean Code 43 or a drive that needs formatting.
View solutionBlack screen after Windows starts
The display goes black when entering Windows or after sign-in. If there was never a boot image or any sign of Windows, start with PC turns on but no display.
View solutionBluetooth disappeared in Windows
Windows no longer offers Bluetooth or cannot turn it on. First check whether the adapter is still detected. A visible Bluetooth adapter that cannot connect to an accessory needs a different troubleshooting path.
View solutionWindows Device Manager Code 10
Identify the device that cannot start and check its specific driver, keeping Code 10 separate from Code 43.
View solutionDevice Manager Code 31
Windows cannot load the drivers the device needs. Check for an appropriate update before removing it from the system.
View solution