Archive

Posts Tagged ‘Driver’

How to Update Drivers in Windows XP

December 3rd, 2009 1 comment

If Windows XP doesn’t install a device automatically, or if the hardware is having some kind of problem, you’ll need to know how to update/install drivers in Windows XP.

If you see a Device Manager Error, sometimes the solution is as easy as updating the driver. Updating the drivers for a piece of hardware will sometimes enable additional features for the hardware as well.

Here’s how to update drivers in Windows XP:

  1. Check the device manufacturer’s web site for the most current drivers available for your hardware. Note: Many drivers come packaged with software that automatically installs the driver. The manufacturer’s website will tell you if the driver download is packaged this way and if so, the steps below aren’t usually necessary.
  2. Open Device Manager
  3. Locate the hardware device you wish to update drivers for.Click on the [+] icon to expand the categories.
  4. After finding the hardware you’re updating drivers for, right click on the hardware’s name or icon and choose Properties. In this Properties window, click the Driver tab.
  5. Click the Update Driver… button. The Hardware Update Wizard will begin.

  6. Click the No, not this time button and then click the Next > button. When asked “Can Windows connect to Windows Update to search for software?”
  7. Choose the Install from a list or specific location (Advanced) button and then click the Next > button. When asked What do you want the wizard to do?” The next window that appears will be the Please choose your search and installation options. window containing several buttons and checkboxes.
  8. Choose the Don’t search. I will choose the driver to install button and then click the Next > button.
  9. Click the Have Disk… button on the Select the device driver you want to install for this hardware. window.
  10. Click the Browse… button on the Install From Disk dialog box that appeared.
  11. Click the INF file that displays in the file list and click the Open button.
  12. Click the OK button back on the Install From Disk dialog box.
  13. Choose the newly added hardware back on the Select the device driver you want to install for this hardware. window and then click the Next > button.

    If you’re prompted with a message warning you about the software for the hardware device not passing the Windows Logo testing, click the Continue Anyway button. Many drivers are not Windows certified but are still perfectly safe to install. (If you’re installing a driver obtained from anywhere other than the manufacturer of the hardware, click the STOP Installation button instead and obtain drivers from the manufacturer directly.)

  14. The Hardware Update Wizard will now use the instructions provided in the INF file from Step 11 to install the updated drivers for your hardware. Follow any additional instructions on screen to complete the driver update.
  15. After the driver update is complete, click Yes to the “Do you want to restart your computer now?” question on System Settings Change and other important areas of your computer. Restarting your machine is a good way to confirm that updating drivers hasn’t negatively impacted some other area of Windows. dialog box. Not all driver updates require a restart of your computer. Even if you’re not prompted, I always recommend restarting anyway. The driver update process involves changes to the Windows Registry (If a driver update causes an issue, you can always roll back the driver)
Categories: Driver FAQ, XP Drivers Tags: ,

STOP Error 0x000000B4 – The video driver failed to initialize

December 3rd, 2009 No comments

STOP error 0xB4 means that Windows was unable to enter graphics mode. Your video driver failed to initialize. This happens because of a conflict with the computer’s parallel port and your video card, if the parallel port I/O address is set to 03BC.

To fix this problem you need to change the parallel port I/O address from 03BC to 0378

  1. Restart your machine, and press F8 at the Starting Windows screen.
  2. Select Safe Mode, and then press ENTER
  3. Log on to your using the local administrator account.
  4. Click Start, Settings, and then click Control Panel.
  5. Double-click System.
  6. Click the Hardware tab, and then click Device Manager.
  7. Click the plus “+” next to ports to expand the ports list.
  8. Select the printer port LPT1, and on the Action menu, click Properties.
  9. Click the Resources tab, and then clear the Use Automatic Settings check box .
  10. In the Settings Based On drop down menu, select a setting that uses an I/O address of 0378 instead of 03BC.
  11. Click OK, and then close Device Manager.

Delete the UpperFilters and LowerFilters Registry Values

December 3rd, 2009 No comments

You can solve several Device Manager error codes by deleting the UpperFilters and LowerFilters registry values from the Windows Registry. Some of the common Device Manager error codes that are caused by UpperFilters and LowerFilters include Code 19, Code 31, Code 39 and Code 41.

It is fairly simple to remove the UpperFilters and LowerFilters registry values. Before you get started, make sure you have backed up the registry keys that you are modifying.

  • Click Start, Run.
  • In the textbox, type regedit (This opens the Registry Editor program.)
  • Click OK.
  • Find the HKEY_LOCAL_MACHINE folder and click the (+) icon to expand the folder.
  • Keep expanding the folders until you reach the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class registry key.
  • Click the (+) icon next to the CLASS list to expand it. You’ll see a list of 32 digit subkeys. Each one is unique and corresponds to a different class of hardware.
  • Now you need to figure out which device glass GUID (Globally Unique Identifier) you need.
  • Click on the correct subkey
  • Right click on UpperFilters and choose Delete. Confirm that you would like to delete it.
  • Now, right click on LowerFilters and choose Delete. Confirm that you would like to delete it.
  • If you see files named UpperFilters.bak or LowerFilters.bak, you don’t need to delete them.
  • Close the Registry Editor and restart your computer.

Yellow Exclamation Point

November 23rd, 2009 No comments

yellow exclamation pointA yellow exclamation point next to a device in Device Manager means that Windows has identified a problem of some kind of problem with that device.

This helps notify you that there might be a system resource conflict, a driver issue or another problem. Seeing the yellow mark itself doesn’t give you any valuable information other than notify you of a problem. It does mean that a “Device Manager Error Code” has been generated. To fix whatever problem is going on, you’ll need to view this code and troubleshoot accordingly.

Updating Windows XP Drivers

November 15th, 2009 1 comment

Why should you take the time to update your Windows XP Drivers? Here’s what you need to understand what you are updating and what it will change:

Windows XP uses drivers that corresponds with your computer and programs every time you use open your computer to do something. To make sure your computer and devices are performing to their max, you need to make sure you have the latest drivers installed on your computer. This includes hardware like mouse drivers, keyboard drivers, graphics card, system essentials, other hardware, internal hardware, motherboard and Windows drivers, etc. There are too many drivers to list , but if you are curious what drivers are installed on your computer currently, look at the ‘System and System 32’ files in your Windows root folder (usually on your C drive).

Anything with a shell or .dll extension is a driver that will Windows XP will be using to launch your applications.

One of the most common problems you will see for computers that don’t have the latest Windows XP drivers installed is the Device Manager error codes, which happens when a hardware fails to install properly.

XP is programmed to have a list of drivers for each manufacturer stored somewhere in the root drive. Driver files are normally small, as they consist normally of only instruction and constructed code. So, Microsoft is able to constantly update and add new device signatures into its data banks and suggest new updates for you to install to your computer. (This is known as the ‘automatic update’ service, where the main Microsoft server will download the files into your computer (which will more than often require a restart) and update it.

STOP Error 0x000000AD: VIDEO_DRIVER_DEBUG_REPORT_REQUEST

November 3rd, 2009 No comments

STOP error 0xAD is a fault issued by video driver. It might indicate a bug in the video driver or that the video port created a non-fatal minidump on behalf of the video driver during run time.

Unfortunately this is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is most likely lost.

STOP code 0x000000AD may also display “VIDEO_DRIVER_DEBUG_REPORT_REQUEST” in the same STOP message.

Problems with a specific USB device in Windows XP

October 12th, 2009 No comments

USB problems are usually an easy problem to solve. First, isolate the problem. Unplug all USB devices from the system, including USB hubs. Next, take a known good USB device and attach it to the system. If the known good device works, then you can be sure that there is nothing wrong with the port itself.

Now take the device that was malfunctioning and plug it directly into one of the computer’s USB ports while no other USB devices are connected to the system. If the device starts working, the problem most likely was that device was conflicting with another USB device. One way that USB devices can conflict with each other is if they share a common serial number. Each USB device in a system must have a unique serial number. Having two devices with a common serial number is very rare, but there are documented cases of it happening.

If the device now works and it isn’t sharing a serial number with another device, it was probably malfunctioning because of an overloaded USB hub or a conflicting device driver (Click here to run a scan for updated drivers). The only real way to sort out the problem is to use trial-and-error by plugging in various combinations of USB devices until you find the device or devices that the malfunctioning device is conflicting with. Once you track this down, you can usually solve the problem by moving the devices to different physical USB ports or by updating the drivers for both devices.

What if plugging in the malfunctioning device without any other USB devices being plugged in doesn’t cure the problem?

Try checking the computer’s Event Logs for clues to the malfunction. If the event log doesn’t give any clues, try plugging the malfunctioning device into another computer. If the device works on the other computer, then you can be sure that the device is good.

If the alternate computer is using an operating system other than Windows XP, the problem could be that the device or its driver isn’t Windows XP-compatible. Check to see if there are updates for your device for XP, if not, contact the device’s manufacturer to see if there are any known issues with using the device with Windows XP.

If the alternate computer is running Windows XP and the device is working, then I recommend checking out what version of the device driver is being used on each machine and using the one that works, even if it isn’t the most recent.

Error Code 3

October 9th, 2009 No comments

The Code 3 error is one of several Device Manager error codes. The Code 3 error will usually appear like:

The driver for this device might be corrupted, or your system may be running low on memory or other resources. (Code 3)

Important: Device Manager error codes are only seen in the Device Manager. If you see the Code 3 error somewhere else in Windows, it is most likely a system error.

What Causes the Code 3 Error?

A Code 3 error is generated when the Device Manager can’t start the device due to  outdated or corrupted drivers or poor system resources.

Resolution

  1. Restart your computer. There is always the chance that the error Code 3 you’re seeing on a device was caused by some temporary memory problem or an issue in the Device Manager or with the hardware. Sometimes rebooting your machine might fix the Code 3 error.
  2. Undo Recent Changes. If you recently installed a device or made a change in the Device Manager just before the Code 3 error appeared, then undo whatever change you made to see if the error is still there. Depending on the changes you made, you might try to:
    • Remove or reconfigure the newly installed device.
    • Roll back the driver to a previous version.
    • Use System Restore to go back to a date prior to your Code 3 error.
  3. Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a likely solution to a Code 3 error. (If a USB device is generating the Code 3 error, uninstall every device under the Universal Serial Bus controllers hardware category in the Device Manager as part of the driver reinstall.) It is important to note that a full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
  4. Update the drivers for the device. It’s also very possible that installing the latest drivers for the device could correct the Code 3 error. If it does, it means that the stored Windows drivers you reinstalled in Step 3 were were probably damaged.
  5. Install the latest Windows service pack Microsoft often releases service packs and other patches for Windows, one of which might contain a fix for the Code 3 error.
  6. Replace the hardware. A problem with the hardware device might be causing the Code 3 error, in which case replacing the hardware is your next logical step. Another possibility, is that the device is not compatible with your version of Windows. You can check the Windows HCL to be sure. If you’re positive that a hardware problem isn’t causing the Code 3 error, you could try to repair your Windows instillation. If that doesn’t work, as a last resort, you may need to contact a local repair shop or try a clean install of Windows.

Device Class GUIDs for Popular Types of Hardware

October 1st, 2009 No comments

Other than programming for a device driver, the Globally Unique Identifier (GUID) for a device class is useful when tracking down driver information in the Windows Registry.

For example, the solution to several Device Manager errors include removing specific registry entries after a device’s GUID.

Note: This is not a complete list of device class GUIDs. Devices can generate unique classes based on various variables making it virtually impossible to list them all.

Device Class Class GUID Notes
Battery Devices Battery {72631e54-78a4-11d0-bcf7-00aa00b7b32a} This class includes battery devices and UPS devices.
Biometric Device Biometric {53D29EF7-377C-4D14-864B-EB3A85769359} Starting with Windows Server 2003, this class includes all biometric-based personal identification devices.
Bluetooth Devices Bluetooth {e0cbf06c-cd8b-4647-bb8a-263b43f0f974} Starting with Windows XP SP1, this class includes all Bluetooth devices.
CD-ROM Drives CDROM {4d36e965-e325-11ce-bfc1-08002be10318} This class includes CD-ROM drives, including SCSI CD-ROM drives. By default, the system’s CD-ROM class installer also installs a system-supplied CD audio driver and CD-ROM changer driver as Plug and Play filters.
Disk Drives DiskDrive {4d36e967-e325-11ce-bfc1-08002be10318} This class includes hard disk drives. See also the HDC and SCSIAdapter classes.
Display Adapters Display {4d36e968-e325-11ce-bfc1-08002be10318} This class includes video adapters. Drivers for this class include display drivers and video miniport drivers.
Floppy Disk Controllers FDC {4d36e969-e325-11ce-bfc1-08002be10318} This class includes floppy disk drive controllers.
Floppy Disk Drives FloppyDisk {4d36e980-e325-11ce-bfc1-08002be10318} This class includes floppy disk drives.
Hard Disk Controllers HDC {4d36e96a-e325-11ce-bfc1-08002be10318} This class includes hard disk controllers, including ATA/ATAPI controllers but not SCSI and RAID disk controllers.
Human Interface Devices (HID) HIDClass {745a17a0-74d3-11d0-b6fe-00a0c90f57da} This class includes interactive input devices that are operated by the system-supplied HID class driver. This includes USB devices that comply with the USB HID Standard and non-USB devices that use a HID minidriver. For more information, see HIDClass Device Setup Class.. (See also the Keyboard or Mouse classes later in this list.)
IEEE 1284.4 Devices Dot4 {48721b56-6795-11d2-b1a8-0080c72e74a2} This class includes devices that control the operation of multifunction IEEE 1284.4 peripheral devices.
IEEE 1284.4 Print Functions Dot4Print {49ce6ac8-6f86-11d2-b1e5-0080c72e74a2} This class includes Dot4 print functions. A Dot4 print function is a function on a Dot4 device and has a single child device, which is a member of the Printer device setup class.
IEEE 1394 Devices That Support the 61883 Protocol 61883 {7ebefbc0-3200-11d2-b4c2-00a0C9697d07} This class includes IEEE 1394 devices that support the IEC-61883 protocol device class.

The 61883 component includes the 61883.sys protocol driver that transmits various audio and video data streams over the 1394 bus. These currently include standard/high/low quality DV, MPEG2, DSS, and Audio. These data streams are defined by the IEC-61883 specifications.

IEEE 1394 Devices That Support the AVC Protocol AVC {c06ff265-ae09-48f0-812c-16753d7cba83} This class includes IEEE 1394 devices that support the AVC protocol device class.
IEEE 1394 Devices That Support the SBP2 Protocol SBP2 {d48179be-ec20-11d1-b6b8-00c04fa372a7} This class includes IEEE 1394 devices that support the SBP2 protocol device class.
IEEE 1394 Host Bus Controller 1394 {6bdd1fc1-810f-11d0-bec7-08002be2092f} This class includes 1394 host controllers connected on a PCI bus, but not 1394 peripherals. Drivers for this class are system-supplied.
Imaging Device Image {6bdd1fc6-810f-11d0-bec7-08002be2092f} This class includes still-image capture devices, digital cameras, and scanners.
IrDA Devices Infrared {6bdd1fc5-810f-11d0-bec7-08002be2092f} This class includes infrared devices. Drivers for this class include Serial-IR and Fast-IR NDIS miniports, but see also the Network Adapter class for other NDIS network adapter miniports.
Keyboard Keyboard {4d36e96b-e325-11ce-bfc1-08002be10318} This class includes all keyboards. That is, it must also be specified in the (secondary) INF for an enumerated child HID keyboard device.
Media Changers MediumChanger {ce5939ae-ebde-11d0-b181-0000f8753ec4} This class includes SCSI media changer devices.
Memory Technology Driver MTD {4d36e970-e325-11ce-bfc1-08002be10318} This class includes memory devices, such as flash memory cards.
Modem Modem {4d36e96d-e325-11ce-bfc1-08002be10318} This class includes modem devices. An INF file for a device of this class specifies the features and configuration of the device and stores this information in the registry. An INF file for a device of this class can also be used to install device drivers for a controllerless modem or a software modem. These devices split the functionality between the modem device and the device driver. For more information about modem INF files and Microsoft Windows Driver Model (WDM) modem devices, see Overview of Modem INF Files and Adding WDM Modem Support.
Monitor Monitor {4d36e96e-e325-11ce-bfc1-08002be10318} This class includes display monitors. An INF for a device of this class installs no device driver(s), but instead specifies the features of a particular monitor to be stored in the registry for use by drivers of video adapters. (Monitors are enumerated as the child devices of display adapters.)
Mouse Mouse {4d36e96f-e325-11ce-bfc1-08002be10318} This class includes all mouse devices and other kinds of pointing devices, such as trackballs. That is, this class must also be specified in the (secondary) INF for an enumerated child HID mouse device.
Multifunction Devices Multifunction {4d36e971-e325-11ce-bfc1-08002be10318} This class includes combo cards, such as a PCMCIA modem and netcard adapter. The driver for such a Plug and Play multifunction device is installed under this class and enumerates the modem and netcard separately as its child devices.
Multimedia Media {4d36e96c-e325-11ce-bfc1-08002be10318} This class includes Audio and DVD multimedia devices, joystick ports, and full-motion video capture devices.
Multiport Serial Adapters MultiportSerial {50906cb8-ba12-11d1-bf5d-0000f805f530} This class includes intelligent multiport serial cards, but not peripheral devices that connect to its ports. It does not include unintelligent (16550-type) multiport serial controllers or single-port serial controllers (see the Ports class).
Network Adapter Net {4d36e972-e325-11ce-bfc1-08002be10318} This class includes NDIS miniport drivers excluding Fast-IR miniport drivers, NDIS intermediate drivers (of virtual adapters), and CoNDIS MCM miniport drivers.
Network Client NetClient {4d36e973-e325-11ce-bfc1-08002be10318} This class includes network and/or print providers.
Network Service NetService {4d36e974-e325-11ce-bfc1-08002be10318} This class includes network services, such as redirectors and servers.
Network Transport NetTrans {4d36e975-e325-11ce-bfc1-08002be10318} This class includes NDIS protocols, CoNDIS stand-alone call managers, and CoNDIS clients, in addition to higher level drivers in transport stacks.
PCI SSL Accelerator Security Accelerator {268c95a1-edfe-11d3-95c3-0010dc4050a5} This class includes devices that accelerate secure socket layer (SSL) cryptographic processing.
PCMCIA Adapters PCMCIA {4d36e977-e325-11ce-bfc1-08002be10318} This class includes PCMCIA and CardBus host controllers, but not PCMCIA or CardBus peripherals. Drivers for this class are system-supplied.
Ports (COM & LPT ports) Ports {4d36e978-e325-11ce-bfc1-08002be10318} This class includes serial and parallel port devices. See also the MultiportSerial class.
Printers Printer {4d36e979-e325-11ce-bfc1-08002be10318} This class includes printers.
Printers, Bus-specific class drivers PNPPrinters {4658ee7e-f050-11d1-b6bd-00c04fa372a7} This class includes SCSI/1394-enumerated printers. Drivers for this class provide printer communication for a specific bus.
Processors Processor {50127dc3-0f36-415e-a6cc-4cb3be910b65} This class includes processor types.
SCSI and RAID Controllers SCSIAdapter {4d36e97b-e325-11ce-bfc1-08002be10318} This class includes SCSI HBAs (Host Bus Adapters) and disk-array controllers.
Smart Card Readers SmartCardReader {50dd5230-ba8a-11d1-bf5d-0000f805f530} This class includes smart card readers.
Storage Volumes Volume {71a27cdd-812a-11d0-bec7-08002be2092f} This class includes storage volumes as defined by the system-supplied logical volume manager and class drivers that create device objects to represent storage volumes, such as the system disk class driver.
System Devices System {4d36e97d-e325-11ce-bfc1-08002be10318} This class includes HALs, system buses, system bridges, the system ACPI driver, and the system volume manager driver.
Tape Drives TapeDrive {6d807884-7d21-11cf-801c-08002be10318} This class includes tape drives, including all tape miniclass drivers.
USB USB {36fc9e60-c465-11cf-8056-444553540000} This class includes USB host controllers and USB hubs, but not USB peripherals. Drivers for this class are system-supplied.
Windows CE USB ActiveSync Devices WCEUSBS {25dbce51-6c8f-4a72-8a6d-b54c2b4fc835} This class includes Windows CE ActiveSync devices.

The WCEUSBS setup class supports communication between a personal computer and a device that is compatible with the Windows CE ActiveSync driver (generally, PocketPC devices) over USB.

Windows SideShow SideShow {997b5d8d-c442-4f2e-baf3-9c8e671e9e21} This class includes all devices that are compatible with Windows SideShow. This class is supported in Windows Vista and later versions of Windows.

System-Defined Device Setup Classes Reserved for System Use

Device Class Class GUID Notes
Adapter Adapter {4d36e964-e325-11ce-bfc1-08002be10318} This class is obsolete.
APM APMSupport {d45b1c18-c8fa-11d1-9f77-0000f805f530} This class is reserved for system use.
Computer Computer {4d36e966-e325-11ce-bfc1-08002be10318} This class is reserved for system use.
Decoders Decoder {6bdd1fc2-810f-11d0-bec7-08002be2092f} This class is reserved for future use.
Global Positioning System GPS {6bdd1fc3-810f-11d0-bec7-08002be2092f} This class is reserved for future use.
Host-side IEEE 1394 Kernel Debugger Support 1394Debug {66f250d6-7801-4a64-b139-eea80a450b24} This class is reserved for system use.
IEEE 1394 IP Network Enumerator Enum1394 {c459df55-db08-11d1-b009-00a0c9081ff6} This class is reserved for system use.
No driver NoDriver {4d36e976-e325-11ce-bfc1-08002be10318} This class is obsolete.
Non-Plug and Play Drivers LegacyDriver {8ecc055d-047f-11d1-a537-0000f8753ed1} This class is reserved for system use.
Other Devices Unknown {4d36e97e-e325-11ce-bfc1-08002be10318} This class is reserved for system use. Enumerated devices for which the system cannot determine the type are installed under this class. Do not use this class if you are unsure in which class your device belongs. Either determine the correct device setup class or create a new class.
Printer Upgrade Printer Upgrade {4d36e97a-e325-11ce-bfc1-08002be10318} This class is reserved for system use.
Sound Sound {4d36e97c-e325-11ce-bfc1-08002be10318} This class is obsolete.
Storage Volume Snapshots VolumeSnapshot {533c5b84-ec70-11d2-9505-00c04F79deaf} This class is reserved for system use.
Categories: Troubleshooting Tags: , ,

How to find the best driver for your hardware

September 12th, 2009 No comments

Are you confused about drivers? Do you have a device that keeps throwing errors or restarting itself? Ready to pull your hair out? Here are some tips on how to find the best drivers for your hardware.

Usually, the best drivers are found on the manufacturer’s website. Find the support page of the manufacturer’s web site. Most manufacturer’s will have a button for drivers and updates. Search for your device name/model number and the website will list drivers/updates available for you to download. If after downloading and installing the driver you continue to have problems, try sending the manufacturer an e-mail detailing the issues you are having. Many updates are developed because of user complaints.

If your hardware is fairly old, the manufacturer might not have the drivers for it in their database of drivers. Try searching the Internet for different websites that have drivers available for download. Include your device manufacturer’s name and model number, and you might find other people posting comments on message boards about what issues/fixes they have found for the same device.

Downloading the latest drivers for your device usually solves the problem. However, there are cases in which the driver will not work. Even a driver from the manufacturer’s website might not work (on rare occasions). You can try to roll back the driver to an older version. Sometimes it won’t have all the new features, but at least your device might work. Are you hesitant to try the older version of your driver? Newer doesn’t necessarily mean better, the best driver is the one your hardware performs best with! Again, try searching the Internet for message boards to see what other people have experienced.

Sometimes you will encounter a problem because the driver files are corrupted. You can solve this by just reinstalling the driver. (It isn’t necessary to upgrade or roll back your driver.) Errors can also be caused by faulty hardware installation. Hardware drivers from the manufacturer’s website should be trusted and preferred over drivers picked randomly off the Web!

Categories: Driver FAQ Tags: ,