Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\010111-27222-01-dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e93e50
Debug session time: Sat Jan 1 11:24:14.770 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:52.440
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80002ce62b3}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
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: 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: fffff80002ce62b3, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efe0e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!IopCompleteRequest+ae3
fffff800`02ce62b3 488b09 mov rcx,qword ptr [rcx]
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: mscorsvw.exe
IRP_ADDRESS: ffffffffffffff89
TRAP_FRAME: fffff8800b1f5410 -- (.trap 0xfffff8800b1f5410)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800b1f5728 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ce62b3 rsp=fffff8800b1f55a0 rbp=fffff8800b1f56f0
r8=fffffa8004e54720 r9=fffff8800b1f56a0 r10=0000000000000002
r11=fffffa8004ca23d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!IopCompleteRequest+0xae3:
fffff800`02ce62b3 488b09 mov rcx,qword ptr [rcx] ds:0001:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cc5ca9 to fffff80002cc6740
STACK_TEXT:
fffff880`0b1f52c8 fffff800`02cc5ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b1f52d0 fffff800`02cc4920 : fffffa80`045e38e0 fffffa80`0373fee0 fffff880`00e161a0 00000000`00000002 : nt!KiBugCheckDispatch+0x69
fffff880`0b1f5410 fffff800`02ce62b3 : fffff880`009e8180 fffffa80`055fcb60 00000000`00000001 00000000`00000017 : nt!KiPageFault+0x260
fffff880`0b1f55a0 fffff800`02ca30c7 : 00000000`00000001 fffff880`0b1f5770 fffffa80`0448ee00 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`0b1f5670 fffff800`02ca3487 : fffff6fc`400311f8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`0b1f56f0 fffff800`02ce7fe7 : 00000000`00000000 00000000`00000000 fffffa80`05b8ca70 fffffa80`05b8c9a0 : nt!KiApcInterrupt+0xd7
fffff880`0b1f5880 fffff800`02cc8ae8 : 00000000`0000008b 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmUnlockPages+0x107
fffff880`0b1f5910 fffffa80`046e58fc : 00000000`00000000 00000000`00000000 fffffa80`05b8ca70 00000000`00000000 : nt!IopfCompleteRequest+0x168
fffff880`0b1f59f0 00000000`00000000 : 00000000`00000000 fffffa80`05b8ca70 00000000`00000000 fffff6fb`7dbed000 : 0xfffffa80`046e58fc
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02cc4920 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: 4c1c44a9
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 [F:\a\Minidump\D M P\DMP\010111-31949-01-dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e95e50
Debug session time: Fri Dec 31 19:41:49.846 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:46.516
Loading Kernel Symbols
....................................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050033, 6f8, fffff80002ca50d2}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002ca50d2
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff80002cc7ca9 to fffff80002cc8740
STACK_TEXT:
fffff880`009eec68 fffff800`02cc7ca9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009eec70 fffff800`02cc6172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eedb0 fffff800`02ca50d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff87f`fffffff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1e2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02cc6172 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\010111-37643-01-dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Sat Jan 1 11:01:54.082 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:23.643
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff8800aaf7738, 2, 1, fffff8800118b074}
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!memmove+64 )
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: fffff8800aaf7738, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800118b074, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebd0e0
fffff8800aaf7738
CURRENT_IRQL: 2
FAULTING_IP:
ataport!memmove+64
fffff880`0118b074 488901 mov qword ptr [rcx],rax
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002f22ad0 -- (.trap 0xfffff88002f22ad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800aaf7738
rdx=000001fff9bca988 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800118b074 rsp=fffff88002f22c68 rbp=fffffa80046c37d0
r8=0000000000000012 r9=0000000000000002 r10=fffffa800469b610
r11=fffff8800aaf7738 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
ataport!memmove+0x64:
fffff880`0118b074 488901 mov qword ptr [rcx],rax ds:18d0:fffff880`0aaf7738=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c84ca9 to fffff80002c85740
STACK_TEXT:
fffff880`02f22988 fffff800`02c84ca9 : 00000000`0000000a fffff880`0aaf7738 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f22990 fffff800`02c83920 : fffffa80`05ed18d0 00000000`00000002 fffffa80`0469a1a0 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02f22ad0 fffff880`0118b074 : fffff880`011844a5 00000000`00000001 fffff880`03d231c6 fffff880`02f22cb4 : nt!KiPageFault+0x260
fffff880`02f22c68 fffff880`011844a5 : 00000000`00000001 fffff880`03d231c6 fffff880`02f22cb4 fffffa80`05eae3d0 : ataport!memmove+0x64
fffff880`02f22c70 fffff880`011840ec : fffffa80`0469a1a0 00000000`00000000 fffffa80`0469a1a0 fffffa80`04281980 : ataport!IdeProcessCompletedRequests+0x18d
fffff880`02f22da0 fffff880`00ef54ce : fffffa80`043c7000 fffff880`02f22e88 fffffa80`0469a050 fffffa80`043c7750 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f22e60 fffffa80`043c7000 : fffff880`02f22e88 fffffa80`0469a050 fffffa80`043c7750 fffffa80`036a8d00 : sptd+0x424ce
fffff880`02f22e68 fffff880`02f22e88 : fffffa80`0469a050 fffffa80`043c7750 fffffa80`036a8d00 01cba9cd`357ae2b2 : 0xfffffa80`043c7000
fffff880`02f22e70 fffffa80`0469a050 : fffffa80`043c7750 fffffa80`036a8d00 01cba9cd`357ae2b2 00000000`00002cea : 0xfffff880`02f22e88
fffff880`02f22e78 fffffa80`043c7750 : fffffa80`036a8d00 01cba9cd`357ae2b2 00000000`00002cea 00000000`00000022 : 0xfffffa80`0469a050
fffff880`02f22e80 fffffa80`036a8d00 : 01cba9cd`357ae2b2 00000000`00002cea 00000000`00000022 00000000`00000000 : 0xfffffa80`043c7750
fffff880`02f22e88 01cba9cd`357ae2b2 : 00000000`00002cea 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffffa80`036a8d00
fffff880`02f22e90 00000000`00002cea : 00000000`00000022 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1cba9cd`357ae2b2
fffff880`02f22e98 00000000`00000022 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0469a118 : 0x2cea
fffff880`02f22ea0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0469a118 fffffa80`0469a050 : 0x22
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!memmove+64
fffff880`0118b074 488901 mov qword ptr [rcx],rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ataport!memmove+64
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc118
FAILURE_BUCKET_ID: X64_0xD1_ataport!memmove+64
BUCKET_ID: X64_0xD1_ataport!memmove+64
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: fffff8800aaf7738, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800118b074, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: fffff8800aaf7738
CURRENT_IRQL: 2
FAULTING_IP:
ataport!memmove+64
fffff880`0118b074 488901 mov qword ptr [rcx],rax
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002f22ad0 -- (.trap 0xfffff88002f22ad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800aaf7738
rdx=000001fff9bca988 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800118b074 rsp=fffff88002f22c68 rbp=fffffa80046c37d0
r8=0000000000000012 r9=0000000000000002 r10=fffffa800469b610
r11=fffff8800aaf7738 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
ataport!memmove+0x64:
fffff880`0118b074 488901 mov qword ptr [rcx],rax ds:18d0:fffff880`0aaf7738=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c84ca9 to fffff80002c85740
STACK_TEXT:
fffff880`02f22988 fffff800`02c84ca9 : 00000000`0000000a fffff880`0aaf7738 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f22990 fffff800`02c83920 : fffffa80`05ed18d0 00000000`00000002 fffffa80`0469a1a0 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02f22ad0 fffff880`0118b074 : fffff880`011844a5 00000000`00000001 fffff880`03d231c6 fffff880`02f22cb4 : nt!KiPageFault+0x260
fffff880`02f22c68 fffff880`011844a5 : 00000000`00000001 fffff880`03d231c6 fffff880`02f22cb4 fffffa80`05eae3d0 : ataport!memmove+0x64
fffff880`02f22c70 fffff880`011840ec : fffffa80`0469a1a0 00000000`00000000 fffffa80`0469a1a0 fffffa80`04281980 : ataport!IdeProcessCompletedRequests+0x18d
fffff880`02f22da0 fffff880`00ef54ce : fffffa80`043c7000 fffff880`02f22e88 fffffa80`0469a050 fffffa80`043c7750 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f22e60 fffffa80`043c7000 : fffff880`02f22e88 fffffa80`0469a050 fffffa80`043c7750 fffffa80`036a8d00 : sptd+0x424ce
fffff880`02f22e68 fffff880`02f22e88 : fffffa80`0469a050 fffffa80`043c7750 fffffa80`036a8d00 01cba9cd`357ae2b2 : 0xfffffa80`043c7000
fffff880`02f22e70 fffffa80`0469a050 : fffffa80`043c7750 fffffa80`036a8d00 01cba9cd`357ae2b2 00000000`00002cea : 0xfffff880`02f22e88
fffff880`02f22e78 fffffa80`043c7750 : fffffa80`036a8d00 01cba9cd`357ae2b2 00000000`00002cea 00000000`00000022 : 0xfffffa80`0469a050
fffff880`02f22e80 fffffa80`036a8d00 : 01cba9cd`357ae2b2 00000000`00002cea 00000000`00000022 00000000`00000000 : 0xfffffa80`043c7750
fffff880`02f22e88 01cba9cd`357ae2b2 : 00000000`00002cea 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffffa80`036a8d00
fffff880`02f22e90 00000000`00002cea : 00000000`00000022 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1cba9cd`357ae2b2
fffff880`02f22e98 00000000`00000022 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0469a118 : 0x2cea
fffff880`02f22ea0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0469a118 fffffa80`0469a050 : 0x22
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!memmove+64
fffff880`0118b074 488901 mov qword ptr [rcx],rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ataport!memmove+64
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc118
FAILURE_BUCKET_ID: X64_0xD1_ataport!memmove+64
BUCKET_ID: X64_0xD1_ataport!memmove+64
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\123110-40544-01-dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50
Debug session time: Fri Dec 31 18:49:15.138 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:20.683
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002c85cd8, 0, ffffffffffffffff}
Probably caused by : msrpc.sys ( msrpc!RpcpDuplicateTokenEx+6b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c85cd8, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
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!KiTryUnwaitThread+28
fffff800`02c85cd8 f0480fba6b4000 lock bts qword ptr [rbx+40h],0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb90e0
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: WerFault.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff8800a5aaa28 -- (.exr 0xfffff8800a5aaa28)
ExceptionAddress: fffff80002c85cd8 (nt!KiTryUnwaitThread+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff8800a5aaad0 -- (.trap 0xfffff8800a5aaad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800a5ab428 rbx=0000000000000000 rcx=fffff80002dfbe80
rdx=fffff80002db5401 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c85cd8 rsp=fffff8800a5aac60 rbp=fffff8800a5aae10
r8=0000000000000100 r9=0000000000000000 r10=0000000000000002
r11=fffffa8006072810 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`02c85cd8 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:adc0:00000000`00000040=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cbba39 to fffff80002c81740
STACK_TEXT:
fffff880`0a5aa258 fffff800`02cbba39 : 00000000`0000001e ffffffff`c0000005 fffff800`02c85cd8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a5aa260 fffff800`02c80d82 : fffff880`0a5aaa28 0000c824`ac894800 fffff880`0a5aaad0 00000000`00000000 : nt!KiDispatchException+0x1b9
fffff880`0a5aa8f0 fffff800`02c7f68a : 00000000`00000000 fffff8a0`042e72a8 fffff880`0a5aaf88 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a5aaad0 fffff800`02c85cd8 : fffff8a0`042e6e3c fffff8a0`042e6e58 fffff8a0`042e6e68 fffff8a0`042d5000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0a5aac60 fffff800`02cfcf74 : fffffa80`06cfd960 fffff880`0a5aae10 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x28
fffff880`0a5aacc0 fffff800`02c5e0c7 : 00103cb2`3d830000 fffff8a0`040d6ed0 00000000`00000000 fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x3ca30
fffff880`0a5aad90 fffff800`02c5e487 : fffff880`0a5ab110 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`0a5aae10 fffff800`02f79541 : fffff8a0`040d6f80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0xd7
fffff880`0a5aafa0 fffff800`02f723d1 : fffff8a0`00000000 fffff8a0`042d5060 00000000`00000000 00000000`00000000 : nt!ObpCreateHandle+0xb1
fffff880`0a5ab0b0 fffff800`02f28db3 : 00000000`0000000e fffff880`0a5ab6c0 00000000`ffffff00 fffff800`02dfbe00 : nt!ObInsertObjectEx+0x291
fffff880`0a5ab2f0 fffff800`02c80993 : fffffa80`06dc7600 fffff880`0a5ab5b8 fffff880`0a5ab3a8 fffff8a0`042ea8f0 : nt!NtDuplicateToken+0x17b
fffff880`0a5ab390 fffff800`02c7cf30 : fffff880`010aa8cb 00000000`00000001 fffff880`010ac1f6 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a5ab598 fffff880`010aa8cb : 00000000`00000001 fffff880`010ac1f6 00000000`00000000 fffff8a0`00000000 : nt!KiServiceLinkage
fffff880`0a5ab5a0 fffff880`010ab0bf : fffffa80`06dc7600 fffff8a0`03e0d300 00000000`00000001 fffffa80`cd637052 : msrpc!RpcpDuplicateTokenEx+0x6b
fffff880`0a5ab620 fffff880`010ab37b : fffff8a0`042ea8f0 00000000`00000000 fffff8a0`042ea8f0 fffff8a0`03e0d300 : msrpc!LRPC_BASE_BINDING_HANDLE::BaseBindingCopy+0x1bf
fffff880`0a5ab760 fffff880`010ae9d2 : fffff8a0`03e0d300 fffff8a0`03e0d300 00000000`00000001 00000000`00000058 : msrpc!LRPC_FAST_BINDING_HANDLE::BindingCopy+0x8b
fffff880`0a5ab790 fffff960`003b54f3 : fffff8a0`0416ef00 fffff900`c2920900 00000000`00000001 00000000`000007ff : msrpc!RpcBindingCopy+0x42
fffff880`0a5ab7c0 fffff960`001324b1 : fffff900`c2920900 00000000`00000000 fffffa80`06dc3b30 00000000`00000000 : win32k!PlaySoundPostMessage+0x77
fffff880`0a5ab820 fffff960`0018d081 : fffff900`c2920900 fffff880`0a5abc20 00000000`00000000 fffff900`c2920900 : win32k!PostPlaySoundMessage+0x25
fffff880`0a5ab850 fffff960`0018421f : fffff900`c2920900 fffff880`0a5abc20 00000000`ffffffff fffffa80`06dc3b30 : win32k!DestroyProcessInfo+0x125
fffff880`0a5ab880 fffff960`0018431a : fffffa80`0541ce00 fffff900`c2920900 00000000`00000000 fffff880`0a5abc20 : win32k!xxxUserProcessCallout+0x15f
fffff880`0a5ab8d0 fffff800`02f66a01 : fffffa80`0541ce60 00000000`00000000 00000000`00000000 fffffa80`06dc7600 : win32k!W32pProcessCallout+0x4e
fffff880`0a5ab900 fffff800`02f3f635 : 00000000`00000000 fffff800`02f80101 fffffa80`78457300 00000000`00000000 : nt!PspExitThread+0x561
fffff880`0a5ab9c0 fffff800`02c5e1db : fffffa80`06c3d001 fffffa80`06cbf010 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`0a5ab9f0 fffff800`02c5e620 : 00000000`00386d10 fffff880`0a5aba70 fffff800`02f3f74c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0a5aba70 fffff800`02c80a37 : 00000000`00000000 00000000`76fa72a0 00000000`00001f80 fffff880`0a5abc20 : nt!KiInitiateUserApc+0x70
fffff880`0a5abbb0 00000000`76ee008a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`01e5f418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ee008a
STACK_COMMAND: kb
FOLLOWUP_IP:
msrpc!RpcpDuplicateTokenEx+6b
fffff880`010aa8cb 85c0 test eax,eax
SYMBOL_STACK_INDEX: d
SYMBOL_NAME: msrpc!RpcpDuplicateTokenEx+6b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: msrpc
IMAGE_NAME: msrpc.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc17c
FAILURE_BUCKET_ID: X64_0x1E_c0000005_msrpc!RpcpDuplicateTokenEx+6b
BUCKET_ID: X64_0x1E_c0000005_msrpc!RpcpDuplicateTokenEx+6b
Followup: MachineOwner
---------