[tri3108]

help

[Phantom010]

Loading Dump File Mini102809-01
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c720
Debug session time: Tue Oct 27 12:48:48.265 2009 (GMT-4)
System Uptime: 0 days 1:24:42.986
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
.................
Unable to load image USBPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {a3a6050, 2, 0, b7548359}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_GetEndpointState+35 )
Followup: MachineOwner
---------
0: 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: 0a3a6050, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b7548359, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: 0a3a6050
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_GetEndpointState+35
b7548359 8b7f28 mov edi,dword ptr [edi+28h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: iw3mp.exe
LAST_CONTROL_TRANSFER: from b754976e to b7548359
STACK_TEXT:
bacc7f08 b754976e 89eaf9f0 8a3a60e0 89eaf9f0 USBPORT!USBPORT_GetEndpointState+0x35
bacc7f30 b754d0a0 8a3a6028 50457270 8054689c USBPORT!USBPORT_CoreEndpointWorker+0x2c4
bacc7f60 b755b24b 8a3a6028 8054689c 8a3a6028 USBPORT!USBPORT_DpcWorker+0x18a
bacc7f9c b755b3c2 8a3a6028 00000001 89f23938 USBPORT!USBPORT_IsrDpcWorker+0x38f
bacc7fb8 8a3e96eb 8a3a664c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacc7fcc 80545c4f 8a3a664c 8a3a6028 00000000 0x8a3e96eb
8a3a60ec 00000000 00000000 00000000 00000000 nt!NtTraceEvent+0x134

STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_GetEndpointState+35
b7548359 8b7f28 mov edi,dword ptr [edi+28h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: USBPORT!USBPORT_GetEndpointState+35
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 46a08e75
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_GetEndpointState+35
BUCKET_ID: 0xD1_USBPORT!USBPORT_GetEndpointState+35
Followup: MachineOwner
---------

The other minidump files are all inconclusive:


Loading Dump File Mini102809-01
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Mini Kernel Dump does not contain driver list
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c720
Debug session time: Tue Oct 27 13:28:39.078 2009 (GMT-4)
System Uptime: 0 days 0:19:58.823
Mini Kernel Dump does not contain driver list
Debugger can not determine kernel base address
Loading Kernel Symbols
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {ff800000, 1, 8054529d, 0}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
1: kd> !analyze -v
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff800000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8054529d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ff800000
FAULTING_IP:
+0
8054529d f00fba2e00 lock bts dword ptr [esi],0
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 00000000 to 8054529d
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x8054529d

STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------

[tri3108]

so whats the likely cause of the bsod? usb port and driver versions? any way to solve these problems?

[Mumbodog]

I would suspect iw3mp.exe as the cause of the bsod.

Something to do with multiplayer games?

What are you doing when this bsod occurs?

[tri3108]

usually playing games.. but all these 4 minidumps are from playing call of duty 4..

[tri3108]

up..

[tri3108]

help?