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\042411-28064-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e4ae90
Debug session time: Sun Apr 24 21:21:08.002 2011 (GMT-4)
System Uptime: 0 days 22:25:58.952
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff88106bce2c8, 2, 0, fffff80002c7c1d5}
Unable to load image \SystemRoot\system32\DRIVERS\connctfy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for connctfy.sys
*** ERROR: Module load completed but symbols could not be loaded for connctfy.sys
Probably caused by : connctfy.sys ( connctfy+2783 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff88106bce2c8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c7c1d5, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb60e8
fffff88106bce2c8
CURRENT_IRQL: 2
FAULTING_IP:
nt!memcpy+1e5
fffff800`02c7c1d5 8b040a mov eax,dword ptr [rdx+rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff8800311b310 -- (.trap 0xfffff8800311b310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80045bf810 rbx=0000000000000000 rcx=fffffa81045bf898
rdx=fffffe000260ea30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c7c1d5 rsp=fffff8800311b4a8 rbp=fffffa8004b61560
r8=00000000fffffffe r9=0000000000000000 r10=fffffa8008f1d010
r11=fffffa80045bf89e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!memcpy+0x1e5:
fffff800`02c7c1d5 8b040a mov eax,dword ptr [rdx+rcx] ds:fffff881`06bce2c8=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c84be9 to fffff80002c85640
STACK_TEXT:
fffff880`0311b1c8 fffff800`02c84be9 : 00000000`0000000a fffff881`06bce2c8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0311b1d0 fffff800`02c83860 : fffffa80`04a00810 fffff880`03ff844e fffffa80`04b61560 00000000`0000000e : nt!KiBugCheckDispatch+0x69
fffff880`0311b310 fffff800`02c7c1d5 : fffff880`03ff7783 00000000`0000000c fffff880`06bce2c0 fffffa80`08aa1102 : nt!KiPageFault+0x260
fffff880`0311b4a8 fffff880`03ff7783 : 00000000`0000000c fffff880`06bce2c0 fffffa80`08aa1102 fffffa80`08aa1318 : nt!memcpy+0x1e5
fffff880`0311b4b0 00000000`0000000c : fffff880`06bce2c0 fffffa80`08aa1102 fffffa80`08aa1318 fffffa80`0000000c : connctfy+0x2783
fffff880`0311b4b8 fffff880`06bce2c0 : fffffa80`08aa1102 fffffa80`08aa1318 fffffa80`0000000c 00000000`00000002 : 0xc
fffff880`0311b4c0 fffffa80`08aa1102 : fffffa80`08aa1318 fffffa80`0000000c 00000000`00000002 00000000`00000000 : 0xfffff880`06bce2c0
fffff880`0311b4c8 fffffa80`08aa1318 : fffffa80`0000000c 00000000`00000002 00000000`00000000 fffff880`016f48d4 : 0xfffffa80`08aa1102
fffff880`0311b4d0 fffffa80`0000000c : 00000000`00000002 00000000`00000000 fffff880`016f48d4 fffffa80`00000000 : 0xfffffa80`08aa1318
fffff880`0311b4d8 00000000`00000002 : 00000000`00000000 fffff880`016f48d4 fffffa80`00000000 fffffa80`045bf810 : 0xfffffa80`0000000c
fffff880`0311b4e0 00000000`00000000 : fffff880`016f48d4 fffffa80`00000000 fffffa80`045bf810 fffffa80`08f1d010 : 0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
connctfy+2783
fffff880`03ff7783 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: connctfy+2783
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: connctfy
IMAGE_NAME: connctfy.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bfe3927
FAILURE_BUCKET_ID: X64_0xA_connctfy+2783
BUCKET_ID: X64_0xA_connctfy+2783
Followup: MachineOwner
---------
