Hi all. I'm new on these forum so please don't kill me when im doing something wrong.
My problem is a BSOD after when i m using Utorrent.Some times woking fine for 6 hours, some times for 15 min or 2min etc.
Probably caused by : bcmwl664.sys

My machine:Athlon 64 x2 6400+ /6GB RAM /Nvidia 260! /Asus Wl-138g pc wirless not overcloced
os:win 7 64 bit
All my drivers up to date.
I have read hundreds of posts on this subject, all told about update my broadcom drivers but my last drivers are broadcom wifi__5.100.82.34-w7(www.station-drivers.com)

Please any 1 known solution for my problem.I try to ad some files may be helpful.
-----------------------------------------------------------------------------------------------------------------------------------------------------


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a0c000 PsLoadedModuleList = 0xfffff800`02c51e90
Debug session time: Wed Apr 6 04:36:31.567 2011 (UTC + 1:00)
System Uptime: 0 days 9:27:23.175
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image \SystemRoot\system32\DRIVERS\bcmwl664.sys, Win32 error 0n2
*** 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, fffff88007f4995e, fffff8800b512678, fffff8800b511ed0}

Probably caused by : bcmwl664.sys ( bcmwl664+4f95e )

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: fffff88007f4995e, The address that the exception occurred at
Arg3: fffff8800b512678, Exception Record Address
Arg4: fffff8800b511ed0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:
bcmwl664+4f95e
fffff880`07f4995e 0fb702 movzx eax,word ptr [rdx]

EXCEPTION_RECORD: fffff8800b512678 -- (.exr 0xfffff8800b512678)
ExceptionAddress: fffff88007f4995e (bcmwl664+0x000000000004f95e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8800b511ed0 -- (.cxr 0xfffff8800b511ed0)
rax=6130e6f9356fe804 rbx=00000000000004e0 rcx=0000000000000730
rdx=6130e6f9356fe857 rsi=fffffa80092ba8d0 rdi=fffff8800b512a30
rip=fffff88007f4995e rsp=fffff8800b5128b0 rbp=fffffa800712fa00
r8=0000000000000000 r9=00000000deadbeef r10=b2add075480c335c
r11=0000000000000000 r12=fffffa8007138010 r13=0000000000000004
r14=fffff880075e6780 r15=fffffa8006fd7960
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010207
bcmwl664+0x4f95e:
fffff880`07f4995e 0fb702 movzx eax,word ptr [rdx] ds:002b:6130e6f9`356fe857=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd0e8
ffffffffffffffff

FOLLOWUP_IP:
bcmwl664+4f95e
fffff880`07f4995e 0fb702 movzx eax,word ptr [rdx]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 00000000000004e0 to fffff88007f4995e

STACK_TEXT:
fffff880`0b5128b0 00000000`000004e0 : fffffa80`092ba8d0 00000000`00000800 fffff880`0b512a30 fffff880`075ec704 : bcmwl664+0x4f95e
fffff880`0b5128b8 fffffa80`092ba8d0 : 00000000`00000800 fffff880`0b512a30 fffff880`075ec704 fffffa80`0608e104 : 0x4e0
fffff880`0b5128c0 00000000`00000800 : fffff880`0b512a30 fffff880`075ec704 fffffa80`0608e104 fffff8a0`022b2a10 : 0xfffffa80`092ba8d0
fffff880`0b5128c8 fffff880`0b512a30 : fffff880`075ec704 fffffa80`0608e104 fffff8a0`022b2a10 fffffa80`0608e180 : 0x800
fffff880`0b5128d0 fffff880`075ec704 : fffffa80`0608e104 fffff8a0`022b2a10 fffffa80`0608e180 00000000`00000004 : 0xfffff880`0b512a30
fffff880`0b5128d8 fffffa80`0608e104 : fffff8a0`022b2a10 fffffa80`0608e180 00000000`00000004 fffff8a0`022b2800 : 0xfffff880`075ec704
fffff880`0b5128e0 fffff8a0`022b2a10 : fffffa80`0608e180 00000000`00000004 fffff8a0`022b2800 fffffa80`06fd7960 : 0xfffffa80`0608e104
fffff880`0b5128e8 fffffa80`0608e180 : 00000000`00000004 fffff8a0`022b2800 fffffa80`06fd7960 fffff880`035df8d4 : 0xfffff8a0`022b2a10
fffff880`0b5128f0 00000000`00000004 : fffff8a0`022b2800 fffffa80`06fd7960 fffff880`035df8d4 fffff8a0`022b2c00 : 0xfffffa80`0608e180
fffff880`0b5128f8 fffff8a0`022b2800 : fffffa80`06fd7960 fffff880`035df8d4 fffff8a0`022b2c00 00000000`00000000 : 0x4
fffff880`0b512900 fffffa80`06fd7960 : fffff880`035df8d4 fffff8a0`022b2c00 00000000`00000000 ffffa656`31cf1600 : 0xfffff8a0`022b2800
fffff880`0b512908 fffff880`035df8d4 : fffff8a0`022b2c00 00000000`00000000 ffffa656`31cf1600 ffffbd98`d0681d00 : 0xfffffa80`06fd7960
fffff880`0b512910 fffff8a0`022b2c00 : 00000000`00000000 ffffa656`31cf1600 ffffbd98`d0681d00 fffff801`00000002 : 0xfffff880`035df8d4
fffff880`0b512918 00000000`00000000 : ffffa656`31cf1600 ffffbd98`d0681d00 fffff801`00000002 fffff880`07f4d643 : 0xfffff8a0`022b2c00


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: bcmwl664+4f95e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bcmwl664

IMAGE_NAME: bcmwl664.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4cec125a

STACK_COMMAND: .cxr 0xfffff8800b511ed0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_bcmwl664+4f95e

BUCKET_ID: X64_0x7E_bcmwl664+4f95e

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