Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\053111-22854-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe50
Debug session time: Tue May 31 09:08:26.936 2011 (GMT-4)
System Uptime: 0 days 0:00:11.934
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
Unable to load image \SystemRoot\system32\DRIVERS\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800419160b, fffff880009a8a28, fffff880009a8290}
Probably caused by : avgldx64.sys ( avgldx64+760b )
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: fffff8800419160b, The address that the exception occurred at
Arg3: fffff880009a8a28, Exception Record Address
Arg4: fffff880009a8290, 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:
avgldx64+760b
fffff880`0419160b 418b5604 mov edx,dword ptr [r14+4]
EXCEPTION_RECORD: fffff880009a8a28 -- (.exr 0xfffff880009a8a28)
ExceptionAddress: fffff8800419160b (avgldx64+0x000000000000760b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000da5025a4
Attempt to read from address 00000000da5025a4
CONTEXT: fffff880009a8290 -- (.cxr 0xfffff880009a8290)
rax=00000000d3a72598 rbx=fffff880041d03f0 rcx=00000000008f63f4
rdx=0000000006199cc1 rsi=00000000008f6488 rdi=0000000006a90008
rip=fffff8800419160b rsp=fffff880009a8c60 rbp=0000000006aad560
r8=0000000000000000 r9=0000000000000000 r10=a58f4da7a5662400
r11=00000000008f62ec r12=0000000000a71838 r13=0000000000a9adb0
r14=00000000da5025a0 r15=000000000000019c
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216
avgldx64+0x760b:
fffff880`0419160b 418b5604 mov edx,dword ptr [r14+4] ds:002b:00000000`da5025a4=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_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: 00000000da5025a4
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a0e0
00000000da5025a4
FOLLOWUP_IP:
avgldx64+760b
fffff880`0419160b 418b5604 mov edx,dword ptr [r14+4]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880041d03f0 to fffff8800419160b
STACK_TEXT:
fffff880`009a8c60 fffff880`041d03f0 : 00000000`008f63f4 00000000`06a90008 fffff8a0`004cb558 00000000`06a90008 : avgldx64+0x760b
fffff880`009a8c68 00000000`008f63f4 : 00000000`06a90008 fffff8a0`004cb558 00000000`06a90008 00000000`005d42c3 : avgldx64+0x463f0
fffff880`009a8c70 00000000`06a90008 : fffff8a0`004cb558 00000000`06a90008 00000000`005d42c3 00000000`0000b54c : 0x8f63f4
fffff880`009a8c78 fffff8a0`004cb558 : 00000000`06a90008 00000000`005d42c3 00000000`0000b54c 00000000`00000000 : 0x6a90008
fffff880`009a8c80 00000000`06a90008 : 00000000`005d42c3 00000000`0000b54c 00000000`00000000 00000000`06a90008 : 0xfffff8a0`004cb558
fffff880`009a8c88 00000000`005d42c3 : 00000000`0000b54c 00000000`00000000 00000000`06a90008 00000000`008f63f4 : 0x6a90008
fffff880`009a8c90 00000000`0000b54c : 00000000`00000000 00000000`06a90008 00000000`008f63f4 00000000`005effd8 : 0x5d42c3
fffff880`009a8c98 00000000`00000000 : 00000000`06a90008 00000000`008f63f4 00000000`005effd8 00000000`07070008 : 0xb54c
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: avgldx64+760b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: avgldx64
IMAGE_NAME: avgldx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d269857
STACK_COMMAND: .cxr 0xfffff880009a8290 ; kb
FAILURE_BUCKET_ID: X64_0x7E_avgldx64+760b
BUCKET_ID: X64_0x7E_avgldx64+760b
Followup: MachineOwner
---------
