Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\022811-22542-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
BugCheck F7, {2b9906a3f610, 2b992ddfa232, ffffd466d2205dcd, 0}
Probably caused by : msrpc.sys ( msrpc!_report_gsfailure+26 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 00002b9906a3f610, Actual security check cookie from the stack
Arg2: 00002b992ddfa232, Expected security check cookie
Arg3: ffffd466d2205dcd, Complement of the expected security check cookie
Arg4: 0000000000000000, zero
Debugging Details:
------------------
DEFAULT_BUCKET_ID: GS_FALSE_POSITIVE_MISSING_GSFRAME
SECURITY_COOKIE: Expected 00002b992ddfa232 found 00002b9906a3f610
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xF7
PROCESS_NAME: conhost.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88006a3f0e8 -- (.exr 0xfffff88006a3f0e8)
ExceptionAddress: fffff80002aaac18 (nt!IopCompleteRequest+0x0000000000000c85)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88006a3f190 -- (.trap 0xfffff88006a3f190)
Unable to read trap frame at fffff880`06a3f190
LAST_CONTROL_TRANSFER: from fffff88001079616 to fffff80002a8af00
STACK_TEXT:
fffff880`06a3e188 fffff880`01079616 : 00000000`000000f7 00002b99`06a3f610 00002b99`2ddfa232 ffffd466`d2205dcd : nt!KeBugCheckEx
fffff880`06a3e190 fffff880`010796b7 : fffff800`02c978b8 fffff800`02a9206c fffff800`02bd47dc fffff880`06a3f0e8 : msrpc!_report_gsfailure+0x26
fffff880`06a3e1d0 fffff800`02ab0bed : fffff880`0108ce34 fffff880`01085dc0 fffff880`01078000 fffff880`06a3f0e8 : msrpc!_GSHandlerCheck+0x13
fffff880`06a3e200 fffff800`02ab8250 : fffff880`01085e6c fffff880`06a3e278 fffff880`06a3f0e8 fffff880`01078000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`06a3e230 fffff800`02ac51b5 : fffff880`06a3f0e8 fffff880`06a3e940 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`06a3e910 fffff800`02a8a542 : fffff880`06a3f0e8 fffffa80`05ff97c0 fffff880`06a3f190 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`06a3efb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
STACK_COMMAND: kb
FOLLOWUP_IP:
msrpc!_report_gsfailure+26
fffff880`01079616 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: msrpc!_report_gsfailure+26
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: msrpc
IMAGE_NAME: msrpc.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc17c
FAILURE_BUCKET_ID: X64_0xF7_MISSING_GSFRAME_msrpc!_report_gsfailure+26
BUCKET_ID: X64_0xF7_MISSING_GSFRAME_msrpc!_report_gsfailure+26
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\022811-20966-01.dmp]
BugCheck A, {0, 2, 0, fffff80002ae6a83}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: 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: 0000000000000000, 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: fffff80002ae6a83, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfd0e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!IopCompleteRequest+ae3
fffff800`02ae6a83 488b09 mov rcx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: BCSSync.exe
IRP_ADDRESS: 0000000100000009
TRAP_FRAME: fffff88007f90190 -- (.trap 0xfffff88007f90190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88007f903f8 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ae6a83 rsp=fffff88007f90320 rbp=0000000000000000
r8=fffffa8005ee4680 r9=fffff88007f90420 r10=0000000000000002
r11=fffffa8005d6e390 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
nt!IopCompleteRequest+0xae3:
fffff800`02ae6a83 488b09 mov rcx,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ac6469 to fffff80002ac6f00
STACK_TEXT:
fffff880`07f90048 fffff800`02ac6469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07f90050 fffff800`02ac50e0 : fffffa80`0594d060 fffffa80`06104de0 fffffa80`05e7c890 00000000`00000002 : nt!KiBugCheckDispatch+0x69
fffff880`07f90190 fffff800`02ae6a83 : fffffa80`05e7c890 fffff800`02accdda 00000000`00000200 fffff880`07f903d1 : nt!KiPageFault+0x260
fffff880`07f90320 00000000`00000200 : 00000001`00000081 fffff880`07f903f8 fffff880`07f903f8 0050e0c2`00000000 : nt!IopCompleteRequest+0xae3
fffff880`07f903f0 00000001`00000081 : fffff880`07f903f8 fffff880`07f903f8 0050e0c2`00000000 fffff880`07f90488 : 0x200
fffff880`07f903f8 fffff880`07f903f8 : fffff880`07f903f8 0050e0c2`00000000 fffff880`07f90488 fffff800`02bf0000 : 0x1`00000081
fffff880`07f90400 fffff880`07f903f8 : 0050e0c2`00000000 fffff880`07f90488 fffff800`02bf0000 00000000`00000000 : 0xfffff880`07f903f8
fffff880`07f90408 0050e0c2`00000000 : fffff880`07f90488 fffff800`02bf0000 00000000`00000000 00000000`00000000 : 0xfffff880`07f903f8
fffff880`07f90410 fffff880`07f90488 : fffff800`02bf0000 00000000`00000000 00000000`00000000 00000000`000000e2 : 0x50e0c2`00000000
fffff880`07f90418 fffff800`02bf0000 : 00000000`00000000 00000000`00000000 00000000`000000e2 fffff880`009ef380 : 0xfffff880`07f90488
fffff880`07f90420 00000000`00000000 : fffffa80`036592a0 fffff880`009ed180 fffff880`07f90d00 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageInsert+0x130
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02ac50e0 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xA_nt!KiPageFault+260
BUCKET_ID: X64_0xA_nt!KiPageFault+260
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\022811-21278-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ad94d8, fffff880059a2a20, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
Followup: MachineOwner
---------
1: 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: fffff80002ad94d8, Address of the instruction which caused the bugcheck
Arg3: fffff880059a2a20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
nt!KiTryUnwaitThread+28
fffff800`02ad94d8 f0480fba6b4000 lock bts qword ptr [rbx+40h],0
CONTEXT: fffff880059a2a20 -- (.cxr 0xfffff880059a2a20)
rax=fffff880059a33f8 rbx=01000000003cfa00 rcx=fffff880009ed180
rdx=fffffa8003669601 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ad94d8 rsp=fffff880059a3400 rbp=fffff880059a35b0
r8=0000000000000100 r9=0000000000000000 r10=0000000000000002
r11=fffffa8005ab4140 r12=0000000000000000 r13=0000000000000000
r14=fffffa8006191060 r15=fffff880009ed180
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!KiTryUnwaitThread+0x28:
fffff800`02ad94d8 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:002b:01000000`003cfa40=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: rundll32.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ad94d8
STACK_TEXT:
fffff880`059a3400 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x28
FOLLOWUP_IP:
nt!KiTryUnwaitThread+28
fffff800`02ad94d8 f0480fba6b4000 lock bts qword ptr [rbx+40h],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTryUnwaitThread+28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff880059a2a20 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!KiTryUnwaitThread+28
BUCKET_ID: X64_0x3B_nt!KiTryUnwaitThread+28
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\022811-28813-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
BugCheck D1, {fffff88006947740, 2, 0, fffff88000dd6c50}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88006947740, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000dd6c50, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd0e0
fffff88006947740
CURRENT_IRQL: 2
FAULTING_IP:
ataport!IdeLogCrbActive+bc
fffff880`00dd6c50 f30f6f4148 movdqu xmm0,xmmword ptr [rcx+48h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002f1b4b0 -- (.trap 0xfffff88002f1b4b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80061544b0 rbx=0000000000000000 rcx=fffff880069476f0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000dd6c50 rsp=fffff88002f1b640 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=fffffa800417cee0
r11=fffff88002f1b770 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ataport!IdeLogCrbActive+0xbc:
fffff880`00dd6c50 f30f6f4148 movdqu xmm0,xmmword ptr [rcx+48h] ds:13f0:fffff880`06947738=????????????????????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a86469 to fffff80002a86f00
STACK_TEXT:
fffff880`02f1b368 fffff800`02a86469 : 00000000`0000000a fffff880`06947740 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b370 fffff800`02a850e0 : 00000000`00000001 fffffa80`0417f8e8 fffffa80`040071a0 fffff880`00deb1a0 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b4b0 fffff880`00dd6c50 : fffffa80`0366adc0 00000000`00000000 fffffa80`0417e1b0 00000000`00000001 : nt!KiPageFault+0x260
fffff880`02f1b640 fffff880`00de0c71 : fffffa80`038740f8 fffffa80`040071a0 fffffa80`03874010 fffffa80`040071a0 : ataport!IdeLogCrbActive+0xbc
fffff880`02f1b670 fffff800`02ff69ce : fffffa80`038740f8 00000000`00000018 00000000`00000000 00000000`00000001 : ataport!IdeStartIoCallBack+0xc9
fffff880`02f1b7e0 fffff800`02ff713d : fffffa80`0414bd40 fffffa80`04150ea0 fffffa80`04150e00 00000000`00000000 : hal!HalpAllocateAdapterCallback+0x146
fffff880`02f1b880 fffff800`02ff671f : fffffa80`038740b0 00000000`00000200 fffffa80`04150ea0 fffffa80`05b0e450 : hal!HalAllocateAdapterChannel+0x101
fffff880`02f1b8c0 fffff880`00c5d0d3 : fffffa80`03874010 fffff880`00c5d12c fffffa80`000000a0 fffffa80`04150ea0 : hal!HalBuildScatterGatherList+0x2f3
fffff880`02f1b930 fffff880`00de0b3b : fffffa80`03874010 fffffa80`0417e1b0 fffffa80`040071a0 fffffa80`03874010 : PCIIDEX!BmSetup+0x6b
fffff880`02f1b990 fffff880`00ddf7eb : fffffa80`04008500 fffffa80`0417e1b0 fffffa80`04008500 fffffa80`040071a0 : ataport!IdeDispatchChannelRequest+0xef
fffff880`02f1b9c0 fffff880`00ddf31e : 00000000`00000001 fffffa80`03874010 00000000`00000001 fffffa80`03874010 : ataport!IdeStartChannelRequest+0x113
fffff880`02f1ba40 fffff880`00de1582 : fffffa80`036e2c01 00000000`00000000 fffffa80`0417e1b0 fffffa80`03869680 : ataport!IdeStartNextDeviceRequest+0x18e
fffff880`02f1bae0 fffff880`00de10ec : fffffa80`040071a0 00000000`00000000 fffffa80`040071a0 fffffa80`03869680 : ataport!IdeProcessCompletedRequests+0x26a
fffff880`02f1bc10 fffff800`02a925dc : fffff880`009ed180 00000000`0fd31f0c fffffa80`04007050 fffffa80`04007118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f1bcd0 fffff800`02a8f6fa : fffff880`009ed180 fffff880`009f7f40 00000000`00000000 fffff880`00de0f44 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!IdeLogCrbActive+bc
fffff880`00dd6c50 f30f6f4148 movdqu xmm0,xmmword ptr [rcx+48h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ataport!IdeLogCrbActive+bc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc118
FAILURE_BUCKET_ID: X64_0xD1_ataport!IdeLogCrbActive+bc
BUCKET_ID: X64_0xD1_ataport!IdeLogCrbActive+bc
Followup: MachineOwner
---------