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


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

Symbol search path is: SRV*C:\Symbole*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.100216-1441
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Aug 28 21:26:45.343 2010 (UTC + 2:00)
System Uptime: 1 days 10:22:45.063
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.....................................
Unable to load image bcmwl5.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmwl5.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl5.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {10, 2, 0, b25a2700}

Probably caused by : bcmwl5.sys ( bcmwl5+25700 )

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: 00000010, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b25a2700, address which referenced memory

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


READ_ADDRESS:  00000010 

CURRENT_IRQL:  2

FAULTING_IP: 
bcmwl5+25700
b25a2700 8b5f10          mov     ebx,dword ptr [edi+10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b25a3a53 to b25a2700

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
805503a8 b25a3a53 805503bc 20000000 894b2000 bcmwl5+0x25700
805503d0 b25ad128 ffffffff 894b70f1 00000000 bcmwl5+0x26a53
805503ec b258cb27 20000000 00000000 8990f130 bcmwl5+0x30128
80550410 b7d14f09 894b70f4 8055b0a0 ffdff9c0 bcmwl5+0xfb27
80550428 8054510f 894b70ac 894b7098 00000000 NDIS!ndisMDpcX+0x21
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544ff4 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bcmwl5+25700
b25a2700 8b5f10          mov     ebx,dword ptr [edi+10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  bcmwl5+25700

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bcmwl5

IMAGE_NAME:  bcmwl5.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  452ecbd3

FAILURE_BUCKET_ID:  0xD1_bcmwl5+25700

BUCKET_ID:  0xD1_bcmwl5+25700

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