Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD : Don't understand =/


21 Jun 2011   #1

Windows 7 Pro x64
 
 
BSOD : Don't understand =/

Hi All,

First I want to say that I'm French, so I making my best to speak english.

Then, I've read the bsod postings instructions, so you will find my Windows_NTS6_BSOD_jcgriff2 and perform /report log in attachment.

I have Windows 7 Pro x64, official, full retailed.
The OS / Hardware were installed 1 year ago.
Everything was OK until now. I brought my PC in another house, everything worked, i had no problems. I brought back my computer at home, and a nice bluescreen appeared !!!
I have nothing special in my pc, just a mouse/keyboard USB.

If you have any question ( be simply because i'm not bilingual ^^ ).


Thank you.


Nico.


My System SpecsSystem Spec
.

21 Jun 2011   #2

Windows 8.1 Pro x64
 
 

Les écrans bleus ont été causés par votre pilote Broadcom Wifi, il doit être mis à jour
Voici le lien pour trouver les nouvelles versions

Utilisez ce logiciel si vous ne pouvez pas trouver de nouvelles versions de Broadcom. Ce logiciel vous permet de mettre à jour les pilotes

Code:
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, fffff88004ab81af, fffff880033a0998, fffff880033a01f0}

Probably caused by : bcmwl664.sys ( bcmwl664+171af )

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

3: 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: fffff88004ab81af, The address that the exception occurred at
Arg3: fffff880033a0998, Exception Record Address
Arg4: fffff880033a01f0, 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+171af
fffff880`04ab81af 0fb707          movzx   eax,word ptr [rdi]

EXCEPTION_RECORD:  fffff880033a0998 -- (.exr 0xfffff880033a0998)
ExceptionAddress: fffff88004ab81af (bcmwl664+0x00000000000171af)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff880033a01f0 -- (.cxr 0xfffff880033a01f0)
rax=fffffa80054b7d34 rbx=fffffa80054b7bb0 rcx=fffffa80054b7bb0
rdx=0000000000000804 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004ab81af rsp=fffff880033a0bd0 rbp=0000000018001000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=fffff88004689000 r13=00000000ffffffff
r14=0000000000000011 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
bcmwl664+0x171af:
fffff880`04ab81af 0fb707          movzx   eax,word ptr [rdi] ds:002b:00000000`00000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

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:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0c100
 0000000000000000 

FOLLOWUP_IP: 
bcmwl664+171af
fffff880`04ab81af 0fb707          movzx   eax,word ptr [rdi]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff88004ab81af

STACK_TEXT:  
fffff880`033a0bd0 00000000`00000001 : fffff880`04ab6e28 fffff800`4243800d fffffa80`054b7bb0 fffff880`00000004 : bcmwl664+0x171af
fffff880`033a0bd8 fffff880`04ab6e28 : fffff800`4243800d fffffa80`054b7bb0 fffff880`00000004 00000000`00000801 : 0x1
fffff880`033a0be0 fffff800`4243800d : fffffa80`054b7bb0 fffff880`00000004 00000000`00000801 fffff880`04689000 : bcmwl664+0x15e28
fffff880`033a0be8 fffffa80`054b7bb0 : fffff880`00000004 00000000`00000801 fffff880`04689000 fffff880`04ab668a : 0xfffff800`4243800d
fffff880`033a0bf0 fffff880`00000004 : 00000000`00000801 fffff880`04689000 fffff880`04ab668a fffffa80`054b7bb0 : 0xfffffa80`054b7bb0
fffff880`033a0bf8 00000000`00000801 : fffff880`04689000 fffff880`04ab668a fffffa80`054b7bb0 fffffa80`054b7bb0 : 0xfffff880`00000004
fffff880`033a0c00 fffff880`04689000 : fffff880`04ab668a fffffa80`054b7bb0 fffffa80`054b7bb0 00000000`00000001 : 0x801
fffff880`033a0c08 fffff880`04ab668a : fffffa80`054b7bb0 fffffa80`054b7bb0 00000000`00000001 fffffa80`054b7c70 : 0xfffff880`04689000
fffff880`033a0c10 fffffa80`054b7bb0 : fffffa80`054b7bb0 00000000`00000001 fffffa80`054b7c70 00000000`00000011 : bcmwl664+0x1568a
fffff880`033a0c18 fffffa80`054b7bb0 : 00000000`00000001 fffffa80`054b7c70 00000000`00000011 fffffa80`054b7d34 : 0xfffffa80`054b7bb0
fffff880`033a0c20 00000000`00000001 : fffffa80`054b7c70 00000000`00000011 fffffa80`054b7d34 fffff880`04689000 : 0xfffffa80`054b7bb0
fffff880`033a0c28 fffffa80`054b7c70 : 00000000`00000011 fffffa80`054b7d34 fffff880`04689000 00000000`18001000 : 0x1
fffff880`033a0c30 00000000`00000011 : fffffa80`054b7d34 fffff880`04689000 00000000`18001000 00000000`18000000 : 0xfffffa80`054b7c70
fffff880`033a0c38 fffffa80`054b7d34 : fffff880`04689000 00000000`18001000 00000000`18000000 00000000`00000001 : 0x11
fffff880`033a0c40 fffff880`04689000 : 00000000`18001000 00000000`18000000 00000000`00000001 00000000`00000000 : 0xfffffa80`054b7d34
fffff880`033a0c48 00000000`18001000 : 00000000`18000000 00000000`00000001 00000000`00000000 00000000`00004318 : 0xfffff880`04689000
fffff880`033a0c50 00000000`18000000 : 00000000`00000001 00000000`00000000 00000000`00004318 fffff880`04689000 : 0x18001000
fffff880`033a0c58 00000000`00000001 : 00000000`00000000 00000000`00004318 fffff880`04689000 00000000`00000001 : 0x18000000
fffff880`033a0c60 00000000`00000000 : 00000000`00004318 fffff880`04689000 00000000`00000001 fffff880`04689000 : 0x1


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  bcmwl664+171af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bcmwl664

IMAGE_NAME:  bcmwl664.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a53ec10

STACK_COMMAND:  .cxr 0xfffff880033a01f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_bcmwl664+171af

BUCKET_ID:  X64_0x7E_bcmwl664+171af

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 BSOD : Don't understand =/




Thread Tools



Similar help and support threads for2: BSOD : Don't understand =/
Thread Forum
Solved BSOD, I understand it is a stop 124 error but need more help. BSOD Help and Support
BSOD playing games, listening to music - still trying to understand BSOD Help and Support
BSOD - Struggling to understand BSOD Help and Support
Solved BSOD during shut down attempts, don't understand error? BSOD Help and Support
BSOD while browsing help needed to understand the problem BSOD Help and Support
Please help me understand these BSOD BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:09 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33