Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\BSOD Info\Windows_NT6_BSOD_jcgriff2\100410-22510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Mon Oct 4 00:14:21.978 2010 (GMT-5)
System Uptime: 0 days 2:24:01.978
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image \SystemRoot\system32\drivers\NAVx64\1108000.005\ccHPx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ccHPx64.sys
*** ERROR: Module load completed but symbols could not be loaded for ccHPx64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004097c52, fffff880031bd8f8, fffff880031bd160}
Probably caused by : ccHPx64.sys ( ccHPx64+6c52 )
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: fffff88004097c52, The address that the exception occurred at
Arg3: fffff880031bd8f8, Exception Record Address
Arg4: fffff880031bd160, 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:
ccHPx64+6c52
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h]
EXCEPTION_RECORD: fffff880031bd8f8 -- (.exr 0xfffff880031bd8f8)
ExceptionAddress: fffff88004097c52 (ccHPx64+0x0000000000006c52)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031bd160 -- (.cxr 0xfffff880031bd160)
rax=8948f98b48da8b00 rbx=fffffa800521b188 rcx=fffff80002e3c940
rdx=fffffa800531ed00 rsi=0000000000000001 rdi=8948f98b48da8b00
rip=fffff88004097c52 rsp=fffff880031bdb30 rbp=fffff80002e665f8
r8=0000000000001130 r9=0000000000000070 r10=fffff80002c51000
r11=000000000000006e r12=fffff88009237830 r13=fffff880041195e8
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
ccHPx64+0x6c52:
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h] ds:002b:8948f98b`48da8b10=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef90e0
ffffffffffffffff
FOLLOWUP_IP:
ccHPx64+6c52
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa80047474e0 to fffff88004097c52
STACK_TEXT:
fffff880`031bdb30 fffffa80`047474e0 : 00000000`00000000 00000000`00000000 fffff800`02ccacff fffffa80`0521b180 : ccHPx64+0x6c52
fffff880`031bdb38 00000000`00000000 : 00000000`00000000 fffff800`02ccacff fffffa80`0521b180 fffff880`040982b4 : 0xfffffa80`047474e0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ccHPx64+6c52
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ccHPx64
IMAGE_NAME: ccHPx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b6c8829
STACK_COMMAND: .cxr 0xfffff880031bd160 ; kb
FAILURE_BUCKET_ID: X64_0x7E_ccHPx64+6c52
BUCKET_ID: X64_0x7E_ccHPx64+6c52
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: fffff88004097c52, The address that the exception occurred at
Arg3: fffff880031bd8f8, Exception Record Address
Arg4: fffff880031bd160, 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:
ccHPx64+6c52
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h]
EXCEPTION_RECORD: fffff880031bd8f8 -- (.exr 0xfffff880031bd8f8)
ExceptionAddress: fffff88004097c52 (ccHPx64+0x0000000000006c52)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031bd160 -- (.cxr 0xfffff880031bd160)
rax=8948f98b48da8b00 rbx=fffffa800521b188 rcx=fffff80002e3c940
rdx=fffffa800531ed00 rsi=0000000000000001 rdi=8948f98b48da8b00
rip=fffff88004097c52 rsp=fffff880031bdb30 rbp=fffff80002e665f8
r8=0000000000001130 r9=0000000000000070 r10=fffff80002c51000
r11=000000000000006e r12=fffff88009237830 r13=fffff880041195e8
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
ccHPx64+0x6c52:
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h] ds:002b:8948f98b`48da8b10=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
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: ffffffffffffffff
READ_ADDRESS: ffffffffffffffff
FOLLOWUP_IP:
ccHPx64+6c52
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa80047474e0 to fffff88004097c52
STACK_TEXT:
fffff880`031bdb30 fffffa80`047474e0 : 00000000`00000000 00000000`00000000 fffff800`02ccacff fffffa80`0521b180 : ccHPx64+0x6c52
fffff880`031bdb38 00000000`00000000 : 00000000`00000000 fffff800`02ccacff fffffa80`0521b180 fffff880`040982b4 : 0xfffffa80`047474e0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ccHPx64+6c52
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ccHPx64
IMAGE_NAME: ccHPx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b6c8829
STACK_COMMAND: .cxr 0xfffff880031bd160 ; kb
FAILURE_BUCKET_ID: X64_0x7E_ccHPx64+6c52
BUCKET_ID: X64_0x7E_ccHPx64+6c52
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: fffff88004097c52, The address that the exception occurred at
Arg3: fffff880031bd8f8, Exception Record Address
Arg4: fffff880031bd160, 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:
ccHPx64+6c52
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h]
EXCEPTION_RECORD: fffff880031bd8f8 -- (.exr 0xfffff880031bd8f8)
ExceptionAddress: fffff88004097c52 (ccHPx64+0x0000000000006c52)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031bd160 -- (.cxr 0xfffff880031bd160)
rax=8948f98b48da8b00 rbx=fffffa800521b188 rcx=fffff80002e3c940
rdx=fffffa800531ed00 rsi=0000000000000001 rdi=8948f98b48da8b00
rip=fffff88004097c52 rsp=fffff880031bdb30 rbp=fffff80002e665f8
r8=0000000000001130 r9=0000000000000070 r10=fffff80002c51000
r11=000000000000006e r12=fffff88009237830 r13=fffff880041195e8
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
ccHPx64+0x6c52:
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h] ds:002b:8948f98b`48da8b10=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
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: ffffffffffffffff
READ_ADDRESS: ffffffffffffffff
FOLLOWUP_IP:
ccHPx64+6c52
fffff880`04097c52 488b4710 mov rax,qword ptr [rdi+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa80047474e0 to fffff88004097c52
STACK_TEXT:
fffff880`031bdb30 fffffa80`047474e0 : 00000000`00000000 00000000`00000000 fffff800`02ccacff fffffa80`0521b180 : ccHPx64+0x6c52
fffff880`031bdb38 00000000`00000000 : 00000000`00000000 fffff800`02ccacff fffffa80`0521b180 fffff880`040982b4 : 0xfffffa80`047474e0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ccHPx64+6c52
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ccHPx64
IMAGE_NAME: ccHPx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b6c8829
STACK_COMMAND: .cxr 0xfffff880031bd160 ; kb
FAILURE_BUCKET_ID: X64_0x7E_ccHPx64+6c52
BUCKET_ID: X64_0x7E_ccHPx64+6c52
Followup: MachineOwner
---------