Home > Windows Server Tips > > Troubleshooting Windows XP Device Manager error codes
Windows Server Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 


Troubleshooting Windows XP Device Manager error codes


Brien M. Posey, Contributor
10.23.2007
Rating: -4.05- (out of 5)


Expert advice on Windows-based systems and hardware
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


Part 1 | Part 2 | Part 3

In Windows XP, the Device Manager is a centralized console for configuring all of your system's hardware. If a piece of hardware is malfunctioning, you will almost always be alerted through the Device Manager.

Unfortunately, Device Manager errors tend to consist of error codes and a brief, often cryptic, description of the problem. IT administrators need to familiarize themselves with error codes used by Windows XP Device Manager so they will know how to fix the problem.

You access Device Manager by opening the Control Panel and clicking the Performance and Maintenance links, followed by the System link. Upon doing so, Windows will display the System Properties sheet. Select the properties sheet's Hardware tab, and click the Device Manager button. Windows will now open the Device Manager, shown in Figure A.

[IMAGE]
Figure A: This is the Device Manager.

Device Manager is organized in a hierarchical fashion. Normally, the Device Manager will initially display only device categories. This keeps the view nice and clean, and you can simply expand a category to gain more information about the devices in that category.

The exception to this rule is that if a device is having problems, then the category containing the problem device will be expanded automatically upon opening Device Manager. For example, in Figure A, you can see three devices that are configured incorrectly and listed within the Other Devices section.

In this case, I know what the problem is: No drivers have been installed for these particular devices. I can tell the problem is driver related, because the screen capture was taken from my wife's computer, and I'm the one that set it up. If, however, I didn't already know what the problem was, I could simply right click on a device and select the Properties command from the resulting shortcut menu. Upon doing so, Windows would display the device's proper


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Windows Hardware Strategies
Troubleshooting your toughest Windows server crashes
High-tech solutions for monitoring computer heat
Server virtualization at the hardware level with Hyper-V
Virtualization and 64-bit: A match made in Windows heaven
How to use the g4u network-based hard disk cloning utility
Multi-core processors on the desktop offer major boost
When and how to migrate to a 64-bit platform
64-bit Windows – help or hype?
How to install low-voltage wiring such as Ethernet or coax cable
Bluetooth card reader/USB hub reads files from offbeat media

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


ties sheet, as shown in Figure B.

[IMAGE]
Figure B: A device's properties sheet gives you much more detailed information about a device.

As you can see in the figure, the properties sheet's General tab contains a Device Status section. This section shows that the drivers for the device are not installed and that the error code is 28. It even tells me that I can click the Reinstall Drivers button to take care of the problem. It just doesn't get any easier than that.

Unfortunately, not all Device Manager errors are that easy to decipher. You will notice that the error codes are not sequential. This is because some of the Device Manager error codes that existed in other versions of Windows have been retired and are not used in Windows XP.

Here are some other error codes and their meanings:

The Device is not Configured Correctly (Code 1) -- This error message usually means that an incorrect device driver is associated with the device. Windows XP takes steps to prevent you from installing an invalid device driver, but the problem can occur if the system was upgraded from a previous operating system or if you take steps to circumvent the Device Manager.

To fix, I recommend visiting the hardware manufacturer's Web site and downloading the correct driver for the device.

The Driver for this Device May be Corrupt or Your System May be Running Low on Memory or Other Resources (Code 3) -- In this case, the Device Status section actually gives you a pretty good description of the problem but not a lot of information about what to do about the problem. Initially, go with the assumption that the device driver is corrupt. That being the case, you should begin the process by downloading the latest version of the driver from the hardware manufacturer's Web site.

Once you have the new driver in hand, go to the Device Manager's Driver tab, shown in Figure C, and click the Uninstall button. This will remove the corrupt driver.

[IMAGE]
Figure C: Click the Uninstall button to remove the corrupt driver.

Once the corrupt driver has been removed, the error code should change from Error 3 to Error 1. Follow the steps in the section above to install the new device driver and correct the problem.

Error code 3 also cited a lack of system resources as a possible cause of the problem. In all of my years working with Windows XP, I have seen only one system that was so low on memory that a device driver refused to load, and that problem was because of a virus. Typically, if memory gets to be so low that a device driver can't be loaded, you are going to see some other rather severe performance and stability problems before the system ever gets to the point of rejecting device drivers.

Even so, if you want to check your system's available memory, the easiest way to do so is to press Ctrl+Alt+Delete and click the Task Manager button. When the Windows Task Manager opens, go to the Performance tab. In Figure D, the Performance tab shows you how much physical memory is installed in the computer and how much of that memory remains.

[IMAGE]
Figure D: Use the Windows Task Manager's Performance tab to check memory availability.

You can easily resolve some of the error messages produced by Device Manager. The first step in fixing the problem is knowing what the problem is.

[IMAGE]
[IMAGE]TROUBLESHOOTING WINDOWS XP DEVICE MANAGER
[IMAGE]
[IMAGE] Intro plus error codes 1 and 3
[IMAGE] Error codes 10, 12 and 14
[IMAGE] Error codes 16, 18, 19, 21, 22, 24 and 28

[TABLE]

Rate this Tip
To rate tips, you must be a member of SearchWindowsServer.com.
Register now to start rating these tips. Log in if you are already a member.




DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



Server Room Design - Planning, Cooling, Maintenance
HomeTopicsBlogsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2004 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts