Stop 0xFE or BUGCODE_USB_DRIVER
The Stop 0xFE message occurs if the kernel detects an error in a USB driver.
Interpreting the Message
This Stop message has four parameters. Parameter 1 indicates the type of violation, whereas parameters 2 through 4 provide more information specific to that error type. Typically, only parameter 1 is useful to system administrators, although parameters 2 through 4 might be useful to Microsoft developers, who will be able to extract that information from the memory dump.
Parameter 1 can have a value of 0x1 to 0x5, as described here:
- An internal error has occurred in the USB stack.
- The USB client driver has submitted a USB request block (URB) that is still attached to another I/O request packet (IRP) that is pending in the bus driver.
- The USB miniport driver has generated a Stop error. This usually happens in response to a catastrophic hardware failure.
- The caller has submitted an IRP that is already pending in the USB driver.
- A hardware failure has occurred because of a bad physical address found in a hardware data structure. This is not due to a driver bug.
Resolving the Problem
The following suggestions are specific to Stop 0xFE errors. For additional troubleshooting suggestions that apply to all Stop errors, see the section titled "Stop Message Checklist" later in this tutorial.
To resolve this problem, follow these procedures:
- Check the computer or motherboard manufacturer's Web site for updated system firmware.
- Upgrade the firmware and drivers of all USB devices attached to the computer.
- Verify that all hardware is compatible with Windows 7.
- Remove USB devices and external hubs one by one and determine whether the Stop error reoccurs. If the Stop error does not reoccur when a specific device is not attached, that device might be malfunctioning, or it might not be compatible with Windows. Contact the device manufacturer for additional support.
- If problems persist, you might have a computer hardware failure. Contact your computer manufacturer for additional assistance.
In this tutorial:
- Troubleshooting Stop Messages
- Stop Message Overview
- Identifying the Stop Error
- Finding Troubleshooting Information
- Stop Messages
- Bugcheck Information
- Technical Information
- Debug Port and Dump Status Information
- Types of Stop Errors
- Memory Dump Files
- Configuring Small Memory Dump Files
- Configuring Kernel Memory Dump Files
- Configuring Complete Memory Dump Files
- How to Manually Initiate a Stop Error and Create a Dump File
- Using Memory Dump Files to Analyze Stop Errors
- Using Windows 7 Error Reporting
- Using Symbol Files and Debuggers
- Being Prepared for Stop Errors
- Record and Save Stop Message Information
- Check Software Disk Space Requirements
- Install a Kernel Debugger and Symbol Files
- Stop 0xA or IRQL_NOT_LESS_OR_EQUAL
- Stop 0x1E or KMODE_EXCEPTION_NOT_HANDLED
- Understanding Kernel Stack Overflows
- Stop 0x24 or NTFS_FILE_SYSTEM
- Stop 0x2E or DATA_BUS_ERROR
- Stop 0x3B or SYSTEM_SERVICE_EXCEPTION
- Stop 0x3F or NO_MORE_SYSTEM_PTES
- Stop 0x50 or PA GE_FAULT_IN_NONPA GED_AREA
- Stop 0x77 or KERNEL_STACK_INPA GE_ERROR
- Stop 0x7A or KERNEL_DATA_INPA GE_ERROR
- Stop 0x7B or INACCESSIBLE_BOOT_DEVICE
- Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP
- Stop 0x9F or DRIVER_POWER_STATE_FAILURE
- Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
- Stop 0xC2 or BAD_POOL_CALLER
- Stop 0xCE or DRIVER_UNLOADED_WITHOUT_CANCELLING_ PENDING_OPERATIONS
- Stop 0xD1 or IRQL_NOT_LESS_OR_EQUAL
- Stop 0xD8 or DRIVER_USED_EXCESSIVE_PTES
- Stop 0xEA or THREAD_STUCK_IN_DEVICE_DRIVER
- Stop 0xED or UNMOUNTABLE_BOOT_VOLUME
- Stop 0xFE or BUGCODE_USB_DRIVER
- Stop 0x00000124
- Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED
- Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
- Hardware Malfunction Messages
- Stop Message Checklist
- Check Your Software
- Use the Last Known Good Configuration
- Restart the System in Safe Mode
- Check Event Viewer Logs
- Install Compatible Antivirus Tools
- Report Your Errors
- Install Operating System and Driver Updates
- Install and Use a Kernel Debugger
- Check Your Hardware
- Check for Nondefault Firmware Settings
- Check for Non-Default Hardware Clock Speeds
- Check by Running Hardware Diagnostic Tools
- Check for SCSI Disk and Controller Settings
- Check Memory Compatibility
- Check by Temporarily Removing Devices
- Check by Replacing a Device