Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\XPMUser\My Documents\122810-13556-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Documents and Settings\XPMUser\My Documents\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50
Debug session time: Tue Dec 28 15:59:31.987 2010 (UTC - 5:00)
System Uptime: 0 days 0:41:40.671
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ca12b3, fffff88007b5ff50, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
Followup: MachineOwner
---------
8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ca12b3, Address of the instruction which caused the bugcheck
Arg3: fffff88007b5ff50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!IopCompleteRequest+ae3
fffff800`02ca12b3 488b09 mov rcx,qword ptr [rcx]
CONTEXT: fffff88007b5ff50 -- (.cxr 0xfffff88007b5ff50)
rax=0000000000010008 rbx=fffffa8013fa6010 rcx=0100612ecd1892f5
rdx=0100612ecd1892f5 rsi=0000000000000000 rdi=fffffa8017ddcd20
rip=fffff80002ca12b3 rsp=fffff88007b60920 rbp=fffff88007b60ca0
r8=0000000000005320 r9=0000000000000070 r10=0000000000000002
r11=0000000000000214 r12=0000000000010000 r13=fffffa80163885f0
r14=fffffa8016364060 r15=fffff880031db180
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216
nt!IopCompleteRequest+0xae3:
fffff800`02ca12b3 488b09 mov rcx,qword ptr [rcx] ds:002b:0100612e`cd1892f5=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: sqlservr.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ca12b3
STACK_TEXT:
fffff880`07b5f688 fffff800`02c80ca9 : 00000000`0000003b 00000000`c0000005 fffff800`02ca12b3 fffff880`07b5ff50 : nt!KeBugCheckEx
fffff880`07b5f690 fffff800`02c805fc : fffff880`07b606e8 fffff880`07b5ff50 00000000`00000000 fffff800`02cafc90 : nt!KiBugCheckDispatch+0x69
fffff880`07b5f7d0 fffff800`02ca740d : fffff800`02ea211c 00000000`00000000 fffff800`02c11000 fffff880`07b606e8 : nt!KiSystemServiceHandler+0x7c
fffff880`07b5f810 fffff800`02caea90 : fffff800`02dd11a0 fffff880`07b5f888 fffff880`07b606e8 fffff800`02c11000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`07b5f840 fffff800`02cbb9ef : fffff880`07b606e8 fffff880`07b5ff50 fffff880`00000000 fffffa80`17ddcd20 : nt!RtlDispatchException+0x410
fffff880`07b5ff20 fffff800`02c80d82 : fffff880`07b606e8 fffffa80`13fa6010 fffff880`07b60790 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`07b605b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceHandler+7c
fffff800`02c805fc b801000000 mov eax,1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceHandler+7c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c
BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\XPMUser\My Documents\122810-12495-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Documents and Settings\XPMUser\My Documents\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50
Debug session time: Tue Dec 28 19:13:47.579 2010 (UTC - 5:00)
System Uptime: 0 days 1:41:36.875
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 48, {fffffa8013e06010, fffff80002d02530, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3c1f0 )
Followup: MachineOwner
---------
10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CANCEL_STATE_IN_COMPLETED_IRP (48)
This bugcheck indicates that an I/O Request Packet (IRP) that is to be
cancelled, has a cancel routine specified in it -- meaning that the packet
is in a state in which the packet can be cancelled -- however, the packet
no longer belongs to a driver, as it has entered I/O completion. This is
either a driver bug, or more than one driver is accessing the same packet,
which is not likely and much more difficult to find. The cancel routine
parameter will provide a clue as to which driver or stack is the culprit.
Arguments:
Arg1: fffffa8013e06010, Pointer to the IRP
Arg2: fffff80002d02530, Cancel routine set by the driver.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x48
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002d3476e to fffff80002cb9740
STACK_TEXT:
fffff880`080b6888 fffff800`02d3476e : 00000000`00000048 fffffa80`13e06010 fffff800`02d02530 00000000`00000000 : nt!KeBugCheckEx
fffff880`080b6890 fffff800`02f9f0b9 : fffff880`080b6c01 fffffa80`176e1f48 00000000`00000000 fffffa80`17625b30 : nt! ?? ::FNODOBFM::`string'+0x3c1f0
fffff880`080b68d0 fffff800`02f9ea2b : fffffa80`16306920 00000000`00000000 fffff880`080b6c20 00000000`00000000 : nt!IoCancelThreadIo+0x59
fffff880`080b6900 fffff800`02f77635 : 00000000`c0150014 00000000`00001700 00000000`78457300 00000000`00000000 : nt!PspExitThread+0x58b
fffff880`080b69c0 fffff800`02c961db : 00000000`00001660 00000000`000016a4 00000000`000016ac 00000000`000016b4 : nt!PsExitSpecialApc+0x1d
fffff880`080b69f0 fffff800`02c96620 : 00000000`0b745db0 fffff880`080b6a70 fffff800`02f7774c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`080b6a70 fffff800`02cb8a37 : fffffa80`176e1b60 00000000`031bf9c8 fffff880`080b6bc8 00000000`ffffffff : nt!KiInitiateUserApc+0x70
fffff880`080b6bb0 00000000`7790030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`031bf9a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7790030a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+3c1f0
fffff800`02d3476e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3c1f0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x48_nt!_??_::FNODOBFM::_string_+3c1f0
BUCKET_ID: X64_0x48_nt!_??_::FNODOBFM::_string_+3c1f0
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\XPMUser\My Documents\122810-13868-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Documents and Settings\XPMUser\My Documents\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50
Debug session time: Tue Dec 28 17:30:43.500 2010 (UTC - 5:00)
System Uptime: 0 days 1:29:39.780
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {2b0, 2, 0, fffff80002d3198c}
Probably caused by : ntkrnlmp.exe ( nt!PsCheckThreadCpuQuota+8c )
Followup: MachineOwner
---------
8: 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: 00000000000002b0, 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: fffff80002d3198c, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb10e0
00000000000002b0
CURRENT_IRQL: 2
FAULTING_IP:
nt!PsCheckThreadCpuQuota+8c
fffff800`02d3198c 394330 cmp dword ptr [rbx+30h],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: sidebar.exe
TRAP_FRAME: fffff88009025610 -- (.trap 0xfffff88009025610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000008
rdx=0000069600000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d3198c rsp=fffff880090257a0 rbp=fffff880031db180
r8=fffffa80137c6060 r9=0000000000000000 r10=0000000000000080
r11=00000000000f00ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!PsCheckThreadCpuQuota+0x8c:
fffff800`02d3198c 394330 cmp dword ptr [rbx+30h],eax ds:58b8:00000000`00000030=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c78ca9 to fffff80002c79740
STACK_TEXT:
fffff880`090254c8 fffff800`02c78ca9 : 00000000`0000000a 00000000`000002b0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`090254d0 fffff800`02c77920 : 00000000`00000000 00000000`00000280 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09025610 fffff800`02d3198c : fffffa80`13bdfc20 00000000`00000001 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`090257a0 fffff800`02c7fad2 : 00000000`00000001 fffff880`031db180 fffffa80`173894b0 fffffa80`137c6060 : nt!PsCheckThreadCpuQuota+0x8c
fffff880`090257d0 fffff800`02c7f5da : fffffa80`746c6644 fffff880`09025850 00000000`00000000 fffff800`02c7f900 : nt!SwapContext_PatchXRstor+0xec
fffff880`09025810 fffff800`02c80992 : ffffffff`fffffffe fffffa80`173894b0 00000000`0716f580 00000000`0000000a : nt!KiSwapContext+0x7a
fffff880`09025950 fffff800`02c842a1 : fffff880`09025ca0 fffffa80`173894b0 00000000`00000000 fffffa80`173895b8 : nt!KiCommitThreadWait+0x1d2
fffff880`090259e0 fffff800`02f74df7 : 00000000`00000000 fffff880`09025bc8 fffffa80`00000008 ffffbc35`00000000 : nt!KeRemoveQueueEx+0x301
fffff880`09025a90 fffff800`02c89aa6 : 00000000`00000000 fffff880`09025ba8 fffff880`09025bc8 00000000`00000001 : nt!IoRemoveIoCompletion+0x47
fffff880`09025b20 fffff800`02c78993 : fffffa80`173894b0 00000000`77244270 00000000`06836360 fffffa80`13fdd230 : nt!NtWaitForWorkViaWorkerFactory+0x285
fffff880`09025c20 00000000`7719165a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0716f798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7719165a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PsCheckThreadCpuQuota+8c
fffff800`02d3198c 394330 cmp dword ptr [rbx+30h],eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!PsCheckThreadCpuQuota+8c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_nt!PsCheckThreadCpuQuota+8c
BUCKET_ID: X64_0xA_nt!PsCheckThreadCpuQuota+8c
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\XPMUser\My Documents\122810-13197-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Documents and Settings\XPMUser\My Documents\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Tue Dec 28 19:23:49.858 2010 (UTC - 5:00)
System Uptime: 0 days 0:04:46.542
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002f5648c, fffff8800758de10, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+78 )
Followup: MachineOwner
---------
10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f5648c, Address of the instruction which caused the bugcheck
Arg3: fffff8800758de10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!ObpQueryNameString+78
fffff800`02f5648c 4d8b92a0000000 mov r10,qword ptr [r10+0A0h]
CONTEXT: fffff8800758de10 -- (.cxr 0xfffff8800758de10)
rax=0000000000000040 rbx=fffffa8015652160 rcx=fffffa80156521d0
rdx=fffffa8013987000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002f5648c rsp=fffff8800758e7e0 rbp=fffff8800758e940
r8=0000000000002000 r9=fffff8800758e958 r10=0000000000000000
r11=fffffa8013471402 r12=fffffa8013987000 r13=fffff80002c00000
r14=fffffa8013987000 r15=fffffa80156521a0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!ObpQueryNameString+0x78:
fffff800`02f5648c 4d8b92a0000000 mov r10,qword ptr [r10+0A0h] ds:002b:00000000`000000a0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: WMIADAP.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002f5648c
STACK_TEXT:
fffff880`0758e7e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpQueryNameString+0x78
FOLLOWUP_IP:
nt!ObpQueryNameString+78
fffff800`02f5648c 4d8b92a0000000 mov r10,qword ptr [r10+0A0h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpQueryNameString+78
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff8800758de10 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ObpQueryNameString+78
BUCKET_ID: X64_0x3B_nt!ObpQueryNameString+78
Followup: MachineOwner
---------