До основного вмісту

← До всіх статей

Windows stopped this device — Code 43

Ця стаття поки що доступна лише англійською мовою.

Code 43 is a Device Manager error. Windows shows it when a driver controlling a device reports that the device has failed in some way. Microsoft describes the message as:

“Windows has stopped this device because it has reported problems. (Code 43)” [R1][R2]

That tells you the device is not operating normally. It does not tell you the exact cause.

The underlying problem may be the device hardware, its connection or power, the driver, or other driver software. Microsoft makes this distinction explicitly for graphics devices that report Code 43. [R3]

First: identify which device has Code 43

Open Device Manager, find the device with the warning symbol, and open Properties. The error code appears in the Device status area. [R2]

Before changing anything, note:

These details help distinguish a connection problem from a driver or hardware problem.

If it is an external device, check the connection first

For a removable USB device, start with the lowest-risk tests.

Disconnect it, wait briefly, and reconnect it. If possible, try another compatible USB port. Microsoft recommends these checks for USB peripherals before deeper driver troubleshooting. [R4]

If a hub or dock sits between the device and the PC, test the device directly on the computer where practical. Also check that the device has the power it requires.

These tests are useful because reinstalling a driver cannot repair a loose cable, an unpowered hub, or a damaged peripheral.

Check whether something changed recently

If Code 43 appeared immediately after a driver update, that timing is important evidence.

Microsoft documents Roll Back Driver as an appropriate option when a device problem began after a recent driver or Windows update. [R5]

A rollback restores the previous driver version. That can fix a regression, but it also gives up changes in the newer driver, including any fixes it contained. It should therefore be used when the timing and device evidence point toward the driver change, not as a routine first action.

Reinstalling the device can be appropriate

Microsoft's documented resolution for Code 43 is to uninstall the affected device in Device Manager and then scan for hardware changes so Windows reinstalls it. [R1][R2]

This can repair a damaged or incorrectly initialized driver installation.

If a newer driver is needed and Windows Update does not provide one, Microsoft recommends obtaining it from the hardware manufacturer's official site rather than from an unrelated driver-download website. [R5]

When should I suspect hardware?

Code 43 does not mean “the hardware is definitely dead.”

But hardware becomes more suspicious when the error survives sensible software and connection checks. For an external device, another useful test is whether the device works on another compatible PC. Microsoft recommends this kind of cross-device test for USB peripherals; if the device does not work there either, replacement may be necessary. [R4]

For internal hardware such as a graphics card, storage controller, or built-in device, use the PC or component manufacturer's diagnostics and documentation if Code 43 remains after supported driver troubleshooting. Microsoft also directs users with persistent Code 43 errors to the hardware documentation or manufacturer. [R2][R3]

How do I know it is fixed?

Do not stop when the driver installation finishes successfully.

Check Device Manager again. The device should no longer report Code 43, and Microsoft says its status should show that the device is working properly after a successful repair. [R3]

Then test the actual function that failed: use the graphics output, connect with Bluetooth, transfer data through the USB device, or perform whatever task the device is supposed to do.

Code 43 is a useful starting point.

It means the device reported failure — not the driver is definitely bad and not the hardware is definitely broken.


Джерела

  1. Code 43 - CM_PROB_FAILED_POST_START — Microsoft Learn (2026-09-20)

    “This Device Manager error message indicates that a driver has reported a device failure.”

    https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-failed-post-start

  2. Error codes in Device Manager in Windows — Microsoft Support (2026-09-20)

    “One of the drivers controlling the device notified the operating system that the device failed in some manner.”

    https://support.microsoft.com/en-us/windows/hardware/drivers/error-codes-in-device-manager-in-windows

  3. Fix graphics device problems with error code 43 — Microsoft Support (2026-09-20)

    “This may mean that the device has a hardware problem, or that the driver or driver software is failing.”

    https://support.microsoft.com/en-us/windows/hardware/display-graphics/fix-graphics-device-problems-with-error-code-43

  4. Mouse and keyboard problems in Windows — Microsoft Support (2026-09-20)

    “Try using a different USB port on your PC.”

    https://support.microsoft.com/en-us/windows/hardware/input-devices/mouse-and-keyboard-problems-in-windows

  5. Update drivers through Device Manager in Windows — Microsoft Support (2026-09-20)

    “If the issue occurred after a Windows Update, reinstalling the previous driver often resolves it.”

    https://support.microsoft.com/en-us/windows/update-drivers-through-device-manager-in-windows-ec62f46c-ff14-c91d-eead-d7126dc1f7b6