Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021310-33836-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`0309be50
Debug session time: Sat Feb 13 15:53:42.833 2010 (GMT+1)
System Uptime: 0 days 1:40:22.613
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {80, 2, 0, fffff88003f46f6f}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+4398a )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003f46f6f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031060e0
 0000000000000080 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_ReleaseEpListLock+17
fffff880`03f46f6f 8b13            mov     edx,dword ptr [rbx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88002f92c70 -- (.trap 0xfffff88002f92c70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa800005f050
rdx=fffffa800505f102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003f46f6f rsp=fffff88002f92e00 rbp=0000000000000000
 r8=000000004f444648  r9=0000000000000000 r10=00000000ffffffff
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
USBPORT!USBPORT_ReleaseEpListLock+0x17:
fffff880`03f46f6f 8b13            mov     edx,dword ptr [rbx] ds:1702:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecf469 to fffff80002ecff00

STACK_TEXT:  
fffff880`02f92b28 fffff800`02ecf469 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f92b30 fffff800`02ece0e0 : fffffa80`058aea10 00000000`00000080 00000000`00008000 fffff880`04fd8487 : nt!KiBugCheckDispatch+0x69
fffff880`02f92c70 fffff880`03f46f6f : fffffa80`0005f050 00000000`00000000 fffffa80`05001702 fffffa80`0505fb98 : nt!KiPageFault+0x260
fffff880`02f92e00 fffff880`03f43f89 : fffffa80`0505f050 00000000`00000000 fffffa80`05001702 fffffa80`0505fb98 : USBPORT!USBPORT_ReleaseEpListLock+0x17
fffff880`02f92e30 fffff880`00e7198a : fffffa80`05001000 fffffa80`0505fb98 fffffa80`05001750 fffffa80`0505fbb0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f92e60 fffffa80`05001000 : fffffa80`0505fb98 fffffa80`05001750 fffffa80`0505fbb0 00000000`00000000 : sptd+0x4398a
fffff880`02f92e68 fffffa80`0505fb98 : fffffa80`05001750 fffffa80`0505fbb0 00000000`00000000 fffffa80`04ffa1a0 : 0xfffffa80`05001000
fffff880`02f92e70 fffffa80`05001750 : fffffa80`0505fbb0 00000000`00000000 fffffa80`04ffa1a0 00000000`73912450 : 0xfffffa80`0505fb98
fffff880`02f92e78 fffffa80`0505fbb0 : 00000000`00000000 fffffa80`04ffa1a0 00000000`73912450 00000000`00000022 : 0xfffffa80`05001750
fffff880`02f92e80 00000000`00000000 : fffffa80`04ffa1a0 00000000`73912450 00000000`00000022 00000000`00000000 : 0xfffffa80`0505fbb0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sptd+4398a
fffff880`00e7198a ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  sptd+4398a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sptd

IMAGE_NAME:  sptd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49f05a7a

FAILURE_BUCKET_ID:  X64_0xD1_sptd+4398a

BUCKET_ID:  X64_0xD1_sptd+4398a

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003f46f6f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS:  0000000000000080 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_ReleaseEpListLock+17
fffff880`03f46f6f 8b13            mov     edx,dword ptr [rbx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88002f92c70 -- (.trap 0xfffff88002f92c70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa800005f050
rdx=fffffa800505f102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003f46f6f rsp=fffff88002f92e00 rbp=0000000000000000
 r8=000000004f444648  r9=0000000000000000 r10=00000000ffffffff
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
USBPORT!USBPORT_ReleaseEpListLock+0x17:
fffff880`03f46f6f 8b13            mov     edx,dword ptr [rbx] ds:1702:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecf469 to fffff80002ecff00

STACK_TEXT:  
fffff880`02f92b28 fffff800`02ecf469 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f92b30 fffff800`02ece0e0 : fffffa80`058aea10 00000000`00000080 00000000`00008000 fffff880`04fd8487 : nt!KiBugCheckDispatch+0x69
fffff880`02f92c70 fffff880`03f46f6f : fffffa80`0005f050 00000000`00000000 fffffa80`05001702 fffffa80`0505fb98 : nt!KiPageFault+0x260
fffff880`02f92e00 fffff880`03f43f89 : fffffa80`0505f050 00000000`00000000 fffffa80`05001702 fffffa80`0505fb98 : USBPORT!USBPORT_ReleaseEpListLock+0x17
fffff880`02f92e30 fffff880`00e7198a : fffffa80`05001000 fffffa80`0505fb98 fffffa80`05001750 fffffa80`0505fbb0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f92e60 fffffa80`05001000 : fffffa80`0505fb98 fffffa80`05001750 fffffa80`0505fbb0 00000000`00000000 : sptd+0x4398a
fffff880`02f92e68 fffffa80`0505fb98 : fffffa80`05001750 fffffa80`0505fbb0 00000000`00000000 fffffa80`04ffa1a0 : 0xfffffa80`05001000
fffff880`02f92e70 fffffa80`05001750 : fffffa80`0505fbb0 00000000`00000000 fffffa80`04ffa1a0 00000000`73912450 : 0xfffffa80`0505fb98
fffff880`02f92e78 fffffa80`0505fbb0 : 00000000`00000000 fffffa80`04ffa1a0 00000000`73912450 00000000`00000022 : 0xfffffa80`05001750
fffff880`02f92e80 00000000`00000000 : fffffa80`04ffa1a0 00000000`73912450 00000000`00000022 00000000`00000000 : 0xfffffa80`0505fbb0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sptd+4398a
fffff880`00e7198a ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  sptd+4398a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sptd

IMAGE_NAME:  sptd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49f05a7a

FAILURE_BUCKET_ID:  X64_0xD1_sptd+4398a

BUCKET_ID:  X64_0xD1_sptd+4398a

Followup: MachineOwner
---------