¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[FONT=Lucida Console]*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004e4eed6, fffff880074f2588, fffff880074f1de0}
Probably caused by : bcmwl664.sys ( bcmwl664+4eed6 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004e4eed6, The address that the exception occurred at
Arg3: fffff880074f2588, Exception Record Address
Arg4: fffff880074f1de0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
bcmwl664+4eed6
fffff880`04e4eed6 410fb744240c movzx eax,word ptr [r12+0Ch]
EXCEPTION_RECORD: fffff880074f2588 -- (.exr 0xfffff880074f2588)
ExceptionAddress: fffff88004e4eed6 (bcmwl664+0x000000000004eed6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880074f1de0 -- (.cxr 0xfffff880074f1de0)
rax=fffffa80057fc410 rbx=fffffa8005804010 rcx=0000000000015aac
rdx=0000000000000002 rsi=fffffa8005805a60 rdi=fffffa8005868f80
rip=fffff88004e4eed6 rsp=fffff880074f27c0 rbp=fffffa8006fca010
r8=fffffa80057fc410 r9=fffff880074f2920 r10=fffff88004e00000
r11=0000000000000004 r12=000600000002ffff r13=0000000000000001
r14=fffffa8005805a60 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
bcmwl664+0x4eed6:
fffff880`04e4eed6 410fb744240c movzx eax,word ptr [r12+0Ch] ds:002b:00060000`0003000b=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100
GetUlongFromAddress: unable to read from fffff80002efa1c0
ffffffffffffffff
FOLLOWUP_IP:
bcmwl664+4eed6
fffff880`04e4eed6 410fb744240c movzx eax,word ptr [r12+0Ch]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880074f27e4 to fffff88004e4eed6
STACK_TEXT:
fffff880`074f27c0 fffff880`074f27e4 : fffff880`074f27e8 00000000`00000000 fffffa80`047e4ae0 5362dabd`02533502 : bcmwl664+0x4eed6
fffff880`074f27c8 fffff880`074f27e8 : 00000000`00000000 fffffa80`047e4ae0 5362dabd`02533502 0000006d`3a988033 : 0xfffff880`074f27e4
fffff880`074f27d0 00000000`00000000 : fffffa80`047e4ae0 5362dabd`02533502 0000006d`3a988033 00000000`0000359f : 0xfffff880`074f27e8
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: bcmwl664+4eed6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bcmwl664
IMAGE_NAME: bcmwl664.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c08019d
STACK_COMMAND: .cxr 0xfffff880074f1de0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_bcmwl664+4eed6
BUCKET_ID: X64_0x7E_bcmwl664+4eed6
Followup: MachineOwner
---------
0: kd> lmvm bcmwl664
start end module name
fffff880`04e00000 fffff880`051ff000 bcmwl664 T (no symbols)
Loaded symbol image file: bcmwl664.sys
Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
Image name: bcmwl664.sys
Timestamp: Fri Jun 04 01:25:17 2010 (4C08019D)
CheckSum: 003FB521
ImageSize: 003FF000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/FONT]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to "Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card" and reboot the system. Delete remnants of its drivers/older drivers using Driver Sweeper.
