• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Anyone ever get a BSOD in win XP that say's...

prob usb 🙂 Do you have a hard disk thats usb 2.0?




Bugcheck 0x000000FE Under Stress with USB 2.0 Hard Disks
View products that this article applies to.
This article was previously published under Q331988
SYMPTOMSWhen a computer that is running Windows XP is accessing USB 2.0 hard disks under heavy stress conditions, you may receive a bugcheck 0xFE message similar to the following:

BUGCODE_USB_DRIVER (fe)
In a USB Driver bugcheck, the first parameter is a USB bugcheck code that has the following arguments:
Argument 1: 00000002, BAD_URB. The USB client driver has submitted a USB Request Block (URB) that is still attached to another Input/Output (I/O) request packet (IRP) that is still pending in the USB driver.
Argument 2: 8162ea78, Address of the pending IRP.
Argument 3: 81707950, Address of the IRP that is passed in.
Argument 4: 8156db7c, Address of the URB that caused the error.
CAUSEThis behavior occurs because in the NT Kernel two threads try to start an I/O operation on the same packet.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows XP service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Date Time Version Size File name SP Level
----------------------------------------------------------------------
12-Nov-2002 23:21 5.1.2600.106 1,848,320 Ntkrnlmp.exe SP1
12-Nov-2002 23:21 5.1.2600.106 1,902,080 Ntkrnlpa.exe SP1
12-Nov-2002 23:21 5.1.2600.106 1,874,944 Ntkrpamp.exe SP1
12-Nov-2002 23:21 5.1.2600.106 1,880,064 Ntoskrnl.exe SP1
13-Nov-2002 00:28 5.1.2600.1143 1,892,352 Ntkrnlmp.exe SP2
13-Nov-2002 00:28 5.1.2600.1143 1,948,160 Ntkrnlpa.exe SP2
13-Nov-2002 00:28 5.1.2600.1143 1,921,024 Ntkrpamp.exe SP2
13-Nov-2002 00:28 5.1.2600.1143 1,924,480 Ntoskrnl.exe SP2



STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The information in this article applies to:
Microsoft Windows XP Professional SP1
Microsoft Windows XP Professional
Microsoft Windows XP Home Edition SP1
Microsoft Windows XP Home Edition




 
You must log in or register to reply here.

TRENDING THREADS

Back
Top