Introduction:- startup problems in XP
In the Windows family of operating systems, XP is by far the most reliable. Still, it’s not without its problems, and there are chances of things going wrong. Startup and shutdown troubles are mostly due to incompatible hardware and software. Before getting down to troubleshooting, it is advisable to make sure your system has all the latest hardware device driver updates, patches and software programs updates that are XP-specific. At the minimum, you should run Windows Update and download all the latest patches. If you are not sure whether there is an update required for any device or software program, and are not sure where to start looking, don’t worry—let’s get on with the troubleshooting.
There are many sources of problems that could give you Startup troubles. These include (but are not limited to): defective, incompatible, or incorrectly configured hardware, incompatible (software) device drivers, or a recently installed program.
Troubleshooting unknown devices in Device Manager (Those with a yellow question mark)
There are many reasons that a Device Manager will list a device asunknown and hence, there is no foolproof way to troubleshoot theerror. Some of the causes for Unknown Device error are:- The hardware does not have the requisite software drivers, andWindows is not able to determine the device type
- The driver is not compatible with the OS and hence it is not ableto inform Windows about the hardware. This is common if aWindows 9x/ME driver is installed on Windows 2000/XP.
- Each hardware component should normally communicate a basic device ID to Windows. If the hardware does not have this device ID or Windows does not recognise the device ID of the hardware, then the device is listed as unknown.
SOLUTION
Programs can also install virtual devices. Usually, these virtualdevices act as a bridge between the software and some hardwarefunction. Sometimes, device driver software for hardware isinstalled in a non-standard way. When the hardware along withdriver software is removed, all the entries in the Registry are not deleted.
- First, boot the computer into Safe Mode. If the device is nolonger listed in Device Manager, then most likely it was a virtualdevice driver.
- Next, check the programs loaded at systemstartup (Start > Programs > Startup). By trial and error, disableeach program till you identify the software that is causing thedevice to be unknown. Uninstall and reinstall the software.
- Ifthese steps do not work, or if you suspect that the problem ishardware-related, remove hardware devices from your computer one at a time until Device Manager no longer lists theunknown device. Or, if you know what hardware is causing theerror, verify that the hardware is working and that you have all the correct and updated drivers for the OS. Install the driversthrough the Add Hardware Wizard.
device manager error codes(21-25)
Code 21
Code Meaning: The device is being removed as it has a problem, and Windows needs to be restarted.
Recommended Resolution: Wait a few seconds and refresh the Device Manager. If the device still shows, then restart the computer.
Code 22
Code Meaning: The device has either been disabled by a user or has not started.
Recommended Resolution: Wait a few seconds and refresh the Device Manager. If the device still shows, then restart the computer. Trying enabling the device. If that is not possible, remove the device, reboot the computer and reinstall it using the Add Hardware Wizard.
Recommended Resolution: Wait a few seconds and refresh the Device Manager. If the device still shows, then restart the computer. Trying enabling the device. If that is not possible, remove the device, reboot the computer and reinstall it using the Add Hardware Wizard.
Code 23
Code Meaning: (Not applicable to Windows XP) This indicates a problem with the drivers of either the primary or secondary display adaptor. The device loader program delayed loading the device and then did not inform Windows.
Recommended Resolution: Verify that the drivers for all the display adaptors on the computer are correct and updated. Remove the display adaptors and reboot. Windows will automatically detect the adaptors and configure them. If the device is not a display adaptor, then remove the device and reinstall it using the Add Hardware Wizard.
Code 24
Code Meaning: Windows couldn’t detect the device. This error may happen if the device has been set for removal.
Recommended Resolution: Verify that the hardware is working and that the physical installation is correct. Remove the device from Device Manager. Reinstall it using the Add Hardware Wizard. Update the device driver to the latest.
Code 25
Code Meaning: (Not applicable to Windows XP) The device installation has not yet been completed.
Recommended Resolution: Restart the computer. Windows may require to be reinstalled depending on whether the reboot solves the problem or not.
device manager error codes(16-20)
Code 16
Code Meaning: The device is only partially configured and Windows could not find all the resources required by this device.
Recommended Resolution: Run msinfo32.exe to get more information on the conflict. Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the manufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the “Automatic Settings” checkbox, click the “Change Settings” button, and input the values.
Code 17
Code Meaning: (Not applicable to Windows XP) The hardware is a multi-function device whose driver file is reporting invalid information on how to split the resources.
Recommended Resolution: Remove the device from Device Manager and reinstall it using the Add Hardware Wizard. Use an updated device driver if required.
Code 18
Code Meaning: The drivers for this device should be reinstalled.
Recommended Resolution: Select the driver tab and click the “Update Driver” button. Use an updated device driver if required.
Code 19
Code Meaning: A problem with the Windows Registry entry for this device was detected.
Recommended Resolution: In Windows 9x/ME/2000, run the Registry scanner (scanreg.exe). If this does not solve the problem, run “scanreg.exe /restore”. If this still does not solve the problem, remove the device and reinstall it using the Add New Hardware Wizard. In Windows XP, run the Troubleshooting Wizard from the General tab of the Device Properties sheet. Click Uninstall and then click “Scan for hardware changes” to reinstall the device. If that doesn’t solve the problem, restart the computer in Safe Mode and select “Last Known Good Configuration”.
Code 20
Code Meaning: (Not applicable to Windows XP) One of the drivers for this device could not be loaded, and Windows is not able to interpret the result.
Recommended Resolution: Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Related Articles
Device Manager error Codes 1-5
Device Manager error Codes 6-10
Device Manager error Codes 11-15
Device Manager error Codes 21-25
Device Manager error Codes 26-30
Device Manager error Codes 31-35
Device Manager error Codes 36-40
Device Manager error Codes 41-45
Device Manager error Codes 45-49
device manager error codes(11-15)
Code 11
Code Meaning: (Not applicable to Windows XP) Windows stopped responding when it tried to start the device, and hence will never try to start this device again.
Recommended Resolution: Run the Update Driver Wizard and reinstall with an updated driver from the manufacturer.
Code 12
Code Meaning: Two devices have been assigned the same I/O port, interrupt or DMA channel. This could be by the BIOS, by Windows, or both. Also, it could be that the BIOS has not allocated enough resources for the device.
OR
Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the manufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the “Automatic Settings” checkbox, click the “Change Setting” button, and input the values.
AND/OR
Reconfigure the BIOS resource allocation if possible. Refer to the motherboard documentation along with the device documentation.
Code 13
Code Meaning: (Not applicable to Windows XP) Windows did not detect the hardware.
AND
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Code 14
Code Meaning: The device cannot work properly until the system is restarted.
Recommended Resolution: Restart the computer.
Code 15
Recommended Resolution: Run msinfo32.exe to get more information on the conflict. Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the manufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the “Automatic Settings” checkbox, click the “Change Settings” button, and input the values.
Related Articles
Device Manager error Codes 1-5
Device Manager error Codes 6-10
Device Manager error Codes 16-20
Device Manager error Codes 21-25
Device Manager error Codes 26-30
Device Manager error Codes 31-35
Device Manager error Codes 36-40
Device Manager error Codes 41-45
device manager error codes(6-10)
Code 6
Code Meaning: (Not applicable to Windows XP) Another device is using a resource that this device needs.
Recommended Resolution: Run msinfo32.exe to get more information on the conflict. Check the Resources tab to get details of the conflict. Refer to the hardware documentation and/or the manufacturer’s Web site for instructions on the correct values that need to be set manually. Clear the Automatic Settings checkbox, click the Change Setting button and input the values.
OR
Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
AND/OR
Remove the device from Device Manager and reinstall it using Add Hardware Wizard.
Code 7
Code Meaning: (Not applicable to Windows XP) The drivers need to be reinstalled.
Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Code 8
Code Meaning: (Not applicable to Windows XP) Windows cannot load the basic device loader file that loads the device driver, or it is missing or corrupt, or a software value for the device is missing or corrupt.
Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Code 9
Code Meaning: (Not applicable to Windows XP) The BIOS is reporting the resources for this device incorrectly and the Windows Registry is invalid.
Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver and the correct Registry entries from the manufacturer.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
OR (as a last resort)
Reinstall Windows.
Code 10
Code Meaning: The hardware will report the reason for failure that Windows should display. If the hardware doesn’t report the reason for failure, Windows will say that the device is not present, not working correctly or does not have all the required drivers installed.
Recommended Resolution: If the failure message is present, use that to troubleshoot the problem by referring to the documentation or manufacturer’s Web site.
AND/OR
Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Recommended Resolution: If the failure message is present, use that to troubleshoot the problem by referring to the documentation or manufacturer’s Web site.
AND/OR
Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Related Articles
Device Manager error Codes 11-15
Device Manager error Codes 16-20
Device Manager error Codes 21-25
Device Manager error Codes 26-30
Device Manager error Codes 31-35
Device Manager error Codes 36-40
Device Manager error Codes 41-45
Device Manager error Codes 45-49
device manager error codes(1-5)
Device Manager Error Codes
Additionally, a problem code explaining the problem is displayed for the device. The next step is to understand what each of these error codes mean and apply the recommended resolution. The list of problem codes and the recommended resolution are as follows:
Code 1
Code Meaning: The device is not configured correctly.
Recommended Resolution: The software drivers for the device have been incorrectly installed or incorrectly configured. Select the Driver tab and click the Update Driver button. This will launch an update Wizard. Follow the instructions and locate the correct driver for the device to install it.
Additionally, you could try removing the device from Device Manager and reinstalling it using the Add Hardware Wizard. Verify from the hardware documentation/manufacturer’s Web site that the device will work with your OS.
Code 2
Code Meaning: (Not applicable to Windows XP) Depending on the type of device, this could indicate either a problem with the BIOS or a problem with loading the device driver.
Recommended Resolution: Check with the BIOS manufacturer for an updated BIOS. See the BIOS section of this guide on how to update the BIOS.
OR
Get an updated driver for the device from the manufacturer and update the device software by clicking Update Driver on the Driver tab.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Code 3
Code Meaning: The driver is corrupt or your system is running low on memory and other resources.
Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
AND/OR
Close any applications using memory.
AND/OR
Add more RAM. See the chapter on Memory on how to do that.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Code 4
Code Meaning: (Not applicable to Windows XP) One of the drivers for the device may have been corrupted, or its Windows Registry entry may be damaged.
Recommended Resolution: Check the registry by running scanregw. exe. Click Start > Run. Type scanregw.exe and hit [Enter]. This program will check the Registry for corruption and prompt you to restore a previous good version of the Registry if it encounters any damaged entries.
AND
Remove the device from Device Manager and reinstall it using Add Hardware Wizard.
Code 5
Code Meaning: (Not applicable to Windows XP) The device has requested a resource that Windows doesn’t know how to handle.
Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Additionally, a problem code explaining the problem is displayed for the device. The next step is to understand what each of these error codes mean and apply the recommended resolution. The list of problem codes and the recommended resolution are as follows:
Code 1
Code Meaning: The device is not configured correctly.
Recommended Resolution: The software drivers for the device have been incorrectly installed or incorrectly configured. Select the Driver tab and click the Update Driver button. This will launch an update Wizard. Follow the instructions and locate the correct driver for the device to install it.
Additionally, you could try removing the device from Device Manager and reinstalling it using the Add Hardware Wizard. Verify from the hardware documentation/manufacturer’s Web site that the device will work with your OS.
Code 2
Code Meaning: (Not applicable to Windows XP) Depending on the type of device, this could indicate either a problem with the BIOS or a problem with loading the device driver.
Recommended Resolution: Check with the BIOS manufacturer for an updated BIOS. See the BIOS section of this guide on how to update the BIOS.
OR
Get an updated driver for the device from the manufacturer and update the device software by clicking Update Driver on the Driver tab.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Code 3
Code Meaning: The driver is corrupt or your system is running low on memory and other resources.
Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
AND/OR
Close any applications using memory.
AND/OR
Add more RAM. See the chapter on Memory on how to do that.
AND/OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Code 4
Code Meaning: (Not applicable to Windows XP) One of the drivers for the device may have been corrupted, or its Windows Registry entry may be damaged.
Recommended Resolution: Check the registry by running scanregw. exe. Click Start > Run. Type scanregw.exe and hit [Enter]. This program will check the Registry for corruption and prompt you to restore a previous good version of the Registry if it encounters any damaged entries.
AND
Remove the device from Device Manager and reinstall it using Add Hardware Wizard.
Code 5
Code Meaning: (Not applicable to Windows XP) The device has requested a resource that Windows doesn’t know how to handle.
Recommended Resolution: Run the Update Driver Wizard and reinstall the driver or get an updated driver from the manufacturer.
OR
Remove the device from Device Manager and reinstall it using the Add Hardware Wizard.
Related Articles
Device Manager error Codes 6-10
Device Manager error Codes 11-15
Device Manager error Codes 16-20
Device Manager error Codes 21-25
Device Manager error Codes 26-30
Device Manager error Codes 31-35
Device Manager error Codes 36-40
Device Manager error Codes 41-45
Device Manager error Codes 45-49
Using Device Manager
The Device Manager utility provides a graphical view of all the hardware installed on the computer along with their associated device drivers and resources. It also acts as a central point to change any hardware settings and update associated device drivers. To access Device Manager on Windows 9x/ME, right-click My Computer and select Properties. Select the Device Manager tab. On Windows 2000/XP, right-click My Computer, select Manage, and click Device Manager in the left pane.
Device Manager will list all the hardware in the PC in a tree structure. You can view devices by device-type or by connectiontype. In either view, Device Manager will list the devices causing problems. The problem devices will be listed with any of the following symbols:
Device Manager will list all the hardware in the PC in a tree structure. You can view devices by device-type or by connectiontype. In either view, Device Manager will list the devices causing problems. The problem devices will be listed with any of the following symbols:
- A black exclamation mark (!) in a yellow circle means that the device has a problem. Note: A problem-state device could still be working.
- A red “X” means the device is disabled. That is, it is physically present in the computer and is consuming resources, but does not have a driver loaded.
- A blue “i” on a white circle means that the device’s “Use Automatic Settings” feature is not selected for the device, and that the resources were manually allocated, usually for non-Plug and Play devices. Note: This does not mean that the device is in a problem or disabled state.
- A green question mark (?) in Device Manager means that a compatible (and not the actual) driver for this device is installed,which makes it possible that all the functionality may not b available. Note: This applies only to Windows ME.
- A yellow question mark (?) with “Unknown Device” means that Windows has not recognised the device.
Once you’ve identified the device(s) with problems, double-click on the device to bring up the property page for the device. The property page or sheet has a General tab that shows the details of the device, and its current status (enabled or disabled). Depending on the type of device, there may be additional tabs such as Resources, Driver and Settings.
Installation of non-Plug and Play devices
If the device is not getting detected by Plug and Play during system startup, this usually means that you have a non-Plug and Play device. If you have the manufacturer’s CD and/or manual, look for installation instructions. Non-Plug and Play devices are usually older, and require manual allocation of resources, usually through setting jumpers or switchers on the device itself. Once you have ensured that the device has been configured as per the manufacturer’s guidelines, boot up and install any software provided by the manufacturer as per the installation guidelines.
If there are no installation guidelines or the device is a second hand component with no documentation or you don’t have the required software drivers, then you can try to force Windows to recognise the device. First try to verify if the physical installation and the jumper/switch settings on the device are correct. Search the Internet for information on how to do this. If you are able to do this, good; if not, don’t worry too much about it and go on to forcing Windows to recognise the device:
1. Click on the Add New Hardware (Windows 9x/ME) / Add Hardware (Windows 2000/XP) in the Control Panel. The Add Hardware Wizard will start up. Click Next.
2. If you have Windows 9x/ME go to Step 3, else go to Step 5.
3. In Windows 9x/ME, the Wizard will inform you that it is going to search for new hardware. Allow it to do so by clicking Next twice. After Windows finishes searching for Plug and Play Devices it will report that no Plug and Play devices are found.
4. Click Next. The first option tells Windows to search for non-Plug and Play devices. If it successfully detects the device, follow the on-screen instructions to complete the installation. Otherwise, select “No, I want to select the hardware from a list” and click Next. Go to Step 6.
5. In Windows 2000/XP, select “Add a new hardware device” and click Next. In the next dialog box, you can either ask Windows to search for a driver, or you can install the device manually. For manual device installation, select “Install the hardware that I manually select from a list (Advanced)”.
6. Select the hardware type from the list and click Next.
7. If you know the name of the device manufacturer, select the name of the manufacturer and browse through the list on the right side to see if your device model number is listed or a generic name for your model series e.g. HP DeskJet for DeskJet printers. If you do not know the name of the manufacturer or the device model number, check if there are standard device types that you can install. If there are no standard types that can be installed, you will need to find a suitable driver by searching the Internet or getting it from other sources.
8. If the device has a standard type, choose the specification closest matching to your device. If the device does not have a standard type, click the “Have Disk…” button and provide the location for the appropriate driver installation file. Follow the on-screen instructions to complete the installation.
The above steps (for both Plug and Play and non-Plug and Play devices) should normally solve the device conflict and get your hardware operational. However, if you still face problems with the device see the section Using Device Manager for further troubleshooting.
If there are no installation guidelines or the device is a second hand component with no documentation or you don’t have the required software drivers, then you can try to force Windows to recognise the device. First try to verify if the physical installation and the jumper/switch settings on the device are correct. Search the Internet for information on how to do this. If you are able to do this, good; if not, don’t worry too much about it and go on to forcing Windows to recognise the device:
1. Click on the Add New Hardware (Windows 9x/ME) / Add Hardware (Windows 2000/XP) in the Control Panel. The Add Hardware Wizard will start up. Click Next.
2. If you have Windows 9x/ME go to Step 3, else go to Step 5.
3. In Windows 9x/ME, the Wizard will inform you that it is going to search for new hardware. Allow it to do so by clicking Next twice. After Windows finishes searching for Plug and Play Devices it will report that no Plug and Play devices are found.
4. Click Next. The first option tells Windows to search for non-Plug and Play devices. If it successfully detects the device, follow the on-screen instructions to complete the installation. Otherwise, select “No, I want to select the hardware from a list” and click Next. Go to Step 6.
5. In Windows 2000/XP, select “Add a new hardware device” and click Next. In the next dialog box, you can either ask Windows to search for a driver, or you can install the device manually. For manual device installation, select “Install the hardware that I manually select from a list (Advanced)”.
6. Select the hardware type from the list and click Next.
7. If you know the name of the device manufacturer, select the name of the manufacturer and browse through the list on the right side to see if your device model number is listed or a generic name for your model series e.g. HP DeskJet for DeskJet printers. If you do not know the name of the manufacturer or the device model number, check if there are standard device types that you can install. If there are no standard types that can be installed, you will need to find a suitable driver by searching the Internet or getting it from other sources.
8. If the device has a standard type, choose the specification closest matching to your device. If the device does not have a standard type, click the “Have Disk…” button and provide the location for the appropriate driver installation file. Follow the on-screen instructions to complete the installation.
The above steps (for both Plug and Play and non-Plug and Play devices) should normally solve the device conflict and get your hardware operational. However, if you still face problems with the device see the section Using Device Manager for further troubleshooting.
Installation of Plug and Play Devices
If the device is a new installation, Windows should detect the device at startup. One of three things can happen:
1. Windows will already have the required software device drivers and configure the system with or without user prompts
2. Windows will prompt the user for the OS installation CDs to retrieve the required drivers
3. Windows will prompt the user to provide the location for the required drivers supplied by the device manufacturer.
This would be your cue to insert the manufacturer’s CD that came with the device and point Windows to the correct driver installation file for the OS. Alternately, the manufacturer’s installation guide may provide a different method for installation.
Example: most USB devices require that you install the software first before connecting the device.
If Windows recognizes the device but you don’t have the manufacturer’s
CD, there is a good chance that you can enable basic
functionality by using the default Windows drivers. See the section
Installation of non-Plug and Play Devices on how to tell Windows to use
the default Windows drivers.
1. Windows will already have the required software device drivers and configure the system with or without user prompts
2. Windows will prompt the user for the OS installation CDs to retrieve the required drivers
3. Windows will prompt the user to provide the location for the required drivers supplied by the device manufacturer.
This would be your cue to insert the manufacturer’s CD that came with the device and point Windows to the correct driver installation file for the OS. Alternately, the manufacturer’s installation guide may provide a different method for installation.
Example: most USB devices require that you install the software first before connecting the device.
If Windows recognizes the device but you don’t have the manufacturer’s
CD, there is a good chance that you can enable basic
functionality by using the default Windows drivers. See the section
Installation of non-Plug and Play Devices on how to tell Windows to use
the default Windows drivers.
Resolving conflicts
With thousands of devices that work with Windows operating systems, it is practically impossible to describe all scenario specific solutions. What remains is to describe a strategy that will help you identify and resolve the problem.
The first step is to determine that the problem is really a hardware conflict at the OS level and not something caused by an incorrect physical installation. If you are able to normally boot into the OS, this would probably mean that the physical installation is fine. However, you cannot be certain at this stage. Try accessing the device. If the system hangs, crashes or starts acting weird, then it is pretty safe to assume that the physical installation is fine and the problem is because of the operating system’s interaction with the device. However, just to be on the safe side, power off and inspect the device for proper installation.
If everything seems correct, verify that you have followed the installation procedure as described in the manufacturer’s manual, have all the required software driver CDs and/or floppies on hand and switch the PC on.
If the device drivers are already installed and you are facing system instability when accessing or using the device, go to the Using the Device Manager section.
The first step is to determine that the problem is really a hardware conflict at the OS level and not something caused by an incorrect physical installation. If you are able to normally boot into the OS, this would probably mean that the physical installation is fine. However, you cannot be certain at this stage. Try accessing the device. If the system hangs, crashes or starts acting weird, then it is pretty safe to assume that the physical installation is fine and the problem is because of the operating system’s interaction with the device. However, just to be on the safe side, power off and inspect the device for proper installation.
If everything seems correct, verify that you have followed the installation procedure as described in the manufacturer’s manual, have all the required software driver CDs and/or floppies on hand and switch the PC on.
If the device drivers are already installed and you are facing system instability when accessing or using the device, go to the Using the Device Manager section.
Problems causing conflicts
A wide range of problems may
be causing the above and other symptoms. Assuming that the hardware is not defective and has been installed correctly, at the operating system level the problems can be broadly classified as follows:
Note: Some devices, such as PCI devices, can share a single IRQ without conflicts in Windows 2000/XP.
be causing the above and other symptoms. Assuming that the hardware is not defective and has been installed correctly, at the operating system level the problems can be broadly classified as follows:- There could be a resource allocation (IRQ/memory address) conflict. Two devices are allocated the same IRQ/memory address space.Usually, non-Plug and Play devices would give this problem. Since Windows is unable to detect these devices it may not allocate the resources properly and hence cause conflicts with an existing device.
Note: Some devices, such as PCI devices, can share a single IRQ without conflicts in Windows 2000/XP.
- The software device drivers may not be compatible with the operating system, or may have been corrupted, or may not have been installed. If you have recently upgraded from Windows 95/98, this would usually be the problem.
- A new software program installed is trying to use system resources allocated to other hardware devices or software programs.
Subscribe to:
Posts (Atom)
Times