Pojawia się BSOD, czasami nawet komputer nie da rady wyświetlić blue screena.
Odczyt z pliku .dmp:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\032513-37284-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17207.amd64fre.win7_gdr.130104-1435
Machine Name:
Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`03297e70
Debug session time: Mon Mar 25 19:25:23.944 2013 (GMT+1)
System Uptime: 0 days 10:11:37.792
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, fffff88005a572c2, fffff880033b5ca8, fffff880033b5510}
Probably caused by : bcmwl664.sys ( bcmwl664+1d2c2 )
Followup: MachineOwner
---------
2: 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: fffff88005a572c2, The address that the exception occurred at
Arg3: fffff880033b5ca8, Exception Record Address
Arg4: fffff880033b5510, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
bcmwl664+1d2c2
fffff880`05a572c2 44387052 cmp byte ptr [rax+52h],r14b
EXCEPTION_RECORD: fffff880033b5ca8 -- (.exr 0xfffff880033b5ca8)
ExceptionAddress: fffff88005a572c2 (bcmwl664+0x000000000001d2c2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000052
Attempt to read from address 0000000000000052
CONTEXT: fffff880033b5510 -- (.cxr 0xfffff880033b5510)
rax=0000000000000000 rbx=fffffa8003e99000 rcx=fffff88001926d00
rdx=fffff880009ea740 rsi=0000000000000001 rdi=00000000c0000001
rip=fffff88005a572c2 rsp=fffff880033b5ee0 rbp=fffffa80077421a0
r8=fffffa80036e4720 r9=000000000000000c r10=fffff8000305b000
r11=fffff880033b5ed0 r12=000000004e574d42 r13=fffff880033b6020
r14=0000000000000000 r15=00000000c000009a
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
bcmwl664+0x1d2c2:
fffff880`05a572c2 44387052 cmp byte ptr [rax+52h],r14b ds:002b:00000000`00000052=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000052
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033020e0
0000000000000052
FOLLOWUP_IP:
bcmwl664+1d2c2
fffff880`05a572c2 44387052 cmp byte ptr [rax+52h],r14b
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffffa800000000e to fffff88005a572c2
STACK_TEXT:
fffff880`033b5ee0 fffffa80`0000000e : fffffa80`03e99000 fffffa80`077421a0 00000000`00000001 00000000`00004727 : bcmwl664+0x1d2c2
fffff880`033b5ee8 fffffa80`03e99000 : fffffa80`077421a0 00000000`00000001 00000000`00004727 fffffa80`077433d4 : 0xfffffa80`0000000e
fffff880`033b5ef0 fffffa80`077421a0 : 00000000`00000001 00000000`00004727 fffffa80`077433d4 fffff880`00000004 : 0xfffffa80`03e99000
fffff880`033b5ef8 00000000`00000001 : 00000000`00004727 fffffa80`077433d4 fffff880`00000004 fffffa80`07743400 : 0xfffffa80`077421a0
fffff880`033b5f00 00000000`00004727 : fffffa80`077433d4 fffff880`00000004 fffffa80`07743400 00000100`00100180 : 0x1
fffff880`033b5f08 fffffa80`077433d4 : fffff880`00000004 fffffa80`07743400 00000100`00100180 00000000`4e574d42 : 0x4727
fffff880`033b5f10 fffff880`00000004 : fffffa80`07743400 00000100`00100180 00000000`4e574d42 00000000`00000001 : 0xfffffa80`077433d4
fffff880`033b5f18 fffffa80`07743400 : 00000100`00100180 00000000`4e574d42 00000000`00000001 00000000`00000001 : 0xfffff880`00000004
fffff880`033b5f20 00000100`00100180 : 00000000`4e574d42 00000000`00000001 00000000`00000001 00000000`00000000 : 0xfffffa80`07743400
fffff880`033b5f28 00000000`4e574d42 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`093a3020 : 0x100`00100180
fffff880`033b5f30 00000000`00000001 : 00000000`00000001 00000000`00000000 fffffa80`093a3020 fffffa80`077421a0 : 0x4e574d42
fffff880`033b5f38 00000000`00000001 : 00000000`00000000 fffffa80`093a3020 fffffa80`077421a0 fffff880`019640a5 : 0x1
fffff880`033b5f40 00000000`00000000 : fffffa80`093a3020 fffffa80`077421a0 fffff880`019640a5 fffffa80`077433d0 : 0x1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: bcmwl664+1d2c2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bcmwl664
IMAGE_NAME: bcmwl664.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c4fe2a5
STACK_COMMAND: .cxr 0xfffff880033b5510 ; kb
FAILURE_BUCKET_ID: X64_0x7E_bcmwl664+1d2c2
BUCKET_ID: X64_0x7E_bcmwl664+1d2c2
Followup: MachineOwner
---------
Znalazłem już w internecie informacje, że plik który najprawdopodobniej powoduje błąd, to sterownik karty sieciowej, co by się zgadzało gdyż przed zawieszeniem komputera zazwyczaj wysiada mi właśnie karta sieciowa. Karta to broadcomm 802.11n
Wg menedżera urządzeń posiadam aktualne sterowniki do karty. Z góry dziękuję za pomoc.
