Random BSOD on Dell T-5400 bugcheck 0x000000FE problem with Spyder 3 Utility
-
Sunday, October 30, 2011 2:38 PM
All,
Debugger output below. I'm getting the following crashes at random a couple of times a week. I've checked online for driver updates and people with similar problems to no avail. The Spyder 3 Utility monitors a USB colorimeter made by datacolor. Any thoughts or suggestions as to next steps would be appreciated.
John
---------------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is availableSymbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a8670
Debug session time: Thu Sep 1 22:05:35.974 2011 (UTC - 4:00)
System Uptime: 1 days 18:21:28.753
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck FE, {2, fffffa80134fac10, fffffa800ef96330, fffffa800ceb0900}
*** ERROR: Module load completed but symbols could not be loaded for Spyder3.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
Probably caused by : usbuhci.sysFollowup: MachineOwner
---------5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000002, BAD_URB The USB client driver has submitted a URB that is
still attached to another IRP still pending in the bus
driver.
Arg2: fffffa80134fac10, Address of pending IRP.
Arg3: fffffa800ef96330, Address of IRP passed in.
Arg4: fffffa800ceb0900, Address URB that caused the error.Debugging Details:
------------------*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************IRP_ADDRESS: fffffa80134fac10
DEVICE_OBJECT: fffffa800fe4c050
DRIVER_OBJECT: fffffa800f737c50
IMAGE_NAME: usbuhci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0bff
MODULE_NAME: usbuhci
FAULTING_MODULE: fffff8800f44b000 usbuhci
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: Spyder3Utility
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff88004f15f79 to fffff80002edfc40
STACK_TEXT:
fffff880`08c38408 fffff880`04f15f79 : 00000000`000000fe 00000000`00000002 fffffa80`134fac10 fffffa80`0ef96330 : nt!KeBugCheckEx
fffff880`08c38410 fffff880`04f2144a : fffffa80`0f7d9000 fffffa80`1160acb0 00000000`00000000 fffffa80`0f7d9050 : USBPORT!USBPORT_Core_DetectActiveUrb+0x155
fffff880`08c38460 fffff880`04f29e74 : fffffa80`0ef96330 fffffa80`0fe40017 fffffa80`0ef96330 fffffa80`0ceb0900 : USBPORT!USBPORT_ProcessURB+0xad6
fffff880`08c38510 fffff880`04f03af4 : 00000000`00000000 fffffa80`0fe4c050 fffffa80`13cb4410 fffffa80`0ef96330 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff880`08c38550 fffff880`0559c566 : fffffa80`0fe57050 fffffa80`0f4bc060 fffffa80`0ef96330 fffffa80`0fe571a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff880`08c38590 fffff880`055ccd8f : 00000000`00000000 00000000`00000000 fffffa80`0f4bc060 fffffa80`1231fa90 : usbhub!UsbhFdoUrbPdoFilter+0xde
fffff880`08c385c0 fffff880`0559afb7 : 00000000`00000001 0000057f`edce0568 fffffa80`115f6b80 00000000`00000005 : usbhub!UsbhPdoInternalDeviceControl+0x373
fffff880`08c38610 fffff880`00f4278e : 00000000`00000000 00000000`00000001 0000057f`edce0568 fffff880`0e47e5f8 : usbhub!UsbhGenDispatch+0x57
fffff880`08c38640 fffff880`05ff8fda : fffffa80`0f4bce80 fffffa80`1231fa90 fffffa80`0f4863d0 0000057f`f0b79c28 : Wdf01000!imp_WdfRequestSend+0x43a
fffff880`08c38690 fffff880`05ff922d : fffffa80`1231fa90 fffffa80`12310017 0000057f`f0b89fd8 00000000`00000017 : Spyder3+0x5fda
fffff880`08c38760 fffff880`00f67f90 : fffffa80`1231fa90 fffffa80`0f4bcd30 fffffa80`0f4bcd30 fffff880`00000001 : Spyder3+0x622d
fffff880`08c38800 fffff880`00f6799f : 00000000`00000000 fffffa80`1231fa90 fffffa80`0f476020 fffffa80`0f476020 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x4b8
fffff880`08c38880 fffff880`00f66f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`1231fbe2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`08c388f0 fffff880`00f6c558 : fffffa80`0ef96500 fffffa80`1231fa90 fffffa80`0ef96330 fffffa80`1231fa90 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`08c38960 fffff880`00f56245 : fffffa80`1231fa90 fffffa80`137fbf20 fffff880`08c38ca0 fffffa80`137fbf20 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`08c389e0 fffff800`031faa97 : fffffa80`137fbf20 fffff880`08c38ca0 fffffa80`0ef96568 fffffa80`0ef96330 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`08c38a10 fffff800`031fb2f6 : 00000000`0008e358 00000000`00000214 00000000`00000001 00000000`0018f588 : nt!IopXxxControlFile+0x607
fffff880`08c38b40 fffff800`02edeed3 : fffffa80`0d7f5ad0 00000000`0008e2f8 fffff880`08c38bc8 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`08c38bb0 00000000`741b2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x741b2e09
STACK_COMMAND: kbFOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xFE_IMAGE_usbuhci.sys
BUCKET_ID: X64_0xFE_IMAGE_usbuhci.sys
Followup: MachineOwner
---------5: kd> lmvm usbuhci
start end module name
fffff880`0f44b000 fffff880`0f458000 usbuhci (pdb symbols) C:\ProgramData\dbg\sym\usbuhci.pdb\B413F7DC89174A0282783237E46F5A001\usbuhci.pdb
Loaded symbol image file: usbuhci.sys
Image path: \SystemRoot\system32\DRIVERS\usbuhci.sys
Image name: usbuhci.sys
Timestamp: Thu Mar 24 23:29:03 2011 (4D8C0BFF)
CheckSum: 0000B788
ImageSize: 0000D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
All Replies
-
Sunday, October 30, 2011 9:11 PM
Bug Check Code 0xFE: http://msdn.microsoft.com/en-us/library/ff560407(v=VS.85).aspx
The faulty driver is usbuhci.sys. More about it: http://www.file.net/process/usbuhci.sys.html
The BSOD occured when Spyder3Utility process was running.
I think it will be better to contact Datacolor Technical Support for assistance.
To make sure that there is no hardware problems with your USB adapter, contact your manufacturer Technical Support.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Microsoft Student Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer- Marked As Answer by Vincent HuModerator Tuesday, November 01, 2011 3:42 PM
.png)
