Code:
-
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [K:\BSODDmpFiles\ZachY2072\Windows_NT6_BSOD_jcgriff2\012412-16676-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c56e70
Debug session time: Tue Jan 24 17:07:20.791 2012 (GMT-7)
System Uptime: 0 days 0:10:49.632
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff7ffca01ee60, 0, fffff8000300464f, 2}
Could not read faulting driver name
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+40d80 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff7ffca01ee60, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000300464f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc10e0
fffff7ffca01ee60
FAULTING_IP:
hal!KeQueryPerformanceCounter+77
fffff800`0300464f 8b1d0ba80100 mov ebx,dword ptr [hal!HalpPmTimerTimeBias (fffff800`0301ee60)]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88002d8bae0 -- (.trap 0xfffff88002d8bae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000022aab5001 rbx=0000000000000000 rcx=000000022aab5001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000300464f rsp=fffff88002d8bc70 rbp=0000000000000000
r8=000000002aab5001 r9=0000000000da7a64 r10=00000000000370ef
r11=fffffa8005a16c00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
hal!KeQueryPerformanceCounter+0x77:
fffff800`0300464f 8b1d0ba80100 mov ebx,dword ptr [hal!HalpPmTimerTimeBias (fffff800`0301ee60)] ds:5380:fffff800`0301ee60=????????
Resetting default scope
MISALIGNED_IP:
hal!KeQueryPerformanceCounter+77
fffff800`0300464f 8b1d0ba80100 mov ebx,dword ptr [hal!HalpPmTimerTimeBias (fffff800`0301ee60)]
LAST_CONTROL_TRANSFER: from fffff80002b087d2 to fffff80002a895c0
STACK_TEXT:
fffff880`02d8b978 fffff800`02b087d2 : 00000000`00000050 fffff7ff`ca01ee60 00000000`00000000 fffff880`02d8bae0 : nt!KeBugCheckEx
fffff880`02d8b980 fffff800`02a876ae : 00000000`00000000 00000000`00000000 fffff800`02a96200 00000000`00000011 : nt! ?? ::FNODOBFM::`string'+0x40d80
fffff880`02d8bae0 fffff800`0300464f : 00000002`2aab5001 00000000`00000246 fffff880`02d8bc98 00000000`00000018 : nt!KiPageFault+0x16e
fffff880`02d8bc70 fffff800`02a97147 : 00000000`ffffffed 00000000`00000000 fffff880`02d6dfc0 00000000`00000001 : hal!KeQueryPerformanceCounter+0x77
fffff880`02d8bca0 fffff800`02a91d5c : fffff880`02d63180 fffff880`00000000 00000000`00000000 fffff880`03f0b588 : nt!PoIdle+0x5b7
fffff880`02d8bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+40d80
fffff800`02b087d2 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+40d80
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\ZachY2072\Windows_NT6_BSOD_jcgriff2\012412-16816-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c41e70
Debug session time: Tue Jan 24 16:28:07.083 2012 (GMT-7)
System Uptime: 0 days 0:04:58.924
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000096, fffff88003f0fbd0, fffff88002788a70, 0}
Probably caused by : hardware ( dxgkrnl!DxgkCddSetPointerPosition+160 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff88003f0fbd0, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88002788a70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
FAULTING_IP:
dxgkrnl!DxgkCddSetPointerPosition+160
fffff880`03f0fbd0 f0e6f9 lock out 0F9h,al
CONTEXT: fffff88002788a70 -- (.cxr 0xfffff88002788a70)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000024
rdx=fffffa80057eb1c0 rsi=fffff880027894e0 rdi=000000000000018b
rip=fffff88003f0fbd0 rsp=fffff88002789440 rbp=0000000000000b01
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff88002b15120 r12=0000000000000000 r13=0000000000000188
r14=0000000000000243 r15=0000000000000246
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgkrnl!DxgkCddSetPointerPosition+0x160:
fffff880`03f0fbd0 f0e6f9 lock out 0F9h,al
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
dxgkrnl!DxgkCddSetPointerPosition+160
fffff880`03f0fbd0 f0e6f9 lock out 0F9h,al
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88003f0fbd0
STACK_TEXT:
fffff880`02789440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkCddSetPointerPosition+0x160
FOLLOWUP_IP:
dxgkrnl!DxgkCddSetPointerPosition+160
fffff880`03f0fbd0 f0e6f9 lock out 0F9h,al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgkrnl!DxgkCddSetPointerPosition+160
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff88002788a70 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_dxgkrnl.sys
BUCKET_ID: X64_IP_MISALIGNED_dxgkrnl.sys
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\ZachY2072\Windows_NT6_BSOD_jcgriff2\012412-24538-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e70
Debug session time: Tue Jan 24 16:02:19.108 2012 (GMT-7)
System Uptime: 0 days 0:21:43.950
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffffa7ff1f068c4, 2, 1, fffff880047a50cc}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+1030cc )
Followup: MachineOwner
---------
3: 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: fffffa7ff1f068c4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880047a50cc, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cad0e0
fffffa7ff1f068c4
CURRENT_IRQL: 2
FAULTING_IP:
atikmdag+1030cc
fffff880`047a50cc 488bc4 mov rax,rsp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002dfb960 -- (.trap 0xfffff88002dfb960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004ea0000
rdx=fffffa8005702f00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880047a50cc rsp=fffff88002dfbaf8 rbp=fffffa8005097480
r8=fffff88002dfbb20 r9=fffff88002dfba40 r10=fffff880046a2000
r11=fffff88002dfbac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
atikmdag+0x1030cc:
fffff880`047a50cc 488bc4 mov rax,rsp
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a74b29 to fffff80002a755c0
STACK_TEXT:
fffff880`02dfb818 fffff800`02a74b29 : 00000000`0000000a fffffa7f`f1f068c4 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02dfb820 fffff800`02a737a0 : 00000000`00000001 fffffa80`056f2000 fffffa80`056f2ef0 fffffa80`056f99b0 : nt!KiBugCheckDispatch+0x69
fffff880`02dfb960 fffff880`047a50cc : fffff880`047a2a28 fffffa80`056f2000 fffffa80`05097480 fffff880`02dddfc0 : nt!KiPageFault+0x260
fffff880`02dfbaf8 fffff880`047a2a28 : fffffa80`056f2000 fffffa80`05097480 fffff880`02dddfc0 00000000`00000000 : atikmdag+0x1030cc
fffff880`02dfbb00 fffffa80`056f2000 : fffffa80`05097480 fffff880`02dddfc0 00000000`00000000 00000000`00000000 : atikmdag+0x100a28
fffff880`02dfbb08 fffffa80`05097480 : fffff880`02dddfc0 00000000`00000000 00000000`00000000 fffffa80`05703090 : 0xfffffa80`056f2000
fffff880`02dfbb10 fffff880`02dddfc0 : 00000000`00000000 00000000`00000000 fffffa80`05703090 00000000`00000000 : 0xfffffa80`05097480
fffff880`02dfbb18 00000000`00000000 : 00000000`00000000 fffffa80`05703090 00000000`00000000 00000000`00000000 : 0xfffff880`02dddfc0
STACK_COMMAND: kb
FOLLOWUP_IP:
atikmdag+1030cc
fffff880`047a50cc 488bc4 mov rax,rsp
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: atikmdag+1030cc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e
FAILURE_BUCKET_ID: X64_0xD1_atikmdag+1030cc
BUCKET_ID: X64_0xD1_atikmdag+1030cc
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\ZachY2072\Windows_NT6_BSOD_jcgriff2\012412-32588-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe70
Debug session time: Tue Jan 24 13:51:57.871 2012 (GMT-7)
System Uptime: 0 days 2:23:11.338
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002d8a24c, fffff88007ce0040, 0}
Probably caused by : ntkrnlmp.exe ( nt!IopXxxControlFile+2bc )
Followup: MachineOwner
---------
2: 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: fffff80002d8a24c, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007ce0040, 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!IopXxxControlFile+2bc
fffff800`02d8a24c 0f8229050000 jb nt!IopXxxControlFile+0x7eb (fffff800`02d8a77b)
CONTEXT: fffff88007ce0040 -- (.cxr 0xfffff88007ce0040)
rax=0000000000000010 rbx=fffffa8003abe070 rcx=0000000000000000
rdx=000000000851f140 rsi=000000000851f140 rdi=fffffa8003abe0c0
rip=fffff80002d8a24c rsp=fffff88007ce0a10 rbp=fffff88007ce0ca0
r8=fffff8a00305b000 r9=000000000000001c r10=fffffa80039fa200
r11=00000000001f0003 r12=0000000000000000 r13=0000000000000001
r14=0000000000012024 r15=000000000000001c
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!IopXxxControlFile+0x2bc:
fffff800`02d8a24c 0f8229050000 jb nt!IopXxxControlFile+0x7eb (fffff800`02d8a77b) [br=0]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: launcher.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d8adf6 to fffff80002d8a24c
STACK_TEXT:
fffff880`07ce0a10 fffff800`02d8adf6 : 00000000`00000000 00000000`0000071c 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x2bc
fffff880`07ce0b40 fffff800`02a71813 : 00000000`00000000 fffffa80`05d1b100 00000000`746c6644 fffff880`07ce0c38 : nt!NtDeviceIoControlFile+0x56
fffff880`07ce0bb0 00000000`756f2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`050aef38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x756f2dd9
FOLLOWUP_IP:
nt!IopXxxControlFile+2bc
fffff800`02d8a24c 0f8229050000 jb nt!IopXxxControlFile+0x7eb (fffff800`02d8a77b)
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IopXxxControlFile+2bc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44
STACK_COMMAND: .cxr 0xfffff88007ce0040 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!IopXxxControlFile+2bc
BUCKET_ID: X64_0x3B_nt!IopXxxControlFile+2bc
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\ZachY2072\Windows_NT6_BSOD_jcgriff2\012412-43602-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02819000 PsLoadedModuleList = 0xfffff800`02a56e70
Debug session time: Tue Jan 24 11:01:51.695 2012 (GMT-7)
System Uptime: 0 days 0:00:35.536
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
3: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff88002dfba68 -- (.exr 0xfffff88002dfba68)
ExceptionAddress: fffff80002896cec (nt!PoIdle+0x000000000000015c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000066c5a8fa
Attempt to write to address 0000000066c5a8fa
TRAP_FRAME: fffff88002dfbb10 -- (.trap 0xfffff88002dfbb10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001e9584ae rbx=0000000000000000 rcx=000000001e9584ae
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002896cec rsp=fffff88002dfbca0 rbp=0000000000000000
r8=000000001e9584ae r9=0000000000da7a64 r10=fffffa800478d330
r11=fffff88002dfbcc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz na po nc
nt!PoIdle+0x15c:
fffff800`02896cec 48894c2430 mov qword ptr [rsp+30h],rcx ss:0018:fffff880`02dfbcd0=fffff88002dd3180
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028812ee to fffff80002889590
STACK_TEXT:
fffff880`02dfab58 fffff800`028812ee : fffffa80`054563f8 fffffa80`0478d1b0 fffff880`02dfb2d0 fffff800`028b6524 : nt!KeBugCheck
fffff880`02dfab60 fffff800`028af2dd : fffff800`02a97eb8 fffff800`029d0de4 fffff800`02819000 fffff880`02dfba68 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02dfab90 fffff800`028b6950 : fffff800`029d8b0c fffff880`02dfac08 fffff880`02dfba68 fffff800`02819000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02dfabc0 fffff800`028c38cf : fffff880`02dfba68 fffff880`02dfb2d0 fffff880`00000000 fffffa80`039f5b60 : nt!RtlDispatchException+0x410
fffff880`02dfb2a0 fffff800`02888c02 : fffff880`02dfba68 fffffa80`051d3598 fffff880`02dfbb10 fffff880`02dd3180 : nt!KiDispatchException+0x16f
fffff880`02dfb930 fffff800`0288777a : 00000000`00000001 fffffa80`051d3598 00000000`00000000 00001f80`00e60060 : nt!KiExceptionDispatch+0xc2
fffff880`02dfbb10 fffff800`02896cec : 00000000`00000000 fffffa80`051d3598 00000000`00000000 ffffd319`2f001e22 : nt!KiPageFault+0x23a
fffff880`02dfbca0 fffff800`02891d5c : fffff880`02dd3180 fffff880`02dddfc0 00000000`00000000 fffff880`00dc0f44 : nt!PoIdle+0x15c
fffff880`02dfbd80 00000000`00000000 : fffff880`02dfc000 fffff880`02df6000 fffff880`02dfbd40 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`028812ee 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------