Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a89e50
Debug session time: Mon Jan 31 14:09:25.610 2011 (GMT-5)
System Uptime: 0 days 0:06:12.343
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {190, 2, 0, fffff800028c48db}
Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+26b )
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: 0000000000000190, 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: fffff800028c48db, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af40e0
0000000000000190
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiSearchForNewThread+26b
fffff800`028c48db 66453b9080010000 cmp r10w,word ptr [r8+180h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f1bb50 -- (.trap 0xfffff88002f1bb50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000100 rbx=0000000000000000 rcx=fffff88002fd8700
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028c48db rsp=fffff88002f1bce0 rbp=0000000000000001
r8=0000000000000010 r9=0000000000000008 r10=0000000000000000
r11=fffff880031a1b80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiSearchForNewThread+0x26b:
fffff800`028c48db 66453b9080010000 cmp r10w,word ptr [r8+180h] ds:bc98:00000000`00000190=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028bbca9 to fffff800028bc740
STACK_TEXT:
fffff880`02f1ba08 fffff800`028bbca9 : 00000000`0000000a 00000000`00000190 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1ba10 fffff800`028ba920 : 00000000`2f45b17c 00000000`00000000 fffffa80`05766101 fffffa80`047bf1b0 : nt!KiBugCheckDispatch+0x69
fffff880`02f1bb50 fffff800`028c48db : 00000000`33f0a83b 00000000`0000003b fffffa80`043db600 400000c2`400000c1 : nt!KiPageFault+0x260
fffff880`02f1bce0 fffff800`0287409a : 00000000`00000000 00000000`00000000 fffff880`00000000 00000000`00000001 : nt!KiSearchForNewThread+0x26b
fffff880`02f1bd50 fffff800`028c4fc6 : fffff880`009e6180 fffff880`009f0fc0 00000000`00000000 fffff880`00c14f44 : nt!KiIdleSchedule+0x7a
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x136
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSearchForNewThread+26b
fffff800`028c48db 66453b9080010000 cmp r10w,word ptr [r8+180h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiSearchForNewThread+26b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_nt!KiSearchForNewThread+26b
BUCKET_ID: X64_0xA_nt!KiSearchForNewThread+26b
Followup: MachineOwner
---------
Debug session time: Mon Jan 31 14:32:19.893 2011 (GMT-5)
System Uptime: 0 days 0:05:40.000
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8800318dc47, 1, fffff80002883590, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
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: fffff8800318dc47, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002883590, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abd0e0
fffff8800318dc47
FAULTING_IP:
nt!KiGeneralProtectionFault+10
fffff800`02883590 c645ab01 mov byte ptr [rbp-55h],1
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880031851c0 -- (.trap 0xfffff880031851c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f63180 rbx=0000000000000000 rcx=ffff00000573ead0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002883590 rsp=fffff88003185350 rbp=fffff8800318dc9c
r8=fffffa8003b24348 r9=fffffa8003b24240 r10=fffffa8005f6c010
r11=fffffa8003b24390 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz na po nc
nt!KiGeneralProtectionFault+0x10:
fffff800`02883590 c645ab01 mov byte ptr [rbp-55h],1 ss:0018:fffff880`0318dc47=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002905f14 to fffff80002885740
STACK_TEXT:
fffff880`03185058 fffff800`02905f14 : 00000000`00000050 fffff880`0318dc47 00000000`00000001 fffff880`031851c0 : nt!KeBugCheckEx
fffff880`03185060 fffff800`0288382e : 00000000`00000001 fffffa80`047c8100 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`031851c0 fffff800`02883590 : 00000000`00000000 fffffa80`00fa5200 00000580`00000001 fffffa80`039f8f48 : nt!KiPageFault+0x16e
fffff880`03185350 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
30 errors : !nt (fffff8000288358c-fffff8000288367d)
fffff80002883580 55 48 81 ec 58 01 00 00 48 8d ac 24 *4c *89 00 00 UH..X...H..$L...
fffff80002883590 c6 45 ab 01 48 89 45 b0 48 89 4d b8 *65 *4c 55 c0 .E..H.E.H.M.eLU.
fffff800028835a0 4c 89 45 c8 4c 89 4d d0 4c 89 55 d8 *80 *fa 5d e0 L.E.L.M.L.U...].
fffff800028835b0 f6 85 f0 00 00 00 01 74 64 0f 01 f8 *00 *00 8b 14 .......td.......
fffff800028835c0 25 88 01 00 00 41 f6 42 03 80 74 3c *79 *82 01 00 %....A.B..t<y...
fffff800028835d0 c0 0f 32 48 c1 e2 20 48 0b c2 49 39 *8a *c4 00 00 ..2H.. H..I9....
fffff800028835e0 00 74 25 49 39 82 b0 01 00 00 74 1c *83 *02 92 b8 .t%I9.....t.....
fffff800028835f0 01 00 00 41 0f ba 6a 4c 0b 66 41 ff *00 *fc 01 00 ...A..jL.fA.....
fffff80002883600 00 48 89 82 80 00 00 00 41 f6 42 03 *af *55 c7 85 .H......A.B..U..
fffff80002883610 80 00 00 00 00 00 74 05 e8 d3 25 00 *29 *65 0f ae ......t...%.)e..
fffff80002883620 5d ac 65 0f ae 14 25 80 01 00 00 0f *01 *00 f0 0f ].e...%.........
fffff80002883630 29 4d 00 0f 29 55 10 0f 29 5d 20 0f *00 *00 30 0f )M..)U..)] ...0.
...
fffff80002883650 85 e0 00 00 00 48 f7 85 f8 00 00 00 *33 *d2 00 00 .....H......3...
fffff80002883660 74 01 fb b9 01 00 00 10 ba 02 00 00 *7f *e1 8b 8d t...............
fffff80002883670 e0 00 00 00 41 81 e1 ff ff 00 00 4d *48 *83 4c 8b ....A......MH.L.
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
Debug session time: Mon Jan 31 14:36:48.806 2011 (GMT-5)
System Uptime: 0 days 0:03:59.912
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8000284b95b, fffff88006f10e60, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+e0 )
Followup: MachineOwner
---------
0: 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: fffff8000284b95b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006f10e60, 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!ExQueryPoolUsage+e0
fffff800`0284b95b 8379e400 cmp dword ptr [rcx-1Ch],0
CONTEXT: fffff88006f10e60 -- (.cxr 0xfffff88006f10e60)
rax=000000000288a6dc rbx=0000000000000000 rcx=000003880000049f
rdx=fffff88006f1197c rsi=0000000000033cc3 rdi=00000000001bf290
rip=fffff8000284b95b rsp=fffff88006f11830 rbp=fffff88006f11ca0
r8=fffff88006f11978 r9=fffff80002a31720 r10=0000000000000005
r11=fffff88006f1195c r12=0000000000000004 r13=0000000000009a62
r14=fffff80002ac4900 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
nt!ExQueryPoolUsage+0xe0:
fffff800`0284b95b 8379e400 cmp dword ptr [rcx-1Ch],0 ds:002b:00000388`00000483=????????
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 fffff80002b897ab to fffff8000284b95b
STACK_TEXT:
fffff880`06f11830 fffff800`02b897ab : 00000000`00000000 00000000`00033cc3 00000000`00033cc3 00000000`00000026 : nt!ExQueryPoolUsage+0xe0
fffff880`06f11840 fffff800`02b8b1e5 : 00000000`001bf290 fffff800`02b8710e 00000000`00000003 00000000`00000000 : nt!ExpQuerySystemInformation+0x5a9
fffff880`06f11be0 fffff800`0288b993 : 00000000`00000164 fffff880`06f11ca0 ffffffff`fffe7960 00000000`00000000 : nt!NtQuerySystemInformation+0x4d
fffff880`06f11c20 00000000`773500ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001bf1d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773500ba
FOLLOWUP_IP:
nt!ExQueryPoolUsage+e0
fffff800`0284b95b 8379e400 cmp dword ptr [rcx-1Ch],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExQueryPoolUsage+e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff88006f10e60 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ExQueryPoolUsage+e0
BUCKET_ID: X64_0x3B_nt!ExQueryPoolUsage+e0
Followup: MachineOwner
---------
Debug session time: Mon Jan 31 15:01:04.954 2011 (GMT-5)
System Uptime: 0 days 0:00:40.060
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {744a2dd9, 0, ffff, fffff88002baeca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 00000000744a2dd9, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffff88002baeca0, Previous KernelApcDisable
Debugging Details:
------------------
FAULTING_IP:
+5ac0952f01a5def0
00000000`744a2dd9 c3 ret
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: AvastSvc.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000287dca9 to fffff8000287e740
STACK_TEXT:
fffff880`02baea68 fffff800`0287dca9 : 00000000`00000001 00000000`744a2dd9 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`02baea70 fffff800`0287dbe0 : 00000000`04fafd20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02baebb0 00000000`744a2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`04faf0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x744a2dd9
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`0287dbe0 4883ec50 sub rsp,50h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245
Followup: MachineOwner
---------
Debug session time: Mon Jan 31 13:14:37.323 2011 (GMT-5)
System Uptime: 0 days 0:04:52.055
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
---------
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: 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:
+5ac0952f01b7ddf0
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: 2
EXCEPTION_RECORD: fffff80000b9c248 -- (.exr 0xfffff80000b9c248)
ExceptionAddress: fffff800028c90a2 (nt!KiDeferredReadyThread+0x00000000000001c2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80000b9c2f0 -- (.trap 0xfffff80000b9c2f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff000002a4cb80 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028c90a2 rsp=fffff80000b9c480 rbp=0000000000000002
r8=0000000000000001 r9=fffff80002bb78dc r10=fffff80002854000
r11=fffff80002a3ee80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KiDeferredReadyThread+0x1c2:
fffff800`028c90a2 663b5048 cmp dx,word ptr [rax+48h] ds:ffff0000`02a4cbc8=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028bc46e to fffff800028c4710
STACK_TEXT:
fffff800`00b9b338 fffff800`028bc46e : 00000000`00000000 00000000`00000000 fffff800`00b9bab0 fffff800`028f1668 : nt!KeBugCheck
fffff800`00b9b340 fffff800`028ea40d : fffff800`02ad2b7c fffff800`02a0ce84 fffff800`02854000 fffff800`00b9c248 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b370 fffff800`028f1a90 : fffff800`02a13b14 fffff800`00b9b3e8 fffff800`00b9c248 fffff800`02854000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b3a0 fffff800`028fe9ef : fffff800`00b9c248 fffff800`00b9bab0 fffff800`00000000 fffffa80`039fc040 : nt!RtlDispatchException+0x410
fffff800`00b9ba80 fffff800`028c3d82 : fffff800`00b9c248 fffff880`02f63180 fffff800`00b9c2f0 fffff800`02a3ee80 : nt!KiDispatchException+0x16f
fffff800`00b9c110 fffff800`028c268a : 00000000`00000000 fffffa80`05e0c050 fffff880`04341250 fffffa80`03fef1a8 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c2f0 fffff800`028c90a2 : fffffa80`00000000 00000000`00000002 fffff800`00b9c540 00000000`215e7003 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c480 fffff800`028cc1aa : 00000000`00000000 fffff800`02a695f8 fffffa80`039fc040 fffffa80`039fc148 : nt!KiDeferredReadyThread+0x1c2
fffff800`00b9c500 fffff800`028d029e : fffffa80`06d59cd0 fffff800`00b9c618 00000000`00000002 00000000`00000003 : nt!ExQueueWorkItem+0x21a
fffff800`00b9c570 fffff800`028cfdd6 : fffffa80`05e5c1f0 fffffa80`05e5c1f0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`028d04be : 00000000`ae1423a2 fffff800`00b9cc58 00000000`00004921 fffff800`02a416a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`028cfcb7 : 00000000`28c116c3 00000000`00004921 00000000`28c11663 00000000`00000021 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`028cceea : fffff800`02a3ee80 fffff800`02a4cc40 00000000`00000000 fffff880`03f60db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`028bc46e 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: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------