Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\35JPVY5O\Mini%20Dumps[1]\Mini Dumps\091810-34803-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02817000 PsLoadedModuleList = 0xfffff800`02a54e50
Debug session time: Sat Sep 18 05:18:00.537 2010 (GMT-4)
System Uptime: 0 days 0:00:36.519
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\BcmBusCtr_64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BcmBusCtr_64.sys
*** ERROR: Module load completed but symbols could not be loaded for BcmBusCtr_64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880053500a5, fffff88002fcdf58, fffff88002fcd7b0}
Probably caused by : BcmBusCtr_64.sys ( BcmBusCtr_64+70a5 )
Followup: MachineOwner
---------
1: 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: fffff880053500a5, The address that the exception occurred at
Arg3: fffff88002fcdf58, Exception Record Address
Arg4: fffff88002fcd7b0, 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:
BcmBusCtr_64+70a5
fffff880`053500a5 488b4040 mov rax,qword ptr [rax+40h]
EXCEPTION_RECORD: fffff88002fcdf58 -- (.exr 0xfffff88002fcdf58)
ExceptionAddress: fffff880053500a5 (BcmBusCtr_64+0x00000000000070a5)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000040
Attempt to read from address 0000000000000040
CONTEXT: fffff88002fcd7b0 -- (.cxr 0xfffff88002fcd7b0)
rax=0000000000000000 rbx=0000000000000006 rcx=fffffa8003a8b790
rdx=fffffa80065e3a60 rsi=0000000000000000 rdi=fffff88002fce2c0
rip=fffff880053500a5 rsp=fffff88002fce190 rbp=0000000000000000
r8=fffffa8004f58150 r9=000000000000000f r10=fffffa80024e9190
r11=fffffa80024ca680 r12=0000000000000000 r13=fffff880014e3310
r14=0000000000000010 r15=fffffa8003a8b705
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
BcmBusCtr_64+0x70a5:
fffff880`053500a5 488b4040 mov rax,qword ptr [rax+40h] ds:002b:00000000`00000040=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 0000000000000040
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abf0e0
0000000000000040
FOLLOWUP_IP:
BcmBusCtr_64+70a5
fffff880`053500a5 488b4040 mov rax,qword ptr [rax+40h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 0000000000000003 to fffff880053500a5
STACK_TEXT:
fffff880`02fce190 00000000`00000003 : fffffa80`065e3b78 00000000`00000000 00000000`00000000 fffffa80`065e3a60 : BcmBusCtr_64+0x70a5
fffff880`02fce198 fffffa80`065e3b78 : 00000000`00000000 00000000`00000000 fffffa80`065e3a60 fffff800`02b71c14 : 0x3
fffff880`02fce1a0 00000000`00000000 : 00000000`00000000 fffffa80`065e3a60 fffff800`02b71c14 00000000`00000000 : 0xfffffa80`065e3b78
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: BcmBusCtr_64+70a5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BcmBusCtr_64
IMAGE_NAME: BcmBusCtr_64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49def828
STACK_COMMAND: .cxr 0xfffff88002fcd7b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_BcmBusCtr_64+70a5
BUCKET_ID: X64_0x7E_BcmBusCtr_64+70a5
Followup: MachineOwner
---------
