Device Manager Error Codes

By: Arie Slob

If there is a problem with one of your devices, Windows will list the device with 1 of 3 symbols in the Device Manager (Control Panel > System > Device Manager tab):

indicates the device is in a problem state. A device in a problem state can be functioning. A problem code explaining the problem is displayed for the device.
indicates a disabled device. A disabled device is a device that is physically present in the system, consuming resources, but does not have a protected-mode driver loaded.
on a device resource in Computer properties indicates that Use Automatic Settings is not selected for the device and that the was manually selected. It does not indicate a problem or disabled state.

Note: Some sound cards and video adapters do not report all the resources they are using to Windows. This can cause Device Manager to show only one device in conflict, or no conflicts at all. This can be verified by disabling the sound card, or using the standard VGA video driver to see if the conflict is resolved. (This is a known problem with S3 video cards and 16-bit Sound Blaster sound cards, or those sound cards using Sound Blaster emulation for Sound Blaster compatibility).

Error Codes:

Code 1: This code means the system has not had a chance to configure the device. To resolve the problem, follow the instructions in the Device Status box. In addition, you may be able to resolve this issue by removing the device in Device Manager, and then running the Add New Hardware wizard from Control Panel.

Solution button: Update Driver

Code 2: Depending on which device is failing, you may see either of two different messages. This code means that the device loader (DevLoader) did not load a device. When this device is a Root Bus DevLoader (for example, ISAPNP, PCI, or BIOS), the following message is displayed:

Windows could not load the driver for this device because the computer is reporting two <type> bus types. (Code 2)

Contact your computer manufacturer to get an updated BIOS for your computer.

where <type> is ISAPNP, PCI, BIOS, EISA, or ACPI.

Solution button: None

When the device is not a root bus DevLoader, the following message is displayed:

The <type> device loader(s) for this device could not load the device driver. (Code 2)

To fix this, click Update Driver to update the device driver.

where <type> is the DevLoader such as FLOP, ESDI, SCSI, and so on.

Solution button: Update Driver

In addition to following the recommended solution, try removing the device from Device Manager, and then running the Add New Hardware wizard from Control Panel.

Code 3: This code means the driver for this device is bad, system is running low on memory.

Solution button: Update Driver

As an alternative, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel.

Code 4: This code means the .inf file for this device is incorrect or the registry may be damaged. For example, the .inf file specifies a field that should be text, but is binary instead. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer for an updated .inf file.

Solution button: Update Driver

Code 5: This code means there was a device failure due to the lack of an arbitrator. If a device requests a resource type for which there is no arbitrator, you receive this error code. To resolve this error code, update the driver as suggested, or use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel.

Solution button: Update Driver

Code 6: This code means there is a conflict between this device and another device. To resolve this error code, see the "Troubleshooting Conflicting Hardware" topic in Windows Help, or see Microsoft Knowledge Base Article Q133240: Troubleshooting Device Conflicts with Device Manager.

Solution button: Hardware Troubleshooter

Code 7: This code means that no configuration can be performed on the device. If the device works correctly, you do need not to perform any steps to correct the code. If the device does not work correctly, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel. If you continue to receive this error code and the device does not function properly, check with the hardware's manufacturer or the Microsoft Software Library for an updated driver.

Solution button: Reinstall Driver

Code 8: This code means the device loader (DevLoader) for a device could not be found. For example, the .inf file for the device may refer to a missing or invalid file. For most cases, the resolution is to reinstall or update the driver. As an alternative, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer about updated drivers.

When the problem DevLoader is a system DevLoader, Windows should be re-installed because this driver is built into the Vmm32.vxd file.

Note: A system DevLoader is one that is part of Vmm32.vxd, and typically begins with an asterisk (*). If the DevLoader is a system DevLoader, the following text is displayed:

This device is not working properly because Windows cannot load the file <name> that loads the drivers for the device. (Code 8)

To fix this problem, run Windows Setup again using your Windows CD-ROM.

where <name> is the system DevLoader that cannot be found.

Code 9: This code means that the information in the registry for this device is invalid. It may be possible to resolve this error by using Device Manager to remove the device and then running the Add New Hardware wizard in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer for the proper registry settings.

Solution button: None

Code 10: This code means that the device failed to start (for example, it is missing or is not working properly). To resolve this error code, make sure the device is attached to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are plugged into their slots fully. Follow the suggested solution button and update the device driver. It may be possible to remove the device and re-detect it using the Add New Hardware wizard in Control Panel.

Solution button: Update Driver

Code 11: This code means that the device failed. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel. If the problem persists, contact the hardware manufacturer for updated drivers.

Solution button: Update Driver

Code 12: This code means one of the resource arbitrators failed. This can occur if the device is software configurable and it does not currently have a resource, if the system is out of resources (for example, all the interrupts are in use), or if the device requests a resource and that resource is currently in use by another device that will not release the resource. To resolve this error code, see the "Troubleshooting Conflicting Hardware" topic in Windows Help, or see Microsoft Knowledge Base Article Q133240: Troubleshooting Device Conflicts with Device Manager.

Solution button: Hardware Troubleshooter

Code 13: This code means the device failed due to a problem in the device driver. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel.

Solution button: Detect Hardware

Code 14: This code means the device has a problem that may be resolved by restarting your computer. To resolve this error code, shut down Windows, turn off your computer, and then turn it back on.

Solution button: Restart Computer

Code 15: This code means the device's resources are conflicting with another device's resources. To resolve this error code, see the "Troubleshooting Conflicting Hardware" topic in Windows Help, or see Microsoft Knowledge Base Article Q133240: Troubleshooting Device Conflicts with Device Manager.

Solution button: Hardware Troubleshooter

Code 16: This code means the device was not fully detected. When a device is not fully detected, all of its resources may not be recorded. To resolve this error code, click the Resources tab in the device's properties to manually enter the settings.

Solution button: None

Code 17: This code means the hardware is a multiple-function device and the .inf file for the device is providing invalid information on how to split the device's resources to the child devices. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer about an updated .inf file.

Solution button: Update Driver

Code 18: This code means that an error has occurred and the device needs to be reinstalled. To resolve this issue, follow the recommended solution. If that does not work, try removing the device from Device Manager and then running the Add New Hardware wizard in Control Panel.

Solution button: Reinstall Driver

Code 19: This code means the registry returned an unknown result. To resolve this issue, remove the device from Device Manager, and then re-detect it using the Add New Hardware wizard in Control Panel.

Code 20: This code means VxD Loader (Vxdldr) returned an unknown result. For example, there could a version mismatch between the device driver and the operating system. To resolve this issue, follow the recommended solution. If that does not work, try removing the device from Device Manager and then running the Add New Hardware wizard in Control Panel.

Solution button: Update Driver

Code 21: This code means the device has a problem that may be resolved by restarting your computer. To resolve this error code, shut down Windows, turn off your computer, and then turn it back on.

Solution button: Restart Computer

Code 22: This code means the device is disabled.

To resolve this error code, enable the device. To do so, follow these steps:

Select Start > Setting > Control Panel, then double-click System
Select the Device Manager tab
Double-click the category for the device you want to enable, and then double-click the device
In the Device Usage box, select the check box for the configuration in which you want to enable the device
Click OK, and then click Close
Shut down Windows, and restart your computer

If this doesn't work, try removing the device in Device Manager, then re-detecting it using the Add New Hardware wizard. If the problem persists, try a clean boot to rule out software interference. If the error persists, contact the hardware manufacturer.

Code 23: This code means the device loader delayed the start of a device and then failed to inform Windows when it was ready to start the device. To resolve this error code, verify the settings for the primary display adapter in Display properties. Try removing the primary and secondary display adapters from Device Manager, and then rebooting to allow Windows to re-enumerate these devices. Verify that the drivers are current and installed correctly.

For devices other than display adapters, follow the recommended solution. If that does not work, try removing the device from Device Manager and using the Add New Hardware wizard to re-detect the device.

Code 24: This code means that the device was not found (for example, it is missing or is not working properly). To resolve this error code, follow the recommended solutions. If the device still does not work, make sure the device is connected to your computer correctly. For example, make sure all cables are correctly installed, or that the adapter cards are properly seated in their slots.

Code 25: This problem typically exists only during the first and second boots after Windows Setup copies all the files. As such, if this code is identified, it is likely an incomplete installation.

To resolve this issue, follow the recommended solution. Reinstalling Windows may be required, depending on whether or not the reboot resolves the issue.

Solution button: Restart Computer

Code 26: This code means a device did not load. There may be a problem in the device driver or not all the drivers were installed.

To resolve this error code, follow the recommended solution. If this does not work, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, check with the hardware's manufacturer or the Microsoft Software Library for an updated driver.

Solution button: Restart Computer

Code 27: This code means the portion of the registry describing possible resources for a device does not contain valid entries. For example, the device is marked as configurable, but the configuration information in the .inf file is set to hardwired.

To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware wizard in Control Panel. If the device still does not work, consult the hardware manufacturer for updated drivers or further assistance.

Solution button: None

Code 28: This code means the device was not installed completely.

To resolve this issue, follow the recommended solution. If that does not work, try removing the device from Device Manager and using the Add New Hardware wizard to re-detect it. You may need to obtain updated drivers if the error still occurs.

Solution button: Reinstall Driver

Code 29: This code means the device has been disabled because the device does not work properly and cannot be made to work properly with Windows.

You may be able to resolve this error code by enabling or disabling the device in the computer's CMOS settings. Windows cannot override this setting. Please contact the computer's manufacturer for assistance with using the computer's CMOS setup program.

Solution button: None

Code 30: This code means that an IRQ cannot be shared. This may occur when a PCI/EISA SCSI controller is sharing an IRQ that is also in use by a real-mode device driver that Windows can't change.

To resolve this error code, remove the real-mode driver that is using the same IRQ as this device. The real-mode driver may be loading in the Config.sys or Autoexec.bat file.

Solution button: None

If you believe that a protected-mode driver should be controlling a device, but the device appears with a real-mode driver in the Device Manager in Control Panel, you can check entries in Ios.log. The Ios.log file in the Windows directory is created when a protected-mode driver is not available or the operating system detects that an unknown device driver is controlling a device.

In most cases, the first line in Ios.log states why the protected-mode driver was not loaded. If the first line mentions Mbrint13.sys, the problem most likely is a virus (unless you are using a driver that replaces the master boot record).

Site menu:

Device Manager Error Codes